Writing an RFP response a procurement committee can score

Procurement committees rarely read a response from start to finish. They work through an evaluation sheet and look for the part of your response that answers each line. If they can’t find it quickly, you lose the marks, even if the answer is somewhere in your document.

Mirror their structure

Use the same headings and order as the request for proposals. If the RFP lists requirements R-01 to R-23, refer to them by number. Reviewers should never have to guess where you addressed something.

Include a compliance matrix

A compliance matrix is a table listing every requirement, whether you comply, and where in your response it is covered. It is the single most useful page for an evaluator and a quick way to check you haven’t missed anything.

Make the approach concrete

Describe the work as phases with activities, outputs and how you will check quality. Name tools and methods. A committee can score “weekly route optimisation using fleet telematics, reviewed by the operations lead” far more easily than “an innovative, data-driven approach”.

Show the schedule and the team

• A milestone schedule with week numbers and deliverables
• Named key people, their roles and relevant experience
• Two or three similar projects, with the client and the result

Price clearly

Give a pricing table that adds up, state VAT separately and propose a payment schedule linked to milestones. Make sure every number in the commercial proposal matches the rest of the response.

Try it free: 5 projects, no card. You only sign in with your email when you start.