The most profitable work is the easiest to lose
Recurring work — the quarterly service, the seasonal tune-up, the standing maintenance visit — is the best revenue in field service. You already won the customer, so there's no acquisition cost. You already know the site, so the job is faster and safer. The customer already trusts you, so there's no selling. Every dollar of recurring revenue is worth more than a dollar of new work because it costs so much less to earn.
And it's the work that goes missing most. The reason is structural, not careless: a recurring job's next instance lives in the future, and "we'll be back in about six months" is a promise that exists in nobody's calendar. It's not on this week's board, so this week ignores it. It's not on next week's board either. By the time anyone would naturally notice, the window has passed, the customer has either called a competitor or simply gone without — and you've lost a renewal you'd already earned, plus the recurring relationship behind it. The repeat visit doesn't get dropped because it's hard. It gets dropped because nothing is responsible for remembering it.
Why the manual reminder always fails
The instinct is to assign the remembering to a person: a spreadsheet of due dates, a calendar nudge, a note to "follow up in Q3." These fail for the same reason every time — they compete with live work and lose. A reminder to schedule a visit three months out will always rank below the customer on the phone right now. So the reminder gets snoozed, then buried, then forgotten, and the recurring job quietly falls off the books. Worse, the spreadsheet rots: techs change, dates drift, and within a year nobody trusts it enough to act on it. Manual tracking of future work is a tax you pay forever and still can't rely on.
The only thing that reliably remembers recurring work is the system that runs the rest of your jobs — because that's the surface everyone is already looking at every day. The repeat visit has to appear on the board on its own, as a real job, at the time it's due, without anyone tracking a date by hand.
Two real ways to make the repeat schedule itself
In Hosting Field, recurring work is handled by making it appear automatically, so it lands in the same place as everything else you're already working:
- Service intervals that auto-spawn. For maintenance work on a fixed cadence — and for the trucks and equipment behind it — you define a service interval, and overdue intervals auto-spawn a draft job with a "due soon" warning. The visit a customer is owed shows up on your dispatch board by itself, flagged as coming due, with no one tracking the calendar. The recurring maintenance program stops depending on memory and starts depending on the system.
- Duplicate the job to repeat it. For repeat work that isn't on a rigid interval — a customer you service whenever they call, a job that recurs but irregularly — you can duplicate a job to stand up the next instance in seconds, carrying its line items, site, and scope forward. You're not rebuilding the job from scratch each time; you're cloning a known-good template of work you've already done at a site you already know.
Either way, the next visit becomes a real job on the board — schedulable, assignable, visible — instead of a promise in someone's head.
Book the next visit before the truck leaves the last one
The single most powerful habit for protecting recurring revenue is to schedule the next instance before the current one ends, while you're still on site and the customer is engaged. A customer who watches you put the next visit on the calendar has effectively renewed on the spot, and a job that's already on the board can't be forgotten. This is also the natural moment to confirm the cadence — "we'll see you again in the spring; you're on the board for it" — which turns a vague intention into a committed service relationship.
When the next job is created on site, the customer also drops into the same lifecycle as any other appointment: they'll get the automatic confirmation and reminder messages as the date approaches, so the recurring visit gets the same no-show protection as a fresh booking. The repeat job isn't a special case you have to manage by hand — it's an ordinary job that happens to recur, running on the same rails as everything else.
Keep the recurring book honest
Two cautions keep auto-recurring work from turning into noise. First, an auto-spawned job is a draft for a reason — it's a prompt to schedule, not a commitment to bill. Someone still confirms the customer wants it before it goes on the calendar, or you'll annoy customers with visits they didn't ask for. The system surfaces the due work; a human still decides. Second, prune dead recurrences. A customer who's moved on or a piece of equipment that's been retired shouldn't keep spawning jobs forever. Review the recurring book periodically so the "due soon" flags you see are real work, not ghosts — because a board full of stale prompts trains everyone to ignore the prompts that matter.
What to measure
- Recurring-visit retention rate — of the recurring jobs due in a window, how many actually got scheduled and done. This is the number that tells you whether your repeat revenue is leaking. If it's well under 100%, you're losing renewals you already earned.
- Lead time on recurring jobs — how far ahead of the due date the next visit gets booked. Visits booked on site before the prior one ends retain far better than ones scrambled together after the window opens.
- Recurring revenue as a share of total — the slice of your revenue that comes from work you'd already won. A healthy, growing share is the signature of an operation that isn't paying to re-acquire the same customers — it's compounding them.
Recurring work is the revenue you've already earned and the easiest to lose, because the next visit lives in a future that no busy week makes room for. Stop assigning the remembering to a person who'll always have something more urgent — let the interval auto-spawn the job, duplicate the ones that don't fit a cadence, and book the next visit before the truck leaves the last one. The repeat revenue you keep is the cheapest revenue you'll ever have.