Review an RFP response before it loses marks

A final review only catches what would get a response rejected or marked down if two conditions hold. It must run in the order the buyer evaluates, and every check needs a named owner and a stated test for how it is judged. That order is pass/fail requirements first, then scored answers weighted by the published marking scheme, then evidence that's current on the submission date, then named approvals for anything that binds your organisation. This guide follows the review as it happens: booking time, clearing pass/fail requirements, marking scored answers, proving every fact is current, reading the response as one document and recording approvals, and ending with a checklist you can reuse.

Who runs the review and what it needs

The review works on the response exactly as you will upload it. Each reader checks it against everything the buyer has said about how it will be judged. Gather these inputs before the first check starts:

• the final files, in the formats and file names you will upload
• the tender instructions, including format and submission rules
• the evaluation methodology: award criteria, weightings and any scoring descriptors
• every clarification answer and addendum the buyer has issued
• the compliance matrix, updated for those changes

The roles matter as much as the files. The bid manager owns the review, sets the timetable, and gives the final sign-off, because they carry accountability for what the response commits to. A reviewer who didn't write any of the response runs the pass/fail and consistency reads, since authors tend to read what they meant to write rather than what's on the page. The pricing owner checks the price schedule and every figure that depends on it. Legal reads the commitments, contract terms and any exceptions. Each piece of evidence, such as a certificate, a policy or a case study, has an evidence owner who confirms it's current.

None of this depends on how the response was drafted, whether by writers, subject matter experts or general-purpose AI. The review judges the result. Our guide to RFP response covers the work before it, from qualifying through planning and drafting.

Book the review back from the upload deadline

Plan the review process backwards from the time you'll upload to the buyer's portal, not from the submission deadline. The deadline is when the portal closes. The upload is when your work ends, and you need room between the two for a slow portal, a rejected file type, or a lapsed login.

Put the pass/fail slot first. A miss found there may require something from outside the bid team, such as a signed declaration or a renewed certificate, and that takes longer to fix than a weak paragraph. Then book the scoring read, the evidence check, the consistency read and the approvals, each followed by time to fix what it finds and to re-check the fix. Without a re-check slot, changes go into the response without anyone reading them.

Book every reviewer by name and by the hour, not as "legal, sometime that week". This makes the cost visible. Add up the hours each named person needs for their checks on this pack, plus the re-checks, and you have the review's size in people and time. On a large multi-file tender, that total is a staffing decision in its own right. If the people aren't free in the window, you find out while there's still time to move the plan, or to ask whether the bid is still worth the effort it now needs.

The review window is set when you plan the response before drafting. How to respond to an RFP shows how that plan is built.

In SEQUESTO: James, the agent who orchestrates the work in SEQUESTO aOS, reads your organisation's governance process alongside the tender. He places sign-off stages and financial verification points in the tender timeline as milestones, each with a time and a named reviewer, and your bid manager accepts, adjusts, or rejects each one.

Clear every pass/fail requirement first

Clear every pass/fail requirement before anyone reads for quality. A missed attachment, an answer over its word limit or an ignored formatting instruction can cost the response before an evaluator reads a word of it. This compliance checklist work has a different standard from everything that follows, because no answer, however good, makes up for a missing form.

Re-run the compliance matrix against the final files, not the drafts it was built alongside. Requirements move during a bid: an addendum adds a form, a clarification answer changes a limit, a late edit pushes a section over. Check each line against the page where the final response meets it, and add any requirement that arrived after the matrix was built.

Mandatory questions, forms and attachments

Confirm that every mandatory question has an answer where the buyer asked for it, in the buyer's own form where one is supplied. Check that every mandatory attachment is present, in the version the response refers to, and named as instructed. Have someone authorised sign each form or declaration that requires a signature. At selection stage, set your answers against any thresholds the buyer has published, such as minimum turnover, insurance levels or certifications. An incomplete answer or missing evidence can remove you before the buyer assesses your capability.

Limits and format instructions

Count word, character and page limits the way the tender instructions count them. Some include headings, tables or appendices and some don't, and your word processor's count can't tell which applies. Then check the remaining format instructions: font and size, file type, file naming, maximum file size and any rule on where content may go. Each one is a requirement like any other, and it's far easier to fix now than to explain after the deadline.

Mark each scored answer as the evaluator will

Read the award criteria and weightings again, then spend review hours on each answer in proportion to the marks it carries. How much of the evaluation turns on quality depends on the market. The European Commission's Single Market and Competitiveness Scoreboard tracks how often public buyers award on price alone in procedures published in TED. In 2024, that was 7% of procedures in Ireland and 80% in Greece. No single split of review time fits both ends of that range.

Weight the review by the marks

Where a tender awards on price alone, the quality answers still have to meet their pass/fail tests, but the marks come from price. The review hours therefore go to the price schedule: its arithmetic, its completeness and its fit with the buyer's pricing template. Where quality carries weight, list the scored questions with their weightings and book reading time against each in the same proportion. A question worth twice the marks of another gets twice the review. Never rewrite a question worth a few marks at the expense of one worth many.

Test each claim against its criterion

Read each scored answer with the marking scheme open beside it, as the evaluator will. For every claim, ask which criterion it scores against and what evidence in the answer proves it. A claim that answers no criterion uses words the evaluator can't mark. A criterion that no claim addresses leaves its marks unclaimed. Before you start, set a target score for each answer against the buyer's scoring descriptors. Any answer below its target goes back to its author with the missing evidence named, while there's still time. How to write a tender bid covers writing each answer to its question, and this read checks the result.

Prove every fact is current on submission day

Check every certificate, figure and case study against the submission date, not the day you happen to read it, and give each one a named owner who confirms it. A document that was valid during drafting but expires the week the response goes in is exactly what this review exists to catch.

Certificates, insurance and accounts

The evidence owner confirms each document is in date on the submission date. They also confirm the insurance cover meets any level the buyer has set, and that the accounts are the ones the buyer asked for. If anything expires before submission, put the renewed version in now. For a tender in the European Economic Area, the Commission's eCertis database lists the documentary evidence each country uses for eligibility criteria. It helps you check whether a certificate or declaration matches the evidence the criterion requires.

Case studies and figures

A case study has to match the question it supports. One that doesn't costs more than citing none, because it points the evaluator at the gap instead of filling it. Check that each client named in a case study has agreed to be cited in this response. Every figure, such as headcount, response times or delivery volumes, should trace to a dated internal source with an owner. Keeping evidence with owners and review dates through the year keeps this check short, and an auditable evidence library shows how.

AI-drafted answers

A draft from general-purpose AI, whether ChatGPT, Microsoft Copilot or a model inside your content library, arrives quickly and reads well. But fluent text tells a reviewer nothing about where a claim came from. Check each claim in an AI-drafted answer against an approved source, such as a current policy, a certificate, an approved answer or a delivery record. The owner of that source confirms the claim. Anything without a source comes out, or goes to a subject matter expert who will stand behind it. Apply the same test to answers people wrote. The claim binds you, whoever drafted it.

Read the response as one document

Have one reader who wrote none of the response read it end to end, across every file, and check that names, numbers, dates and promises match throughout. Sections written by different people over different weeks drift apart. Each may pass its own review, but an evaluator reading the pack in order still sees the drift.

Start with names. A reused answer can carry another buyer's name, another contract's service levels or a product you've since renamed. Check the buyer's name, your legal entity's name, and the names of any people you've put forward wherever they appear.

Then check numbers and dates. Headcount, service levels, response times, mobilisation dates, and prices must agree across the narrative, the price schedule, and every appendix. Take one example: a method statement commits to a named account manager, but the price schedule has no line for one. The evaluator now has two different stories, and one of them is a commitment you've priced at nothing.

Then check promises. Every commitment in the response should be something the organisation has agreed it can deliver. The account lead reads the commitments against what the buyer has been told in meetings and presentations, because the evaluator may already have heard a different version.

When a fix changes a number or a promise, change it everywhere it appears and re-read each place. A fix in one section can create the next inconsistency.

Record named approvals, then submit

Get each binding part of the response approved by the person who owns it, and record each approval before anything is uploaded. Legal approves the contract terms, any exceptions or assumptions you've stated, and any commitments beyond your standard terms. The pricing owner approves the price and every figure that depends on it. The bid manager gives the final sign-off on the whole response.

A usable record says who approved which commitment, on which version of the file, and when. "Legal has seen it" isn't a record. If a commitment is questioned after award, the team has to show what was approved and by whom, and the version number ties the approval to the words the buyer received.

Upload early, inside the window you booked. Once the portal confirms the upload, keep the receipt and a copy of the files exactly as submitted, stored apart from the working versions, so a later edit can't overwrite the record of what the buyer holds.

In SEQUESTO: every edit, approval and export is logged with the person, the timestamp and the item, and you can search and export the log whenever you need to show who approved what. A person on your team still uploads the response in the buyer's portal.

The RFP review checklist

Reuse this review checklist on every proposal, with one owner per line. Each line says how it's judged: once for the whole response, each one with no misses, or against a threshold set before the review starts. After each debrief, add a line for anything that lost marks that the checklist didn't catch.

• The review is booked back from the planned upload time, with every reviewer named and a re-check slot after each read (once; owner: bid manager).
• Every line of the compliance matrix, updated for all addenda and clarification answers, points to where the final files meet it (each one, no misses; owner: non-author reviewer).
• Every mandatory question is answered in the buyer's form, and every mandatory attachment is present in the right version and named as instructed (each one, no misses; owner: non-author reviewer).
• Someone signs every form and declaration that needs an authorised signature (each one, no misses; owner: bid manager).
• Every answer is within its word, character or page limit, counted as the tender instructions count it (each one, no misses; owner: non-author reviewer).
• Every file meets the format instructions for type, naming, size and layout (each one, no misses; owner: non-author reviewer).
• Review hours on each scored question and on the price schedule follow their weightings (once; owner: bid manager).
• Every scored answer reaches its preset target score against the buyer's criteria (against threshold; owner: assigned reviewer).
• Every certificate, insurance document and set of accounts is valid on the submission date and meets the buyer's stated levels (each one, no misses; owner: evidence owner).
• Every case study matches its question, and its client has agreed to be named (each one, no misses; owner: evidence owner).
• Every figure, and every claim in an AI-drafted answer, traces to an approved, current source confirmed by its owner (each one, no misses; owner: source owner).
• Names, numbers, dates and promises match across every section and file (each one, no misses; owner: non-author reviewer).
• Commitments match what the buyer has been told by the account team (once; owner: account lead).
• Legal and the pricing owner have approved their parts, each approval recorded with version and date (each one, no misses; owner: bid manager).
• The bid manager's final sign-off is recorded against the version uploaded (once; owner: bid manager).
• The upload receipt and the submitted files are stored apart from the working versions (once; owner: bid manager).