Approval Without Applause: Writing Proposals for the Reviewer Who Never Joins the Call

In most competitive processes, the document is not assessed by the people who will attend the pitch. It is assessed by procurement officers, finance business partners, risk and compliance specialists, legal advisers, information security reviewers and, on occasion, the owner of a framework agreement. They read in sequence, against a scoring matrix, within a fixed window. Their view of the firm is formed entirely from the paper in front of them.

Bid teams tend to write for the audience they will meet. That is a reasonable instinct and an incomplete one. The presentation can win over a room; only the document can win over the file.

The room behind the room

A useful discipline is to picture three readers who will never speak to you.

The procurement lead is asking whether the arrangement can be governed safely. Can the requirement be met in full, on the stated timetable, by a supplier with the capacity and the standing to deliver it? Are the terms acceptable? Is there anything here that will create work at contract signature or dispute at month nine?

The finance reviewer is asking whether the number is defensible. Is the price complete and internally consistent? Are the assumptions stated? Does the cost model hold together when a colleague opens the spreadsheet and starts testing it?

The compliance and risk reader is asking whether exposures have been identified and owned. Data protection, information security, subcontractor dependency, insurance, business continuity, exit. They are not looking for a firm with no risks; they are looking for a firm that can describe its risks accurately, because that is the behaviour that will persist after award.

None of these readers is hostile. They are, however, accountable for a recommendation that may be scrutinised later. That changes what the document needs to do.

Self-sufficiency as a design principle

A written submission should not depend on the reader having been in a prior conversation. Phrases such as as discussed, as agreed and as you will be aware of are all, in effect, requests for credit that the unseen reviewer cannot grant.

Practical consequences follow. Define acronyms at first use, and then use them consistently. Avoid referring to section 4 before the reader has reached it. Do not assume a familiarity with the firm's proprietary method names; explain them once, plainly. Put the answer to each requirement where the evaluator expects to find it, rather than where it reads best. If the scoring matrix asks a question, answer it in the order the matrix asks it, under a heading that mirrors the wording.

This is not a concession to bureaucracy. A document that can be read straight through, by someone with no context, in a single sitting, is a document that gets marked accurately. Ambiguity is rarely scored as generosity.

Pre-empting the risk question

Most deferrals are not rejections. They are requests for information that arrive too late to be answered inside the timetable.

The most effective defence is a short, plainly written risk section that anticipates the questions before they are put. A table of four to six material risks — with likelihood, impact, mitigation, owner and residual position — does more for a proposal's credibility than a page of assurances. Add the matters that procurement routinely checks and that bid teams routinely leave out: the data protection position and any sub-processors; the insurance cover and its limits; the proportion of delivery that depends on subcontractors; what happens to client data and intellectual property at termination; and who is accountable if the named lead leaves.

Each of these is a question that will be asked eventually. Answering it in the document converts a potential objection into evidence of competence.

Making the price legible

Price is where unseen reviewers spend the most time and where bids most often lose quiet marks. A single total invites scepticism; a total with a clear build-up invites scrutiny, which is a better outcome.

State the assumptions that generate the number: the volumes, the service levels, the working pattern, the duration. State the exclusions plainly and early, because an exclusion discovered later reads as a hidden cost rather than an honest boundary. Show how any rate has been constructed, at least in outline, and reconcile the pricing schedule to the narrative so that a reader testing one against the other finds no contradiction. Where relevant to a UK audience, address indexation, VAT treatment and whole-life cost rather than the headline figure alone.

Consistency is the point. A finance reviewer who finds two different totals in the same submission will not necessarily query it; they will simply discount the whole document.

Giving the reviewer a defensible yes

People who must justify a recommendation need material they can quote. It is worth writing with that in mind: one clear sentence per section that could be lifted into an evaluation sheet without distortion.

A firm's differentiator, stated in a single specific claim and supported by a reference on the same page, is worth more than a paragraph of adjectives. So is an unequivocal statement of what the firm will commit to, expressed in terms the contract can adopt. Where a requirement cannot be met exactly, say so once, clearly, and offer the alternative; a precise partial answer is easier to approve than a vague claim of full compliance that collapses under examination.

The deferral instinct

Evaluators defer when they are uncertain, not when they are unimpressed. Uncertainty is produced by gaps, by inconsistencies between the narrative and the pricing schedule, by unverifiable claims, and by assurances where evidence was expected.

Every gap is a small invitation to ask a clarifying question, and clarifying questions cost time that a bid timetable rarely has. Close the gaps in the writing, and the reviewer is left with a document they can approve on its own merits — which is the only endorsement the unseen reader is ever in a position to give.