Post-Close Reporting Can Hide Control Failure

Post-close programmes generate impressive reporting: accounts migrated, devices enrolled, applications connected, risks closed.

The buyer may still lack control of the domain, recovery contacts, service identities or critical data. Activity becomes a substitute for ownership.

Report control outcomes

- Can the buyer authorise?

- Can it observe?

- Can it revoke?

- Can it recover?

- Can it reconcile?

- Can it exit the seller dependency?

Value object — The Post-Close Control Scorecard

- Critical domain.

- Outcome and evidence.

- Open seller or vendor dependency.

- Exception owner.

- Thesis milestone affected.

- Next proof date.

Reject percentage completion

A migration can be ninety-nine percent complete while the final one percent contains the sovereign account. Weight metrics by consequence.

The board needs to know whether ownership has become control—not whether the programme has been busy.

Where this breaks

Programme dashboards reward completed tasks even when the remaining task controls the entire environment. Percentage completion masks consequence concentration.

The operating move

Report evidence of authority, observation, revocation, recovery and independence for each critical domain. Weight unresolved items by thesis impact.

Replace task count with control outcome.

Show seller access explicitly.

List untested recovery paths.

Escalate expired exceptions.

The test

Ask the board which unresolved item could still prevent control. If the dashboard cannot answer directly, it is measuring activity rather than ownership.