The sponsor receives a long update ending with “please advise”. The team knows there is a problem but has not presented a decision. A sponsor decision paper should state the choice required, who can make it, viable options, their consequences and the last useful decision date.
It prepares a choice before it is made. A decision log records the outcome afterwards. APM's governance commentary emphasises explicit decision authority; the one-page structure here is an original practical recommendation for a small project.
Photo by Vitaly Gariev on Unsplash.
Put the requested choice first
Write one sentence that names the decision. For example: approve a later full launch, or approve a smaller initial service within the existing event date. Identify any part requiring a different commercial, technical or operational authority.
Avoid asking the sponsor to approve an outcome without the corresponding trade-off. “Confirm the launch remains on Friday” is not a complete option if the team cannot produce the accepted scope by then.
Use an option brief rather than an evidence dump
Include:
Decision required and authorised decision-maker.
Current agreement and the evidence that challenges it.
Meaningful options, including maintaining the current approach where viable.
Delivery, resource, quality and operating consequences.
Important assumptions and information still missing.
Recommendation and the reason for it.
Decision deadline and options lost after that point.
People and records affected by the result.
Keep supporting detail available, but distinguish evidence from opinion. A confident recommendation can still state uncertainty honestly.
A hypothetical service launch
A supplier cannot provide a component in time for the full planned service. The team identifies two feasible options: move the complete launch, or introduce a specifically bounded first service and complete the rest later.
The brief explains which client needs the limited version would meet, which it would not, and the operational work created by two releases. The sponsor also sees the consequences of postponement and the commercial review required for any changed promise.
The recommendation is conditional on the appropriate service owner accepting the limited operating arrangement. It does not present that condition as already approved simply to make the preferred option look ready.
Make the deadline meaningful
State why the decision is needed by a particular time. A supplier booking might expire or a review window might be lost. Distinguish that practical boundary from a date chosen merely to accelerate a response.
If the sponsor cannot decide, identify what evidence or authority is missing and what work may continue. Do not interpret silence as approval unless the established governance explicitly provides that route.
Close the loop after the choice
Record the decision and its conditions, tell affected owners and update the relevant plan. An approved paper in one person's inbox does not change the team's working instructions. Preserve the option rationale so later changes can be assessed against the actual agreement.
The small-team project planning guide connects those choices to a working sequence. For the connected task, read A Project Decision Log: Record the Choice Without Rewriting the Meeting. If sponsor updates repeatedly produce questions rather than choices, discuss your project requirements.
