Skip to content
CO-02Commissioning the work8 checks · 5 min

How to write a brief an engineer can put a price on

Half a page written this way gets you a fixed number. Ten pages written the other way gets you 'it depends'.

  1. 01

    Describe a Tuesday, not a feature.

    What happens, in order, from the moment the work arrives to the moment it is finished. Features written as features hide the steps that make them expensive.

  2. 02

    Name the systems by name.

    Not "our accounting software" — Xero, and which plan. Half of what makes integration work cheap or ruinous is which specific product, and whether it has an API worth the name.

  3. 03

    Say how many.

    in the PDF

  4. 04

    Say who touches it.

    in the PDF

  5. 05

    Say what happens when it goes wrong today.

    in the PDF

  6. 06

    Say what you have already tried.

    in the PDF

  7. 07

    Name the real constraint.

    in the PDF

  8. 08

    Say what success is, in a sentence someone could check.

    in the PDF

6 more checks in the PDF

The complete checklist — every check with the reasoning under it, the closing note, and the other 12 documents — comes as one PDF.

One email, one PDF, all 13 documents. We don't run a newsletter — unless a new one goes up, that's the only message you'll get.

Before you build

13 numbered documents on scoping software, building it, and taking delivery of it. Free, and free to copy — put them in your own wiki, take them into your own meetings, send them to whoever is about to sign something.

Free to use, share and adapt. No attribution required. © 2026 TechBuilds.