1. Data Entry & Validation
  2. Features
  3. Correction evidence
Feature · Correction evidence

Correction evidence

Keep correction tasks and earlier execution records visible.

OverviewFailed Runs
Data Entry & Validation · Correction evidence

Failed Runs

Operation runs

New
SourceOperation keySource revisionStarted atStatusFailure reason
IB-84339OK-28341012 OctFailedCut to length
IB-96361OK-50079020 OctFailedWeld frame
IB-53921OK-91146010 OctFailedDrill and tap
IB-50197OK-18452014 OctFailedDeburr
IB-96171OK-98983027 OctFailedAssemble
6 of 6 records
OK-283Operation runs · OR-68823
Failed
SourceIB-84339
Source revision410
Started at12 Oct
Failure reasonCut to length
Example screen with sample data

What you can do

Correction evidence in daily work

A correction begins with the existing batch revision and its completed execution record still visible. The correction owner records a follow-up title, assignee, due date and resolution. Evidence documents retain source attachments and verification details. State history records each batch transition, actor and reason so a later reviewer can reconstruct the sequence.

How the work is organized

  • Earlier execution. Retain the prior run, completed steps and receipt.
  • Successor work. Assign a follow up and prepare a new batch revision for review.
  • Verification. Record the corrected output, decision and resolution against the batch.

The Correction Owner takes a follow up from a returned decision or a later target discrepancy. The earlier operation and receipt remain available so the team can see what was already executed. A successor revision receives its own validation results and Independent Reviewer decision. If the target must be corrected, the new operation step records its output identity and receipt. The follow up remains open until the owner records what was verified.

What to agree during setup

For an executed revision, agree how a compensating output will be identified in the target system before creating a successor revision. The execution operator checks the prior step outputs and receipts. The independent reviewer examines the corrected source and records a new decision for its revision. The correction owner closes the follow up only after verification evidence is available.

Agree who can request a correction, who owns its due date and who checks the final target state. The Validation Steward confirms any revised mapping; the Independent Reviewer decides the successor revision. Preserve the earlier source hash, decision and operation evidence. When a compensating target action is needed, identify its output and receipt so the Correction Owner can explain both the original and corrected states.

Check the handoff on an actual case

Suppose a committed row was mapped to the wrong target value. The team retains the earlier receipt and run, creates a successor revision with the corrected mapping and records the compensating target output. A new review decision authorizes the corrected partition. The follow up records who verified the final target state.

Trace the wrongly mapped target value back to the earlier operation step and receipt. Show the revised mapping and new row outcome to the Independent Reviewer. After approval, compare the compensating output with the target and record the evidence in the follow up resolution before marking it completed.

What your team sees

  • Open Follow Ups — Find assigned correction and verification tasks with due dates.
  • Returned Decisions — Trace the reviewer reason behind a correction request.

Follow the work through

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

What it keeps track of

Data model
Follow up actions
Correction and verification tasks raised against validated batches.
Evidence documents
Source documents and receipt evidence attached to a batch.
State history
Immutable status transition log for every validated batch.
Import batches
Staged inbound data submissions validated against a frozen rule set.
Operation runs
Workflow-maintained run ledger for parse, commit and correction operations.
Review decisions
Independent reviewer sign-off or return against an exact source revision.

Who uses it

Permissions
Correction Owner
, Independent Reviewer, Execution Operator.

Set up Data Entry & Validation your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started