Telynt / Documentation

Search documentation

Search platform contracts, developer guides, package manuals and the Technology Consulting & Delivery solution.

Browse documentation

Ethics and Compliance Review

Ethics & Compliance — Policies

On this page

Navigation: Intelligence → Ethics & Compliance → Policies
Access: restricted policy-administration permission
Primary audience: compliance, HR, legal, policy owners, and authorized administrators

Purpose

Policies manages the versions, jurisdictions, review dates, and category mappings used by the controlled review process. It helps policy owners see coverage gaps and prepare governed changes without altering active decisions retrospectively.

Scope controls and indicators

Policy State filters active, draft, retired, or scheduled versions. Jurisdiction selects configured regions. Review Date limits upcoming policy reviews. Mapping State filters complete, partial, unmapped, or conflicting category coverage.

Active Policies shows currently effective versions. Mappings Covered shows category coverage. Review Due counts policies requiring owner attention. Draft Versions shows unpublished changes awaiting review or approval.

Policy catalog

The catalog lists policy, version, effective state, jurisdictions, owner, next review, and approval state. Selecting a policy opens its authorized text, change history, applicability, category mappings, review roles, and effective dates.

Detection mapping coverage

This panel shows how candidate categories map to policy sections by jurisdiction and where mappings are missing, partial, or overlapping. A mapping supports routing and review; it does not automatically determine a violation.

Supporting analysis

Mapping coverage by policy compares completeness. Upcoming policy reviews shows due date, owner, and required approval. Policy actions surfaces missing regional wording, publication-ready versions, and route reviews.

Actions

  • Create or edit a draft policy version.
  • Map a candidate category to one or more policy sections.
  • Compare versions and preview affected review guidance.
  • Request approval and publish an effective version.
  • Retire a version prospectively while preserving historical applicability.
  • Review jurisdiction and reporting routes.

Resolve unmapped and conflicting categories before publishing. Confirm jurisdiction, effective date, reviewer guidance, and approval. Test the new version against representative examples, then publish prospectively; do not silently reclassify historical cases.

Review Queue, Cases, and Governance.