Resources › Systems

How to Document Systems in a Trade Business When You're Flat Out

By Luke Tadich · The Tradie Owner

You know you need this written down. You've known it for a year. Every time a new starter asks how you do the pre-start checklist, or the office rings because nobody else knows which supplier gets the urgent orders, you think: I really should write that up. Then the phone rings again and it doesn't happen. It never happens, because "sit down and write the manual" is a four-hour job you don't have four hours for.

So the business keeps running on what's in your head. Which means every time something needs doing properly, it needs you. Not because your crew can't do it — because nobody ever wrote down how you want it done, so the only safe copy of that knowledge is you, standing on site, telling them again.

You're trying to write a manual. Stop.

A manual is a document someone writes from memory, in one sitting, hoping they remembered everything. That's backwards, and it's why it never gets written — you're trying to recall a process instead of just capturing one while you're doing it.

The fast way is the opposite. You don't write anything from memory. You catch the process the next few times it actually happens, in real time, with almost no extra effort — and what comes out the other end is more accurate than anything you'd have written at a desk anyway, because it's exactly what really happens, not what you think happens.

The two-minute method

Pick one process this week — the pre-start checklist, how you cost a standard job, how a complaint gets handled, whatever currently only works because you're the one doing it. Then:

1. Do the job as normal. Don't slow down, don't perform it for an audience. Just do it the way you actually do it.
2. The moment you finish, open your phone and talk. Voice memo, or voice-to-text into a note — whatever's fastest. Walk through what you just did, step by step, out loud, like you're telling a new starter. Two minutes, no more.
3. Do it again next time the job comes up, and record it again. By the third time, you'll notice you're saying the same steps in the same order — that's the actual process, not the version you imagined when you were trying to write it from scratch.
4. Hand the recording to one person — office admin, a senior tradie, whoever's got half an hour — and get them to turn it into a short checklist. Not prose. Five to ten steps, plain language, the kind of thing you could tape inside a van door.

That's it. No software, no template, no afternoon blocked out. You've turned something that only existed in your head into something that exists on paper, and you did it without changing how you work for a single day.

Start with the process that interrupts you the most

Don't try to document everything at once — that's just the manual trap wearing a different hat. Pick the one thing that generates the most phone calls to you personally. For most owners over $1M it's one of a handful: how a standard quote gets priced, how materials get ordered on a job, how a new starter is brought up to speed in week one, or how a customer complaint gets handled before it reaches you.

Say you run three crews and you're still the one who prices every switchboard upgrade because "it's just quicker if I do it." It's quicker today. It's also why every quote still waits on you, every single week, forever. Capture that one process this month and it stops being a decision only you can make — it becomes a checklist someone else follows, and you review in minutes instead of building from scratch.

Keep it as a living checklist, not a finished document

The reason most SOPs rot in a folder nobody opens is that they're treated as finished the day they're written. They're not finished. The first time someone follows your new checklist and it's missing a step, that's not a failure — that's the system catching up to reality. Fix the line, move on. A checklist that gets corrected twice a month is doing its job. A perfect document nobody ever touches again is dead the day you save it.

• One process at a time. Pick the next one only once the last one is actually being used without you.
• Steps, not paragraphs. If it needs more than ten lines, it's probably two processes wearing one name.
• Store it where the work happens — a shared folder your crew actually opens, not a drive only you check.
• Review it when it breaks, not on a schedule. The gaps show up when someone else runs it, not when you reread it.

What this is actually buying you

This isn't a tidiness project. Every process still stuck in your head is a process that still needs you — to do it, to check it, to be rung about it. Every one you get out and onto a checklist is one less reason your phone goes off on a Saturday. Do this for the handful of things that interrupt you most and you've bought back real hours: evenings you're not finishing a quote, a weekend where the crew runs the job without a call.

It also changes what delegation actually means in your business. Right now, handing something over probably means explaining it from scratch, again, to whoever's taking it on. Once it's written down, handing something over means pointing at the checklist. That's a different job for you — less teaching the same thing on repeat, more reviewing whether the system's still working. That's the job of an owner who's getting off the tools, not the job of the best tradesman on the crew.