Mandatory Requirement (M)

When you're responding to a federal RFP, mandatory requirements are the red lines you absolutely cannot cross. Miss even one, and your proposal gets tossed before evaluators ever look at your technical scores or pricing. They're the government's way of establishing a minimum bar—and there's no negotiating your way back in once you've failed to meet them.

How It Works

According to Section 4.35.1 of the Supply Manual, mandatory evaluation criteria "identify the minimum requirements that are essential to the successful completion of the work." These appear in solicitation documents marked with an "M" or labeled "Mandatory," and they're assessed strictly on a pass/fail basis. You either meet the requirement completely, or you don't. Partial credit doesn't exist.

Here's the thing: contracting officers at departments like PSPC and SSC are actually instructed to keep mandatory criteria to a minimum. The Directive on the Management of Procurement explicitly states that agencies should limit mandatory technical criteria "to those determined to be essential requirements in order to achieve the desired outcomes and ensure that no bid is unnecessarily disqualified." What does this look like in practice? You'll typically see mandatory requirements focused on absolute essentials—security clearance levels, specific certifications, mandatory insurance, or critical technical capabilities that directly align with the Statement of Work.

The evaluation sequence matters. Compliance with mandatory requirements gets checked first, before any point-rated criteria are even considered. If your bid fails mandatory compliance, evaluators stop right there. Your pricing doesn't matter. Your superior technical approach doesn't matter. You're out. This is why experienced bidders create compliance matrices that explicitly cross-reference each mandatory requirement with the specific section of their proposal that addresses it—making the evaluator's job easier and reducing the risk of an accidental non-compliance.

Key Considerations

• Timing is everything: Some mandatory requirements must be met at bid closing (like providing proof of insurance), while others must be satisfied before contract award or within a specified timeframe. Read the compliance timing carefully.

• Format requirements can be mandatory too: It's not just about what you submit—sometimes how you submit it matters. Page limits, file formats, or the number of references required can all be mandatory. Submitting 11 pages when the mandatory limit is 10 can disqualify you.

• The 5% Indigenous procurement target: Federal departments must ensure a minimum 5% of total contract value goes to Indigenous businesses. While this creates set-aside opportunities, when you're bidding on Indigenous set-asides, meeting the Indigenous business definition becomes a mandatory requirement.

• Don't assume you can clarify later: If your proposal is ambiguous about whether you meet a mandatory requirement, you may not get a chance to explain. Some solicitation documents allow contracting officers to seek clarification, but many don't—particularly for mandatory criteria.

Related Terms

Point-Rated Criteria, Statement of Work (SOW), Compliance Matrix

Sources

• Supply Manual - Section 4.35.1, Public Services and Procurement Canada

• Directive on the Management of Procurement, Treasury Board Secretariat

• Mandatory Minimum 5% Indigenous Procurement Target, Indigenous Services Canada

Bottom line: treat mandatory requirements like the gatekeepers they are. Build your compliance matrix first, double-check every single requirement, and make it painfully obvious to evaluators that you've met each one.