The Merger Filing Date Label

An assumption is something taken as true for planning but not yet confirmed; it needs an owner, a validation date, and contingency. A constraint is a boundary imposed externally or by a decision that limits the project's options; it is not negotiable inside the project. A dependency is an input or action required from another party or activity; it sits on the critical path and needs a commitment date and escalation trigger.

Classification:

• Regulator's 30-day window - constraint. It is statutory and sets the outer boundary for the schedule.
• 14 March filing date - a derived schedule commitment, not a true assumption. It is conditional on the seller's consent and on internal filing preparation.
• Seller's licence transfer consent - dependency. It is an external party input, currently unrequested. If the team treats it as likely, it is also an unvalidated assumption, but its primary management category is dependency.

The labels drive behaviour. Assumptions attract contingency and validation tasks. Constraints define what cannot be changed. Dependencies attract named owners, request dates, and escalation. Calling 14 March an assumption makes it look controllable and hides the missing request; calling the consent a dependency but not tracking it leaves no owner. The five-day contingency is also mis-sized against a two-week holiday delay. 'Fixed by the baseline' confuses approval with certainty: a baseline is a reference point, not evidence that the date is achievable.

The main consequence is that the risk is invisible in the places where decisions are made. If 14 March is logged as an assumption, the risk register probably contains no entry for 'consent not requested', and no one owns the request to the seller. Contingency is attached to the wrong object: five days sits against an assumption, while the actual dependency has a two-week delay exposure. The 30-day statutory window means a late filing is not just a schedule slip; it is a regulatory breach with potential penalties and reputational impact.

Risk reporting is also distorted. A dependency with an unrequested input should be rated on likelihood and impact, with a clear trigger, such as 'if consent is not received by 7 March, escalate'. Instead, the programme manager's refusal to move the baseline turns an issue into a surprise. Escalation has no defined route because the consent appears to be an internal planning variable rather than an external commitment.

Reclassification changes the picture:

• The dependency gets an owner in regulatory affairs or legal, a written request date, a promised response date, and a red/amber threshold.
• The risk register gets an entry with likelihood, impact, mitigations, and a review date.
• Contingency is sized against the dependency lead time, not the five-day assumption.
• The constraint is stated explicitly so no one proposes 'just filing late' as a schedule option.

This is not paperwork. It determines whether the steering committee sees the problem with enough time to act.

Present a one-page reclassification with four columns: item, current label, correct label, evidence and impact. Show the timeline: closing date, 30-day deadline, earliest consent request (today), seller legal return (up to two weeks), internal filing preparation, and the latest safe filing date. Show two scenarios: consent received within five working days versus consent delayed by the holiday period. Make clear that the 14 March date is a forecast, not a fixed fact, and that the statutory window is the real constraint.

Ask the steering committee to:

1. Approve the reclassification and the new risk register entry.
2. Direct legal and regulatory affairs to request consent in writing today and escalate to the seller's general counsel if no response is received within three working days.
3. Approve a decision point: if consent is not received by 7 March, trigger regulator engagement and an executive briefing.
4. Confirm that baseline changes follow change control, not personal refusal.

Handle the programme manager by separating the person from the problem. Acknowledge that the baseline was approved and that the pressure is real, then say: 'The plan used the wrong label; correcting it protects the credibility of the baseline.' Avoid blaming them in the room. Use evidence: the consent has not been requested, the seller's legal team is away, and five days of contingency cannot absorb a two-week delay. If they resist, ask them to agree the classification first and defer the date debate to the evidence. Document the decision and the owner.