Mandatory Requirements in Government Bids

Most suppliers who lose public tenders assume they were outbid. Often they were not evaluated at all.

Mandatory requirements are the conditions a bid must satisfy simply to remain in the competition. They are assessed before anyone reads your methodology, before your references are checked, and before your price is opened. A bid that fails one mandatory is set aside — and the evaluator usually has no discretion to do otherwise, however strong the rest of the response is.

This is the single most important asymmetry in public procurement. Rated criteria reward effort proportionally: a better answer earns more points. Mandatory requirements do not. They are pass or fail, and there is no partial credit for nearly meeting one.

] The practical consequence is that mandatory requirements should be the first thing you read in any solicitation — before the scope, before the evaluation criteria, and certainly before you start writing.

Mandatory requirements are rarely gathered in one convenient list. In a typical federal solicitation they appear in at least three places, and missing any one of them is a live risk.

**In the evaluation section.** This is where most bidders look, and where mandatories are usually labelled explicitly — often as a table with a column for the bidder to cross-reference where each is addressed.

**In the bid preparation instructions.** These contain procedural mandatories: the submission channel, format, page limits, required forms, signature requirements, and how many copies. These are just as binding as technical mandatories and are more commonly missed, because suppliers treat them as administrative rather than substantive.

**In the statement of work or resulting contract clauses.** Occasionally a requirement that functions as a mandatory is stated only in the scope or in the contract terms — a certification the contractor must hold, an insurance limit, a security condition.

• ✓Read the evaluation section first and list every mandatory
• ✓Read the bid preparation instructions and add every procedural requirement to the same list
• ✓Skim the statement of work for conditions phrased as "the contractor must" or "the bidder shall"
• ✓Check the resulting contract clauses for insurance, bonding and clearance obligations
• ✓Re-check after every amendment, because mandatories are frequently added or altered[/Checklist

] Build one consolidated list from all of these. Do not rely on the solicitation's own summary table being complete.

Mandatory requirements are written to be evaluated objectively, which means they are usually more literal than they first appear. Reading them loosely is how compliant-looking bids fail.

Three habits help.

**Separate the requirement from the evidence.** Many mandatories have two parts: a condition you must meet, and a specific way you must demonstrate it. "The bidder must have completed two projects of similar scope within the last five years, demonstrated by reference letters from the client organisation" contains both. Meeting the condition without providing the stated evidence is still a failure.

**Notice the qualifiers.** Words like *at bid closing*, *within the last five years*, *for the proposed resource*, and *of similar scope and complexity* are not filler. They narrow the requirement, and evaluators apply them as written. A project completed six years ago does not satisfy a five-year window, however relevant it is.

**Distinguish "must" from "should".** In most solicitations *must* and *shall* signal mandatory; *should* and *may* signal desirable, which usually maps to rated criteria. If the distinction is unclear in a specific document, ask during the question period rather than assuming.

]

Evaluators work through mandatories methodically, usually against a checklist, often under time pressure and across many bids. Your job is to make each one findable in seconds.

**Answer in the evaluator's structure, not yours.** If the solicitation numbers its mandatories M1 to M12, use those labels in your response and address them in that order. A response organised around your own narrative forces the evaluator to hunt, and anything they cannot find is treated as absent.

**Include a cross-reference table.** Many solicitations require one; include it even when they do not. A simple table mapping each mandatory to the page and section where it is addressed removes ambiguity entirely.

**State compliance explicitly, then evidence it.** Do not make the evaluator infer. "We meet this requirement" followed by the specific evidence is stronger than a paragraph that implies compliance without asserting it.

The right-hand column is not better writing in a literary sense. It is better because an evaluator can score it without interpretation.

The correct response is usually to stop, and the value of reading mandatories first is that you can stop early.

Before you do, three things are worth checking.

**Ask during the question period.** If a requirement seems disproportionate, ambiguous, or written around one supplier's specific characteristics, ask. Buyers do amend requirements in response to questions, particularly where a condition unintentionally narrows competition. Questions are usually published anonymously along with the answers.

**Consider whether a partner satisfies it.** Some mandatories can be met by a subcontractor, a joint venture partner, or a proposed resource who is not currently your employee. Whether this is permitted depends on the wording — read carefully, because some requirements attach specifically to the bidding entity rather than to the team.

**Check whether it can be met before closing, not just eventually.** Certifications, clearances and insurance can often be obtained, but the relevant date is bid closing. An application in progress is not compliance.

Compliance failures are almost entirely preventable, and the prevention is procedural rather than clever. The most effective control is simple: someone who did not write the bid checks it against the mandatory list.

The person who wrote a response knows what they meant, and reads their own text as satisfying requirements it does not explicitly address. A second reader working only from the solicitation and the bid does not have that blind spot.

• ✓Every mandatory on your consolidated list is addressed explicitly and labelled
• ✓Required evidence is attached, not just referenced
• ✓All amendments are acknowledged in the form the instructions specify
• ✓Required forms are complete and signed by someone with authority to bind the company
• ✓Format, page limits and file naming match the instructions
• ✓Submission is through the specified channel, with time to spare before closing
• ✓A second person has verified the above against the solicitation, not against the bid[/Checklist

] Run this pass with enough time to fix what it finds. A verification that happens an hour before closing is a formality, not a control.

Mandatory requirements are assessed before merit and applied literally. Failing one eliminates a bid regardless of its quality or price, which makes them the highest-leverage part of any solicitation to read carefully and the cheapest place to lose. Read them first, from all three places they appear. Build one consolidated list. Answer in the evaluator's structure with explicit compliance statements and attached evidence. Ask questions where a requirement is ambiguous. And have someone who did not write the bid verify it before submission. If you cannot meet one, stopping early is a good outcome. The proposal hours you protect are worth more than a bid that was never going to be evaluated.