1. Freeze the original state
Hash and preserve the submitted file, form fields, screenshots, source export and rejection response.
2. Reproduce before changing
Confirm the failure using the applicable authoritative rules or customer-approved package. A guessed cause should remain a hypothesis.
3. Separate deterministic and judgmental issues
Formatting, type and count errors may be deterministic. Eligibility, classification, legal interpretation and unsupported business facts are not.
4. Maintain a single exception register
Each exception needs a source, owner, decision, rationale, status and effect on release.
5. Change only supported facts
A correction should point to the source evidence or explicit customer instruction that justifies it.
6. Revalidate the exact release candidate
Do not validate one artifact and deliver another. Record the final hash and rule-set version.
7. State the limitation plainly
External acceptance, substantive compliance and agency discretion remain outside the preparer’s control.
Release test
Before the artifact is released, ask four questions: Can every material value be traced to a source? Are unresolved facts still visible? Was the exact release candidate rechecked? Does the final claim stay inside the evidence?
Questions teams ask
It prevents repeated rediscovery and parallel, undocumented edits.
Normalize, compare, validate and trace. It should not invent missing facts.
Material exceptions, unsupported assumptions, change justification and the wording of the final claim.