Winning work
How to Write an RFP Response That Scores
An RFP response that scores is one built around the client’s evaluation criteria, in their order and words, with proof beside every claim. Evaluators score with a grid beside them, and the response that wins makes every point easy to find.
On this page
Terms Used
- RFP: a request for proposal, in which the client publishes the work, the evaluation criteria and the rules for responding.
- Evaluation criteria: the headings the response is scored against, each with its weight.
- Mandatory requirements: forms, limits and documents a response must include to be scored at all.
- Debrief: the client’s explanation, after the award, of how a response scored.
Write for the Person Scoring It
An RFP response for engineering work is usually marked by a panel. Each evaluator reads it with a scoring grid beside them, often on their own, and scores each criterion against its published weight. The response that wins is the one that makes every point easy to find and easy to award.
That changes how to write it. The evaluator is not reading for pleasure or for the firm’s story; they are looking for the answer to each criterion, in the place the grid says it should be, with proof they can point to when the panel compares scores.
Before Writing
- Decide whether to bid. See the go/no-go decision.
- Read the evaluation criteria twice. List every criterion and sub-criterion with its weight. This list becomes the outline.
- List every mandatory requirement. Forms, page limits, font sizes, insurance certificates, signed addenda. A missing form can disqualify a strong response.
- Ask questions early. Within the question period, in writing. The answers can show what the client cares about.
- Name the team before writing. The people the response names decide what the experience and approach sections can say.
Build the Outline from the Grid
Use the RFP’s own section names and numbers, in its order. For example, if the criteria are “Understanding of the project (15), Approach and methodology (30), Team (25), Relevant experience (20), Schedule (10)”, the response has those five headings, in that order, with roughly that share of the pages. An evaluator looking for the schedule should find it under “Schedule”, not inside the approach.
| Example: criterion and weight | Share of a 20-page limit | What evaluators usually look for |
|---|---|---|
| Understanding (15) | 3 pages | The client’s goals, constraints and risks, in their terms |
| Approach (30) | 6 pages | The work phase by phase, the risks and how each is handled |
| Team (25) | 5 pages | Named people, their roles here, their similar projects |
| Experience (20) | 4 pages | Three close matches, with references |
| Schedule (10) | 2 pages | Dates that fit, review periods, dependencies |
Section by Section
Understanding
Show you understand this project: its purpose, its constraints, the risks the client worries about, and anything you learned from a site visit or the documents. Avoid restating the RFP back to the client; an evaluator scores what you add to it.
Approach
Explain how you will do the work, phase by phase, and why that way. Name the risks and how you will handle each. Specific beats general: “we will survey the existing structure in the first two weeks, before the layout is fixed” scores better than “we take a thorough approach”.
Team
Name the people who will do the work, their role on this project and their relevant experience. Keep résumés short and focused on similar projects. Evaluators often check that the people named in the proposal are the ones who show up.
Experience
Choose the projects most like this one, and for each say the client, the scope, your firm’s role, the outcome and a reference. Three close matches score better than ten loose ones.
Schedule
A schedule that fits the client’s dates, shows the review periods and names what it depends on. A date the firm can’t meet scores now and costs later, in past performance ratings.
Show, Then Claim
Every claim in a response needs proof the evaluator can point to. For example, “experienced in culvert replacement” earns little; “twelve culvert replacements for three municipalities since 2020, the last two delivered ahead of schedule” is the kind of line evaluators can score, if it is true and the projects are listed. Put the proof next to the claim, not in an appendix the evaluator has to search. And never claim what the firm can’t show: a panel that finds one inflated line marks down the rest.
Make It Easy to Score
- Put the key point first in each section, then the proof.
- Use the client’s words for their project, and their numbering for the criteria.
- Short paragraphs, clear headings, tables where a comparison helps.
- Answer every criterion, even ones that seem minor. Unanswered criteria score zero.
- Keep within the page limit; pages past it may not be read at all.
Price
Where price is scored, its weight tells you how much it can move the total. Where the fee is negotiated after selection, the technical score is everything. We explain both, with a worked score, in qualifications-based selection.
A Final Check Before It Goes
- Every mandatory form, signature and addendum is in.
- Every criterion has its heading, in the RFP’s order and words.
- The page count, font size and file format meet the rules.
- Every name, project, figure and date is right for this client.
- Someone who didn’t write it has scored it against the grid.
- It is submitted before the deadline, with time to spare for an upload that fails.
After the Result
Ask for a debrief, win or lose. Public RFPs often say how to request one. Note your score by criterion against the winner’s where they share it, and keep the notes with the response. The next proposal to the same client starts from them, and your win rate tracks whether it worked.
Keep a Library
Much of each response repeats from the last: résumés, project sheets, firm descriptions, standard approaches. Keep them current in one place, so each response starts from a draft and the time goes to the understanding and the approach, the parts that win. Our article on using AI to write proposals covers how the library becomes a first draft.
Common RFP Mistakes
- Writing the firm’s story instead of answering the criteria. The grid has no box for history.
- Missing a mandatory form. The best response isn’t scored if it isn’t compliant.
- Generic approach text. An approach that would fit any project scores like it.
- Naming the A team and staffing the B team. Evaluators and past performance ratings remember.
- No debrief. Without it, the next response repeats the same weak section.
How We Approach This
We build proposal templates, project sheets and résumés your team reuses through our marketing work, and first drafts assembled from your past work through our software work, for your engineers to check.
Questions
How Do You Write a Winning RFP Response?
Build it around the evaluation criteria, in the RFP’s order and words, answer every criterion with proof, meet every mandatory requirement, and have someone who didn’t write it score it against the grid.
How Long Should Each Section Be?
In proportion to its weight, within the page limit. For example, a criterion worth 30 of 100 points gets about 6 of 20 pages (20 × 0.3).
What Do Evaluators Look for in the Team Section?
Named people, their role on this project and their similar projects, and confidence that those people will do the work.
What Makes an Approach Section Score Well?
Specifics: the work phase by phase, the risks named with how each is handled, and why this approach suits this project.
Should You Ask for a Debrief?
Yes, win or lose. The scores by criterion show which section to strengthen next time.
Updates
- : Rewritten at full length: the evaluator’s view, an outline table from the grid, proof beside every claim, a final check, the library and common mistakes.