The RFP Looks Like a Good Job. Then You Read the Fine Print.

The scope looks like work his crew can handle, so he starts pricing. He calls suppliers, checks labor, sends questions to a subcontractor, and spends half a day building the number.

Then he finds it. Payment depends on the owner paying first. There is a daily penalty if the job runs late. The bid requires a bond he does not have lined up. There was a mandatory site walk two days ago.

At that point, the problem is not just the clause. The problem is that he found it too late.

That is how RFPs waste time. Not because contractors do not know their trade, but because the risky parts are often buried in legal terms, attachments, addenda, and submission instructions instead of sitting next to the scope of work.

A job can look profitable and still be a cash-flow problem. That usually starts with payment language.

If the RFP or contract says you get paid only after someone else gets paid, you may be carrying labor, materials, payroll, equipment, and supplier costs while waiting on money outside your control.

That matters more for small contractors than it does for large companies with deep cash reserves.

Words like paid when paid, paid if paid, payment contingent on owner payment, retainage held until final acceptance, or reimbursement subject to agency approval should slow you down.

The question is not only, Can we do the work? It is also, Can we afford to float this job if payment slows down?

Liquidated damages sound like legal language, but they are really a pricing issue.

If the contract charges $500, $1,000, or more for every day past the completion date, the schedule becomes part of the risk calculation.

That does not automatically mean you should walk away. It does mean you need to know what you are agreeing to.

The danger is when strict penalties are paired with things you do not fully control: long-lead equipment, owner approvals, delayed access, other trades, weather, phased work, or occupied-building restrictions.

A tight schedule is one thing. A tight schedule with daily penalties and unclear delay protection is something else.

Some bids are lost before the estimate is even finished.

A mandatory pre-bid meeting or site walk is a good example. If the RFP says attendance is required and you miss it, your number may never be considered.

This is frustrating because it has nothing to do with whether you can do the work. It is a compliance problem.

The words to watch for are simple: mandatory, required, must attend, only attendees may bid, failure to attend will result in rejection.

When you first open an RFP, the meeting dates deserve the same attention as the bid due date.

Addenda are where projects move after the RFP is issued.

They can change drawings, specs, bid dates, wage requirements, alternates, product requirements, and submission forms. Sometimes they answer a question. Sometimes they change the price.

The mistake is treating addenda like paperwork.

Before submitting, you need to know whether every addendum has been reviewed, whether it changed your price, and whether the bid form requires you to acknowledge it.

A missed addendum can make a bid nonresponsive even when the price is good.

Insurance and bonding requirements can decide whether you are eligible to bid.

If the RFP requires coverage you do not carry, endorsements you have not priced, or a bond you cannot get in time, that is not a minor detail. It affects the go/no-go decision.

This is where contractors should slow down early.

General liability, workers' comp, commercial auto, umbrella coverage, professional liability, pollution coverage, additional insured language, waiver of subrogation, bid bonds, performance bonds, and payment bonds all need to be checked before the bid is nearly done.

If you need your broker or bonding agent involved, bring them in before the deadline pressure hits.

Not every risk is legal. Some risk is hidden in vague scope.

Who handles demolition? Who pulls permits? Who owns temporary utilities? Is after-hours work required? Are substitutions allowed? Are closeout documents included? Who is responsible for testing, startup, training, restoration, or cleanup?

These details can look small until they become your cost.

A vague scope does not always mean you should skip the job. But it does mean you should either ask a question before the RFI deadline or price the uncertainty on purpose.

Guessing is not a strategy.

The final trap is the simplest one: submitting the bid wrong.

Wrong form. Missing signature. No bid bond. Late upload. Wrong portal. Missing references. Addendum not acknowledged. Envelope labeled incorrectly. Required certification left blank.

Owners do reject bids for this.

That is why the submission instructions deserve their own review, separate from the estimate. The number can be right and the bid can still fail.

Most contractors start with scope. That is natural. Scope tells you whether the work fits your crew.

But before you go deep on pricing, it helps to do a fast risk pass.

Can you meet the mandatory requirements? Did you miss any meetings or site walks? Are there payment terms that could hurt cash flow? Are there schedule penalties? Do you have the insurance, bonding, licenses, and certifications? Have all addenda been reviewed? Is the submission package clear? Is the scope clear enough to price?

If the answer is yes, keep going. If the answer is no, pause before you spend the next six hours building a number.

The point is not to avoid every RFP with tough terms. Good contractors take on hard jobs all the time.

The point is to know what you are agreeing to before you bid.

Before you price the job, review the terms that can change the bid.