Does your plan match your code?

Before you tell your board what’s built, you want to know it’s true, and a claims check gives you one page that says what’s built, what isn’t, and where the documents disagree. In any company’s documents, a sentence describing something already running reads exactly like a sentence describing something nobody has decided yet, and only the code settles which is which.

What you get

The page opens with the short answer: what’s built, what isn’t, and what that means for what you’re building next. Then it shows what the code confirms is already built, and what has to change, with each item sized, whether that’s a small server change or something bigger. Last comes where the documents disagree with themselves or with each other, and every one of those goes back to the person who owns that document to settle.

How it works

Every claim in the plan, the specs and the other documents goes on its own line and gets marked true, false or partly true, with the line of code that settles it. Before anyone relies on a verdict, it’s checked a second time, independently.

Where it comes from

On the product where I’m technical lead, I work from a stack of documents written by different people at different times, and one rule in that work is that no claim gets passed on until it’s been checked against the source. A claims check is that rule turned into a method.

It’s the check behind the first question a board asks, are we building what the business needs, and it keeps Intent, the first of the Four Handoffs, honest. If you’re not sure your plan and your code agree, I want to talk to you.

Read next

Reporting engineering progress to your board, with evidence behind every line

How I build with AI