Why do you need an instruction manual in your trade business?
If a key admin person walks out tomorrow, or threatens to unless you give them a pay rise you cannot afford, you have two options: cave in or replace them fast. Without documented processes, you cave in. With an instruction manual, you can confidently bring someone new in and point them at exactly how every task in the business is done.
The instruction manual is not a dusty folder. It lives inside your task management software, linked directly to each staff member's hit list, so it is always current and always accessible.
What goes into the instruction manual?
The instruction manual is built around your non-negotiable tasks: the things that, if they are not done, the business either stops growing or falls over entirely. Invoicing is the clearest example. If invoicing does not happen, there is no business.
For each task you record:
- The task title and which department it belongs to (admin and HR, operations, sales and marketing, and so on)
- Who is currently responsible and who you want to be responsible in the future
- Whether it is a daily, weekly, or monthly task, and a time allocation in minutes
- A Loom video of the task being completed, recorded by the person doing it, dropped into the task description
That Loom video is the instruction. If the person goes sick, leaves, or is let go, the next person opens the task, watches the video, and knows what to do.
What is a hit list and how does it connect to the instruction manual?
A hit list is a visual, prioritised to-do list inside your task management software, Asana being the tool used here. It is different from a generic "my tasks" list because you can group, sort, and filter by priority (low, medium, important, urgent) and by task type, so it does not become one long anxiety-inducing scroll.
Each person in the business has their own hit list. When you add a task to the instruction manual and assign it to someone, it populates directly on their hit list. When they complete it and it is a recurring task, it repopulates automatically on the next due date. The instruction manual and the hit list stay connected, so nothing falls through.
How do you handle recurring non-negotiable tasks?
Non-negotiable tasks are set to repeat on a schedule. If quotes are followed up every Tuesday and Thursday, that is set to repeat on those days. If staff performance submissions happen every Friday at six in the evening, that is set to repeat weekly on Friday. The person assigned does not need to remember it because the system tells them.
This is what keeps the business running like what was described as a sausage factory: even when you are flat out with work, quoting still happens; even when the bank account looks healthy, invoicing still happens. The rhythm of the business does not depend on anyone remembering.
How do you get your team actually using the system every day?
The single rule that makes the hit list work is to open it first thing in the morning and check it last thing before you finish for the day. That is it. It sounds simple, but the biggest struggle with any task management system is staff not building the habit of being in it regularly.
For emails, the approach described is a two-minute rule: if an email can be replied to in two minutes, reply straight away. If it takes longer, forward it to the hit list, prioritise it, assign it a time allocation, and deal with it in a power block. That way, the inbox does not become the to-do list, and tasks do not get lost.
What mindset shift does building this system require?
When you are adding tasks to the instruction manual, the question to ask yourself is not "what do I need to do today?" but "who can do this for me?" If that person does not yet exist in your business, the instruction manual makes it clear where the gap is and what the hire needs to cover.
The goal is to reach a point where every repeating task in the business has an owner, a process, a video, and a schedule, and you are managing the system rather than doing the tasks yourself. That is what turns a business from something that depends on you into something that runs without you.
