The Forwarded Document: A Proposal That Speaks for You in the Next Room

Most proposals are not read in the order they are written. A UK buyer receives your document after a conversation, a referral or a short enquiry, then forwards it to a finance lead, a director, a procurement colleague or a board member who was not in the room. That person arrives without your tone of voice, your caveats or the context you built up over two meetings. They see a document and a decision. Your proposal has to stand on its own.

This is not a reason to make proposals longer. It is a reason to make them clearer. The consultant who writes only for the person who asked for the proposal often leaves the second reader to reconstruct the case. The consultant who writes for the forwarded reader gives the original buyer a document they can defend without having to rewrite it.

Write for the person who arrives late

The opening page should do three things in plain English: name the decision, explain why it matters now, and state the outcome being bought. Avoid opening with your methodology. The second reader has not come to admire your process; they have come to understand whether the work is worth approving.

A useful test is to imagine the proposal has been separated from your covering email. Could a sensible colleague read the first page and explain to someone else what is being proposed? If not, the opening is doing too little. Keep the first few sentences free of acronyms and internal shorthand. If a term is necessary, define it once. A finance lead should not have to infer what a phase name means, and a procurement colleague should not have to guess whether a workshop is included.

A short risk-and-outcome section earns its place

Many proposals describe activity: discovery, workshops, interviews, analysis, reporting. Those are inputs. The second reader is usually asking a different set of questions. What will be different if this is approved? What could go wrong? Who is responsible for what? What are the assumptions? What will it cost, and when?

A short risk-and-outcome section can answer those questions without turning the proposal into a legal document. It should sit near the front, not buried in an appendix. Set out the intended outcome in concrete terms, then list the two or three material risks and the practical way each will be managed. For example: access to the right people may slow the work, so the proposal names the roles needed and the dates by which they are needed. A decision may depend on data quality, so the proposal states what will be checked first and what happens if it is incomplete.

This section also helps the original buyer. When they forward the proposal, they can point to a page and say, this is the risk we discussed. They are not asking the second reader to trust a relationship they cannot see. They are asking them to review a reasoned case.

Give the buyer a decision ask, not a mood

A proposal that ends with a warm paragraph about looking forward to working together leaves the second reader unsure what they are being asked to do. Be direct. State the decision required: approval to proceed, agreement to a short discovery phase, permission to prepare a full scope, or a date for a scoping meeting. Say what happens next and by when. If there are two viable options, label them clearly and explain the trade-off in one sentence each.

A small summary box near the end can be especially useful for forwarded documents. It might contain the decision requested, the amount, the start date, the key dependency and the person who can answer questions. This is not a gimmick. It is a courtesy to the reader who has joined the conversation late.

A practical check before the proposal leaves your desk

Before sending, read the document as if you were the colleague in the next room. The following check is worth keeping beside your desk.

• Can the first page be understood without the covering email?
• Is the decision requested stated in one clear sentence?
• Are the outcomes described in plain English rather than activity?
• Are the two or three main risks named, with a practical response?
• Are assumptions, dependencies and exclusions visible without hunting?
• Is the cost profile clear enough for a finance reader?
• Is there a short summary that can be forwarded or pasted into an internal note?
• Does the document avoid language that only makes sense after your pitch?

This is not about diluting your judgement. It is about making your judgement portable. A proposal that depends on your presence is fragile. A proposal that can be read, questioned and defended in your absence is more likely to keep moving.

Help the original buyer champion the work

When you send the proposal, ask who else is likely to read it and what they will need to decide. That single question can save a week of revision. You might also offer a two-line summary that the buyer can use in an internal message. This is not asking them to do your selling for you. It is recognising that they may have to carry the document into a room you will never enter.

The strongest proposals are not the ones with the most pages. They are the ones that remain coherent when forwarded, printed, skimmed and questioned by someone who was not there. Write for that second reader, and you give the first reader a better chance of saying yes.