In Canadian federal procurement, a salient requirement is a mandatory technical or performance specification that goes to the heart of what the government is trying to buy. Miss one of these in your bid, and you're done—contracting officers don't have discretion to overlook the gap. While you won't find the term "salient requirement" explicitly defined in federal policy documents, it's what procurement professionals mean when they talk about the mandatory criteria that actually matter for delivering core functionality.
How It Works
The Supply Manual Section 3.70 makes the stakes clear: your bid must meet all requirements of the solicitation and address all evaluation criteria to be considered responsive. If you fail to meet mandatory requirements, the contracting officer must reject your bid—even if you're offering the best price or strongest overall value. This isn't optional. The same section directs that non-compliant bids cannot be considered, period.
Here's the thing: not every specification in a solicitation carries equal weight. Section 3.15 of the Supply Manual emphasizes that mandatory requirements should be limited to those essential to performance of the work. This is where the concept of salience comes in. A salient requirement directly affects whether you can actually deliver what the government needs. Can your software handle bilingual data entry? Can your vehicle operate in -40°C conditions? Will your cloud infrastructure meet Protected B security standards? These aren't nice-to-haves—they're the line between responsive and rejected.
In practice, the Standard Acquisition Clauses and Conditions Manual reinforces this through its evaluation procedures. Part 4 explicitly states that to be declared responsive, a bid must comply with all requirements and meet all mandatory technical evaluation criteria. Procurement teams at PSPC, DND, and other departments structure their evaluation criteria to separate these essential elements from rated criteria where you can earn competitive points. The mandatory criteria are your salient requirements—the threshold you must cross before anyone even looks at your pricing or added value.
Key Considerations
- Compliance matrices are your friend: Don't make evaluators hunt through your proposal to confirm you've addressed salient requirements. Create a clear table that maps each mandatory criterion to where you've addressed it in your response.
- Interpretation matters, but guessing doesn't: If a requirement seems ambiguous or unclear, submit questions during the solicitation period. Assuming you understand what "enterprise-grade" or "fully compatible" means can cost you the entire opportunity if your interpretation doesn't match the government's intent.
- Subcontractor capabilities count: When you're relying on partners or subcontractors to meet salient requirements, you need explicit commitments in place before bid closing. Vague letters of intent won't cut it if the requirement is truly mandatory.
- Past performance isn't proof: Successfully delivering similar work for another department doesn't automatically satisfy a salient requirement in a new solicitation. You still need to demonstrate compliance explicitly in your statement of work response.
Related Terms
Mandatory Requirements, Evaluation Criteria, Responsive Bid, Non-Compliance, Technical Evaluation
Sources
- Supply Manual – Section 3.70: Evaluation of Bids
- Supply Manual – Section 3.15: Developing the Procurement Strategy
- Standard Acquisition Clauses and Conditions Manual – Part 4: Evaluation Procedures
Bottom line: treat every mandatory requirement as potentially disqualifying. Address them directly, demonstrate compliance clearly, and never assume evaluators will give you the benefit of the doubt.