How to respond to an RFP

Get the issuer's own document

Start by downloading the complete package from the issuer's own procurement portal — not a bid-matching service summary, not a PDF a colleague forwarded, not the two-paragraph abstract that showed up in an alert email. Those secondary sources are written to help you decide whether to look. They are not written to be complied with, and they routinely drop the attachments where the binding requirements live.

The complete package is usually more than one file:

• The base solicitation document, including the instructions to responders and the evaluation section.
• Every exhibit and attachment, including the ones that arrive as scanned images rather than searchable text.
• The sample contract or agreement the winner will be asked to sign.
• The pricing form or workbook, in the exact file format the issuer published it in.
• Every addendum issued after release, including any issued the morning the response is due.

Register in the portal in your own company's name. On most systems, being a registered plan holder is the only thing that puts you on the notification list for addenda. If you obtained the solicitation second-hand, you are not on that list, and the addendum that moves the due date or changes the page cap will be published to everyone except you. Registration takes a few minutes and removes an entire category of failure.

Then find the order-of-precedence clause. Most solicitations contain one, and it tells you which document controls when two of them conflict — typically the latest addendum first, then the base solicitation, then the attachments. You will need it, because conflicts are normal rather than exceptional in a document assembled by several departments.

Read the sample contract now, at the start, while declining to bid is still free. Insurance limits, indemnification, liquidated damages, payment timing and termination-for-convenience language are all easier to evaluate before you have spent three weeks writing.

Diary the question deadline before the due date

Every competitive solicitation has at least two dates. The one everybody writes down is the submission deadline. The one that actually determines the quality of your response is the question deadline — the last day the issuer will accept written questions — and it usually falls weeks earlier.

It binds harder than the due date for four mechanical reasons:

• Ambiguity transfers to you when it closes. Before the deadline, an unclear requirement is the issuer's problem to clarify. After it, the same ambiguity is your problem to price, defend and live with for the term of the contract.
• The answers become binding. Issuers publish responses as an addendum, and that addendum is itself a compliance obligation — you normally have to acknowledge it on a form. Answers regularly change scope, quantities, deadlines and caps.
• It is the only sanctioned route to a change. If a specification is impossible, a qualification is unnecessarily narrow, or a form contradicts the instructions, the question window is the one moment when raising it can fix the document rather than merely annoy the buyer.
• A no-contact rule usually follows it. Many solicitations forbid contact with anyone other than the named procurement officer during the open period, and some make improper contact grounds for disqualification. Once the window shuts, you often cannot ask at all.

How to actually use the window

Read the entire document within forty-eight hours of downloading it, on a first pass whose only purpose is to find things you cannot comply with, cannot price, or do not understand. That pass is not drafting. It is a hunt for problems while problems are still solvable.

File in the format demanded. Solicitations frequently specify a form, an email address, a subject line, or a portal module, and questions sent any other way are simply not answered. Number your questions, and anchor each one to the section it concerns by quoting the language: "Section IV.B.3 requires… Please confirm whether…" An unanchored question gets an unhelpful answer, because the person drafting the reply has to guess what you meant.

File early enough that a follow-up is possible. A question submitted an hour before the window closes gets one answer and no chance to clarify it. Read every other responder's published question too — the answers apply to you whether or not you asked, and they are often the clearest statement of what the issuer actually wants.

Finally, never assume the original due date holds. An addendum can move it in either direction, and the version of the date in your calendar is not authoritative — the version in the latest addendum is.

Make the bid decision honestly

The bid decision is the highest-leverage moment in the whole process, and it is almost always made emotionally — by whoever is most excited about the opportunity, in a meeting where nobody has yet read Section III. Make it on paper instead, against these:

Mandatory minimum qualifications

Read them literally, then read them again looking for the qualifiers. "Five years of continuous operation of a comparable facility" means five, means continuous, and means comparable as that document defines comparable. A buyer generally has no authority to waive a published minimum for one responder, because doing so hands that responder an advantage nobody else was offered and gives every competitor grounds to protest. Eligibility is not something persuasive writing creates.

The incumbent

Find out whether there is one, how long they have held it, and whether the scope reads like a description of how they already operate. An incumbent is not a reason to walk away, but it changes what you have to do: you are no longer arguing that you are competent, you are arguing that a transition is worth the disruption. If you cannot articulate that argument in two sentences, you are bidding to make up the numbers.

The contract vehicle

Confirm the procurement is actually open to you. Some are restricted to a cooperative purchasing schedule, a pre-qualified pool, a specific licence, or a certification — small-business, minority- or women-owned, disadvantaged-business, veteran status — that has to be granted by a certifying body on its own timeline. Certifications take months. Being on the wrong side of a vehicle is a hard stop no amount of effort closes before Friday.

Bonding, insurance and financial capacity

Note the bid bond percentage, the performance and payment bond requirements, the insurance limits and the required additional-insured wording. Then call your surety and your broker before you commit, not after. Underwriting runs on someone else's calendar. If the limits cannot be issued in the time available, that is a no-bid regardless of how well you would perform the work.

Realistic capacity

Ask the uncomfortable version of the question: if we win this at the price we would have to bid to win it, can we staff it, mobilise it on the required date, and perform it without damaging the contracts we already hold? A win you cannot perform costs more than a loss — it costs the performance bond, the relationship and the past-performance reference you will need next time.

Write the no-bid reason down. It stops the same solicitation being re-litigated at eleven at night, and it tells you what to fix so the next one of these is a yes.

The instrument matters here too. A best-value RFP rewards a strong narrative; a low-bid ITB does not read one at all. If you are not sure which you are holding, the comparison of RFPs, RFQs and ITBs sets out the three clauses that tell you.

Build the compliance matrix

Before a single sentence of narrative is drafted, walk the solicitation front to back and give every requirement its own row: the issuer's own identifier, the requirement quoted verbatim, whether it is a pass/fail gate or a scored criterion, where in your response it will be satisfied, who owns it, its status, and what evidence proves it.

Doing this first is not administrative overhead. The matrix is the outline. Once it exists, the response has a defined shape, every writer knows exactly what they are answering and where it goes, and you have converted a sixty-page document into a finite list of obligations that can be counted and closed.

Requirements hide outside the requirements section. Instructions to responders contain gates. The sample contract contains gates. The pricing form contains gates. Addenda add and delete them. A matrix built only from the section labelled "Scope of Work" will be missing most of the things that actually disqualify people.

The full column-by-column construction, a worked example, and the rule that keeps it honest are in the companion guide: how to build an RFP compliance matrix.

Assign one owner per requirement

One named person per row. Not a department, not "operations", not two people who will sort it out between them. A requirement owned by a team is owned by nobody, and it will be discovered unowned on the last day by the person doing the final read.

Then set internal dates backwards from the submission deadline, with real slack in them:

• Content lock — narrative stops changing; only corrections after this.
• Forms lock — every form executed, notarised and scanned.
• Pricing lock — the number is final and the workbook foots.
• Render and assemble — produce the actual files that will be uploaded.
• Verification day — the gate check, run against those files.
• Submission — with at least a full business day of margin.

Pricing always arrives last and always slips, so build the schedule assuming it will. The two dependencies people consistently forget are both calendar problems rather than writing problems: the person with signature authority has to be physically available to sign, and a notary has to be booked. Both are discovered on the final afternoon by teams who did everything else well.

Write to the evaluation criteria, in the issuer's order and vocabulary

Somewhere in the solicitation is a section that says how the response will be scored, and usually how the points are distributed. That section is the specification for your document. Structure the response so that an evaluator working down their scoring sheet finds each criterion in the order they expect it, under a heading that uses their words.

If the issuer calls it the Operational Plan, call it the Operational Plan — not "How We Work". If a paragraph asks five sub-questions, answer five, in that order, numbered to match. If the criteria are weighted, let the page count follow the weight: a criterion worth thirty points and a criterion worth five should not receive the same three pages.

This is not a stylistic preference. An evaluator with a stack of responses and a rubric is searching for a specific answer against a specific line, frequently under time pressure and often scoring alone. Content they have to hunt for scores lower than identical content placed where they expected it, and the difference is not malice — it is that a scorer can only award points for what they found.

Answer the question that was asked

The most common defect in an otherwise strong proposal is a paragraph that answers an adjacent question the writer preferred. If the requirement asks how you will handle a same-day equipment failure, describe what happens in the first hour, who is called, what the replacement is, and how long it takes — not your general commitment to reliability.

Specificity is what separates a top score from a middling one: names, headcounts, frequencies, response times, equipment models, escalation paths, schedules that can be checked. Marketing copy pasted from a capability statement reads as an absence of an answer, because it is one.

Where the solicitation requires a cross-reference table mapping requirements to page numbers, fill it from the matrix rather than by hand. And where you are permitted to include material that is not requested, be honest about whether it earns its space. Uncapped, unscored content dilutes the scored content it sits next to.

Assemble the forms package

The forms package is where good responses die. It is unglamorous, it is delegated late, and it carries a disproportionate share of the hard gates. Treat it as its own workstream with its own owner and its own lock date, running in parallel with the narrative rather than after it.

What is typically in it:

• The signature or proposal submittal form, executed by an authorised officer.
• The addenda acknowledgement form, listing every addendum by number.
• A non-collusion or non-conflict affidavit, frequently requiring a notary.
• A W-9, and vendor registration with the issuer if it is separate from the bid.
• A certificate of insurance carrying the required limits and additional-insured wording.
• A bid bond or other bid security, in the required form and percentage.
• References, on the issuer's template rather than yours.
• Jurisdiction-specific certifications — drug-free workplace, public entity crimes, scrutinised-company or lobbying disclosures, E-Verify attestations.
• Subcontractor, participation-goal or local-preference forms where those programmes apply.

Use their form, unmodified. Do not retype it into your own letterhead, do not reformat it to fit, do not delete a clause you find objectionable. A retyped form is not the form, and altering a sworn statement can invalidate it outright.

Fill every blank. An explicit "N/A" beats an empty box, because a blank is indistinguishable from an oversight while an "N/A" is visibly a decision someone made.

Get the signatory right. The person signing must have authority to bind the company, and the company named must be the exact registered legal entity — matching your state registration and your W-9, not a trading name. Some issuers additionally require a corporate resolution or secretary's certificate evidencing that authority. Check whether an electronic signature is accepted or an original wet signature must be delivered; the two have very different lead times.

Verify the hard gates against the rendered file

Separate the pass/fail list from the scored list and verify the pass/fail list mechanically — against the exact file that will be uploaded, not against the working draft. Drafts and rendered output disagree constantly: a document that is thirty pages in a word processor becomes thirty-one when the fonts embed, the tables reflow, or the cover is added by whoever assembles the package.

Run the check on the artefact:

• Page count, and what the cap counts. Read the cap language precisely. Does it exclude the cover, the table of contents, tab dividers, résumés, required forms, the pricing volume? Each exclusion is a different number.
• Font size, line spacing and margins as specified, in the rendered PDF.
• Tabs and section labels present, in the required order, named the way the solicitation names them.
• File naming convention, file format, and per-file size limits.
• Volume separation — pricing is very often required to be a separate sealed file or envelope so technical scoring happens blind to price. Combining them is fatal and easy to do by accident.
• Number of copies, and whether an original wet-signed set must be physically delivered even for an electronic submission.
• Envelope or label wording for anything hand-delivered: solicitation number, title, opening date, responder name, exactly as prescribed.

Make the check able to fail. A verification step that produces a warning is a verification step people learn to scroll past under deadline pressure; one that stops the process is one they cannot. In our own production the page cap is enforced by a check that exits non-zero and fails the build rather than printing a caution — the detail is in the production method.

The other half of verification is the matrix itself. Every row reconciles: how many requirements exist, how many are verified against evidence, how many are not. If those numbers do not add up, the response is not finished, however good the prose is.

Submit early enough to survive a portal failure

The submission is a technical event, and technical events fail. Procurement portals reject uploads for file-size limits, time out on large files over ordinary connections, expire sessions mid-upload, demand fields nobody knew were required, and — the classic — accept every file successfully while leaving a final submit step unclicked, so the response sits in a draft state at the deadline.

Most systems lock at the stated second, on the issuer's clock rather than yours. "Received by 2:00 PM" is not "sent by 2:00 PM", and an upload that begins at 1:58 and completes at 2:00:41 is late. Lateness in competitive procurement is normally a flat bar rather than a deduction, because a buyer who accepts one late response has given that responder extra time nobody else received.

So: submit a full business day early where the portal permits it. Then verify the submission:

• Log back in as a separate action and confirm the status reads submitted, not draft.
• Check the file list shows every file, with the sizes you expect.
• Save the confirmation number, the confirmation email and a screenshot with a visible timestamp.
• Check the portal once more on the morning of the deadline for a late addendum.

For hand-delivered or couriered responses, the clock is where the document is received — a specific department, a specific room, sometimes a specific counter — not when you arrived at the building. Large public buildings have security queues, freight elevators and mailrooms that route internal deliveries on their own schedule. Deliver to the named office, get the receipt time-stamped, and keep it.