The RFP lands on a Tuesday. It has a 40-page specification, a pricing schedule in Excel, a questionnaire with word limits, and a scoring table near the back that nobody on your team has read yet. The temptation is to open a blank document and start writing about the company. That is usually where the marks start leaking.
An RFP response is not read the way a brochure is read. It is marked, question by question, by someone holding a scoring guide. If they cannot find the answer, or cannot match it to the criterion, it does not matter how good the work behind it is. Structure is how you make the answer findable, checkable and scorable.
This guide sets out a structure that follows how evaluators work, from the compliance check through to the final read. It applies to formal RFPs, public sector tenders, and the commercial requests for proposal that arrive from larger private buyers.
Start With How the Response Will Be Marked
Before you plan a single heading, find out how the buyer intends to score. Most RFPs say this somewhere, though not always in the same place. Look for an evaluation section, a scoring matrix, an instructions-to-bidders document, or weightings shown beside each question.
You are looking for four things:
- Pass or fail items. Mandatory documents, minimum insurance levels, accreditations, financial thresholds. Miss one and the rest of the response may not be read.
- Weightings. How the marks split between quality, price and any social value or sustainability element.
- The scoring scale. What separates a mid score from a top score. Buyers often describe the top band in terms like full confidence, specific evidence and no gaps.
- Format rules. Word or page limits, font requirements, whether attachments are allowed, and which template must be used.
Write the scoring scale out and keep it next to you while drafting. If the top band says the answer must be supported by relevant evidence, every top-scoring answer needs evidence the evaluator can see, not a statement that evidence exists.
Practical rule: If you cannot say which criterion an answer is earning marks against, the evaluator will not be able to either.
Our guide to tender evaluation criteria and scoring goes further into reading scoring guides. For structure, the point is simple: the buyer has already told you what the marking sheet looks like. Build the response to match it.
Build a Compliance Matrix Before You Write
The compliance matrix is the spine of the response. It is a working table, not something you submit unless the buyer asks for it. It lists every requirement in the RFP and shows where your response meets it.
| Column | What goes in it | Why it matters |
|---|---|---|
| Reference | The buyer's question or clause number | Lets you mirror their numbering exactly |
| Requirement | The requirement in the buyer's words | Stops the team paraphrasing it into something easier |
| Type | Pass or fail, scored, or information only | Tells you where effort earns marks |
| Weighting and limit | Marks available and word or page limit | Sets how long the answer should be |
| Owner | The person who drafts or supplies evidence | Gives each answer a name, not a team |
| Evidence | The case study, policy or certificate that supports it | Shows gaps before drafting starts |
| Status | Not started, drafted, reviewed, approved | Tracks progress against the deadline |
Read the whole pack when you build it, not just the questionnaire. Requirements hide in the specification, the terms and conditions, the pricing schedule and clarification notices. A specification clause that says the supplier shall provide monthly reporting is a requirement even if no question asks about reporting directly. The answer that covers service management should mention it.
The evidence column does a second job. If a scored question has nothing in that column, you have found a weakness before you have written a word. That is useful information for the bid decision as well as the draft. A question worth a large share of the quality marks with no relevant case study behind it is a reason to think hard about whether to bid.
The Overall Shape of the Response
Where the buyer supplies a template, use it and do not reorganise it. Evaluators are often marking several responses side by side, and moving sections around makes yours the slow one to mark. Where there is no template, a dependable shape looks like this:
- Cover letter. Short. Who you are, what you are responding to, the named contact, and confirmation that you accept the terms or a pointer to any clarifications.
- Executive summary. One to two pages on what the buyer gets and why your approach fits their stated needs.
- Compliance and mandatory information. Company details, declarations, insurances, accreditations and anything pass or fail.
- Responses to scored questions. In the buyer's order, with the buyer's numbering, each answer standing on its own.
- Pricing. In the buyer's format, with assumptions stated.
- Appendices. Only if allowed, and only where each one is referenced from an answer.
Two principles sit under that shape. First, each scored answer must make sense if it is the only page the evaluator reads, because sometimes it is. Questions are often split between evaluators by subject, so the person marking your mobilisation answer may never see your executive summary. Second, do not make the evaluator search. If an answer depends on information elsewhere, repeat the key point briefly rather than writing see section 4.
How to Structure Each Answer
Most of the marks sit in the individual answers, so this is where structure pays most. A pattern that works across most question types:
1. Answer the question in the first two sentences
State what you will do, directly, using the buyer's own terms. If the question asks how you will maintain service during mobilisation, the opening should say how you will maintain service during mobilisation. Not a paragraph on your history, not your values, not your headcount.
Evaluators read the opening to decide what they are marking. A direct opening tells them they are in the right place and sets up everything that follows as support.
2. Break the question into its parts
Many RFP questions are several questions joined together. Describe your approach to quality management, including how you monitor performance, handle non-conformances and report to the client, is four questions. Use the buyer's own sub-points as subheadings or bold lead-ins, in the order they wrote them.
This does two things. It proves to the evaluator that every part has been covered, and it stops you writing three paragraphs on the part you find easiest and one line on the part that carries the marks.
3. Give the method, not the intention
Weak answers describe commitment. Strong answers describe mechanism. We are committed to high-quality reporting earns little. A named account manager sends a monthly report covering the agreed indicators, and any indicator below target triggers a review meeting within the reporting cycle is a method the evaluator can picture and score. Only write the second kind of sentence if it is true of how you actually work, because the buyer may hold you to it in the contract.
Useful questions to ask of every paragraph: who does it, how often, using what, and what happens when it goes wrong.
4. Prove it with evidence
Each scored answer needs at least one piece of evidence the evaluator can recognise. That might be a short case study, a named accreditation, a relevant policy, a role and its experience, or a process you already run for another client. Choose evidence that matches the buyer's situation as closely as you can: similar sector, similar scale, similar problem.
Keep case studies inside the answer short. Situation, what you did, what changed. Three or four sentences is often enough. Our guide on how to present case studies covers this in more depth.
5. Close on the benefit to the buyer
End with what the approach means for them, tied back to something they said in the specification. If the specification mentioned a previous problem with missed visits, close by connecting your scheduling method to that. One or two sentences. This is not a summary of what you just said.
| Part | Purpose | Common mistake |
|---|---|---|
| Direct opening | Tells the evaluator what is being marked | Opening with company history |
| Sub-point structure | Shows every part has been covered | Merging parts into one long paragraph |
| Method | Shows how the work actually happens | Describing intent and values instead |
| Evidence | Moves the score into the top bands | Claiming experience with nothing to show |
| Buyer benefit | Connects the answer to their stated need | Generic closing lines that fit any bid |
Using the Word Limit Well
Word limits are a signal of how much the buyer wants. A 250-word limit on a lightly weighted question and a 1,500-word limit on a heavily weighted one tell you where they expect detail. Use most of the limit on heavily weighted questions. Leaving half of it empty usually means leaving evidence out.
On the other hand, do not pad short answers to look thorough. Evaluators notice repetition, and every repeated sentence is one that could have carried a fact.
A rough way to allocate words in a long answer: a short opening, most of the space split across the buyer's sub-points in proportion to how much they matter, a slice for evidence, and a line or two to close. Check the instructions on whether headings, tables and diagrams count towards the limit. If the rules are unclear, ask a clarification question rather than guessing.
The Executive Summary
Some RFPs score the executive summary, many do not. Either way it shapes how the evaluator reads everything after it, so it deserves care. Write it last, once the answers exist, so it reflects what you actually said.
A useful structure:
- Their need, in their words. One short paragraph showing you understood the problem they described.
- Your approach in brief. The two or three things that matter most in how you would deliver.
- Why it fits. Relevant experience and evidence, briefly.
- What they get. The outcomes, tied to their stated priorities.
Leave out mission statements and long company histories. If your company background is relevant, it belongs where a question asks for it. Our tender executive summary guide has more detail.
Formatting That Helps the Evaluator
Formatting is not decoration. Its job is to let a tired evaluator find the scorable content quickly. The basics:
- Mirror the buyer's numbering. If they call it question 3.2(b), so do you.
- Repeat the question. Paste the full question above each answer unless the template does it for you.
- Use headings that match the sub-points. The evaluator can tick them off.
- Use tables for comparable information. Roles and responsibilities, timetables of activities, service levels.
- Bold sparingly. One key phrase per paragraph at most, or it stops meaning anything.
- Short paragraphs. Three or four sentences. Long blocks hide answers.
- Diagrams only if allowed and useful. A process flow can carry a lot, but check whether images count towards the limit or are permitted at all.
Use the buyer's terminology throughout. If they say service users, do not say customers. If they call it the contract manager, do not rename the role. Matching language makes it easier for the evaluator to map your answer onto their scoring guide.
Pricing Structure
Price responses fail on structure more often than on numbers. Use the buyer's pricing schedule exactly as supplied. Do not add columns, change formulas or submit your own format unless invited to. Complete every cell, even if the answer is zero or not applicable, so nothing looks missing.
State assumptions clearly where the format allows: what is included, what is excluded, how volumes were estimated, and how prices change if volumes change. Check that the price matches the quality answers. If your mobilisation answer describes a dedicated team, the price should include that team. Evaluators do compare the two, and an inconsistency is an easy reason to mark down or to question the bid.
Common Structural Failures
Most low scores come from a short list of problems:
- Answering the question you wanted. A reused answer to a similar question that misses what this buyer asked.
- Missing sub-parts. The question had four parts, the answer covered three.
- Claims without evidence. Experienced, proven and robust, with nothing behind them.
- Cross-references. See our response to 2.1, when the evaluator marking this question never saw 2.1.
- Generic content. Text that could be pasted into any bid for any buyer.
- Inconsistencies. Different team sizes, dates or names in different sections.
- Out-of-date evidence. An expired certificate, a case study naming someone who has left.
Reused content causes several of these at once. Reuse is sensible, because most RFPs ask variations of questions you have already answered. The risk is in pasting an old answer without adapting it to the new question, buyer and scoring criteria. Treat any reused answer as a starting point and rewrite the opening and the closing for this buyer at minimum.
Reviewing Against the Scoring Guide
Review is where structure gets tested. The most useful review is not a proofread. It is someone marking the answer the way the buyer will.
- Compliance pass. Using the matrix, check every requirement is met, every mandatory document is attached, every limit respected.
- Scoring pass. Give a reviewer who did not write the answer the question and the scoring guide. Ask them to score it and say what would move it up a band.
- Evidence pass. Check every factual claim against its source. Certificates in date, case studies accurate, named people still in post.
- Consistency pass. Names, numbers, dates and commitments match across all answers and the price.
- Final read and sign-off. A named person with authority approves the response before submission.
Leave enough time for the scoring pass to change things. A review the day before the deadline can only fix typing. A review with a few days to spare can fix a weak answer. Our bid review checklist sets out the checks in more detail.
RFP Software and Where It Fits
If you are reading this while comparing tools, the structure above is a good test for them. Software can help with two parts of the work: finding the right existing answer and evidence quickly, and producing a first draft to adapt. It cannot decide your approach, judge whether the evidence fits, or sign off what you commit to. The scoring pass and the sign-off stay with people.
The main difference between tools is where the answers come from. Enterprise RFP platforms such as Loopio are generally built around a content library that your team maintains by hand, sold on sales-led annual contracts. That suits bid teams of ten or more with a procurement budget. Bidwell takes a different route for small firms writing their own bids: it reads the bids, policies and case studies you have already written, turns them into a knowledge base of your own answers, and drafts each new response from it with the source document shown for every answer, so the evidence pass has something to check against. Our Bidwell and Loopio comparison sets out the differences, and the RFI and tender response pages show the workflow.
Whichever tool you look at, run a real RFP through it and check three things. Does each draft answer the question that was asked, or a similar one? Can you see where each claim came from? And does the output arrive in a format, such as Word or Excel, that lets you apply the buyer's template and numbering without rebuilding it?
A Working Checklist
Keep this alongside the compliance matrix for every RFP:
- Scoring guide, weightings and format rules found and written down.
- Compliance matrix built from the whole pack, including specification and clarifications.
- Every scored question has an owner and named evidence before drafting starts.
- Buyer template used, numbering mirrored, question repeated above each answer.
- Each answer opens with a direct answer, covers every sub-point in order, gives method and evidence, and closes on buyer benefit.
- Word limits used in proportion to weightings.
- No cross-references that leave an evaluator without the information.
- Pricing in the buyer's format, every cell complete, consistent with quality answers.
- Independent scoring review completed with time to act on it.
- Every claim checked against its source, and a named person signs off.
A well-structured RFP response is not cleverer writing. It is a response built to the buyer's marking sheet, where each answer can be found, understood and scored on its own. Get that right and the quality of your work has a fair chance of showing through.
