Two Provider Service Reviews Swapped Approved Action Logs: Restore Owners and Closure Proof

Two provider service reviews were attached to the wrong action logs. The repair is to restore the approval chain, not to rewrite history. Each action needs one accountable review and one owner, with evidence that the action was completed or remains open.

Start by freezing edits and exporting both logs. Assign a repair lead who is independent of the two provider owners where possible. Preserve the original records and timestamps. A corrected log should show what changed, why it changed, who approved the correction, and where the original record remains available.

This is an operating-control repair. It does not decide whether either provider performed well. It decides which review had authority over each decision and action.

• Freeze both review logs and preserve their current versions.
• Collect the approved review minutes, decision records, action-log exports, provider correspondence, and closure evidence.
• Assign each disputed action to the review that approved it, then obtain confirmation from the accountable owner.

Which decisions and actions belong to each provider review?

Use the approved decision as the primary binding. A service review owns an action when the review record approved the action, named the owner, accepted the dependency, or set the deadline. An action merely discussed in a review does not automatically belong there.

Separate accepted bindings from observed bindings. An accepted binding is what the approved review record says. An observed binding is where the action appeared in the current logs, tickets, messages, or operational records. The mismatch between those two fields is the repair queue.

The U.S. Government Accountability Office's Green Book says internal-control systems support operational/reporting objectives and compliance objectives, and its 2025 revision emphasizes documenting risk-assessment results and change-assessment processes. Use that as a control principle: record the reassignment decision and its basis rather than silently moving rows between logs. GAO Green Book, May 15, 2025

How do you correct the logs without erasing valid work?

Move the association, not the evidence. If an action was correctly executed but filed under the wrong review, retain the execution date, artifact, owner, and result. Add a correction entry that identifies the prior location, the correct review, the evidence used to decide, and the approver of the change.

Do not backdate a correction to make the logs look clean. The record should show the original observed binding and the new accepted binding. NIST's Guide to Computer Security Log Management describes the need for sound log-management practices and practical processes for maintaining them across an enterprise. NIST SP 800-92, September 13, 2006

Where a deadline passed while the action sat under the wrong review, preserve the original deadline and add a current recovery deadline only when the accountable owner sets one. Do not infer a new owner or due date from provider-specific metadata, including the provider name and action-log position, or a later discussion.

• Add a correction note to the original log entry. Include the original review ID, corrected review ID, evidence links, correction approver, and timestamp.
• Create or update the action under the correct review without changing the historical execution evidence.
• Mark the old association as superseded, not deleted.
• Ask the accountable owner to confirm the corrected owner and remaining dependency, as well as whether it is open or closed.

What closure proof should each corrected action have?

Closure proof should establish the action, the responsible owner, the completion event, and the reviewer who accepted closure. A status label alone is weak proof when two reviews have been crossed.

Use the system that recorded the work where possible. Microsoft says audit records are generated when users or administrators perform audited activities, but it does not guarantee a specific time for a record to appear in search results. Treat a missing fresh audit record as an open verification step, not automatic proof that no action occurred. Microsoft Purview Audit

For tools with limited retention, export the relevant evidence before the repair window closes. Atlassian says organization audit-log activity can be stored for up to 180 days, depending on the available audit-log scope. That statement is specific to Atlassian's documented service and should not be treated as a universal retention period. Atlassian audit-log activities

• Approved review decision or signed review minutes.
• Action record with accountable owner and original deadline.
• Execution artifact, ticket history, message, deployment record, or provider deliverable.
• Closure acceptance from the owner or review authority.
• Correction record and completed negative-swap test.

How do you run the negative-swap test before closing the repair?

Test both directions. First, list every action currently attached to Review A and confirm that Review A has the approving decision and the owner with closure authority. Then repeat for Review B. Any action supported only by the other review remains unresolved.

Search by action ID, provider name, decision reference, owner, and deadline. Check links in both the review minutes and the action system. Google Cloud states that its audit-log entries are immutable, a useful example of why the evidence record should remain distinct from a later correction note. Google Cloud Audit Logs overview

Close the repair only after the review owners sign off on the association ledger. Every disputed action must have a corrected link or documented exception, and both negative-swap checks must pass.

• Review A contains no action whose only approval or closure authority is Review B.
• Review B contains no action whose only approval or closure authority is Review A.
• Each carryover action identifies the next review, owner, dependency, and current status.
• The correction register links to the preserved original records.