Job scheduling software for Australian tradies
Good job scheduling software does one thing brilliantly: it puts customer work in front of the right person at the right time, and keeps that plan honest when Tuesday falls apart at 9:40am. Opsler gives you a drag-and-drop diary of booked and unbooked jobs, assignment and reassignment in one gesture, and a warning the moment two jobs land on the same tradie at the same time — before two customers are waiting.
It is scheduling software for tradies in the field-service sense: a customer job diary, connected to the quote, the scope and the invoice behind every booking. Route optimisation is in the same plan rather than sold as an add-on, at $25 a seat with no minimum — and the first two seats are free, permanently.
- 2 seats
- free, no expiry
- 50 jobs
- a month on free
- $25
- per seat, per month
- 30 days
- of recurring work ahead
What job scheduling software means in field service
Ask what is job scheduling software in a field-service context and the useful answer is: a list of commitments to customers, not a list of hours. Each entry has an address, a person, a time and an agreed scope of work behind it. That last part is what separates field service scheduling software from a shared calendar. A calendar entry says “9am, Beach Road.” A scheduled job says 9am, Beach Road, hot water system replacement, quoted at $1,840 and approved on Tuesday, previous visit November, gate code on the customer record.
The payoff is two things you can feel in a week. Whoever turns up already knows what they agreed to do, so the first ten minutes on site are work rather than phone calls. And the office answers a customer without ringing the van, which is the single biggest interruption in a small trade business.
Here is a fast way to size up any product in this category: ask how a job exists before it has a time. If the only way to create work is to drop it in a slot, you are looking at a calendar with extra fields. If work can sit in a queue waiting to be scheduled, it was built for field service. Opsler was built for field service.
Job scheduling versus employee rostering and IT schedulers
Three genuinely different products compete for this search term, and buying the wrong one costs a fortnight. Thirty seconds here saves it.
Field-service job scheduling — this page
A diary of customer jobs, built around addresses, scopes and commitments. It answers “who is at which customer, when, doing what, and what did we quote them.” This is what Opsler does, and it is the whole product rather than one module of a suite.
Employee rostering and workforce management
Shift patterns, availability, leave, award interpretation, clock-in and clock-out, timesheet approval feeding payroll. Built around people rather than customers, and a separate category of software with its own bill. Running a job diary as a roster is how someone ends up booked on their day off; running a roster as a job diary is how you lose the record of what you promised.
IT and batch job schedulers
A completely different industry: software that triggers automated tasks on servers at set times. A job scheduler in that sense shares two words with this page and nothing else. If a result mentions workflows, pipelines or server tasks, that is what you have found.
The self-test: if the thing you are scheduling has a customer attached to it, you want the first one, and you can have it running this afternoon.
Capture unscheduled work before choosing a time
Most jobs are agreed before they are booked. A customer accepts a quote on Tuesday and wants the work “sometime in the next fortnight.” A landlord rings about a leaking tap and you need a part first. Force a date at creation and both become guesses in a calendar nobody trusts by Friday.
In Opsler a job exists without a time. Accepted quotes convert straight into jobs that sit in the unscheduled column of the dispatch board with the customer, the address and the agreed scope already attached — visible, countable, and impossible to forget about. When you are ready, drag it onto a day and a tradie and it is booked.
That unscheduled column is quietly the most valuable number on the board: work you have already won and not yet delivered. A Perth plumbing business with eleven jobs sitting there knows something a business with an empty diary and a full inbox does not — and knows it without building a spreadsheet on Sunday night.
View the team diary and job capacity
One screen answers “can we fit this in Thursday?” The dispatch board shows the team’s committed work across days and technicians with the unscheduled queue beside it, so the answer takes a glance instead of three phone calls.
Capacity in a trade business is not a spreadsheet calculation — it is whether Dave can realistically do four hot water services and still reach Fremantle by three. What the diary gives you is the visibility to make that call fast: what is committed, to whom, and what is queued behind it. The judgement stays with the person who knows how long a switchboard upgrade actually takes, which is exactly where it belongs.
Be precise about what this view measures: capacity in committed customer work, not in rostered hours. A roster answers who is available on Thursday. This board answers who is already promised to a customer on Thursday, at which address, and what they agreed to do when they get there. That is the whole difference between field-job scheduling and employee rostering, and it is why the two sit in different systems.
Access follows role. A tradie sees their own work; the office sees the whole board. That is the difference between a field team who open the app and know the next job, and one scrolling past everyone else’s work looking for their own.
The free Budding plan covers two seats — one admin and one technician, 50 jobs a month — which is enough to run the board properly before you pay anything. Scheduling starts earning real money at three or four people, and that is $25 per seat per month with no minimum and no tier above it. Your fifth tradie costs the same as your second.
Assign and reassign a customer job
Assignment is a drag. Move an unscheduled job onto a technician and a day and it is booked. Reassignment is the same movement to a different name, and the job takes its customer, address, scope, notes and history with it — nothing is retyped, so nothing is lost in the handover. Covering a sick day takes about four seconds per job.
The assigned technician is notified when work lands on them. One deliberate exception worth knowing: jobs generated by a recurring series arrive quietly, without an individual assignment notification, because a quarterly series across forty customers would otherwise fire forty notifications in one overnight run. They appear on the board normally — they just do not wake anybody up.
You choose who goes. There is no skills-based automatic dispatch weighing You choose who goes, which at four or ten technicians is exactly right: the person doing the dispatching already knows which of them you would send to a difficult customer in Fremantle, and no board should pretend to know that better. Opsler gives them a clear picture to decide from and then gets out of the way.
Handle conflicts, cancellations and field changes
Days do not survive contact with reality. Three things go wrong repeatedly, and how a product handles them tells you more than its feature list ever will.
Double-booking
Assign a technician two overlapping jobs and Opsler surfaces the clash rather than letting it through quietly. You find out while you can still fix it, not when two customers are waiting. This earns its keep most on the Monday morning where two people are dispatching at once and the office books a call-out into a slot someone already filled.
Cancellations and reschedules
A cancelled job returns to the unscheduled queue instead of vanishing, so the commitment survives the change of date and gets rebooked rather than forgotten. A rescheduled job moves with its full history attached. The record of what was agreed never depends on when it was agreed to happen.
Changes made from site
Status moves as the day does — en route, on site, complete — so the office watches a job run long without ringing to ask. Notes and photos added on site are on the record before the technician has left the driveway.
How the customer hears about a change
Move a job and the customer gets an email with a link straight to their own job — no account, no password, no app to download for a tradie they will use twice. Every step you remove between a customer and the information costs you fewer phone calls, and it costs you nothing per message.
Plan repeat work without inventing automation
Recurring job series handle the work that repeats on a known rhythm — a quarterly filter change, a six-monthly service, a fortnightly clean. Set the interval once and occurrences generate automatically up to 30 days ahead on a daily refresh, landing on the dispatch board like any other job. That is contracted revenue turning itself into scheduled work while you sleep.
Three specifics, because this is exactly where vendors describe more than they do.
- The interval is fixed, not adaptive. A quarterly series generates on the calendar rule you set. If the March visit actually happened in April, the June occurrence stays in June rather than drifting a month later every year. It is a schedule you can plan a year of capacity around.
- The horizon is 30 days. You see the next month of generated work, not the next two years, which keeps the board readable and stops a long series filling your diary with speculative bookings.
- It comes with the Pro plan. Recurring series sit alongside route optimisation and the accounting export in the same $25 seat.
This is calendar-driven repeat work, not condition-based or predictive scheduling. Nothing raises a job because a meter reading crossed a threshold or an asset is due by usage hours — that is maintenance-management territory, built around an asset register rather than a customer diary. For the overwhelming majority of Australian trade businesses, the calendar rule is the one that gets used.
Where job scheduling starts paying for itself
A diary that only records the day is worth about what a whiteboard is worth. Three things turn it into money, and they are the three worth testing on anything you shortlist.
Route optimisation
Included with the Pro plan. Give Opsler the day’s work and it puts the stops in a sensible order, so the ute stops crossing the same three suburbs and the appointment you already promised stays where you promised it. The hours that were disappearing between jobs come back as capacity.
Do the arithmetic on your own numbers. One extra job a week, at whatever your average ticket is, covers a small team’s seats several times over — and it needs no new customers, no advertising and no extra van.
The office knowing without ringing
On the way, arrived, done. The job moves on the board as the technician moves, so a customer asking at half past two where he is gets a real answer from whoever picks up rather than a promise to find out and call back. It also settles the “what time did we actually get there” question weeks later, which is the question a disputed call-out fee turns on.
The day finishing on site
Basement car parks, plant rooms, a shed an hour off the highway. With no signal at all a technician still opens the job they were assigned, works the checklist, takes the before and after photos, writes the notes, moves the status, gets the customer to sign, raises the invoice and records the payment. It holds on the device and syncs itself the moment coverage returns.
That is the difference between a job that is finished when the ute pulls away and one written up three days later by someone who has been on four other sites since — which is how work gets done and never gets billed.
Job scheduling software evaluation checklist
11 claims, and exactly where Opsler lands on each. Take this list into your next demo and ask for the same 11 answers in the same words. Compare those, not the marketing — most vendors will not commit this much to paper.
| Claim | Opsler | Detail |
|---|---|---|
| Drag-and-drop team diary | Booked and unscheduled jobs in one view | |
| Unscheduled work queue | A job can exist before it has a time | |
| Assign and reassign to a technician | Same gesture in both directions, four seconds a job | |
| Double-booking detection | The clash surfaces while you can still fix it | |
| Recurring job series | Contracted work books itself 30 days ahead — Pro plan | |
| Route optimisation | The day's stops in a sensible order, so less of it goes on driving — Pro plan | |
| The day's progress visible from the office | On the way, arrived, done — without ringing a van | |
| The whole job finished with no signal | Checklist, photos, notes, signature, status, invoice and payment | |
| Customer access with no account | A link to their own job — no login, no password, no app | |
| GST applied per line on every invoice | Set the rate once, mark it default, and it lands on everything | |
| Free for two people, permanently | 50 jobs a month and unlimited customers before anyone pays |
Book Thursday properly, starting this afternoon
Load next week onto the board and break it on purpose — that is the only test that matters, and it costs nothing. The Budding plan runs 1 admin and 1 technician with 50 jobs a month, unlimited customers and 21 core features, permanently. From the third person it is $25 a seat with no minimum, and nothing is held back for a bigger plan: the recurring series, route optimisation and the accounting export all sit in that one number. The 14-day Pro trial asks for no card.
Job scheduling software puts customer jobs in front of the right person at the right time and keeps that plan honest as the day changes. In field service specifically, it runs a diary of customer visits — booking work in, assigning it to a technician, moving it when a job runs long, and showing the office where everyone is committed without anyone ringing a van. It is not the same as employee scheduling software, which manages shifts, awards and availability, and it has nothing to do with the IT sense of the term, where a job scheduler runs automated tasks on a server. All three turn up in the same search results, which is why the distinction is worth thirty seconds before you shortlist anything.
They answer different questions. A roster answers "who is working on Thursday." A job diary answers "who is at 42 Beach Road at 9am on Thursday, and what did the customer agree to." A roster is built around people, availability, shift patterns, award conditions and leave. A job diary is built around customer commitments, each attached to an address, a scope of work and a price. Most small trade businesses eventually run one of each, and the expensive mistake is using one as a substitute for the other — either you have a beautifully rostered team with no record of what they promised customers, or a full diary that has quietly booked someone on their day off. Opsler is the diary, and it is very good at being the diary.
Opsler's does. Route optimisation comes with the Pro plan: give it the day's work and it puts the stops in a sensible order, so the ute stops crossing the same suburb three times and the hours you were losing between jobs turn back into jobs. Appointments you have already promised stay where you promised them. The office also sees the day move without ringing a van — on the way, arrived, done — so whoever picks up the phone can tell a customer when someone is coming instead of promising to find out. Both are in the $25 seat rather than sold as an add-on, which matters because one extra job a week at your average ticket covers a small team's seats several times over.
Ready to Run Your Business Without the Chaos?
Scheduling, dispatch, estimates, invoicing, customer portal, and a free branded website — start completely free, upgrade to Pro when you scale.
Free forever on the Budding plan. No credit card required.