Two Client Reports Swapped Their Action Registers After Review: Restore Decision Ownership

Two correct client reports can still send the wrong work to the wrong people. That happens when each report keeps its narrative, but the action register attached after review belongs to the other client.

Do not rewrite the reports to hide the mistake. Restore the report-to-action bindings. Preserve the record of what happened and make the correction easy to inspect later.

The repair starts with evidence, not with a bulk reassignment. Build one correction register that keeps the accepted and observed action links plus the execution history side by side.

How do you prove that two reports exchanged their action registers?

Start with two fixed report identities: Client A plus Report A, and Client B plus Report B. Then collect every action associated with each report, including completed actions.

For each action, compare the observed client and report binding with the accepted binding. The accepted binding should come from the action's source context, such as the client record, report reference, decision note, or original assignment trail.

A swap is proven when actions expected under Report A appear under Report B, while the matching actions expected under Report B appear under Report A. The report text may be correct throughout. The defect is the association between report and action.

Use clear decision ownership while resolving disputed actions. Atlassian's DACI guidance defines a Driver who gathers information and moves the decision forward, plus one Approver who makes the call.

Which tasks, owners, deadlines, and completed actions must be reversed?

Reverse every open task whose accepted client or report ID differs from its observed report association. Move the action back to its accepted report without changing its title, source note, evidence, owner, or deadline unless the accepted record says those fields differ.

Restore the owner recorded on the accepted action. Do not assign the person currently named in the swapped register merely because they have already seen the task.

Restore the deadline recorded on the accepted action. If no accepted deadline exists, leave it unresolved and ask the decision owner to set one. A swapped report is not evidence for a new deadline.

Keep completed actions visible as completed. Move their association back to the correct report and preserve the completion time and evidence. Add a correction note that names the former incorrect association.

This is a control problem, not a writing problem. The GAO's 2025 Green Book calls for documented risk-assessment results and a documented change-assessment process for significant changes. A correction register gives the team a record of both the issue and the response.

• Reverse open actions that belong to the other client.
• Restore owners and deadlines from accepted records only.
• Rebind completed actions without deleting their execution history.
• Flag records with missing accepted ownership or deadline evidence for a decision.

How do you restore bindings without rewriting report history?

Freeze the two reports and export the current action register before making changes. That snapshot is the observed state. It makes the correction auditable if a later question arises.

Create a correction entry for each mismatched action. Include the action ID, accepted client ID, accepted report ID, observed client ID, observed report ID, old owner, restored owner, old deadline, restored deadline, execution-history reference, correction timestamp, and approver.

Detach the action from the wrong report and attach it to the accepted report. Retain a correction note on the action. Do not delete the old report text. Do not change reporting dates or rewrite prior conclusions.

Record a client notice for each affected client. State that the report content remains unchanged, identify the action register correction, link the restored actions, and say whether any owner or deadline changed.

NIST SP 800-37 Rev. 2, published in December 2018, describes a structured process that establishes responsibility and accountability for controls. Use the correction register as the operational record of who verified and approved each restoration.

What should the negative-association test check?

Run the test after every reversal. For Report A, search for actions whose accepted client ID or accepted report ID belongs to Client B or Report B. The result must be empty. Repeat the same test for Report B against Client A and Report A.

Then test the opposite condition: every action expected under each report must be present once, with the accepted owner and deadline where those values are known. Check completed actions separately so historical work is not lost in an open-task-only review.

Do not declare the repair complete until the correction register agrees with the report bindings and client notices. The UK Government Project Delivery Functional Standard was updated on September 17, 2025 and includes governance roles plus planning and control practices. Those are useful checks for a small repair as well as a large project.

• No Client B action remains bound to Report A.
• No Client A action remains bound to Report B.
• Each accepted action appears once under its correct report.
• Known owners and deadlines match the accepted record.
• Completed actions retain their original execution evidence.
• Each affected client has a recorded correction notice.

Who should decide an action when the records disagree?

Do not guess from a task title or from who completed work. Escalate the action to a named decision owner with the conflicting evidence and a proposed binding.

Use one person as the final approver for each disputed action. Atlassian describes the DACI Approver as the person who makes the decision, while the Driver gathers information and completes action items. Keep those roles distinct in the correction register.

If the accepted client, owner, or deadline cannot be established, leave the field unresolved. Record the missing evidence and identify the decision owner and due date.