Decision needed: one reporting tool or two before Q3 planning?

A dated request from a Planning Lead to an Operations Director, with options, the cost of waiting and a recommendation.

Worked example from Northstar Services, a fictional company. Use it as the pattern for your own blocked decision: one choice, one date, one recommendation.

Printed documents and folders on a desk

The request at a glance

Finance Operations and Regional Delivery each report on project capacity in a different tool, and the Q3 planning cycle starts Monday 30 June 2025. The Planning Lead asks the Operations Director to choose by Thursday 12 June 2025, 17:00 UTC. Recommendation: consolidate into one tool (Option B), starting the week of 16 June, so planning week opens with one shared capacity view.

Options compared

Effort figures are illustrative planning estimates from the fictional example, not measured results.

What changes now
Option A: Keep both tools:
Nothing. Both teams keep their current tool.
Option B: Consolidate first:
Regional Delivery moves its capacity reports into the Finance Operations tool.
View for planning week
Option A: Keep both tools:
Two reports, reconciled by hand
Option B: Consolidate first:
One shared capacity view
Effort before 30 June
Option A: Keep both tools:
Low. About 1 day of reconciliation per team each cycle.
Option B: Consolidate first:
Medium. About 6 working days per team (estimate).
Main risk
Option A: Keep both tools:
Totals differ between reports and slow planning decisions.
Option B: Consolidate first:
Migration overruns into planning week.
Can it be reversed?
Option A: Keep both tools:
Yes. Revisit next cycle.
Option B: Consolidate first:
Before cutover, retain the working source. After validated cutover, keep the old tool as a read-only archive for 60 days; restoring active use would require a separate recovery plan.

If we wait, and what we recommend

Consequence of delay

If no decision is made by Thursday 12 June, the default is Option A. Both teams then enter planning week with separate reports and spend the first planning meeting agreeing which totals to trust. Each cycle it continues, the reconciliation becomes harder to unwind, because new reports are built in both tools.

A decision after 20 June leaves too little time to migrate before planning week. Option B would then slip to the next cycle.

Recommendation, dated 5 June 2025

Choose Option B: consolidate first.

  • The extra effort is a one-time cost of about 6 working days per team. The reconciliation under Option A recurs every cycle.
  • Planning decisions depend on one agreed capacity number, and Option B is intended to provide it after both teams validate the shared reports.
  • Use a cutover checkpoint on 27 June. If migration and shared-report validation are incomplete, defer cutover and keep both working tools for this planning cycle. Start the old tool’s 60-day read-only archive only after a successful validated cutover. The fallback protects the source workflow but still leaves reconciliation work.

Response needed: choose A or B, or name the one question that must be answered first, by 17:00 UTC on 12 June 2025.

Evidence behind the recommendation

A decision maker should see what the claim rests on and how far to trust it.

Requirements comparison

A dated side-by-side of what each team needs from a capacity report. Written by the requesting owner on 2 June after a working session with both teams.
  • Both teams need weekly capacity by role
  • Only Regional Delivery needs site-level detail
  • Both can be met in one tool

Recorded assumptions

The estimates the recommendation depends on, each with an owner.
  • Migration takes about 6 working days per team (team leads' estimate)
  • No new licences are needed (checked by Business Operations)
  • Q3 planning starts 30 June (fixed by the planning calendar)

Known limits

What the evidence does not show, so the decision maker can weigh it.
  • Effort figures are estimates, not a pilot result
  • Regional Delivery has not yet tested its site-level reports in the shared tool

Before you send your own brief

Run this check so the decision maker can answer without a follow-up meeting.

  1. 1

    State the choice in one sentence

    Name what is to be chosen and the date you need the answer, as in the heading and opening paragraph above.
  2. 2

    Limit it to two or three options

    Include the do-nothing option. Compare each on the same rows: what changes, effort, risk and reversibility.
  3. 3

    Say what happens on the deadline

    Describe the default outcome if no one decides, in terms of who has to do extra work or which date slips.
  4. 4

    Recommend one option and date it

    Give the reasons that follow from the comparison, and mark which numbers are estimates and who produced them.
  5. 5

    Name the roles on both sides

    Say who maintains the brief and answers questions, and who is expected to decide.

Who does what in this decision

Requesting owner
Planning Lead, Finance Operations
Department: Maintains this brief, answers questions on the evidence and records the outcome once a decision is given.
Decision maker
Operations Director
Department: Chooses Option A or B, or states the one question that must be answered first, by the requested date.
Contributing team lead
Delivery Lead, Regional Delivery
Department: Confirms the Regional Delivery requirements and migration estimate in the evidence section.