How to Submit a Proposal to a Procurement Process

The first thing to understand is that you are no longer writing a proposal. You are writing a compliance document that also has to be persuasive, and the two requirements are in tension every time they meet. Nearly every mistake in this genre comes from writing the second document when the process asked for the first.

You are being scored, probably against a sheet

A tender, an RFP or a formal quotation request is usually evaluated by someone working through criteria with weightings, sometimes by more than one person independently, sometimes by someone who was not in any of your conversations.

Three consequences follow immediately, and they overturn ordinary proposal advice.

• Answer in their order. If the document asks for six things numbered 1 to 6, your response has six sections numbered 1 to 6. An evaluator looking for section 4 and not finding it does not go hunting; they score what they can see.

• Answer in their words. If they call it “service continuity” and you call it “uptime”, use their phrase and put yours in brackets. This is not writing badly; it is making it possible to be scored.

• Answer everything, including the parts that do not apply. “Not applicable, because …” scores. A blank scores zero and, worse, reads as an omission rather than a decision.

This is the one context where the inverted-pyramid ordering in the structure article is wrong. There, you order for a reader who may stop at any point. Here, the reader is paid to reach the end and is penalising you for making them look for things.

Format compliance is the cheapest marks available

Page limits, font sizes, file formats, file naming, a required cover sheet, a signed declaration, a separate pricing schedule in a supplied template. These are frequently either scored directly or used as a pass/fail gate before anything else is read.

They are also the only part of the whole exercise that requires no expertise, no cleverness and no risk. Do them exactly. If the pricing schedule is a spreadsheet with locked cells, use the spreadsheet — do not send a nicer-looking version of it, however much better yours is.

If they do not specify a file name, use a name that survives their filing system rather than yours: who it is from, what it is, what it is about, and an ISO date. The naming rule has the full version, including the four things to keep out.

This is the case where you send a file

A portal wants an upload. A submission deadline wants an artefact with a timestamp on their system. A records policy wants a document they hold rather than one you host. Send the file, in the format asked for, and do not spend a single sentence arguing for a link instead.

It is worth being clear-eyed about what that costs, because it is the one thing this whole site is otherwise about: an uploaded file generates no evidence at all. Nobody will tell you it was opened, by whom, or how carefully. The full comparison of what each method costs is here, but in this situation the trade is not yours to make.

Which means the blackout is a property of the process, not a failure of your tooling. Do not read silence during an evaluation period as a signal of anything — there is nothing to read. The inference you can normally draw from an unopened document simply does not apply here, and it is worth knowing why before you talk yourself into a conclusion: what it means when a proposal is never opened.

Where a link still does real work

Alongside the formal submission, not instead of it. Three places:

1. Before the process closes to conversation. Most formal processes have a period where you can still talk to a named person. Anything you send during it — a capability summary, a relevant piece of work, a note answering a question they raised — can be a link, and you can tell whether it landed.

2. The internal copy. Your contact often circulates something readable alongside the formal file, because the formal file is unreadable by design. That is where the actual persuading happens and it is the version worth tracking.

3. After the decision. Debriefs, revised scopes, the next opportunity. The relationship outlives the tender and stops being a compliance exercise the moment the process closes.

The mechanics that decide more outcomes than the writing

• Submit a day early. Portals fail, uploads time out, files exceed limits nobody mentioned, and no procurement officer has ever granted an extension for a technical problem at the buyer’s end of your excuse. Submit early, then submit an updated version if they allow replacement.

• Use the clarification window. Ask your questions. But remember that in most public and many private processes the answers are circulated to every bidder — so ask questions whose answers help you and do not reveal your approach. A question that telegraphs your solution is a free gift to the competition.

• Check whether the specification contradicts itself. Long tender documents assembled by several people frequently do. Finding it and asking about it is one of the few genuinely differentiating things you can do before submission.

• Price it in their template, and put your assumptions somewhere they will be read. A locked pricing schedule usually has nowhere to say “assuming you provide X”. Find where the assumptions do belong — a clarifications section, a covering letter — and put them there rather than nowhere.

On the pricing itself, everything in where pricing goes in a proposal about scope, exclusions and assumptions still holds — the difference is that a process will tell you the format and you obey it.

Decide whether to bid at all

The most valuable skill in this genre is declining, and it is the one nobody writes about because it produces no document.

Signals that a process is not worth your week: a specification written around a named competitor’s product, criteria weighted overwhelmingly to lowest price when you do not compete on price, a deadline short enough that whoever helped write the specification is the only party who could meet it, and a scope so vague that any price you give is a guess you will be held to.

Declining early and saying why — briefly, without grievance — is also how you stay on the list for the next one. Nobody remembers the bid you did not submit. Everybody remembers the supplier who quoted for work they clearly could not do.

For the informal copy that runs alongside a formal submission, what a tracked link actually tells you is set out with its limits included, and sending a document to several people at one client covers the committee on the other side of it.