In Canadian federal procurement, you'll often hear about Project Authorities or Technical Authorities—these are the government officials who actually monitor whether your deliverables meet the technical specifications. They're your day-to-day contact on contract performance, but they can't change your contract. That power sits exclusively with the Contracting Authority.
How It Works
According to the Supply Manual Chapter 3 on Contract Administration, the Contracting Authority maintains overall responsibility for contract management. Technical authorities—whether they're called Project Authorities at PSPC, technical monitors at DND, or subject matter experts at SSC—provide specialized expertise on deliverables, but they operate under clear limitations.
The Contracting Authority formally designates these technical roles through written appointment that outlines specific duties and boundaries. In practice, your Project Authority reviews submissions, assesses whether deliverables meet specifications, and monitors contractor performance against statement of work requirements. They'll attend technical meetings, evaluate your progress reports, and flag issues. When problems arise that require contract changes—adjusting scope, extending timelines, modifying pricing—they report to the Contracting Authority who holds the delegated authority under the Financial Administration Act. Only that person can actually change your contract.
This separation exists for good reason. The Treasury Board Policy on Government Contracts establishes that financial and contractual decisions require specific delegations under sections 32 and 34 of the Financial Administration Act. Technical authorities provide the expertise to inform those decisions, but they don't hold the delegation to execute them. You might have a Project Authority tell you that your approach won't meet requirements—they're right to flag that—but any formal direction changing your contract deliverables must come from the Contracting Authority.
Key Considerations
- Contractors sometimes receive what sounds like direction from technical authorities and act on it, only to discover later that the Contracting Authority never approved the change. Confirm that scope changes, even minor ones, go through the proper contracting channel before proceeding. Every time.
- Your Project Authority is typically the person who best understands the technical requirements and can answer day-to-day questions. Build that relationship. They're your advocate when it comes to explaining technical complexities to the Contracting Authority.
- When technical authorities and Contracting Authorities don't communicate effectively, you get caught in the middle. If you're receiving conflicting signals—technical direction that seems to contradict contract terms—flag it immediately and request written clarification from the Contracting Authority.
- The written designation matters. Ask who your designated technical contact is at contract kickoff, and understand what authority they've been given. Not all technical authorities have identical mandates across departments.
Related Terms
Contracting Authority, Financial Administration Act, Project Authority, Contract Amendment
Sources
- Supply Manual - Chapter 3: Contract Administration
- Contracting Officer's Authority and Project Authority Roles
- Treasury Board Contracting Policy - Roles and Responsibilities
The bottom line? Treat your technical authority as your primary contact for performance questions, but route any requests that affect contract terms, cost, or scope through the Contracting Authority. It saves headaches later.