Late in October I spent an afternoon at a Geelong trade business that's been around for decades. They sell, install and repair equipment, and plenty of customers walk in because they know the shop. Work isn't the problem. The owner asked for an audit because the systems behind it hadn't kept up. This is how we planned the move from a whiteboard to ServiceM8.

Here's how a job moved through the place. An enquiry came in, he called the customer back, filled out a form and put it up on the whiteboard. From there, in his words, it was memory.

That's pretty normal for a business built on reputation. It works until someone's away.

Where the gaps showed up

The first was job history. Someone walks in saying you worked on their gear eight months ago, and the only record is a Xero invoice with a short description and nothing from the technician.

The second was follow-up. Everything they install needs servicing, and nobody was checking in afterwards. He couldn't add another manual job to his day.

The third was the field work. The technician out on the road would come back and find a job on the board a few hundred metres from where he'd just been. The owner reckoned that costs about two hours a day.

The plan for moving from the whiteboard to ServiceM8

None of this was set up on the day. It's what we agreed in the audit, and it's a fair picture of what moving onto ServiceM8 looks like for a business like this.

Job and client cards. Each job in ServiceM8 holds its own notes and photos, so whoever's on the job records what they found and what they did. One client can have many jobs, and the client card holds the details that belong to the customer, like a gate code. Open any new job and that client's whole history is right there. It all lives in ServiceM8's cloud, so a broken iPad doesn't take the records with it.

Automatic check-ins after an install. A month after the job, a message asks if everything's working. At six months and twelve months, a reminder that it's due for a service. Once it's set up, nobody has to remember.

Walk-ins and phone calls. Details go into ServiceM8 at the counter or during the call, and walk-ins get a printed docket on the item.

The map. The technician can see jobs on a map instead of a list, and pick up nearby work on his way home. ServiceM8's scheduling can also route a day of jobs in one area.

Two levels of access. Full access for the owners. Technicians can add parts, notes and photos, but can't send invoices or change a client's history.

Invoices. I'd approve and send invoices from ServiceM8. They still land in Xero for the bookkeeper. We'll set ServiceM8 to send from the business's own email address, because the default address tends to end up in junk.

How we'd roll it out

I'd start with the on-site jobs. For a couple of weeks they'd run the whiteboard and ServiceM8 side by side, and we'd adjust anything that doesn't match how they actually work. Then the board comes down.

For training, I'd teach the owner first, then have him teach the team with me in the room. You learn a system properly by explaining it.

What to take from this

If your jobs live on a whiteboard, start by writing down how one job moves from the first call to being paid. That one page tells you most of what your job software needs to do. If you're still choosing software, our ServiceM8 vs Tradify guide compares the two for trade businesses.