Mandatory vs. desirable requirements, in plain English
The distinction that costs bidders contracts. Four examples of how mandatory and desirable requirements look in real RFP language and how to score them differently.
Most RFPs distinguish between requirements that disqualify your bid if you don’t meet them and requirements that score you up if you do. Confuse the two and you either bid against an impossible spec or skip a free scoring opportunity. Both failures are common.
The disqualifying requirements are usually called mandatory, required, or must-meet. The scoring requirements are usually called desirable, preferred, or evaluated. The wording varies by buyer and procurement regime, but the words are signposts you can read off the page. Four examples of how the distinction shows up in real RFP language.
Example 1 — A federal civilian solicitation
Mandatory: “The offeror shall hold an active FedRAMP Moderate authorization at the time of proposal submission.”
Desirable: “The Government will give favorable consideration to offerors holding additional certifications including FedRAMP High, FISMA High, or DoD Impact Level 4 or above.”
Read it: shall hold … at time of proposal submission is a mandatory hard gate. Will give favorable consideration is a scoring lever. If you don’t have FedRAMP Moderate, the bid is a no-bid; the gate fails before evaluation. If you don’t have FedRAMP High, you score lower on the desirable cells but you are not disqualified.
Example 2 — A state-government IT modernization
Mandatory: “Bidders must demonstrate at least three (3) successful implementations of comparable scale within the past five (5) years.”
Desirable: “Implementations within the past three (3) years and within state government environments will be scored higher.”
Same pattern: must demonstrate is the gate. Will be scored higher is the lever. A bid with three implementations from four years ago, none of them in state government, passes the gate but scores low on the desirable. A bid with two implementations does not pass the gate and is non-responsive on its face.
Example 3 — A B2B enterprise security questionnaire
Mandatory (in the prerequisites section): “Vendor must hold SOC 2 Type II and ISO 27001 certifications, with audits completed within the last 12 months.”
Desirable (in the scoring section): “Vendors will be evaluated on additional certifications, including HITRUST CSF, PCI DSS, and FedRAMP.”
The B2B version of the same pattern. The prerequisites bar is the gate; the scoring cells are the levers. The honest read here is that “additional certifications” is plural — the buyer is signalling that one extra cert is good and three extras are better. Score yourself accordingly.
Example 4 — A healthcare provider RFP
Mandatory: “Solution shall integrate with the institution’s existing Epic EHR through HL7 v2.x messaging or FHIR R4 API.”
Desirable: “Solutions providing native FHIR R4 integration with bi-directional patient-record sync will be preferred.”
The gate is “either HL7 v2.x or FHIR R4.” The lever is “native FHIR R4 with bi-directional sync.” A vendor with HL7 v2.x messaging passes the gate. A vendor with FHIR R4 in one direction (read-only) passes the gate and scores partially on the lever. A vendor with bi-directional FHIR R4 passes the gate and scores fully. Three different bid postures, all responsive, ranked by their position against the desirable.
What changes in your response
Mandatory requirements get a one-row compliance-matrix entry with a hard yes-or-no. “Yes, we hold FedRAMP Moderate, certificate number [X], effective [date].” The matrix is not a place to elaborate. It is a place to confirm.
Desirable requirements get a matrix entry plus a substantive paragraph in the technical response. The desirable is the scoring lever; the response is where you make the case.
Implicit-desirable requirements — the ones the RFP doesn’t formally name but the evaluation panel cares about — get a capture-plan entry and become win-theme threads. They decide between two responsive bids.
The cheapest skill is reading the page carefully enough to know which sentences are gates and which are levers. VisibleThread named rushing into writing without fully understanding the requirements the leading cause of proposal failure. Most of that failure is mandatory-vs-desirable confusion.