Start with one recurring task
Clear work instructions tell someone when to start, what to do, when to ask for help, and how to check that the work is finished. These instructions are often called a standard operating procedure, or SOP.
Start with a task your business repeats: booking a job, following up on an estimate, finishing a service visit, or training a new technician. Write it with the people who do the work. The template below is a practical starting point, not a certification standard or a replacement for trade-specific procedures.
What the instructions need to explain
| Section | What to write |
|---|---|
| Task and purpose | Name one task and the problem the instructions should prevent. |
| When to start | The event that tells someone it is time to do the task. |
| Who does it | The responsible role and who covers when that person is away. |
| What is needed first | Records, approvals, tools, or materials, and where to find them. |
| Steps to follow | Actions in order, including decisions along the way. |
| What happens next | What the next person needs, where it is recorded, and when it is due. |
| When to ask for help | When to stop, whom to contact, and what information to provide. |
| How to check it is finished | The record, check, or other evidence that the task was completed. |
| Who keeps it current | The person responsible for the document, its version and date, and when to review it. |
Use role names where possible so the instructions still work when employees change. Name the place where information is stored so a new employee can find it without asking you.
An example: following up on an estimate
This is an illustrative office task, not a record of client results. Adapt its timing and contact rules to your customers and software.
Estimate follow-up instructions
Purpose: make sure each open estimate has a next step and a recorded outcome.
Start when: an estimate has been sent and added to the open-estimate list.
Who does it: the assigned office coordinator. Backup: the designated office lead.
What is needed: the estimate number, customer contact preferences, agreed work, sent date, and assigned salesperson.
- Confirm that the estimate reached the correct customer contact.
- Record the next follow-up date using the schedule your company has agreed to.
- On that date, check for a response or status change before contacting the customer.
- Ask whether the customer needs an explanation or wants to discuss the next step.
- Record the response. Send questions about the work or price to the person authorized to answer them.
- Mark the estimate accepted, declined, waiting for an answer, or due for another follow-up.
Stop and ask for help: the customer asks for no further contact, a complaint remains unresolved, or the requested work has changed and needs a new estimate.
Finished when: the estimate record has an outcome or a dated next step assigned to someone.
Number to watch: open estimates without a dated next step.
Explain decisions in plain language
"Follow up as needed" leaves the employee guessing about timing. "Escalate the issue" leaves them guessing whom to contact. Write the actual rule and name the role that can make the decision.
If the rule has not been agreed, mark the question and resolve it with the team before calling the instructions finished. Keep passwords and customer access codes in your approved secure system; tell authorized employees where to retrieve them.
Test the instructions on a real task
Ask someone who did not write the instructions to use them on a normal example. Watch for questions, missing information, and decisions that are still unclear. Fix the instructions and the way the task is handled together.
Then try a case that does not follow the normal path. For estimate follow-up, use a customer who asks to change the work. Can the coordinator identify who should respond and avoid sending an outdated estimate?
The useful test is whether someone can complete the task correctly. A long document and a box saying "I have read this" do not prove that.
Keep one current version everyone can find
Give each set of instructions a person responsible and a permanent place to find it. Put the version and effective date at the top. Archive old versions so employees do not get different answers from different folders.
Review the instructions when software changes, responsibilities move, or the same problem keeps happening. Update them to solve a real problem, not just to make the document look recent.
Copy the starter and make it your own
Complete the template with the people who do the task, test it, and explain what happens next. A few clear, tested instructions are more useful than a large folder nobody opens.
Sources and context
These instructions and examples describe a suggested way of working. They are not client case studies or a trade standard. Adapt them to your business and the requirements of your work.