Analyse an RFP so a no-bid costs hours

In the final week, legal reads the draft contract and finds a pass/fail condition that nobody working on the bid had seen. RFP analysis prevents that by reading the pack for deal-breakers first, so a no-bid costs hours of reading rather than a half-drafted response. It's finished only when every requirement, criterion, date, risk and clarification question traces to its place in the documents.

Where RFP analysis breaks between the bid team, legal and pricing

RFP analysis breaks when whoever opens the pack first reads it front to back, and the list it produces stops pointing back to the documents. Picture an illustrative pack of five files: a specification, instructions to bidders, a pricing schedule, a draft contract and an addendum issued after release. The writers open the specification first, because that's where the questions are. The draft contract waits for legal, who see it once drafting is underway, and the pricing schedule waits for the commercial lead. The addendum sits in a separate download, while the requirement it changes stays in the extracted list in its original wording.

Each of those habits lands on someone. The writers spend time on answers that a contract term or the addendum later changes. Legal reads the terms when there's little time left to raise a question or reprice. The bid manager signs off the response and answers for its compliance. Yet they hold a requirements list where no line says which clause it came from, so a missed pass/fail item has nowhere to be caught.

In APMP's Winning Business Ecosystem, this step is called RFP Review. It analyses requirements, instructions, evaluation criteria and submission deadlines, and it builds a compliance matrix to track what the response must contain. That's the right output for the first stage of an RFP response. It holds only when the reading order and the trace to source are built into it.

Read the pack for deal-breakers before anything else

Analysing RFP documents starts with the files that can end the bid, not the ones that hold the questions. Read eligibility and the pass/fail items first, then the draft contract, the pricing schedule and any addenda, and the specification last. Eligibility and pass/fail items show whether you can submit at all, whether the bar is a certification, a financial threshold or a required kind of experience. The draft contract shows what you'd be bound to if you won. The pricing schedule shows whether the commercial model fits how you deliver. Each addendum can change something you've just read, so check it against the deal-breakers before moving on. The specification comes last because it's where the writing starts, and that work is wasted if the bid stops.

In the example, this order puts the pass/fail condition in front of the bid manager in the first hours. If it rules the bid out, the no-bid has cost a few hours of reading and nothing else.

Reading the contract and pricing early also guards against a risk the industry's code of practice names. In BSI's description of PAS 360:2023, the code of practice for bid and proposal management, its governance reduces the risk of a contract that's undeliverable in practice or needs more resources than budgeted.

Extract each requirement with its place in the documents

Requirements analysis gives one line per item, and each line carries the file and clause it came from. Every requirement, evidence request, mandatory attachment, word or character limit and date goes into the compliance matrix with its document name and its clause, section or row. A line with a source can be checked against the pack in seconds. A line without one has to be found again by whoever doubts it, often when time is shortest.

Two kinds of items need more than a source. The first is a requirement stated in two files with different wording, such as a service level in the specification that the instructions repeat with another measure. Record both locations on one line and mark it as a conflict. It then goes to the clarification step instead of being settled by whoever drafts the answer.

The second is a dependent requirement, where one answer sets off another. Proposing subcontractors can call for a further form for each one. Confirming a certification can call for the certificate as an attachment. Naming a delivery team can call for CVs within a page limit. Link these lines in the matrix so the follow-on answer or attachment has an owner from the start, rather than showing up missing at upload.

In the example, the addendum's change goes on the line it amends. The addendum's clause becomes the current source, and the original stays beside it.

Read the evaluation criteria for where the marks are

Take the award criteria and weightings from this pack, not from the last bid or the last buyer. How often the cheapest bid wins varies widely. In the European Commission's Single Market Scoreboard, 55% of public procedures across the EEA in 2024 were awarded to the cheapest bid on average, against 8% in Norway.

For each scored question, note what the marking scheme rewards and how many marks it carries. Then test each claim you plan to make against it. A strength the scheme doesn't score is context at best. A strength it scores heavily earns a place in the response plan and an owner. In the example, the marking scheme sits in the instructions to bidders. This is where the specification's questions get ranked by marks rather than by the order they appear in.

How pass marks, weightings and price formulas work is set out in tender criteria. For the analysis, each criterion and its weight go into the record with their clause, like every requirement.

Turn gaps, conflicts and vague points into questions in time

Each conflict, gap and vague point in the record is either settled from the documents or turned into a clarification question, and the buyer's question deadline decides when. For conflicts, start with the order-of-precedence clause where the pack has one, since it says which document governs when two disagree. If it settles the conflict, note the governing clause on the matrix line. If it doesn't, or if following it would change your solution or price, ask.

Vague points earn a question when a precise answer would favour you. Typical cases include a volume given as a range, a service level without a measurement period, or a scope boundary that could include work you'd price separately. The buyer's answer sets the ground for every bidder, so a well-placed question can move it your way. Wording clarification questions so the answers change the bid is a skill in itself.

Whatever the rules, the deadline for questions sits in the pack, and the analysis has to reach it with time to spare. Send each question as soon as the analysis finds it.

Send contract terms to legal and pricing to the commercial lead

Legal gets the contract terms, each with its clause reference, as soon as the deal-breaker read flags them, not when the draft response is ready. Send liability and indemnity, payment terms, intellectual property, insurance and key personnel commitments. Ask for an answer the bid/no-bid call can use, whether that's acceptable, acceptable subject to a clarification, or a risk to weigh. The clause reference lets legal read each term in context and lets you put the answer back on the right line.

The commercial lead gets the pricing schedule and every requirement that drives cost, from volumes and service levels with penalties to payment milestones and indexation. Their read shows whether the commercial model can be priced at a margin the business accepts. It also shows which clarification questions would change the price.

In the example, the draft contract reaches legal on the first day with its flagged clauses listed. The pricing schedule goes to the commercial lead with the addendum's changed service level marked, since a different service level can move the price. Both answers come back to the record before the bid/no-bid call, so the call weighs them rather than hearing about them afterwards.

Hand a traced record to the bid/no-bid call and the plan

Hand the bid/no-bid call a record built for it. In APMP's ecosystem, that decision comes before RFP Review, in the pre-bid stage, so the analysis confirms or reverses a call already taken on less information. The record holds the compliance matrix, the criteria and weights, and a dated plan worked back from submission with the question deadline in it. It adds the risks from legal and the commercial lead, and the open clarification questions. Every item carries its file and clause, so anyone in the room can check a risk against the text instead of taking it on trust.

The same record becomes the response plan. Matrix lines become the sections to assign, weights set where the effort goes, and dates set the reviews. Take the bid/no-bid call on it, and write the tender summary report for management from it rather than from a fresh read of the pack.

How SEQUESTO runs RFP analysis

In SEQUESTO's agentic operating system (aOS), the five-file pack becomes one project. Agent Force, the specialist agents, extracts the requirements, evaluation criteria, evidence requests, mandatory attachments and word and character limits from every file. Each item is written in the team's own template. Every row of every tab in a spreadsheet such as the pricing schedule is read, and unclear rows come back for review instead of being guessed.

James, SEQUESTO's AI bid agent, reads the pack like an experienced bid manager and flags which requirements depend on one another. He lists deviations between the draft contract and the team's standard position for legal review. He also spots vague points where a precise answer would favour the team and suggests clarification questions.

Agent Force puts every dated requirement into a task list from day one. James adds the team's sign-off stages, financial verification points and review gates as milestones, each with a time and a named reviewer. He assigns questions or sections to named colleagues, who are notified in SEQUESTO.

James then writes the bid/no-bid brief from the whole pack, checked against the company's references, certificates and past bids and following the team's own workflow. The brief sets out which requirements the company clearly meets, where it's weak and what the risks are. The team takes the decision and records it on the bid. Every action that led there is on record for the bid manager to check before signing off the plan.

RFP analysis checklist before the bid/no-bid call

Tick each line before the bid/no-bid meeting.

• Eligibility, pass/fail items, the draft contract, the pricing schedule and every addendum have been read for deal-breakers, and each one found is recorded with its file and clause.
• Every requirement, evidence request, attachment, word limit and date sits in the compliance matrix with its file and clause, and conflicts and dependent requirements are marked.
• Each award criterion and its weight is recorded with its clause, and each planned claim has been tested against the marking scheme.
• Every conflict has its governing clause noted or a clarification question sent before the question deadline.
• Legal has answered each flagged contract clause, and the commercial lead has answered the pricing schedule, with each answer on its matching line.
• The hand-off record holds the matrix, criteria and weights, dated plan, risks and open questions, and every item points to its source.

Any line you can't tick goes to the meeting as an open risk, with its file and clause.