Review and evidence

Review and evidence gives the team a place to inspect who decided, which policy revision they saw and what happened when an operation was attempted. Review Decisions links a decision, reviewer, date, reason and source revision to a policy. Record Attachments keeps files, upload time, evidence type and visibility alongside the same policy context. Operation Receipts carries a stable operation key, expected revision, result state and effect references for follow-up.

A returned review differs from approval or rejection. The reviewer should explain what needs correction, and the preparer should bring the changed record back with its new revision. An operation receipt marked pending or failed calls for evidence review. A completed receipt should match the actual persisted effect; a status label alone is not enough to close the investigation.

• Collect the evidence. Attach the relevant file to the policy context and choose internal or shared visibility.
• Record the decision. Keep the reviewer, source revision and reason with an approval, rejection or return.
• Reconcile the effect. Compare operation receipts with the policy, request or claim effect they identify.

Agree which documents may be shared and who may change their visibility. Choose a naming convention for evidence types so staff can find the right file without relying only on its title. Assign independent reviewers for policy and preauthorization decisions and define what a returned case needs before it can be reviewed again. The reviewer should have the correct organization scope and an active team identity.

For operation receipts, agree how the operation key and external reference are generated. The key must stay stable on retry, while the expected revision identifies the source state that was reviewed. Set an owner for failed and needs-review states, including how they compare local effects with any outside acknowledgment.

A submitted preauthorization refers to a policy with a supporting file. Preauthorization Reviewer sees the submitted revision, opens the evidence and returns the case with a reason. Policy Operations Specialist corrects the request. The next review uses the changed revision and produces its own decision evidence. An earlier return remains visible in the policy record instead of being overwritten by the later outcome.

Now suppose the final operation receipt remains pending after the request status changes. Finance Reconciler reads the expected revision and effect references, then checks the actual request and decision. If all effects match, the receipt can be completed. If the request belongs to a different organization or the decision references another revision, it stays in needs-review with a discrepancy reason. This keeps an apparent success from concealing the wrong effect.

• Operation exceptions — Investigate failed or disputed effects with the original key and reason.
• Policy review decisions — Read who decided, when and against which policy revision.
• Submitted preauthorizations — Open the request that needs an independent decision.

Review a preauthorization and reconcile an operation.