When your department wants to pursue a procurement that exceeds your delegated contracting authority—or involves significant policy implications—you'll need Treasury Board approval before you can move forward. This formal submission process acts as a governance checkpoint, ensuring that high-value or sensitive acquisitions align with government-wide priorities and have solid business cases behind them. According to the Supply Manual Chapter 3, contracting authorities are delegated to specific positions within departments by Treasury Board, and you must stay within those limits.
How It Works
Not every procurement needs to go to Treasury Board. Your department has delegated authority thresholds—for example, under the Government Contracts Regulations section 6, non-competitive goods and services are limited to $25,000 without higher approval. But when you're planning something that exceeds these limits, or involves significant risk or policy sensitivity, you'll need to prepare a formal submission.
The Guidance for Drafters of Treasury Board Submissions makes clear what you need to include. Your submission must link procurement activities to the contracting approval limits outlined in the Directive on the Management of Procurement—detailing contract scope and deliverables, explaining your governance and oversight approach, addressing risk management, and covering relevant policy considerations like the Policy on Green Procurement or accessibility requirements.
In practice, the submission becomes an interactive process between your organization and the Treasury Board Secretariat. You're building a business case that justifies not just the expense, but the approach. The Directive on the Management of Procurement Appendix A, subsection A.5.1.1, sets out these business case requirements. Deputy ministers remain responsible for ensuring all contracting authorities are exercised within delegated limits, as specified in both the Treasury Board Contracting Policy and the Financial Administration Act section 123(1).
Key Considerations
- Timeline matters. Treasury Board submissions take time—often weeks or months depending on complexity. You can't launch a competitive process or award a contract until you receive approval, so factor this into your procurement schedule early. Plan ahead.
- Advance contracting approval comes with strings. If you're seeking approval before finalizing all procurement details, you'll need to commit to reporting the resulting contracts back to TBS Program Sector. This isn't optional paperwork—it's part of the accountability framework.
- Policy compliance gets scrutinized. Your submission will be examined against multiple policy instruments simultaneously. Beyond procurement-specific requirements, expect questions about environmental considerations, Indigenous procurement commitments, and alignment with broader government priorities.
- Departmental limits vary. What requires Treasury Board approval at one department might fall within delegated authority at another. Know your organization's specific thresholds and don't assume they match what colleagues at DND or PSPC are working with.
Related Terms
Contracting Authority, Advance Contract Award Notice (ACAN), Departmental Procurement Limits
Sources
- Supply Manual - Chapter 3: Contracting Management
- Guidance for Drafters of Treasury Board Submissions
- Directive on the Management of Procurement
Bottom line: if you're pushing the boundaries of your delegated authority or dealing with a procurement that could raise eyebrows, start the Treasury Board submission process early. The approval isn't just bureaucratic formality—it's your authorization to proceed.