How to Read an RFP Before You Waste a Week on It

An RFP is designed to be read by someone whose full-time job is reading RFPs. You probably do not have that job. So the first skill is not writing a proposal — it is deciding in twenty minutes whether to write one at all.

Here is the screen, in order.

Deadline, method, and the hard gates

Find four things before you read a word of the scope:

• The due date, time, and time zone.
• How it is submitted. If it is a portal you do not have an account for, start that registration today — approval can take days.
• Mandatory pre-bid meeting? If attendance is required and it already happened, you are done. Close the tab.
• Insurance and bonding limits. If a performance bond is required and you have no bonding capacity, you are done.

Roughly a third of the opportunities that look promising die right here, and it costs you four minutes to find out.

The evaluation criteria tell you whether you can win

Almost every public solicitation publishes how it will be scored. That table is the most useful page in the document, and most bidders skim it.

If price is sixty percent and you are a boutique provider, you are bidding against volume shops and you will lose unless something else differentiates you sharply. If technical approach and qualifications together outweigh price, a smaller firm with a specific method has a real path. Read the weighting first and decide against it honestly rather than optimistically.

Scope: what are they actually buying?

Read the scope of work twice. The first pass is for whether you can do it. The second pass is for what is hiding in it:

• Deliverables listed in a sentence that would take a month each
• Travel with no reimbursement clause
• Reporting requirements that add unbilled hours every month
• "Other duties as assigned" attached to a fixed price
• Quantities described as estimated with no minimum guaranteed

None of these are automatic disqualifiers. All of them belong in your price.

Signals that the outcome is already decided

It is legal and normal for an agency to write requirements around what has worked. It is still worth knowing when you are the backup quote:

• A brand-name platform requirement with no "or equivalent"
• Experience thresholds that are oddly precise — seven years in a niche where three would be substantial
• A very short response window on a complex scope
• A previous contract for the same scope, ending, with a familiar vendor name in the public award history

One of those is nothing. Three of them is a pattern. You can still bid to be known — that is a legitimate strategy — but bid the cheap version of your effort, not the four-day version.

The forms checklist is where good bids die

Find the required documents list and copy it into your own checklist immediately. Typical contents: signed addenda acknowledgements, conflict of interest disclosure, felony conviction notice, vendor forms, W-9, insurance certificate, references, and a signature page that must be signed by an authorized representative.

Two rules that will save you a submission:

Acknowledge every addendum, including the ones that only changed a date. And check the portal for new addenda the morning you submit, not the week before.

Then do the arithmetic

Before you commit, estimate three numbers: hours to write the proposal, hours to perform the work if you win, and the revenue at your real price. If a forty-hour proposal chases a contract worth eight thousand dollars, that is a bad trade unless it opens a door you want and cannot open another way.

Write the decision down, with the reason. Six months later, a file of your own no-bid notes becomes the most accurate picture of your market that you will ever have.

If it is a go

Build the compliance matrix first — every requirement in the solicitation, in a table, with where in your response you answer it. It sounds bureaucratic and it is the single habit that most improves scores, because evaluators score what they can find. If they cannot find it, you did not say it.

Then write the proposal in this order: scope response, staffing and qualifications, past performance, price. Price last, always, so that it reflects the work you just described instead of a guess you made on Monday.

Questions people ask

How do I know if an RFP is wired for an incumbent?
Look for requirements only one company could meet — a named software platform, an unusually specific number of years in a narrow niche, or a mandatory site visit scheduled two days out. None of these prove anything on their own, but three together usually mean the outcome is already shaped.

Is it worth bidding if I have no past performance in that exact area?
Sometimes. Read how experience is weighted. If past performance is thirty percent of the score and the rest is approach and price, adjacent experience described honestly can compete. If it is a pass or fail requirement, it is a no-bid.

Should I ask questions during the question period?
Yes, and ask them early. Questions and answers are published to every bidder, so ask about anything ambiguous in the scope or the forms. Never ask a question that reveals your pricing strategy.

What is a reasonable win rate?
For a small firm bidding selectively, one in four to one in six is healthy. If you are winning almost everything, you are probably priced too low. If you never win, you are likely bidding on the wrong work rather than writing it badly.