Why bids are rejected

Responsive, responsible, and the difference

Public purchasing turns on two words that sound like synonyms and are not.

Responsiveness is about the submission. Does the document, as received, conform to the material requirements of the solicitation? It is judged on what is inside the envelope at the moment the envelope was received. That is why responsiveness generally cannot be cured after the deadline: curing it would mean changing the submission after other submissions are known.

Responsibility is about the bidder. Are you capable, financially sound, appropriately licensed, and not debarred? Because responsibility is a fact about you rather than about the paper, a buyer can normally investigate it after opening, ask for more information, and make a determination.

The practical consequence is asymmetric and worth internalising: a responsibility question usually generates a phone call, and a responsiveness failure usually generates a letter. Everything in this guide is a responsiveness failure.

One more distinction sits underneath it. Most public purchasing rules let a buyer waive a minor informality — a deviation that does not affect price, quantity, quality or delivery and does not give the bidder an advantage other bidders did not have. What a buyer cannot waive is a material deviation, because waiving it would change the terms one bidder competed on. The line between the two is drawn by the issuer's own purchasing rules and by the solicitation itself, so read both — and never plan around being forgiven. The discretion is theirs, not yours.

Late delivery

What it looks like. An upload that began at 1:58 and finished at 2:00:41 against a 2:00:00 deadline. A courier signature at the building's loading dock rather than at the Purchasing counter named in the solicitation. A portal session that expired during a large file transfer. A response emailed at 1:59 to an address that routes through a filter which timestamps on delivery rather than on send.

Why there is no discretion. The deadline is the mechanism that makes sealed competition fair. Every bidder had the same window; a buyer who accepts one response after it closed has given that bidder time nobody else received, and — critically — has done so at a moment when the number of competing responses, and sometimes their contents, are already known. Most purchasing rules therefore make lateness a flat bar with only narrow exceptions, typically confined to circumstances where the issuer itself caused the delay. Even a buyer who badly wants your response cannot usually take it, because every other bidder would have grounds to protest the award.

How to prevent it. Treat the stated time as the issuer's clock, not yours, and treat "received by" as meaning received. Submit a full business day early where the portal allows resubmission. Then confirm the submission separately: log back in, check the status reads submitted rather than draft, check the file list, and save the confirmation number and a timestamped screenshot. For physical delivery, deliver to the named office and get the receipt stamped there — large public buildings route internal mail on their own schedule, and the mailroom's clock is not the Purchasing counter's clock.

The wrong submission channel

What it looks like. Emailing a response that had to go through the e-procurement portal. Uploading to the correct portal but the wrong solicitation number. Hand-delivering to the City Clerk when the document named the Procurement Division. Submitting one combined PDF where separate sealed technical and pricing files were required. Sending a scanned printout where a native workbook was demanded.

Why there is no discretion. A response received outside the prescribed channel often was not "received" in the sense the rules mean. It was not in the sealed set that was opened at the appointed time, in front of whoever attends the opening. Admitting it afterwards means admitting a submission whose handling nobody can vouch for into a process whose entire legitimacy rests on all responses being treated identically. Where technical and price volumes must be separate, the reason is usually that scoring is required to happen blind to price — a combined file does not just break a formatting rule, it destroys the issuer's ability to run its own evaluation.

How to prevent it. Copy the submission instructions into the compliance matrix verbatim, including the address, the room number, the portal module and the file structure. If the portal permits it, do a dry run with a placeholder file days beforehand so you meet its quirks early rather than at the deadline. Confirm what "sealed" means for an electronic submission on that particular system. And if the instructions in one section contradict the instructions in another — which happens more often than it should — that is a question for the question window, not a judgement call for you to make alone.

Missing or unexecuted forms

What it looks like. A required form omitted entirely. A form present but unsigned. A signed affidavit with an empty notary block. A form retyped onto company letterhead because the original PDF would not fill. A form with a clause struck out because somebody objected to it. Blanks left blank.

Why there is no discretion. Many of these forms are not paperwork; they are sworn statements with independent legal effect — non-collusion affidavits, public entity crime declarations, drug-free workplace certifications, lobbying and conflict disclosures. An unexecuted affidavit is not an affidavit, and an unsworn version of a sworn statement gives the buyer nothing it can rely on. A retyped form is worse still: it is a document of your own drafting bearing a resemblance to theirs, and it is not the instrument the solicitation required. Where the form is the mechanism that binds you to the offer, its absence means there is nothing to accept.

How to prevent it. Run the forms package as its own workstream with its own owner and its own lock date, in parallel with the narrative rather than after it. Use their form, unmodified, in their file format. Fill every blank — an explicit "N/A" is visibly a decision, while an empty box is indistinguishable from an oversight. Book the notary as a calendar item the week you decide to bid, not the afternoon before submission. And build a forms row in the matrix for every single form, because "the forms" as one row is how three of them go missing.

No addendum acknowledgement

What it looks like. A response acknowledging Addenda 1 and 2 when three were issued. An acknowledgement form left blank because someone assumed acknowledging in the cover letter was equivalent. Most commonly of all: never receiving Addendum 3 at all, because the solicitation was forwarded by a colleague and the company was never registered as a plan holder in the issuer's portal.

Why there is no discretion. An addendum changes what everyone is bidding on. If Addendum 3 added a site, extended the term, changed a specification or moved a quantity, then a response that does not acknowledge it is a response to a different solicitation. The buyer has no way to determine from the document whether you priced the change or not — and guessing would mean either awarding on an unpriced scope or interrogating one bidder after opening. Where the addendum is material, acknowledgement is normally treated as non-waivable for exactly that reason.

How to prevent it. Register in the portal in your own company's name the day you download the solicitation; being on the notification list is the whole defence. Create one matrix row per addendum, plus a standing row for the acknowledgement form itself. Re-check the portal on the morning of submission — addenda land late, sometimes within twenty-four hours of the deadline, and an addendum you never opened is still binding. Acknowledge on their form, by number, in the place they ask for it, even if you have also mentioned it elsewhere.

Page and format violations

What it looks like. Thirty-one pages against a thirty-page cap. Ten-point type against an eleven-point minimum. Single spacing where one-and-a-half was specified. Narrowed margins to reclaim a page. Missing tabs, or tabs named differently from the way the solicitation names them. A file named however the assembler felt like naming it, against a prescribed convention. Volumes merged that were required to stay separate.

Why there is no discretion. Format rules are equalisers. A cap of thirty pages is a statement that every responder gets thirty pages to make their case, and a responder who used thirty-four — or used thirty at a smaller font and tighter margins — took space the others were denied. The advantage is small, but it is real, measurable and conferred by the deviation itself, which is the textbook definition of a deviation a buyer cannot waive. Tab and file-structure rules exist because the buyer's own process depends on them: volumes get split among committee members, price volumes go to a different reviewer, and a merged file can break the evaluation before it starts.

How to prevent it. Read the cap language precisely, because the number is meaningless without its exclusions — does the cap count the cover, the table of contents, tab dividers, résumés, forms, the pricing volume? Then verify against the rendered file that will actually be uploaded, not the working draft. Documents grow during assembly: fonts embed, tables reflow, a cover gets added. Render early enough that a cut is a considered edit rather than a panic. And make the check able to fail — a page count that produces a warning is a page count somebody will scroll past at eleven at night, which is why in our own production it exits non-zero and stops the build. That mechanism is described on the method page.

Unsigned, or the wrong signature authority

What it looks like. A proposal coordinator signing where an officer with authority to bind the company was required. A signature block naming a trading name rather than the registered legal entity. An entity name that does not match the W-9 or the state registration. A digital signature where an original wet signature had to be delivered. A corporate resolution demanded and not supplied. And, more often than anyone admits, a signature page that was printed, signed, and then not scanned back into the final file.

Why there is no discretion. The signature is what converts a document into an offer the buyer can accept. Unsigned, there is nothing to accept — the buyer would be awarding a contract to a party that has not committed to anything and could walk away without consequence. Where the signer lacked authority, the same problem exists in a subtler form: the buyer cannot tell whether the company is bound. And where the named entity does not match the registered one, the buyer cannot tell who it would be contracting with, which matters enormously the first time there is a claim.

How to prevent it. Identify the signatory in the first week and confirm their availability against the submission date, including any travel. Verify the exact legal name against your state registration and your W-9, character for character, including "LLC" versus "L.L.C." and any comma. Ask during the question window whether electronic signature is accepted if the document is silent — the answer changes your schedule by days. Then verify the signature exists in the rendered file, on the page, at the end, as part of the gate check.

Missing bid bond or insurance certificate

What it looks like. A bid bond at five per cent where ten was required. A bond issued by a surety that does not appear on the list the solicitation names. A certificate of insurance at limits below those specified. A certificate that omits the additional-insured endorsement, or names the wrong entity as additional insured. An expired certificate. A broker's quotation letter offered in place of a certificate. Bid security in a form the solicitation did not authorise, such as a company cheque where only a bond or cashier's cheque was permitted.

Why there is no discretion. Bid security is not a formality — it is the instrument the buyer relies on if the successful bidder refuses to sign. Its value is the difference between that bid and the next one. A response without it is an offer the bidder can withdraw from for free while every compliant bidder is locked in, which is a genuine and quantifiable competitive advantage. Insurance requirements sit slightly differently: some issuers require the certificate at submission and some at award, and the two are very different obligations. Read which one your solicitation imposes, because assuming the friendlier version is how this becomes fatal.

How to prevent it. Start bonding and insurance on the day you decide to bid. Underwriting runs on somebody else's calendar and you have no ability to compress it. Read the exact percentage, the exact limits, the exact additional-insured wording, and any requirement that the surety be listed by a specific authority. Send your broker the actual solicitation language rather than a description of it. And treat the certificate as a matrix row with its own earlier deadline, not as an attachment to be gathered at the end.

Unbalanced or conditional pricing

What it looks like. "Pricing valid for thirty days" where the solicitation demanded ninety. "Subject to material cost escalation." "Final pricing to be confirmed on site survey." A unit price left blank, or entered as "included". A restructured pricing form with rows added or removed. Arithmetic that does not foot between unit price, quantity and extension. And front-loaded unit pricing — nominal amounts on late line items and inflated amounts on early ones — which is the classic form of unbalanced bidding.

Why there is no discretion. A conditional price is not a price the buyer can accept. In a sealed low-bid procurement the buyer generally cannot negotiate the condition away, so it has nothing to award. A validity period shorter than the one required is a condition in disguise: it means the offer may evaporate before the award is made. Unbalanced pricing is treated separately and seriously, because it distorts the comparison between bids and can shift risk onto the buyer — if the early line items are inflated, the bidder is effectively financed by the contract and the buyer's exposure grows if quantities change. Many purchasing rules allow rejection on that basis alone, independent of the total.

How to prevent it. Bid on their form, unmodified, with every cell filled. Never write a condition, a caveat or a footnote onto a pricing sheet — if a term is unacceptable, that is a question for the question window, not an annotation on the price. Have someone who did not build the pricing check the arithmetic independently. Confirm the validity period the solicitation demands and state exactly that. And if a scope ambiguity is driving you toward a caveat, resolve the ambiguity through a written question, because a caveat is a rejection and a question is not.

Exceptions to mandatory terms

What it looks like. Standard terms and conditions attached to the back of the response. A cover letter noting the submission is "subject to mutual agreement on final terms". A struck indemnification clause. A statement that the required insurance limit will be met "upon award subject to availability". A redlined sample contract enclosed for consideration.

Why there is no discretion. The sample contract is normally part of the solicitation, so the response is an offer to perform on those terms. An exception is therefore a counter-offer, and in a competitive procurement the buyer usually cannot accept a counter-offer without either re-opening the terms to every other responder or awarding on terms different from the ones everybody else priced. Both are unacceptable, so the straightforward resolution is to set the exception-taking response aside. This one is particularly costly because it is often taken by the most sophisticated bidders — the ones with a legal department who reflexively redline anything they are asked to sign.

How to prevent it. Read the sample contract at the bid/no-bid stage, before you have invested in writing. If a term is genuinely unworkable, raise it during the question window in the form of a specific proposed change with a reason — issuers do sometimes amend terms by addendum, and an addendum applies to everyone, which is exactly why it is permissible when a private exception is not. If the answer is no and the term is genuinely unbearable, decline the bid. That is a real, respectable outcome, and it is cheaper than a rejection or a contract you should not have signed.

Failing a mandatory minimum qualification

What it looks like. A licence not held at the submission date, where the document required it at submission rather than at award. Four years of documented experience against a five-year minimum. A certification — small, minority-, women-owned, disadvantaged or veteran business — applied for but not granted by the deadline. References that are not "comparable" as the solicitation defines comparable. And the one that catches the most people: non-attendance at a mandatory pre-bid meeting or site visit.

Why there is no discretion. A published minimum is the buyer's statement of what makes responders comparable to each other. Waiving it for one bidder means that bidder competed against a different standard, and every competitor who was screened out — or who did not bid at all because they read the requirement and believed it — has a grievance. The mandatory-meeting version is even less negotiable, because attendance is normally evidenced by a sign-in sheet held by the issuer. There is no mechanism to retroactively have attended.

How to prevent it. Read the minimums first, before anything else in the document, and read them literally. Check whether each must be satisfied at submission or at award — the difference is often a single preposition and it is decisive. Start certifications months ahead of any specific pursuit, because they are granted on the certifying body's schedule. Put the mandatory meeting in the matrix as its own row with its own earlier deadline, and get a copy of the sign-in sheet or the attendance confirmation on the day. If you cannot meet a minimum, raise it during the question window; if the requirement stands, team with a firm that meets it or decline. A strong narrative does not create eligibility a buyer has no authority to grant.

What a buyer can usually waive

In fairness, not every deviation is fatal. Most public purchasing rules give the buyer discretion to waive a minor informality — the usual test being whether the deviation affects price, quantity, quality or delivery, and whether it gives the bidder an advantage other bidders did not have. Things that often fall on the waivable side:

• A missing page number, a typo, or a mislabelled header.
• A date field left blank on a form that is otherwise properly signed.
• Four copies supplied where five were requested, the original being complete.
• A required attachment supplied in a slightly different but equivalent format, where format was not itself specified as mandatory.

Two warnings attach to that list. First, the discretion belongs to the buyer, and different issuers exercise it very differently — some waive freely, some waive nothing, and some are under a legal regime that narrows what they may forgive. Second, a buyer under protest pressure, or one whose award is being scrutinised, will exercise discretion far more conservatively than the same buyer on an uncontested procurement.

Planning to be forgiven is not a plan. The correct posture is to satisfy everything and be grateful you never needed the discretion.

The common thread

Every item in this taxonomy shares four properties.

It is mechanical. None of them is a judgement about your capability, your price, or the quality of your thinking. A bid can be rejected for an empty notary block by the best operator in the market.

It was knowable in advance. Every one of them is stated in a document you were given, usually weeks before the deadline. There is no hidden information here. The requirement was on page nineteen and nobody read page nineteen with a pen.

It is cheap to prevent relative to what it costs. Registering as a plan holder takes four minutes. Booking a notary takes one call. Checking a rendered page count takes thirty seconds. Set against the cost of producing the response, prevention is a rounding error, and it is the highest-return work in the entire process.

It ends the process before your work is read. That is what makes it so expensive. A low score on the technical approach is at least information about how you compete. A rejection for a missing form tells you nothing about your competitiveness, costs exactly as much to incur, and forfeits the whole investment.

Which is why the instrument matters more than the prose. The compliance matrix exists precisely to make each of these ten failures a visible open row rather than an assumption, and the response sequence exists to make sure the rows get closed while there is still time. If you are not yet sure which kind of instrument you are holding — and the answer changes which of these ten failures is most likely to bite you — start with the difference between an RFP, an RFQ and an ITB.