What a Treasury Board submission actually has to do

The bottom line. A Treasury Board submission is not where you sell your idea. Cabinet already decided the idea was worth doing; the federal Budget already named the money. The submission asks the only Cabinet committee that controls spending authority a different question: how will you do this, what will it cost, what could go wrong, and can a Chief Financial Officer sign their name to your numbers? It's a decision document in a fixed vocabulary. Write it as a pitch and it gets sent back before a minister reads it.

If your work touches federal money, a grant program, a contribution agreement, or a procurement above a department's limit, this is the instrument between a policy announcement and a cheque. Knowing what it has to do tells you why a file moves or stalls — and that's what I want to walk you through here.

Three documents, three jobs

The first thing I clear up with founders is that a federal initiative usually moves through three instruments, and people conflate them constantly. The Memorandum to Cabinet secures the policy decision: the what, and the cover for it. The Budget, through the Department of Finance, names the source of funds. The Treasury Board submission is the how — how the initiative gets built, resourced, governed, measured, and de-risked, plus the formal request for the authorities.

A department brings one forward when an initiative falls outside its delegated authorities. If a deputy minister can already approve it under existing delegation, there's no submission; the document exists because someone needs permission they don't already hold. And the Board implements policy; it doesn't create it. Trying to use a submission to fund something Cabinet hasn't approved is the fastest route to rejection: no policy cover, so nothing to authorize.

Why this Board, and not a department

The Treasury Board is the only Cabinet committee established by statute. It sits under the Financial Administration Act, and its composition is set in law: chaired by the President of the Treasury Board, with the Minister of Finance as a member by statute, plus four other members of the King's Privy Council for Canada. Every other Cabinet committee exists at the Prime Minister's prerogative and can be reorganized.

That statutory footing is why the document exists, and it's the part that's easy to skip past. The authority you want, to spend, to contract above a limit, to set up a grants program, lives with the Board, not the department. You're writing to the keyholder.

Who actually reads it

Here's the part founders find counterintuitive. The Board's ministers decide, but they don't hear the sponsoring minister present. Unlike at other Cabinet committees, the minister doesn't pitch the file in the room.

The first real reader is a Treasury Board Secretariat analyst in a Program Sector, the department's single window into the process. That analyst runs the challenge function: they pressure-test the file and pull in the policy centres for the authorities at issue. Costing and procurement go to the Office of the Comptroller General; digital, IT, and cyber to the Office of the Chief Information Officer; HR, executive classification, and official languages to the Office of the Chief Human Resources Officer. Results and evaluation get a review of their own.

By convention, a Secretariat official at the Assistant Secretary or ADM level presents to the Board, briefing ministers with a synthesized advice package, a précis. So the practical upshot is this: you're writing to win over the analyst and the policy centres. Their read becomes the ministers' read.

Ministers then have moves beyond yes or no: approve, amend, defer, reject, or approve with conditions, such as returning the file at a milestone, holding back funds, or requiring an audit.

The standard it's graded against

A submission has to clear an analytical bar; making a case for the idea isn't the job. The Secretariat's guidance for drafters sets out the core content:

• The authorities sought, in standardized language: typically "It is proposed that Treasury Board…" then a numbered list. This is the actual ask, and it has to be precise.
• The policy cover and source of funds: the Cabinet decision, legislation, or Budget that authorized it. Without this, there's nothing to implement.
• The design, delivery, and implementation plan: milestones, timelines, procurement, governance.
• Costs and financial implications, on both a cash and an accrual basis, with assumptions disclosed and cost-containment addressed.
• A results and performance plan under the Policy on Results: immediate, intermediate, and ultimate outcomes, with indicators, targets, and evaluation timing.
• A risk assessment: an overall rating, the key risks, concrete mitigations, and the risk of doing nothing.

Where triggered, you also address horizontal coordination across departments, legal considerations, GBA Plus, official languages, and Indigenous considerations including the duty to consult and UNDRIP. Check the current section list and any per-section limits against the live Secretariat page before drafting, since the template is revised over time.

The CFO gate

The department's Chief Financial Officer must do a due-diligence review and sign an attestation letter, and that signature is a hard gate. In my experience this is the gate that surprises people most.

Under the Secretariat's guideline on CFO attestation, the CFO attests to a set of assertions. Broadly: that the proposal and its assumptions are described and supported; that significant risks, sensitivities, and mitigations are disclosed; that the financial requirements match those assumptions and cost-containment was considered; that funding is identified and sufficient for the expected duration; and that the proposal complies with financial-management policy, with the right authorities in place or being sought. The CFO then gives an overall opinion: sufficient information to decide, insufficient information, or substantial financial risks still to be addressed. Confirm the exact wording and count against the live guideline before quoting it.

The practical effect is plain. If your costing is soft, the CFO won't attest, and a file without a clean attestation doesn't move. The CFO is the first person you have to win over.

The quality gate before the real review

There's a screen in front of all of this, and it's the one I see catch people out. Under the Secretariat's service standards, a draft gets a quality-review determination soon after it arrives: the review proceeds, doesn't proceed and must be revised, or proceeds exceptionally. Only then do substantive comments come back. (The day counts, commonly cited as five working days for the determination and ten for comments, should be verified against the live page.) So an incomplete file doesn't get a hearing; it gets returned. That's weeks lost, and it's why early engagement with the Secretariat, ideally back at the Memorandum to Cabinet stage, is standard advice.

Rigour beats ambition, every time

If there's one thing I'd ask you to internalize, it's this: the Board rewards predictability and value for money, not vision. A modest plan that will succeed outranks a transformative one with no operational substance under it. Governments are risk-averse for earned reasons; the high-profile IT and procurement failures are why. Realistic capability, phased delivery, conservative costing, and honest risk all read as strength. The files that get sent back or buried in conditions share a few traits: weak costing the CFO won't stand behind, risk waved away with thin mitigations, no policy cover, an unmeasurable results framework, or missing consultation with the departments that have to deliver. Under-justify the file and the analyst recommends ministers defer, reject, or condition it.

The authorities a submission seeks are operational and financial, not political: adjustments to reference levels, new or amended grant-and-contribution terms, project approvals above delegated capacity, contracting authority above a minister's limit, real-property moves, certain HR actions, exceptions to a Treasury Board policy, Crown corporation plans. The approved title flows into the Estimates, so it's tightly worded and often very short. This is a document about execution, drafted to a form.

Where Bayview fits

A founder reading this doesn't need to become a drafter. What you do need is to know what the document has to accomplish, why it stalls, and who actually decides, so the people building it inside government build the right thing and you read the process instead of guessing at it.

That's the work we do. We don't lobby and we don't sit in the room for you — government would rather hear from the person who built the business than a hired voice, and that person is you. What we build is the strategy behind the file, the materials that hold up to the challenge function, and a clear read on who weighs in and what they're graded on. You stay the face, and you carry your own file.

If you've got federal money in front of you and a submission standing between the announcement and the cheque, book a scoping call. I'll tell you what the file has to do, and what it'll take to make it move.