The September checklist

The September checklist

Peak season is about eight weeks away. From late October the phone starts and doesn’t really stop until February, and whatever is loose in your business right now will be twice as loose when every second call is a breakdown.

This is the list we run through with customers in the last weeks of winter. None of it takes long. All of it is easier now than it will be in December.

Block out an hour with whoever runs operations and work down it in order. Most businesses find two items they’re fine on, three that need a fortnight of attention, and one that explains a problem they’ve been living with for a year.

1. Confirm every PM contract, and get the jobs on the board

Preventative maintenance is the only revenue you can forecast, and it’s the first thing that gets bumped when the breakdowns start. Confirm the contracts now, get the scheduled jobs generated for the next six months, and you’ll protect that work when the pressure comes on.

It’s also the cheapest sales conversation available to you. A customer whose PM is confirmed in August isn’t taking a cold call in October — and the ones who’ve let their maintenance lapse are exactly the ones who’ll ring you in a panic on the first 38-degree day.

2. Shrink the gap between finished and invoiced

Pick ten jobs from last month and measure it. Whatever that number is in August, it gets worse in December — the volume doesn’t change the admin capacity. Go into summer with the gap as small as you can make it, because peak season is when cashflow either carries you or squeezes you.

While you’re there, run the list of jobs marked completed but never invoiced. Almost every business has more sitting in that list than they’d guess, and clearing it before summer is the fastest money you’ll make this quarter.

3. Read last summer’s callbacks

Pull the repeat visits from last January and February and look for the pattern. Same site? Same asset? Same fault? That list tells you exactly where the training, the parts stock or the process will fail you again — and you’ve got eight weeks to do something about it.

Two patterns are worth acting on immediately: the same fault at the same site — usually a repair that should have been a replacement, and a conversation to have with the customer now — and the same fault across different techs, usually a training or parts-stock problem you can fix in an afternoon.

4. Check your asset records on the sites that matter

Take your ten biggest maintenance customers. Can you see model, serial and fault history for their critical plant without ringing anyone? If not, make it a standing instruction for the next eight weeks: photograph the plate, capture the details, every visit.

Eight weeks of that habit across a full crew adds up to a surprising amount of history, and it covers exactly the sites you’ll be sending unfamiliar techs to when everyone is stretched in January.

5. Tidy your quoting templates

Summer quoting is fast quoting. If your standard inclusions, rates and after-hours loadings are current before the rush, your techs can quote on site instead of promising to send something through — and the quote sent from the driveway wins far more often than the one that arrives on Thursday.

Check your after-hours and weekend rates while you’re in there. Plenty of businesses go into summer charging what they set two winters ago, then work every Saturday in January for a margin that didn’t survive the last two years of parts pricing.

6. Decide what you’re not doing

The businesses that cope best in summer are the ones that decided in September which work they’d turn down. Know your minimum call-out, your after-hours position and which customers get priority — before you’re making that call at 6pm on a 39-degree Friday.

7. Agree who covers what, in writing

Summer runs on goodwill until it doesn’t. Set the on-call roster for December and January now, agree the rate, and tell everyone in August rather than sorting it out in the second week of a heatwave. The same goes for the office: someone has to keep invoicing moving while the phones run hot, and that person shouldn’t also be the one dispatching.

If working through this list turns up things your current system can’t tell you — how many PMs are due, what’s unbilled, which assets you’ve touched twice — that’s worth a conversation now rather than in November.

Book a 20-minute demo before the season starts, or call us on 0457 228 884. Australian-founded, Australian-led, 30 years in HVAC&R and electrical.

AI won’t fix a broken process

AI won’t fix a broken process

Every vendor in field service software is selling you an AI layer this year. Agents that write your job notes, assistants that answer questions about your data, tools that brief your techs before they arrive.

Some of it is genuinely useful, and we’re building in that direction too. But after 30 years of watching Australian service businesses buy software, we’d say this: none of it helps if your techs still can’t see today’s run and your invoices still go out nine days late.

We’ve been through a few of these waves. Handhelds were going to fix field service. Then the cloud was. Then mobile apps. Each one genuinely helped the businesses that had their process sorted, and each one disappointed the businesses hoping the technology would supply the discipline they didn’t have. There’s no reason to think this wave is different.

What has changed is the pace of the claims. A feature that would once have been sold as a time-saver is now sold as a member of your team. Read the fine print on most of it and you find something genuinely handy — automatic job summaries, better search, a nicer way to ask a question of your own data — wrapped in language that implies it will run the business for you.

Automation is a multiplier, and multipliers work both ways

Point a clever model at a job record nobody filled in properly and you get a confident summary of nothing. Automate a quoting process that’s wrong and you’ll produce wrong quotes faster than you ever could by hand.

The businesses getting real value out of automation are the ones whose data was already clean — because their process was already sound. That’s the uncomfortable bit. The prerequisite isn’t a licence. It’s a workflow your team actually follows.

It’s the same reason a report is only as good as the data behind it. If half your jobs are missing their parts, no amount of clever summarising will tell you your real margin. It will tell you the wrong number faster, and with more confidence than a spreadsheet ever had.

The unglamorous things that actually move the numbers

In our experience there are four, and none of them will ever be a launch announcement.

One thread from quote to invoice, so nothing is re-keyed. A schedule everyone can see. Job costing that includes the parts, so margin is a fact rather than a feeling. And a preventative maintenance program that runs itself, because that’s the revenue you can forecast twelve months out.

Get those four right and the business feels different within a quarter.

If you only do one, do the first. Almost every problem an owner brings us — margin they can’t explain, invoices going out late, techs ringing the office all day — traces back to the job record being re-typed somewhere between the site and the ledger.

The second is the schedule everyone can see, because it’s the fastest to fix and the whole office feels it inside a week. The third is job costing that includes parts, which is where most businesses discover their real margin is several points off what they assumed. The fourth — preventative maintenance running itself — is the one that changes how the business is valued, because forecastable revenue is worth more than reactive revenue to a buyer, a bank, or you.

Where automation genuinely earns its place

We’re not luddites about it. Automation is excellent at the repetitive, rule-based work: raising the PM jobs when they’re due, pulling the parts onto the invoice, flagging the job that’s been sitting at “completed, not invoiced” for a fortnight.

That’s the boring bit, and the boring bit is where the money is. It’s also safe to automate, because the process behind it is deterministic — you’re not asking a model to guess what happened on site.

The distinction we hold to is simple: automate the things where being wrong is obvious and cheap, and keep a human on the things where being wrong is expensive and invisible. Raising a scheduled PM job is the first kind. Deciding what to charge for a contested three hours is the second.

That’s also the honest reason we don’t lead our marketing with AI. We’d rather show you a scheduling board your dispatcher can run on day one than a demo of something clever that depends on data you don’t have yet. When the data is there, the clever parts get much more useful — and we’ll build them.

Ask any vendor these three questions

Including us. What does week one look like, with dates? Who answers the phone when it breaks, and where are they? And what won’t your software do for a business like mine?

That third one is the tell. Everyone can demo the good bits. Thirty years in, we know where we fit — HVAC&R and electrical contractors who need configuration around their own process — and we know where we don’t. We’d rather say so before you sign than six months into an implementation.

Australian-founded, and it matters more than it sounds

We don’t raise the flag for the sake of it. It matters for practical reasons: our support hours are your working hours, we know what a Reece or Actrol account looks like, we’ve built for Australian compliance and after-hours rates, and when something breaks at 7am you speak to someone who can change it — not someone logging a ticket for a team who start work as you’re knocking off.

Thirty years in the same market also means we’ve watched businesses grow from eight techs to forty. We built for that transition specifically, which is why we don’t chase the sole-trader end of the market and don’t pretend to.

If you’re a one-van operation, there are simpler and cheaper tools than us and we’ll happily name them. If you’re running 10 to 50 techs across HVAC&R or electrical, with maintenance contracts, project work and real asset obligations, that’s the shape of business we’ve spent three decades building for.

Ask us the hard question. Call 0457 228 884 or book a demo — Australian-founded, Australian-led, and you’ll speak to someone who knows the industry, not a script.

Your asset history is the moat

Your asset history is the moat

Every maintenance contract eventually comes up for renewal, and when it does you’re in a room with someone comparing you to a number on a page. If the only thing that separates you from the next contractor is price, you’ll win some and lose some, and the ones you win will be the ones you shouldn’t have.

There’s one thing a competitor genuinely cannot copy: what you know about that customer’s equipment.

Not the price. Not the response time — anyone can promise four hours. What they can’t copy is six years of knowing that the unit on the north side ices up every February, that the isolator sits behind the false ceiling, and that the plant room key lives with the café next door.

What the record actually buys you

Three things, and they’re all commercial rather than technical.

You quote from facts. When you know the age, the model, the last four faults and what was replaced in 2022, you price the work properly. The contractor quoting blind is either guessing high and losing, or guessing low and eating it.

You win the conversation about next year. “That compressor is nine years old and it’s tripped twice this summer — here’s what I’d budget for” is a different conversation from “let us know if anything breaks”. It moves you from supplier to advisor, and advisors don’t get re-tendered every year.

You survive the disputes. Photos, times, parts and a signature attached to the job settle the “that’s not what we agreed” conversation before it starts.

There’s a fourth benefit that only shows up when something goes wrong: compliance and warranty. When a manufacturer wants proof the unit was serviced to schedule, or an insurer wants evidence of the last inspection, the business that can produce a dated record with photos attached settles it in an email. The business that can’t spends a fortnight reconstructing it from memory and bank statements.

Why most registers never get built

Not because anyone disagrees with the idea. Because building one as a project is miserable — a spreadsheet, a fortnight of someone’s life, and it’s out of date the month after it’s finished.

The registers that work are the ones that build themselves. Every visit adds to the record because the tech is standing in front of the unit anyway. Photograph the asset plate, capture the model and serial, note what was done. Four seconds a visit, and after a year you have something no competitor can produce.

Keep the capture list short or it won’t happen. Model and serial off the plate, a photo of the plate itself, location on site, and what was done today. That’s it. Anything longer and techs start skipping fields — and a register with holes in it is worse than none, because you stop trusting it, and once you stop trusting it you stop looking.

The one habit worth enforcing: photograph the plate before you touch anything. Four seconds while you’re standing there, and it saves the phone call eighteen months later when someone needs a model number to order a part.

“That’s for the big facilities contracts, not us”

We hear this from businesses with twenty techs who are, in practice, already maintaining a few hundred assets. You don’t need an FM division. You need the last three visits, in one place, before you quote.

And it compounds. Year one it’s useful. Year three it’s the reason you keep the contract when a national comes in under you.

Here’s what that looks like in the room. The customer has two quotes. Yours comes with a list of their twelve critical assets, their age, and a note on the three that will likely need replacing in the next two years. The other one is a price. Even if you’re not the cheapest, you’ve made the decision about risk rather than cost — and you’ve made it hard to switch, because whoever comes next starts from zero.

How it works in TSMPlus

Assets live against the site, jobs attach to the asset, and the tech sees the full history on their phone before they open the plant room door — including offline, which matters in basements and cold stores. Preventative maintenance contracts generate their own jobs against those assets, so the record keeps building whether or not anyone remembers to update it.

Because the register builds itself out of work you’re doing anyway, there’s no project to schedule and nobody spends a fortnight on a spreadsheet. You simply have more history in a year than you have now, and considerably more in three.

Where to start if you’re starting from nothing

Don’t try to back-fill. Pick your ten largest maintenance customers, make asset capture mandatory on every visit to those sites from today, and leave the rest to catch up naturally as work comes through. Within a season you’ll have solid records on the accounts that actually decide your year.

Then use it in front of the customer at least once a quarter — a short note on what you serviced, what you found and what you’d watch. That’s the moment the register stops being an admin task and starts being the reason they renew.

Start the register with your next job. Start a free trial, or book a demo and we’ll show you what a year of asset history looks like in practice.

Live in a week: an honest rollout plan

Live in a week: an honest rollout plan

The question we get asked most often isn’t about features. It’s “how long will this take, and how much of my time is it going to eat?”

The question we get asked most often isn’t about features. It’s “how long will this take, and how much of my time is it going to eat?”

It’s a fair question, and the honest answer is that most software rollouts in this industry go badly for the same two reasons: the business tries to switch everything on at once, and nobody was ever told what week one would actually look like. So here it is — day by day, for a business running around twenty techs.

Before day one: two decisions, one list

You need to decide two things before anyone touches the system. First: which workflow hurts most right now — scheduling, quoting or invoicing? That’s the one you go live with. Second: who owns this internally? One person, usually the operations manager. Not a committee.

Then there’s the list: your customers, your sites, and your active jobs. Most businesses can export that from their accounting system in an afternoon. We do the rest of the data work from there.

Monday: configuration, not training

Day one is us and your operations lead in a room — or on a call — setting the system up around how you already work. Job types, your stages, your invoicing rules, who sees what. This is the part that matters, and it’s the part generic platforms skip: we configure to your process rather than asking you to adopt ours.

Time from your side: about half a day.

It’s worth saying what we do rather than what you do. We handle the data import, the configuration, the accounting integration and the sanity-checking afterwards. What we can’t do is make the decisions — how you want jobs staged, what your invoicing rules are, who’s allowed to change a price. Those need someone from your business in the room, which is why one clear owner matters more than a big committee.

If your process is genuinely unusual — and in HVAC&R and electrical it often is, between site access rules, PO requirements and after-hours rates — this is the day we build around it rather than asking you to change it. That’s the difference between software that sticks and software that gets quietly abandoned in month four.

Tuesday: the office team

Schedulers and admin staff learn the board and the job screen. Two hours, hands on, with real jobs rather than demo data. By the end of the session they’re building jobs faster than they were on the whiteboard — that’s the bar, and if we don’t hit it we keep going until we do.

We start with the jobs already in the diary rather than made-up examples, because the questions people actually have are specific: the customer who wants two POs on one job, the site that needs the same tech every time, the recurring job that has to be split across two months. Answering those in the session is what turns training into confidence.

Expect one person to pick it up in an hour and one person to need a second sitting. That’s normal, and worth planning for rather than pretending everyone learns at the same speed.

Wednesday: the techs

This is the day everyone worries about, and it’s usually the easiest. The mobile app takes about forty minutes to explain, mostly because there isn’t much to explain: here’s your day, here’s the job, here’s the site history, here’s how you sign it off.

Techs aren’t afraid of technology. They’re afraid of software that’s slower than the paper it replaced. If the app doesn’t save them time on the first job, they’ll go back to the docket book and you’ll never get them back — so we design for that first job.

The pitch to the crew is short: you stop writing the same thing twice, you stop driving dockets back to the office, and you stop getting rung at 7pm about a job you did on Tuesday. Framed that way, adoption is rarely the fight people expect.

One thing worth deciding in advance: whether techs capture time as they go or at the end of the day. Both work. Not choosing is what causes the mess.

Thursday: run it in parallel

One day of belt and braces. Jobs go into TSMPlus and the old process keeps running alongside. You’ll find the three or four things nobody thought to mention — the customer who needs two POs, the site that’s technically two sites, the after-hours rate. We fix those on the day.

Parallel running for a single day is deliberate. Run it for a fortnight and you’ll have two half-maintained systems and a team that trusts neither. One day is enough to surface the surprises without letting the old process reassert itself.

Friday: live

Friday you invoice out of TSMPlus. That’s the moment it becomes real, and it’s deliberately the end of week one rather than month three — because the invoicing win is the one everybody in the business feels immediately.

Then you stop. Don’t add modules for a few weeks. Let the new normal settle, then pick the next workflow — purchasing, preventative maintenance, asset registers, project costing.

A realistic month two looks like this: purchasing tied back to jobs so your costing is real, then preventative maintenance contracts generating their own work, then asset registers building themselves off the back of both. Each of those is a couple of hours of setup, not another week.

What actually goes wrong

Three things, in our experience. Dirty customer data that nobody wants to own. A business that tries to switch on eleven workflows in week one. And an owner who delegates it entirely and then changes the rules in week three.

None of those are software problems, which is why we’d rather talk about them before you sign than after.

What it costs you in hours

Add it up: half a day for your operations lead on Monday, two hours for the office team on Tuesday, forty minutes per tech on Wednesday, and a day of mild inconvenience on Thursday. Call it a day and a half of real business time across a week.

Compare that with the number most people carry around in their head — a month of disruption and a system nobody uses. That fear is well earned, but it comes from rollouts that tried to change everything at once, usually with a vendor on another continent.

The other number worth putting next to it is what the current process costs every week. If two people spend an afternoon each chasing dockets and re-keying jobs, that’s a day of wages a week, every week, forever. A day and a half once is not a difficult trade.

And if it does go long — because your data was messier than anyone thought, or a key person was away — you’ll hear it from us early rather than discovering it in week five. Telling you the awkward thing quickly is most of what good implementation actually is.

Ask us for a rollout plan for your business — with dates on it — before you commit to anything. Book a demo, or call 0457 228 884.

Before day one: two decisions, one list

You need to decide two things before anyone touches the system. First: which workflow hurts most right now — scheduling, quoting or invoicing? That’s the one you go live with. Second: who owns this internally? One person, usually the operations manager. Not a committee.

Then there’s the list: your customers, your sites, and your active jobs. Most businesses can export that from their accounting system in an afternoon. We do the rest of the data work from there.

Monday: configuration, not training

Day one is us and your operations lead in a room — or on a call — setting the system up around how you already work. Job types, your stages, your invoicing rules, who sees what. This is the part that matters, and it’s the part generic platforms skip: we configure to your process rather than asking you to adopt ours.

Time from your side: about half a day.

It’s worth saying what we do rather than what you do. We handle the data import, the configuration, the accounting integration and the sanity-checking afterwards. What we can’t do is make the decisions — how you want jobs staged, what your invoicing rules are, who’s allowed to change a price. Those need someone from your business in the room, which is why one clear owner matters more than a big committee.

If your process is genuinely unusual — and in HVAC&R and electrical it often is, between site access rules, PO requirements and after-hours rates — this is the day we build around it rather than asking you to change it. That’s the difference between software that sticks and software that gets quietly abandoned in month four.

Tuesday: the office team

Schedulers and admin staff learn the board and the job screen. Two hours, hands on, with real jobs rather than demo data. By the end of the session they’re building jobs faster than they were on the whiteboard — that’s the bar, and if we don’t hit it we keep going until we do.

We start with the jobs already in the diary rather than made-up examples, because the questions people actually have are specific: the customer who wants two POs on one job, the site that needs the same tech every time, the recurring job that has to be split across two months. Answering those in the session is what turns training into confidence.

Expect one person to pick it up in an hour and one person to need a second sitting. That’s normal, and worth planning for rather than pretending everyone learns at the same speed.

Wednesday: the techs

This is the day everyone worries about, and it’s usually the easiest. The mobile app takes about forty minutes to explain, mostly because there isn’t much to explain: here’s your day, here’s the job, here’s the site history, here’s how you sign it off.

Techs aren’t afraid of technology. They’re afraid of software that’s slower than the paper it replaced. If the app doesn’t save them time on the first job, they’ll go back to the docket book and you’ll never get them back — so we design for that first job.

The pitch to the crew is short: you stop writing the same thing twice, you stop driving dockets back to the office, and you stop getting rung at 7pm about a job you did on Tuesday. Framed that way, adoption is rarely the fight people expect.

One thing worth deciding in advance: whether techs capture time as they go or at the end of the day. Both work. Not choosing is what causes the mess.

Thursday: run it in parallel

One day of belt and braces. Jobs go into TSMPlus and the old process keeps running alongside. You’ll find the three or four things nobody thought to mention — the customer who needs two POs, the site that’s technically two sites, the after-hours rate. We fix those on the day.

Parallel running for a single day is deliberate. Run it for a fortnight and you’ll have two half-maintained systems and a team that trusts neither. One day is enough to surface the surprises without letting the old process reassert itself.

Friday: live

Friday you invoice out of TSMPlus. That’s the moment it becomes real, and it’s deliberately the end of week one rather than month three — because the invoicing win is the one everybody in the business feels immediately.

Then you stop. Don’t add modules for a few weeks. Let the new normal settle, then pick the next workflow — purchasing, preventative maintenance, asset registers, project costing.

A realistic month two looks like this: purchasing tied back to jobs so your costing is real, then preventative maintenance contracts generating their own work, then asset registers building themselves off the back of both. Each of those is a couple of hours of setup, not another week.

What actually goes wrong

Three things, in our experience. Dirty customer data that nobody wants to own. A business that tries to switch on eleven workflows in week one. And an owner who delegates it entirely and then changes the rules in week three.

None of those are software problems, which is why we’d rather talk about them before you sign than after.

What it costs you in hours

Add it up: half a day for your operations lead on Monday, two hours for the office team on Tuesday, forty minutes per tech on Wednesday, and a day of mild inconvenience on Thursday. Call it a day and a half of real business time across a week.

Compare that with the number most people carry around in their head — a month of disruption and a system nobody uses. That fear is well earned, but it comes from rollouts that tried to change everything at once, usually with a vendor on another continent.

The other number worth putting next to it is what the current process costs every week. If two people spend an afternoon each chasing dockets and re-keying jobs, that’s a day of wages a week, every week, forever. A day and a half once is not a difficult trade.

And if it does go long — because your data was messier than anyone thought, or a key person was away — you’ll hear it from us early rather than discovering it in week five. Telling you the awkward thing quickly is most of what good implementation actually is.

Ask us for a rollout plan for your business — with dates on it — before you commit to anything. Book a demo, or call 0457 228 884.

The hidden cost of the paper job sheet

Nobody in this industry loses a job on purpose. They lose it in the gap between a tech finishing at 4:40pm and someone in the office typing it up on Thursday. The docket is in the ute. The ute is at the next site. By the time it lands on a desk, the tech has done six more jobs and can’t remember whether the second contactor went on that unit or the one across the roof.

Everyone knows the paper is a problem. What most businesses have never done is add up what one missing docket actually costs. So let’s do it properly. There are four places a job leaks, and each of them has a number attached.

Leak one: the day nobody can see

Start with the whiteboard. If the schedule lives on a wall, only the people in that room know what today looks like. A breakdown call comes in at 9:15 and the person answering the phone has to guess who’s closest, who’s free, and who’s already running late. They ring two techs to find out. Both of them stop work to answer.

Two interruptions is fifteen minutes across three people. Do that four times a day and you’ve spent the better part of a technician’s afternoon co-ordinating instead of fixing. The cost isn’t the phone call — it’s the job you couldn’t fit in because nobody could see the space.

There’s a quieter cost underneath it. When the person dispatching can’t see the whole day, they send whoever answers rather than whoever is right. The apprentice goes to the site that needed the refrigeration ticket. Someone drives across town past two techs who were closer. None of that shows up as a loss — it shows up as a business that feels busy and isn’t as profitable as it should be.

Leak two: the same job, typed four times

Count the keystrokes on a single service call in most businesses. The job gets written on a docket. The docket gets typed into a spreadsheet or a scheduling tool. The parts get entered again when the supplier invoice arrives. Then the whole thing gets re-entered into the accounting system to raise the invoice.

Four entries, four chances for a number to change. And every one of them is admin time you’re paying for but can’t bill.

The parts are the worst of it. A tech grabs two contactors off the van, notes them on the docket, and the supplier invoice arrives eleven days later under a different description. Somebody has to match them up. When they can’t — and often they can’t — the parts either get missed off the invoice entirely or get charged to an overhead account, and your job costing quietly stops meaning anything.

The re-keying also sets your invoicing speed. You can’t send what hasn’t been typed up, and nobody types up dockets on a Friday afternoon.

Leak three: the invoice that went out nine days late

Here’s a test worth running this week. Pick ten completed jobs from last month. Write down the day the work finished and the day the invoice was sent. Average the gap.

Most service businesses we meet are somewhere between seven and fourteen days, and they’re surprised by it — the office feels busy, so it feels fast. But every day in that gap is your money funding somebody else’s business, and the payment terms don’t even start until the invoice lands. A nine-day internal delay on 30-day terms is really 39-day terms.

Worse, a late invoice is a disputed invoice. The further you get from the job, the more likely the customer queries a line they’d have accepted on the day.

And an invoice you can’t evidence is an invoice you discount. Once a customer challenges three hours of labour on a job from a fortnight ago, the conversation is no longer about the work — it’s about whose memory is better. Most businesses write it off to keep the relationship, which is a decision made silently, one job at a time.

Leak four: the history that walked out the door

This is the expensive one, and it doesn’t show up on any report. When a tech with fifteen years on the tools retires, everything he knew about the plant room at that shopping centre goes with him — unless it was written down somewhere findable.

Paper does get filed. It just doesn’t get found. And so you send someone new to a site with no model numbers, no fault history, no note about the isolator that’s in a stupid spot. They spend the first hour discovering what you already knew.

It shows up in tendering too. When a contract comes up for renewal and you can’t produce a service history, you’re bidding on price against people who also can’t produce one. The customer has no way to tell you apart, so they choose the cheapest. Your fifteen years of knowledge about that building was worth something — it just wasn’t written down anywhere you could hand over.

It’s not the paper. It’s the handoffs.

Notice that none of the four leaks are really about paper. They’re about work changing hands. Tech to office. Office to accounts. Accounts to customer. Every handoff is a place where something waits, and waiting is where the money goes.

Which is why replacing dockets with a PDF form doesn’t fix much. The fix is having one record of the job that everyone works from — the tech on site, the person scheduling, the person invoicing. Not four copies of it in four systems.

That’s what TSMPlus does, and it’s the whole reason we build it the way we do: easy enough that the tech in the van actually uses it, and quick enough to set up that you’re not still implementing it at Christmas.

Want to see what your four leaks look like? Book a 20-minute demo and bring one real job with you — we’ll walk it through the system end to end. Or ring us on 0457 228 884 and talk to someone who’s worked in this industry for 30 years.

5 Scheduling Mistakes Costing Australian HVAC Businesses Money (and How to Fix Them)

Ask any HVAC business owner where their day goes, and “sorting out the schedule” is usually near the top. Scheduling feels like admin, but it’s actually one of the biggest levers on your profit. Get it right and your techs do more billable work with less driving. Get it wrong and you’re paying wages for windscreen time, fielding angry calls, and watching invoices slip.

Here are five scheduling mistakes we see again and again — and how to fix each one.

1. Running the schedule out of your head (or a whiteboard)

When the schedule lives in one person’s memory or on a board in the office, only that person can answer “who’s free this afternoon?” The moment they’re on the phone, sick, or on holiday, everything stalls. Worse, the field has no idea what’s changed.

The fix: Move scheduling into a system everyone can see. With a live scheduling board, the office assigns jobs and the tech sees the update instantly on their phone — no phone-tag, no double bookings.

2. Ignoring travel time and location

Sending your northside tech to a southside job because they “had a gap” looks efficient on paper and costs you an hour of unpaid driving. Multiply that across a week and a team, and it’s real money.

The fix: Schedule by location and skill, not just by who’s free. Group jobs in the same area and send the closest qualified tech. Tighter runs mean more jobs per day.

3. Treating every job like it takes the same time

Booking jobs back-to-back without realistic durations is how you end up running 90 minutes behind by lunch — and apologising to every customer after that.

The fix: Use job history. If a particular service or site type always runs long, your system should remember that and block the right amount of time automatically.

4. No buffer for the inevitable

Emergencies, parts that aren’t on the van, a job that’s bigger than quoted — these aren’t surprises, they’re Tuesdays. A schedule with zero slack collapses the first time reality intervenes.

The fix: Build in buffer slots and keep one tech loosely held for urgent call-outs. When nothing blows up, that capacity becomes catch-up or preventive maintenance.

5. The schedule and the invoice living in different worlds

If a completed job has to be re-typed before it can be invoiced, you’ve added a delay between doing the work and getting paid — and a chance for errors to creep in.

The fix: Connect scheduling, job completion, and invoicing. When the tech closes the job on their phone, the office can invoice the same day. Faster cash flow, fewer mistakes.

The bottom line

None of these fixes require working harder — they require a system that does the remembering for you. That’s exactly what TSMPlus was built to do for HVAC&R and electrical businesses: easy to set up, easy for your team to actually use, and backed by a real Australian support team when you need a hand — not an email-only queue.

Want to see it on your own jobs? [Book a quick demo][LINK].

Going Paperless in 2026: The Complete Digital Compliance Checklist for Australian HVAC and Electrical Contractors

Compliance documentation is the unglamorous backbone of every HVAC and electrical contracting business in Australia. It is not the reason you got into the trades. But it is an increasingly significant reason that contracts are won and lost, audits are passed and failed, and businesses thrive or face regulatory consequences. In 2026, if you are still managing compliance on paper, you are carrying risk that your competitors who have gone digital are not.

The Compliance Obligations You Cannot Afford to Ignore

Australian HVAC and electrical contractors operate within a dense and growing framework of regulatory obligations. Safe Work Australia’s SWMS requirements mandate documented risk assessments for high-risk construction work. The Electrical Safety Act imposes testing, inspection, and documentation obligations on electrical contractors. Australian Refrigerants obligations under the Ozone Protection Act require documented evidence of refrigerant handling and disposal. And individual state and territory licensing bodies have their own inspection and certification requirements.

The compliance landscape for a contractor operating across multiple states is genuinely complex. What has changed in recent years is the level of scrutiny — from regulators, from commercial clients, and from insurers — around the quality and completeness of that documentation.

What a Compliance Gap Actually Costs

The consequences of compliance failures exist on a spectrum. At the lower end, a missing SWMS or an incomplete test record creates an admin problem — you spend time tracking down documentation that should already exist, and the gap creates anxiety during an audit.

Further up the spectrum, compliance gaps directly cost you money. A commercial client whose facilities manager discovers incomplete service records may put your maintenance contract out to tender. An insurer reviewing a claim may challenge your coverage if documentation of maintenance history is absent or inadequate.

At the serious end, a regulatory investigation following a workplace incident will examine your compliance documentation in detail. If that documentation does not exist, or exists in a form that cannot be verified, the personal liability implications for business owners are severe.

The 7 Compliance Documents Every Job Should Have

Safe Work Method Statement (SWMS) — required for all high-risk construction work. Must be specific to the task, reviewed by workers before starting, and stored as a permanent record.

Electrical test records — for all electrical work, test results must be documented with readings, equipment identification, and technician credentials.

Refrigerant handling records — documentation of all refrigerant used, recovered, and disposed of, as required under Australian Refrigerants and Ozone Protection legislation.

Risk assessment documentation — identification of hazards, assessment of risk levels, and documented controls, specific to each job site and task.

Safety inspection checklists — pre-start safety checks for equipment and work areas, completed and signed before work begins.

Certification and licence records — documentation that the technicians performing the work hold the required licences for the work type and jurisdiction.

Client sign-off and service reports — completed job documentation provided to the client and retained on the business records, confirming what work was performed and the outcome.

How TSMPlus Builds Compliance Into Every Job

The most effective compliance systems are ones that make compliance the path of least resistance — not an additional burden on top of doing the work. TSMPlus achieves this by embedding compliance documentation directly into the job workflow.

When a technician opens a job in TSMPlus on their mobile, the relevant compliance checklists, SWMS requirements, and safety documentation are already attached — automatically generated based on the job type, asset category, and site requirements. Completing them is part of closing the job, not a separate administrative task.

Test results are entered directly into the mobile app and immediately linked to the asset record. Photos of completed work, signed client acceptance documents, and compliance certificates are captured on-site and stored securely in the job record. Nothing gets lost in transit from the field to the office, because there is no transit — it is all captured in real time.

For business owners and compliance managers, the result is a complete, searchable compliance archive that can be reviewed, audited, or shared with clients on demand. No filing cabinets. No hunting through email attachments. No anxiety about what is missing.

Request a TSMPlus demo at theservicemanager.com and see how Australian HVAC and electrical businesses are making compliance effortless — built into every job, captured in real time, retrievable instantly.

Field Service Scheduling Software: Why Smarter Dispatch Is the Fastest Way to Grow Your Trade Business

The fastest way to grow the revenue of a trade business without hiring another technician is to improve the efficiency of your dispatch process. This is not a marginal improvement. For businesses with more than five technicians, intelligent field service scheduling software can unlock a revenue increase equivalent to having one or two extra technicians on the team — from the same headcount.

Most trade business owners intuitively understand that scheduling could be better. The phone calls to check availability. The WhatsApp messages trying to coordinate who is nearest. The dispatcher working from a whiteboard that is forty minutes out of date. These friction points feel like minor inefficiencies — until you calculate what they actually cost.

The Revenue Hidden in Your Dispatch Process

Consider a business with ten technicians, each completing an average of six jobs per day. That is sixty jobs across the team. Now consider how many of those jobs involve suboptimal routing — a technician driving past a job site to reach another one because the dispatcher did not have real-time location visibility. Or jobs that took two hours but were scheduled for three because the system could not show what was available to fill the gap.

Industry analysis of field service businesses that switch from manual dispatch to intelligent scheduling software consistently shows an improvement of between ten and twenty percent in jobs completed per technician per day. For a ten-technician business at a conservative average job value of two hundred dollars, that improvement is worth between one hundred and two hundred thousand dollars in additional annual revenue. From the same team.

That is not an unusual outcome. It is the predictable result of removing the information gaps that make manual dispatch inefficient.

Scheduling Software vs. Intelligent Dispatch: The Real Difference

Not all scheduling tools deliver the same result. A basic scheduling tool gives your dispatcher a digital calendar to slot jobs into. That is an improvement on a whiteboard, but it does not fundamentally change the quality of dispatch decisions.

Intelligent dispatch — which is what purpose-built field service scheduling software provides — gives your dispatcher real-time visibility over the entire field operation: where every technician is at this moment, what they are currently working on, what skills they have, what parts they are carrying, and what they are available to take next. That information transforms dispatching from a guessing game into a precise operational function.

When a new job comes in, the dispatcher can see immediately which technician is best placed to take it — based on proximity, current job status, skill match, and parts availability. The decision that previously required three phone calls and a map search takes seconds.

5 Ways Smarter Scheduling Directly Increases Jobs Per Technician

Reduced travel time between jobs. When dispatch is based on real-time technician location rather than start-of-day planning, routing becomes dramatically more efficient. Less travel time means more productive hours per technician per day.

Faster job card turnaround. When job details are pushed directly to a technician’s mobile in real time, there is no delay between the dispatcher assigning a job and the technician knowing about it. Jobs start sooner.

Smarter capacity utilisation. Intelligent scheduling identifies gaps in the dispatch board and fills them automatically with jobs that match the available technician’s skills and location. Manual dispatch misses these opportunities constantly.

Reduced rework and second visits. When technicians arrive with complete job information, asset history, and the right parts, they fix the problem correctly the first time. Fewer second visits means more capacity for new jobs.

Better emergency response. When an urgent job comes in, real-time visibility allows you to identify the nearest available technician immediately, without disrupting the entire dispatch board. Emergency response improves without sacrificing planned job completion.

How TSMPlus Scheduling and Dispatch Works

TSMPlus gives dispatchers a live scheduling board that shows every technician’s current status, location, and job queue in real time. Drag-and-drop job assignment is instant. Technicians receive immediate notification on their mobile with all job details — client address, site access instructions, asset history, and required compliance documentation.

When a technician’s status changes — job completed, running late, or parts needed — the dispatch board updates automatically. The dispatcher always has an accurate picture of the field operation, not a snapshot from this morning that is already out of date.

The result is a dispatch process that consistently puts the right technician on the right job at the right time — maximising productive hours across your entire team.

Book a TSMPlus scheduling demo at theservicemanager.com and see exactly how our real-time dispatch board works for Australian trade businesses. The revenue impact of getting this right is immediate and measurable.

What Is Asset Management Software — And Why Every Australian Service Business Needs It in 2026

Asset management software is one of the most searched terms by Australian trade businesses — and one of the least well understood. This article explains exactly what it means in a field service context, why it matters far beyond simple tracking, and how TSMPlus delivers it in a way that directly improves business performance.

Asset Management vs. Job Management: The Difference That Matters

Job management software tracks what your technicians are doing. Asset management software tracks what your technicians are doing it to.

That distinction seems subtle but it has enormous practical implications. A job management system tells you that Technician A visited Client X on Tuesday and spent three hours on site. An asset management system tells you that the commercial refrigeration unit at bay 4 of that client’s site has now been serviced eight times, had its compressor replaced in March last year, is due for its next quarterly service in six weeks, and the last test result showed refrigerant levels within acceptable range.

The second version of that information is what protects your business from compliance risk, what wins you multi-year maintenance contracts, and what prevents the 2 AM call-out that could have been avoided.

What Australian Trade Businesses Actually Need to Track

For HVAC, electrical, and refrigeration businesses operating across multiple client sites, the asset register is the operational backbone of the business. The information that needs to be captured and maintained goes well beyond a simple equipment list:

Location data — which site, which building, which floor, which room. For large commercial clients with dozens of plant rooms, this level of specificity saves technicians significant time on every visit.

Installation and warranty information — when was the equipment installed, what are the manufacturer warranty terms, and when does the warranty expire. Missed warranty claims are a direct financial loss.

Service history — every maintenance visit, every repair, every parts replacement, with dates, technician names, and job notes. This history is what you present to clients as evidence that your maintenance obligations have been fulfilled.

Test results and compliance records — for equipment subject to Australian safety standards, the test results from each service visit are regulatory documents. They must be accurate, complete, and retrievable on demand.

Scheduled maintenance intervals — what service is due, how frequently, and who is responsible for performing it.

The Compliance Angle You Cannot Ignore

For many Australian HVAC and electrical contractors, asset management is not just an operational efficiency question — it is a compliance requirement. Electrical safety standards, refrigerant management regulations, and occupational health and safety obligations all require documented evidence that equipment has been maintained to prescribed standards.

A business that cannot produce accurate, complete asset records on demand is exposed in any audit or investigation. The consequences range from lost contracts to regulatory sanctions, and in serious cases, personal liability for business owners.

Spreadsheets and paper records are not defensible compliance documentation at the level that regulators and commercial clients now expect. A digital asset management system that creates an immutable, timestamped record of every service interaction is the only standard that meets modern compliance requirements.

How TSMPlus Asset Management Works in Practice

In TSMPlus, setting up your asset management system is straightforward. Equipment is registered to a client site using a mobile device — a barcode or QR code scan can pull up an existing asset record instantly, or a new asset can be created in minutes with all the relevant fields captured on the spot.

From that point forward, every interaction with that asset — every service visit, every repair, every test result, every compliance document — is automatically linked to its record. The asset builds its own history over time, without anyone needing to manually maintain a spreadsheet or filing cabinet.

When a technician arrives at a client site, they open the TSMPlus mobile app, scan the asset, and have the complete service history in front of them before they open a panel or touch a control. That context improves diagnostic accuracy, reduces time on site, and increases first-time fix rates — directly impacting your cost per job.

For business owners and managers, the real-time asset dashboard provides visibility across your entire equipment portfolio: what is due, what is overdue, what has been completed, and where compliance gaps exist.

Start your free TSMPlus trial and set up your first digital asset register in under thirty minutes. Visit theservicemanager.com to get started — no credit card required.

How to Build a Preventative Maintenance Schedule That Your Technicians Will Actually Follow

Most preventative maintenance schedules fail within ninety days. Not because the business owner lacks commitment — but because the schedule lives outside the operational system that runs the business day to day. This guide shows you exactly how to build one that sticks.

The businesses that have cracked preventative maintenance at scale share one common characteristic: they did not build a schedule and then try to remember to follow it. They built a schedule that enforces itself — through automated reminders, pre-generated recurring jobs, and a closed-loop system that records every completed service visit against the asset it applies to.

Here is the five-step framework that works in practice.

Step 1: Build a Complete Asset Register

You cannot schedule maintenance for equipment you have not catalogued. The foundation of any preventative maintenance system is a comprehensive asset register — a complete list of every piece of equipment your business is responsible for maintaining.

For each asset, capture: the asset type and model, the installation date, the client site and specific location within that site, the manufacturer’s recommended service interval, the service level your business has contracted to provide, and any regulatory compliance requirements that apply.

For many businesses, this step alone reveals significant gaps. Equipment that was installed years ago and has been maintained informally. Client sites where nobody is sure exactly how many units are on the register. Assets where the service interval has not been reviewed since installation.

A digital asset register — rather than a spreadsheet — gives you a living document that is updated every time a technician interacts with the equipment. Over time, it becomes the most valuable operational record your business has.

Step 2: Set Service Levels by Asset Type and Risk

Not all equipment requires the same maintenance frequency. A commercial refrigeration unit in a food retail environment has a different risk profile and service requirement than an air conditioning system in an office building.

Segment your asset register by equipment type and set service levels accordingly. Consider regulatory requirements — some equipment categories have mandatory inspection intervals under Australian standards. Consider client contract terms — if your maintenance agreement specifies quarterly visits, that is your minimum frequency. And consider the consequence of failure — high-risk equipment in critical environments should be on more frequent schedules.

Document these service levels explicitly. When a technician asks why an asset is scheduled for a particular interval, the answer should be in the system, not in someone’s memory.

Step 3: Build Recurring Job Templates

Manual scheduling is the most common point of failure in preventative maintenance programs. If someone has to remember to create the job, eventually they will not remember.

Recurring job templates solve this. A template defines everything about a maintenance visit: what work needs to be done, what parts are typically required, what compliance documentation needs to be completed, and how long the job should take. When the service interval triggers, the system creates the job automatically, pre-populated with all of this information.

The technician arrives on site knowing exactly what they need to do, with the right tools and parts, and with the documentation requirements built into the job card. There is no ambiguity and no opportunity for the visit to be forgotten.

Step 4: Use Threshold-Based Alerts

Calendar reminders are passive. They appear, get snoozed, and eventually disappear. What you need instead are threshold-based alerts tied directly to your operational system — notifications that trigger when a scheduled job is approaching its due date and has not yet been booked, or when an asset’s service interval has been exceeded.

These alerts should be visible to both the office team and the relevant technicians. They should escalate if not acted on. And they should be logged, so that if a maintenance visit is delayed for any reason, there is a documented record of when the alert was raised and what decision was made.

Step 5: Close the Loop with Asset History

This is the step most businesses miss — and it is the one that makes everything else stick.

Every completed maintenance visit must feed back into the asset record. The date of service, the technician who performed the work, the test results, any parts replaced, any compliance documentation completed. This creates a continuous service history that proves to clients — and to regulators — that maintenance has been performed as required.

It also automatically calculates the next due date, triggering the recurring job creation cycle for the following service interval. The schedule perpetuates itself without manual intervention.

How TSMPlus Handles All Five Steps in One Platform

TSMPlus was built to execute exactly this framework at scale. The asset register, service level configuration, recurring job templates, threshold alerts, and closed-loop history recording are all native features of the platform — not integrations, not workarounds.

From the moment a piece of equipment is registered in TSMPlus, its entire maintenance lifecycle is managed automatically. Technicians in the field get real-time access to asset history on their mobile. The office has complete visibility over what is due, what is overdue, and what has been completed. Nothing falls through the cracks.

See how TSMPlus maintenance scheduling works in practice. Book a demo at theservicemanager.com and let us show you how Australian trade businesses are building maintenance systems that run themselves.