Pool Service · Recurring Rounds
How Do I Run Pool Service Rounds Without the Paperwork?
A pool round generates paper at every step - the run sheet, the docket left on the filter box, the invoice book that gets caught up on Sunday night. AxiomBlue collapses all of it into one system: the run schedules itself, the crew's day lives on their phone, and every completed visit turns into an invoice with a payment link before the ute reaches the next pool.
Quick answerRun the round from one job record instead of three paper systems: recurring series generate every weekly or fortnightly visit on the calendar, the crew works each visit from a phone app, water-test photos attach to the visit's record on site, and an automation invoices each visit the moment it is marked complete. AxiomBlue does all four, from $29 AUD per seat per month with a free plan that has no time limit.
The economics of pool servicing are brutal on admin: lots of small visits, each worth modest money, each dragging its own tail of paperwork. If a visit takes twenty-five minutes and its paperwork takes ten, a third of the business is clerical. Worse, the paperwork is where the money leaks - the visit that never became an invoice, the docket that blew off the passenger seat, the Sunday-night billing session that skipped a street. The fix is not doing the paperwork faster; it is building the round so the paperwork happens as a side effect of doing the work.
- Weekly and fortnightly runs regenerate themselves on the calendar - set each customer once
- The crew's whole day on their phone: visits, history, clock-on, photos - free native apps or any browser
- Water-test and service photos captured poolside, straight onto that visit's job record
- Job Completed → Auto-Generate Invoice: every finished visit bills itself
- Online payment link on every invoice; two-way Xero sync, MYOB sync
| Key facts — pool service rounds in AxiomBlue | |
|---|---|
| Scheduling | Recurring job series — weekly, fortnightly, or any cycle; every visit regenerates itself |
| Crew's day | Free native iPhone and Android apps, plus the full platform in any web browser |
| Service evidence | Water-test and service photos + notes on each visit's own job record |
| Billing | Job Completed — Auto-Generate Invoice template: each completed visit invoices itself |
| Getting paid | Online payment link on every invoice; GST automatic; two-way Xero sync, MYOB sync |
| Safety net | Weekly Unbilled Jobs Report — Friday sweep for completed, uninvoiced visits |
| Seasonal shifts | Fortnightly ↔ weekly is one change to the customer's series |
| Price | From $29 AUD per seat per month; automation on Professional ($59); free plan with no time limit |
How do you run pool service rounds without the paperwork?
You replace the three paper systems a round normally needs - the run sheet, the service docket, and the invoice book - with a single job record that follows each visit from scheduled to billed. In AxiomBlue that looks like: a recurring series generates the visit on the calendar, the technician works it from the phone app, photos and notes attach to the visit's record poolside, and the moment the visit is marked complete an automation raises and emails the invoice. Nothing is written down twice, and nothing waits for the weekend.
AxiomBlue is job management software built in Australia for trade and field-service businesses, and pool servicing is close to the ideal case for it, because the whole business is rhythm: the same pools, the same cycle, the same service, week after week. Rhythm is exactly what software holds better than people. A person keeps forty pools straight on a good week; a recurring series keeps four hundred straight on any week, including the February week when half the crew is new and every pool is green.
The rest of this page walks the round in order - scheduling, the crew's day, the service evidence, and the billing - because the payoff compounds: each stage feeds the next without a human copying anything between them.
How do weekly and fortnightly runs stay on the calendar?
Each customer's service is a recurring job series: created once, with a cycle, and from then on the series regenerates every future visit on the calendar by itself. The Monday northside run is not a laminated sheet in the ute - it is simply Monday's calendar, assembled automatically from every series that falls due, each visit a full job with the customer, the address, the price, and the assigned technician on it.
Changes stay cheap. A customer going away for a month? Skip or move those occurrences; the series keeps its rhythm. A new technician taking over the eastern run? Reassign the jobs. A customer upgrading from fortnightly to weekly for summer? One change to their series. Because each occurrence is an ordinary job on an ordinary calendar, the office rearranges a round by dragging, not by re-planning - and the honest limits are the honest limits of a calendar: the series regenerates scheduled work, it is not a payment subscription or a contract auto-renewal, and stopping a lapsed customer's series is a deliberate one-click decision.
Seasonality is where this pays hardest. In an Australian summer a pool business can double its visit count in six weeks, and paper systems fail precisely then - at maximum revenue and maximum chaos. A calendar built from series absorbs the surge: the extra visits generate themselves, and every one of them still carries the record-keeping and billing described below, no matter how flat-out the fortnight is.
What does the crew see on their phone?
Their whole day, in visit order, with everything each visit needs. AxiomBlue's free native apps for iPhone and Android show the technician today's schedule and each job's details; they clock on and off with GPS, so the timesheet writes itself against the visit; they can see the pool's history - last visit's notes and photos - before lifting the filter lid; and they capture new photos and notes on the spot. Marking the visit complete takes a tap, and as the next section covers, that tap is also the act of invoicing.
Nobody is forced onto an install, either. The full AxiomBlue platform runs in any web browser, including on a phone - so the backpacker who joins the crew for the summer surge can work from a link on day one, and the office desktop runs the same always-current app as the field. For a business that staffs up every November, "new starter productive before morning tea" is not a small feature.
The practical consequence is that the crew stops being a source of paperwork and becomes a source of data. Every tap they make poolside - clock-on, photo, note, complete - lands on the job record in real time, which is what lets the office see the round's progress live instead of reconstructing it from dockets at 5pm.
Where do water-test results and service photos go?
Onto that visit's job record, captured poolside from the app. The technician photographs the test-strip or kit reading, photographs the pool, and adds a note - what was dosed, the filter's condition, the gate that wouldn't latch - before leaving the property. Because every visit in a recurring series keeps its own record, the pool's service history assembles itself: scroll the series and you can see what the water looked like and what was done about it, visit by visit, dated and attributed to the technician who was there.
That history earns its keep in two situations every pool business knows. The first is the callback - "the pool's gone green, you were only here Tuesday" - where the Tuesday photos and dosing note turn an argument into a conversation. The second is the absent customer: most pool servicing happens with nobody home, and a visit that leaves no visible trace invites the quiet suspicion that it didn't happen. The record answers it - and if you want to show a customer, you attach the photos to an email or walk them through the record. That sharing is a deliberate act by you; AxiomBlue doesn't broadcast job photos to customers automatically, which for most pool businesses is exactly the right default.
How does each completed visit bill itself, step by step?
Through a ready-made automation template - Job Completed — Auto-Generate Invoice - that turns the completion tap into the whole billing workflow:
- The visit is marked complete. The technician taps complete in the app at the gate. That status change is the trigger - no office involvement.
- The invoice is created from the job. The automation builds the invoice off the visit's record: the service price, any chemicals or parts logged, GST applied automatically.
- Owners are notified, the customer is emailed. An in-app notification tells the owners the invoice exists; the customer receives the branded invoice by email, payment link included, usually while the ute is still in their street.
Multiply by a round: forty visits this week means forty invoices raised and sent this week, none of them by a person, none of them waiting for Sunday night. The customer pays from their phone off the payment link, and the invoice syncs two-way with Xero (MYOB sync is also available) so the books keep themselves in step. The template's full mechanics - including how to add an owner-review step before sending - are in the automatic invoice generation guide.
And for the visits that somehow dodge the flow - a job completed while the automation was paused, an invoice deleted in a dispute - AxiomBlue's Weekly Unbilled Jobs Report runs every Friday afternoon and lists every completed, uninvoiced job to the owners. On a rounds business with hundreds of small visits, that Friday sweep is the difference between a leak and a rounding error.
Paper run sheets vs a booking app vs AxiomBlue
Three honest ways to run a pool round. The row that decides it for most businesses is the last one - what happens between "visit done" and "money in".
| Paper run sheets + invoice book | Standalone booking app | AxiomBlue Round-native | |
|---|---|---|---|
| Building the weekly run | Rewritten by hand every week | Appointments re-entered per booking | ✓ Recurring series regenerate every visit automatically |
| Crew's day in the field | A printed sheet, out of date by 9am | Times and addresses only | ✓ Full job detail, history, clock-on, photo capture — app or browser |
| Proof the visit happened | A docket on the filter box | A tick in a diary | ✓ Photos + notes on the visit's job record, dated and attributed |
| Summer surge | More paper, more misses | More typing | ✓ One series change per customer; everything downstream scales |
| Visit → invoice | Sunday night, from memory | Separate accounting software, retyped | ✓ Automatic on completion, payment link included, Xero synced |
Can I change how the automation works?
Yes - the invoice automation is a template on a visual drag-and-drop canvas, not a locked setting. Open Job Completed — Auto-Generate Invoice in AxiomBlue's editor and every step is a node you can adjust: reword the customer email, add a delay, or remove the auto-send step entirely so the automation raises the invoice and a person reviews it before it goes out - a popular training-wheels variant for the first few weeks. There is no code; a test mode simulates the workflow before it goes live, and the execution history shows every run afterwards, so "did pool 37 get billed?" is a lookup, not an investigation.
What does automating a pool round cost?
The recurring schedules, mobile apps, photo capture, and invoicing with payment links are all part of AxiomBlue from $29 AUD per seat per month on the Basic plan. The automation engine - including Job Completed — Auto-Generate Invoice, the Friday Weekly Unbilled Jobs Report, and 30+ other templates - is part of the Professional plan at $59 AUD per seat per month, alongside two-way Xero sync. Every plan starts with a free plan that has no time limit, no credit card required: long enough to load one real run, service it for two weeks, and watch every visit bill itself.
Pool Service Rounds — Common Questions
Move the three paper systems - the run sheet, the service docket, and the invoice book - onto one job record. In AxiomBlue, recurring series generate every weekly or fortnightly visit on the calendar automatically, the crew works each visit from the free mobile app, photos and notes attach to the visit's job record on site, and an automation invoices each visit the moment it is marked complete.
As recurring job series. You create each customer's service once in AxiomBlue, set the cycle - weekly over summer, fortnightly through winter - and the series regenerates every future visit on the calendar by itself. Each generated visit is a full job assigned to a technician, so the Monday run is simply Monday's calendar, built without anyone re-entering a single pool.
Their day, in order: today's visits with addresses and job details, the ability to clock on and off with GPS, the customer's history including previous visit notes and photos, and capture for new photos and notes on the spot. AxiomBlue's native iPhone and Android apps are free, and the full platform also runs in any web browser - so a casual summer hire can work from a link without installing anything.
Onto that visit's job record. The technician photographs the test strip or kit reading and the pool itself, and adds notes - chemicals dosed, filter condition, anything the owner should know - from the app while still poolside. Every visit keeps its own record, so a pool's full service history is one scroll: what the water looked like, what was dosed, and who was there, dated and attributed.
Yes. AxiomBlue ships a ready-made automation template called Job Completed - Auto-Generate Invoice. The moment a technician marks the visit complete in the app, the automation creates the invoice from that job's record - service price, any chemicals or parts logged, GST applied - then notifies the owners in-app and emails the customer. Forty visits in a week means forty invoices raised without anyone opening an invoice screen.
From their phone, off the invoice email. Every AxiomBlue invoice carries an online payment link, so the customer can pay the moment the email lands - often before the technician has left the street. Invoices sync two-way with Xero (MYOB sync is also available), so payments and receivables flow into your accounting file without retyping.
The system scales where paper collapses. Switching a customer from fortnightly to weekly is one change to their series, and every generated visit still carries its own record and still bills itself on completion. The failure mode of a paper-run summer - dockets written up days late, visits that never became invoices - disappears, because invoicing happens at the moment of completion, not at the end of an exhausted week.
Recurring schedules, the mobile apps, photos and notes on the job record, and invoicing with payment links are all included in AxiomBlue from $29 AUD per seat per month on the Basic plan. The Job Completed - Auto-Generate Invoice automation is part of the Professional plan at $59 AUD per seat per month. There is a free plan with no time limit, and no credit card is required to start.
Retire the Run Sheet This Summer
Load one round, set the cycles, and service it for a fortnight - every visit scheduled by the series, recorded from the phone, and billed the moment it's done. The Sunday-night invoice session doesn't survive the first fortnight.
No credit card required • Free plan, no time limit • Cancel anytime