How do I summarize a long proposal for someone who only needs to make the decision?
Quick answer
Start with the decision the reader needs to make, then state the recommendation and its main reasons. Summarize meaningful alternatives and uncertainties that could change the choice. End with the decision needed and when it is needed, if known. Keep evidence, methods, and detailed comparisons in the proposal, and point to their exact sections so readers can check the basis for the summary.
The question, the details, the next step.
I have a long proposal, but the decision-maker has little time. What should I keep in the summary?
Keep what helps the reader make or defer the decision—not a miniature version of every section. A useful summary answers five questions:
- What decision is being requested?
- What option is recommended?
- Why is it preferred?
- What other option or uncertainty could affect the choice?
- Where can the reader check the supporting detail?
Put the requested decision and recommendation first. Give only the strongest reasons that matter to the choice. Include a material caveat even if it makes the recommendation less tidy; leaving it out can make the summary misleading. For each important claim, direct the reader to the proposal section that supports it.
How do I decide which details count as important, rather than just interesting?
Use a decision test: if the detail changed, could it reasonably change the preferred option, the conditions for approval, or the timing? If yes, include it briefly. If not, leave it in the proposal and provide a section reference only when a reader is likely to want it.
For example, a cost comparison may matter if the choice depends on available funds; a long description of how the team gathered every comment may not. But if that process left a key uncertainty unresolved, name the uncertainty and point to the relevant discussion. Do not turn a summary into a list of every fact. Select details based on the decision, and avoid implying that a point is settled when the proposal itself treats it as uncertain.
Could you show me what that looks like? The proposal uses headings and appendices.
Here is an illustrative example with placeholders, not a claim about a real project. Suppose a proposal asks whether to approve one of two options. A concise summary could read:
“Decision requested: Approve [Option A], [Option B], or request further work by [decision date, if known]. The proposal recommends [Option A] because [main reason] and [second decision-relevant reason]. [Option B] remains a viable alternative if [condition or priority] matters more. The recommendation depends on [key assumption or unresolved question]. See ‘Options and comparison’ for the basis of the comparison, ‘Risks and dependencies’ for the caveat, and Appendix [label] for supporting detail.”
Use the actual heading names and appendix labels from the proposal. If the document uses page numbers, add them only after checking they match the final version. A reader should be able to follow each reference without guessing where the evidence is.
How short should I make it, and how do I keep it from sounding like a sales pitch?
Let the decision’s complexity set the length; there is no fixed word count that suits every proposal. As a starting structure, use one short paragraph or a compact set of labeled sections, then remove anything that merely repeats the body. Keep the recommendation clear, but distinguish evidence from judgment: “The proposal recommends…” is different from presenting a preference as an established fact.
Use balanced wording. State the strongest reason for the recommendation, then identify a meaningful alternative, limitation, or condition. Avoid broad claims such as “best,” “risk-free,” or “guaranteed” unless the proposal actually supports them and the wording is appropriate. If a point is unknown, name it as unknown rather than smoothing it over. The summary should make the decision easier—not pressure the reader into a particular answer.
Can you give me a final outline I can use while editing?
Use this outline, filling in only what the proposal supports:
Decision requested: [What must the reader decide?]
Recommendation: [Which option is proposed, or is no recommendation being made?]
Why: [One to three reasons that matter to this decision.]
Alternative: [What is the most meaningful other option, and when might it be preferred?]
Uncertainty or condition: [What assumption, unanswered question, or dependency could change the choice?]
Next step: [What action or timing is requested, if stated in the proposal?]
Supporting detail: [Exact section heading, appendix label, or verified page reference for the comparison, evidence, and caveat.]
Before sending, check that the summary matches the proposal’s current version, that references lead to the right material, and that no caveat has disappeared. If the proposal does not specify a date, owner, or answer, leave a placeholder or say it is not specified; do not fill the gap by guessing.
A practical checklist
Name the decision the reader is being asked to make.
Put the recommendation—or the absence of one—near the beginning.
Keep only reasons that could affect the choice.
Include a meaningful alternative and any decision-changing uncertainty.
Check each section or appendix reference against the final proposal.
Remove claims, dates, and commitments the proposal does not establish.
A few more useful answers
Should the summary include every option in the proposal?
Include the alternatives that could realistically affect the decision, especially the strongest competing option. Point to the full comparison for additional options.
What if the proposal does not make a recommendation?
Say that no recommendation is made, then summarize the decision options and the key information or uncertainty readers may need to resolve. Do not invent a preferred choice.
How should I reference evidence in a digital proposal?
Use the proposal’s actual section headings, appendix labels, or working internal links. Check that each link or reference points to the relevant supporting detail in the version being shared.