A plumbing contractor hired his third tech in March. By the end of week one, he was getting eight calls a day from the field.
Where's the water shutoff? Which parts did we quote? Is this the right address? What does the job look like when it's done?
The tech wasn't making mistakes. He was filling gaps. And the gaps were in the job cards, not in the tech.
Every experienced tech who has been with you for a few years has quietly learned to compensate for a thin setup. They know to check the client notes before arriving. They know the shorthand. They know that "quote approved" doesn't mean the parts are confirmed or the right unit is on the truck.
A new tech reads the job card literally. If the job card is bare, they call you.
The eight calls a day were not a training problem. They were a system problem. The information that experienced techs carry in their heads was not written anywhere ServiceM8 could show to a new hire.
Three things in ServiceM8 close that gap before the end of week two.
Job description templates. Instead of a blank description or a one-line note, each work type gets a pre-built structure: scope of work, materials to confirm before departure, a checklist of what to complete and document on site. The tech opens the job and the structure is already there. They follow it. If something is missing, the template makes that visible before they leave the shop.
Custom forms attached to job types. For work that requires consistent documentation -- inspections, commissioning, safety sign-offs -- a form can be attached to the job card and required before the job can move to Complete. The tech cannot skip it. You get the same output regardless of who ran the job, and the completed form is stored in the job history.
Client notes that carry forward. Access codes, equipment locations, parking, who to call when arriving. In ServiceM8 this lives in the client record and appears on every job at that property. Your four-year tech already knows it from memory. Your new hire sees it automatically on day one.
When those three are configured, the job card itself does the onboarding. Not in a classroom. On every job, from the first week.
The plumbing contractor went from eight calls in week one to two calls by week three. Not because the tech improved -- he did, but that was not the variable. Because the job cards started carrying what the owner had been carrying in his head.
By month two, the new tech was running jobs the same way the veteran was. Same process. Same documentation. The owner could look at a completed job record and not tell which tech had done it.
That consistency is easy to undervalue when you are in the middle of it. A business where job quality depends on which tech shows up is harder to grow and harder to delegate. A business where the job card tells every tech the same thing is a different kind of operation.
Most ServiceM8 businesses are using a fraction of what the platform can do here. The job type system is there. The custom form builder is there. The client notes carry forward automatically. The configuration just has not been done.
If you are planning to hire, or if you have just brought someone on and are already fielding more calls than you expected, this is the right time to build the setup properly. Getting it right before the hire costs a few hours. Getting it right after costs weeks of your time that you will not get back.
If you want the job templates, custom forms, and client workflow built out before your next hire, that is the kind of ServiceM8 configuration work ChanAutomation does. One-time setup. Pays back every time you bring someone new on.
Reply and tell me what the first week of a new hire looks like in your business right now. I'll tell you which part I would fix first.
Kevin Chan
The Ops Shortcut by ChanAutomation
www.chanautomation.com