Independent decisions

The independent reviewer sees the batch revision, its validation outcomes and any supporting documents before recording a decision. A pending decision identifies work waiting for review. Approval authorizes the accepted partition to proceed; a returned or rejected decision records a reason for the owner. The reviewer name and decision date preserve who made the call.

• Review subject. Read the batch number, source revision and row outcomes together.
• Decision. Record pending, approved, returned or rejected against that revision.
• Reason and evidence. Keep the reviewer, date, reason and evidence reference with the decision.

The Independent Reviewer decides whether the accepted partition for a particular source revision can proceed. The Import Operator supplies the batch and row results; the reviewer checks source documents when they matter to the decision. A returned decision sends the owner back to correct the submission. An approved decision authorizes the Execution Operator to work only from the revision that was reviewed. If the source changes, the prior approval stays with its original revision.

Agree what evidence is needed for a clean decision and who may review a batch owned by a colleague. The reviewer should compare the source revision on the decision with the current batch revision. If the source changes, the old decision remains attached to the earlier version and the new one needs its own review.

Name a reviewer who is separate from the Import Operator. Agree what evidence they must inspect before approval and what reason is needed for a return or rejection. The reviewer needs to see the current validation results, not just the batch status. The Execution Operator must be able to compare the approved source revision with the revision selected for commit.

Suppose an operator fixes a row after an initial approval. The reviewer examines the successor revision and its new results. They do not rely on the earlier decision, because the accepted partition may have changed. A returned decision carries a reason that the operator can resolve before requesting another review.

Ask the reviewer to open the earlier approval and the newly corrected row results side by side. They should create a new decision for the successor revision, recording the reason and evidence reference. The Execution Operator then checks that new decision before moving the accepted rows forward.

• Review Inbox — Open pending decisions with their source revision and reviewer.
• Returned Decisions — Read the reason sent back to the batch owner.

See the related process and the data model to rehearse this handoff with a real submission.