The source needs review.
A possible inconsistency or relationship candidate remains a review prompt, not an authoritative software decision.
When policy is unclear
What happens when the policy does not give a clear answer?
PolicyOps can show the wording that supports an answer, flag wording that may conflict and send the question to the right owner. It does not choose an interpretation or change the policy by itself.
Two different governance questions
Within a policy and across the policy estate are not the same job.
Within one current policy, a rule may depend on a definition, condition, exception, qualification or procedure elsewhere in the document. Where controlled document analysis is configured, PolicyOps can assess that context and bind a released claim to exact original passages. If the policy does not settle the question, it can preserve the relevant source without releasing a rejected interpretation.
Across the policy estate, separate policies may overlap or affect one another. PolicyOps can surface those candidate relationships with supporting context, but an authorised policy owner or reviewer still decides what becomes an accepted organisational relationship.
Governed review routes
From source uncertainty to accountable action.
- 1Distinguish
PolicyOps keeps a checked answer, no clear answer, possible document inconsistency and cross-policy relationship candidate separate.
- 2Show the source
Relevant original passages, policy version and evidence boundary remain visible; rejected answer prose is not presented as authority.
- 3Route
A user can request clarification of possible inconsistent wording, or send a relationship candidate to the appropriate authorised reviewer.
- 4Decide
The assigned policy owner, reviewer or governance administrator records the human outcome without software rewriting or approving policy.
- 5Preserve
The source-bound request, outcome and history remain available for audit and later review, including when the policy subsequently changes.
Worked example
The policy says a form is required, but elsewhere says it is optional.
A staff member asks whether a form must be completed. Two passages in the same current policy appear to apply to the same circumstances but point in different directions. The safe outcome is not for software to choose the more convenient sentence.
Where the controlled capability is available, PolicyOps can present both exact passages as a possible inconsistency and allow the user to request clarification. The request is tied to that policy version and routed to an accountable owner. Any wider connection to another policy remains a separate relationship question.
Estate health and policy work
Turn uncertainty into visible, owned work.
Clarification requests and relationship-review issues can sit alongside overdue reviews, missing ownership, evidence concerns and operational findings. Each item links to the affected policy and supporting records rather than disappearing into an inbox or unexplained score.
The original wording remains visible.
Reviewers can inspect the policy version, exact passages, request history and whether the source has since changed.
Open the accountable control.
The right person can clarify, dismiss, accept or reject the relevant item with a reason; software does not silently complete it.
Common questions
Policy uncertainty and relationships, answered clearly.
What is the difference between a document inconsistency and a relationship between policies?
A document inconsistency concerns passages within one current policy that may give materially different answers to the same question. A cross-policy relationship is a candidate connection between separate policies. PolicyOps keeps those two review routes distinct.
Can PolicyOps identify relationships between policies?
PolicyOps can suggest relationships and show the evidence, reason and confidence attached to a candidate. An authorised reviewer accepts or rejects what becomes authoritative.
Does PolicyOps automatically resolve policy conflicts?
No. Where controlled analysis is configured, PolicyOps can preserve separate passages behind a possible inconsistency and let a user request clarification. An authorised policy owner or reviewer records the outcome; the software does not declare a defect or alter the policy.
What happens if the policy changes after clarification is requested?
The request remains tied to the original policy version and source wording. That evidence can remain available as history, but it cannot silently be clarified as though it belonged to the new current version.
What is recorded when a relationship is reviewed?
The candidate, supporting context and the authorised accept or reject decision can be recorded so later reviewers can reconstruct what became authoritative and why.
Related guidance
Connect uncertainty to policy authority and evidence.
Buyer evaluationTest unclear and inconsistent source behaviourUse the expanded Policy Proof Test with controlled material and accountable roles.EvidencePolicy audit trails and evidence packsPreserve the question, source context and human follow-up.ReviewPolicy review and clarification workflowsKeep ownership, evidence and accountable outcomes attached.
Explore PolicyOps
See how this fits into your working day.
Keep your library organised, get help with policy questions and leave approvals with your people.