Most proposals are written for an imagined reader: a thoughtful decision maker who reads the whole document, appreciates the nuance in your methodology section, and forms an overall impression of your firm.

That reader does not exist.

The actual reader is one of four or five people working through a scoring sheet, often on an evening or a weekend, on top of their day job. They are looking for specific things in a specific order, and they are awarding points against evaluation criteria they did not write and cannot deviate from.

Once you understand how that works, a lot of standard proposal advice turns out to be wrong. This is the second half of the story we started in Most RFPs Are Lost Before Anyone Writes a Word: that post covers deciding whether to bid, this one covers what happens to the document once you do.

Scoring is mechanical, not impressionistic

In most structured evaluations, each criterion has a weight and a scoring band. The evaluator reads your response to that criterion, decides which band it falls into, awards the score, and writes a one-line justification.

The bands are usually crude. Something close to: fully meets the requirement with strong evidence, meets the requirement, partially meets, does not meet or not addressed.

Two consequences follow, and both are uncomfortable.

First, a brilliant answer and a solid answer often score identically, because both land in the same band. Effort spent polishing an already-compliant answer from good to exceptional frequently buys nothing.

Second, a partially addressed mandatory requirement can cost the same points as one you ignored entirely. There is rarely credit for having tried.

The implication is not that quality is irrelevant. It is that coverage beats polish.

Getting every criterion into the meets band is worth far more than getting three into the exceptional band and missing two.

The evaluator cannot help you

This is the single most expensive misunderstanding in bid writing.

If the answer to a scored question sits in an appendix, in a different section, or is implied by something you said elsewhere, the evaluator is usually not permitted to go looking for it. In regulated and public sector procurement, they are explicitly instructed not to. Scoring what a bidder probably meant is exactly the behaviour that gets a procurement challenged.

They also cannot infer. If a requirement asks you to describe your escalation process and you describe your support model without naming escalation tiers and timeframes, they mark against what is on the page.

And they cannot advocate for you in moderation if the words are not there. Even an evaluator who knows your firm well and rates you highly is limited to defending what you actually wrote.

Write as though the reader has no memory of the rest of your document and no knowledge of your company. Because for scoring purposes, that is true.

Six things that quietly cost points

Write to the scoring model, literally

The most effective structural change most teams can make costs nothing: mirror the RFP's own language and order.

Use the buyer's section numbering and their headings, in their sequence. If they call it "Service Continuity", do not call it "Business Resilience" because that is your internal term. The evaluator is working through a checklist, and every point of friction between their sheet and your document is a chance to score you lower for something you actually covered.

Within each answer, use a consistent four-part shape.

  1. State the answer in the first sentence. Directly, in the buyer's terms.
  2. Explain how you deliver it, briefly and specifically.
  3. Provide evidence: a named client, a metric, a certification, a document reference.
  4. Close with the implication for this buyer, in one line.

It is a formula, and it reads like one if you look for it. It also scores consistently well, because it puts every element the scoring band is looking for exactly where the evaluator expects to find it.

Moderation is where inconsistency gets punished

In most formal processes, individual scores are reconciled in a moderation session. Evaluators compare marks, argue the outliers, and agree a consensus score.

Two things happen there that matter to how you write.

Contradictions surface. If one evaluator scored your resourcing section well and another read your timeline section and saw a conflict, moderation is where that gets raised and where your score gets pulled down to the more sceptical reading.

Vague content converges downward. When evaluators disagree about whether an answer meets a requirement, the resolution is almost never to award the higher band. Ambiguity in your writing becomes a lower consensus score.

Both risks are reduced by the same discipline: specificity, and one person doing a full consistency read before submission.

The executive summary is not what most people think

In a scored evaluation, the executive summary frequently carries no marks at all.

That does not make it useless. It is often the only part read by senior stakeholders who influence the decision without scoring it, and it sets the frame for everyone else. But it should be written in an hour by someone senior, not agonised over for two days by the team that still has scored sections outstanding.

Spend the effort where the marks are. It is a simple reallocation and very few teams make it.

A test worth running before you submit

Hand your response and the evaluation criteria to someone who did not write it and has no context on the deal. Ask them to score it as an evaluator would, using only what is on the page.

Then compare their scores with what your team expected.

The gaps are almost always in the same places: answers that assume knowledge the reader does not have, claims nobody evidenced, and requirements the team believes were covered somewhere, which is the failure mode we unpack in Most Losing Bids Are Never Actually Read. Every one of those is fixable in the last 48 hours, and none of them will be visible to the people who wrote the document.

RFPropel maps every scored requirement from the RFP to your response, drafts in your firm's voice with citations to your own evidence, and flags unsupported claims and coverage gaps before you submit. Response time drops from 32 hours to under 4. See how it compares with Loopio, Responsive and other RFP tools on our comparison page, or read the FAQ. Currently in beta with early access open.