Technical Acceptance Criteria

Technical Acceptance Criteria are the specific, measurable standards written into your contract that determine whether the Contracting Authority will accept your deliverable and authorize payment. Get these wrong—or misunderstand them—and you're looking at payment delays, disputes, or rejected work. They're the contractual threshold your work must clear, period.

How It Works

These criteria function as a bridge between what you promise in your proposal and what you must actually deliver during contract performance. According to PSPC's Supply Manual (sub-section 4.35.1), mandatory technical evaluation criteria must align consistently with the Statement of Work and any Flexible Grid requirements. Here's the thing: if there's a significant gap between what's described in the SOW and what's listed as mandatory criteria, you're either looking at an inaccurate work description or potential process manipulation.

During the evaluation phase, these criteria help weed out unqualified bidders and solutions—as outlined in the Technology Supply Chain Guidelines (TSCG-01). But their role doesn't end when the contract is awarded. They become the yardstick against which your actual deliverables are measured. Treasury Board Contracting Policy (sub-section 10.7.25) reinforces that for procurements covered by trade agreements, all evaluation criteria must be fully disclosed upfront—no surprises, no moving targets.

In practice, acceptance criteria typically include quantifiable measures: performance benchmarks, quality standards, certification requirements, security compliance levels, or specific deliverable formats. When you submit a deliverable, the Contracting Authority reviews it against these predetermined standards. Pass? Payment gets authorized. Fail? You're back to revising and resubmitting, and the payment clock stops ticking.

Key Considerations

• Read them during proposal development, not after contract award. Bidders often focus intensely on mandatory requirements to qualify their proposal but skim the acceptance criteria. Big mistake. You need to know exactly what "done" looks like before you price your work.

• Inconsistencies between SOW and acceptance criteria are red flags. If what's described in the Statement of Work doesn't match the acceptance standards, seek clarification immediately. Recent procurement practice reviews of PSPC have examined these discrepancies as potential process issues.

• Certification and security requirements often appear here. The Treasury Board Policy on Government Security (sub-section 5.9 and Appendix A.6) requires certain certifications to be listed in mandatory evaluation criteria or specifications—and these become acceptance hurdles you must clear before payment.

• Document everything during performance. When you believe you've met an acceptance criterion, your supporting documentation needs to demonstrate compliance clearly. Ambiguity works against you in disputes.

Related Terms

Statement of Work, Mandatory Requirements, Evaluation Criteria, Deliverables, Payment Authorization

Sources

• PSPC Supply Manual, Sub-section 4.35.1

• Assessor Guidance for Supply Arrangement Requirements

• Technology Supply Chain Guidelines (TSCG-01)

The bottom line? Treat acceptance criteria as non-negotiable contractual commitments, not aspirational targets. Your cash flow depends on meeting them.