If your file went back, look at the costing, not the idea

If your Treasury Board submission came back, I'd put money on it not being your idea that failed. Cabinet already blessed the idea. The Budget already named the money. By the time a file reaches the Board, the whether is settled, and a different question is on the table: how will you do this, what does it cost, what could go wrong, and will a Chief Financial Officer put their name to the numbers.

That reframe is the thing I keep watching trip founders up, because it inverts the instinct you spent years building. Selling the vision is the thing you're best at. It's also the thing the submission isn't asking for.

So watch what actually moves a file backward. Not "unambitious." Not "lacks impact." The returns I see cluster on a short, unglamorous list — costing the CFO won't stand behind, risk addressed with a sentence and a shrug, no policy cover, a results framework no one could measure, missing sign-off from the departments that have to deliver the thing. Every one of those is a rigour failure, not an ambition failure. A modest plan that will work outranks a transformative one with nothing operational under it, and that ordering surprises almost everyone.

Government is risk-averse for earned reasons. The high-profile IT and procurement wrecks are why a Secretariat analyst reads conservative costing and phased delivery as strength, not timidity. The move that feels like settling — scaling the pitch down to what you can defend line by line — is the move that gets you through.

The CFO gate is where this gets concrete. The department's CFO has to do a due-diligence review and sign an attestation letter, and that signature is a hard stop. Under the Secretariat's guideline, the CFO ends with an overall opinion: enough information to decide, not enough, or substantial financial risks still open. Confirm the exact wording against the live guideline before you quote it. The mechanism is the part I'd want you to internalize — soft costing means no attestation, and no attestation means the file doesn't move. The CFO is the first person you have to win, and you win them with numbers that hold, not a better story.

There's a screen in front of the real review, too. A draft gets a quality determination soon after it lands: proceeds, or goes back to be revised. The day counts get cited as five working days for that determination and ten for substantive comments, but check those against the live Secretariat page, because the standards get revised. The point under the numbers holds either way. An incomplete file doesn't get argued down in the room — it gets returned at the door, and that's weeks gone.

And here's who's actually reading, because it's not who I find founders picture. The Board's ministers decide, but the sponsoring minister doesn't present the file. The first real reader is a Treasury Board Secretariat analyst running the challenge function, pulling in the policy centres on costing, digital, HR, results. By convention a Secretariat official briefs ministers with a synthesized package. So the audience you're writing to win is the analyst and the CFO — and their read becomes the ministers' read.

What I want you to take from all of this is simpler than it sounds: the document the department builds will only ever be as good as the read sitting behind it. The people inside the department do the drafting. Your job is to walk in already knowing what the file has to accomplish, where files like yours tend to stall, and who weighs in on what — so you can look at a draft and tell whether it'll clear the challenge function or come back at the door, and so you can actually talk shop with the officials writing it instead of nodding along. That read is what I build with you. The file stays yours; I'm the strategist in your corner while you carry it.

If you want the longer treatment, the full version walks the whole instrument end to end. And if a returned submission is sitting between you and a cheque that's already been named, walk it through with me before you resubmit and I'll point to where the costing or the risk is losing it.