Ask a pest control owner what their most valuable asset is and you will usually hear about the trucks, or the route, or the crew. Almost nobody says the renewal book. Yet for most companies doing termite work, the file of active bonds and treatment warranties represents more predictable annual revenue than any single route, and it requires no marketing spend to keep. It just requires knowing what is in it and when each piece expires.
That last part is where it falls apart. A termite bond written in 2019 is a folder in a cabinet, an entry in an old spreadsheet, or a line in a system nobody queries. The renewal notice goes out when somebody thinks of it, which is usually after the anniversary. Some percentage of customers do not renew simply because nobody asked them clearly and on time, and the loss never appears as a line item anywhere. It shows up two years later as a route that feels thinner than it used to.
As of August 2026, this is still the most common quiet leak in pest control operations. Nothing about fixing it is complicated: a warranty is a dated record, renewal is a scheduled and invoiced event, and renewal rate is a number you can watch monthly. This guide covers how to structure the record, what actually decides a disputed claim, how to run renewal outreach as segmentation instead of a call list, and what happens to a company when the book is left to expire on its own.
A bond is a dated asset, not a folder
The mental shift that makes everything else work is treating each agreement as a queryable record rather than a document. A document is something you retrieve when you already know it exists. A record is something the system can hand you a list of.
A workable warranty record carries, at minimum:
- The property and the structure covered. A bond on a house is not a bond on the detached garage the customer assumed was included. Ambiguity here is where claims turn ugly.
- Start and end dates. Explicit, not inferred from a treatment date somebody has to look up.
- The obligation. Re-treat only, re-treat plus repair, annual inspection included, or whatever you actually sold. In your own plain words.
- The renewal fee and terms. So the invoice can be generated without a decision.
- The treatment history behind it. Date, product used, application locations, the technician who did the work.
That last item is not decoration. It is the difference between a warranty you can defend and a warranty that is really just a promise. Warranty tracking for service businesses is a general discipline, but termite work is where it earns the most, because the obligations are long-lived and the claims arrive years after the technician who did the work has moved on.
Once records look like this, the operationally important question becomes trivial: what expires in the next 60 days? That query is the entire renewal program. Everything else is execution.
The property record is what decides a disputed claim
Every termite company has had the phone call. A customer with a bond reports activity, and the conversation immediately turns on facts nobody can produce. Was the addition covered? What did we apply, and where? When was the last inspection, and did we note conducive conditions the customer never fixed?
If the answer to those questions lives in a technician's memory, you will lose the argument even when you are right, because the customer's memory is confident and yours is not. If the answers live in the record, the call takes four minutes.
What makes a record decisive is boring specificity: the structure as it existed at treatment, the date, the product and application points, the technician, and photos taken on completion. That is also the same data that supports internal chemical and product usage tracking, so the effort is not additional work; it is the same capture used twice.
Being honest about the economics helps here. A re-treat is not free. It is a truck, a technician, product, and a slot on the schedule that a paying job could have occupied, plus the follow-up inspection. Companies that carry thin documentation end up absorbing re-treats they did not actually owe, simply because contesting a claim without evidence costs more in goodwill than the treatment costs in labor. The documentation is what lets you say yes to legitimate claims quickly and decline the rest without a fight.
Renewal is a scheduled, invoiced event
The most expensive assumption in this whole area is that renewals happen because somebody remembers them. They do not. They happen because an invoice goes out on a schedule with a way to pay attached.
Structurally, the renewal should behave like any other recurring billing: generated on the agreement's anniversary window, itemized so the customer understands what they are buying, and delivered with a payment link they can settle from a phone. Treating renewals as ordinary pest control invoicing rather than a special annual project is what removes the human failure point.
The timing of the ask matters more than the wording. An invoice that arrives two weeks after the anniversary reads as an afterthought, and it invites the customer to reconsider whether they need the coverage at all. An invoice that arrives before expiration, following a reminder they already saw, reads as continuity. Same product, entirely different conversion.
There is also a cash-flow reason to be strict about this. Intuit's small-business research consistently finds that late and unpaid invoices are among the most common cash-flow problems owners report, and a renewal book billed on memory produces exactly that pattern: a lumpy, unpredictable stream that arrives whenever someone got around to it. Scheduled renewal billing turns the same revenue into something you can forecast.
Renewal outreach is segmentation, not a call list
Most companies run renewals as a call list, which is why most companies run out of energy in March. The work does not scale, so it gets deprioritized, and the book leaks.
The alternative is to treat the expiring cohort as a segment and touch it in tiers:
- Sixty days out, email or SMS the whole segment. One message, one clear renewal amount, one link to pay. Most renewals need nothing more than this.
- Thirty days out, message the non-responders. Shorter, plainer, same link.
- Inside thirty days, call the remainder. Now your calling time goes only to accounts that genuinely need a human, which is usually the ones with claim history or a pricing question.
- After expiration, run a short win-back. A lapsed bond is still a warm customer with a known structure and a known treatment history.
This is where a self-service path earns its keep. A customer portal that lets a homeowner check their coverage and pay online removes the phone tag that eats the office's spring. It also handles the customer who wants to renew at 9 p.m. on a Sunday, which is a larger group than most owners expect.
The segmentation itself depends on having the dates in a queryable place, which loops back to the record structure. You cannot message an expiring cohort you cannot list.
Measuring the renewal rate
Renewal rate is the number that tells you whether the book is compounding or bleeding. Compute it plainly: renewals collected divided by agreements that came up for renewal in the same window. Then cut it two ways that actually change decisions.
Cut it by origination year, and you will see whether older bonds churn faster than recent ones, which usually says something about how the coverage was explained at the point of sale. Cut it by the technician or branch that wrote the agreement, and you will see whether one person is selling coverage customers do not understand and therefore do not renew. Both cuts are available for free once the agreement record carries who sold it.
Watch it monthly, because slow leaks are invisible at any single point. A book losing eight percent a year looks perfectly healthy every month and is a materially smaller business in five years. The monthly view is what makes that visible while it is still cheap to fix.
Here is how the three common approaches to a renewal book compare:
| Paper folders and memory | Spreadsheet of expirations | Warranty records in your system | |
|---|---|---|---|
| "What expires in 60 days" | Manual dig through files | Sort a column, if it is current | A query anyone can run |
| Renewal billing | Typed when remembered | Typed from the sheet | Recurring invoice with payment link |
| Claim evidence | Technician's memory | Date only | Structure, product, tech, photos |
| Outreach | Call list, until it stalls | Call list, until it stalls | Segment messaged by SMS and email |
| Renewal rate | Not measured | Counted by hand, sometimes | Reported and cut by year and tech |
| Lapsed accounts | Discovered accidentally | Noticed at year end | A win-back list you can work |
What a lapsed book does to a route
The strategic cost of ignoring renewals is not the individual fee. It is what the erosion does to the shape of the business.
A company with a large active bond book has a reason to be in a neighborhood on a predictable cycle. That is the foundation of route density, which is the single biggest lever on drive time and therefore on gross margin per technician hour. Every non-renewal removes a stop from a route that still costs the same to drive. Lose enough of them across a subdivision and the route stops being a route.
The same erosion changes what the company sells. Recurring coverage and recurring treatment scheduling produce revenue you can staff against months in advance. One-off jobs do not. As the recurring base shrinks, hiring becomes reactive, seasonal swings hit harder, and the owner spends more on lead generation to replace revenue they already had. The U.S. Small Business Administration's guidance on managing business finances makes the general point that stable, predictable revenue is what lets a small business plan rather than react, and a renewal book is about the cheapest predictable revenue a service company can own.
Owners evaluating systems for this should look specifically at how warranties are stored, queried, and billed rather than at the calendar feature set, since that is where the differences actually show up. It is worth seeing how IntelliDrive OS compares against Jobber and ServiceTitan, including where each is the better fit.
Rolling it out
You do not need a migration project. You need the expiring accounts loaded first.
- Load the next twelve months of expirations. Do not start with 2014. Start with what is about to renew, because that is the only cohort where speed pays this quarter.
- Standardize what "covered" means. Write your obligation language once so every new agreement records the same fields instead of freeform notes.
- Turn on recurring renewal invoicing. Anniversary-dated, with a payment link.
- Build the 60/30/call cadence. One SMS template, one email template, one call script. That is the whole program.
- Start reporting renewal rate monthly. Even a rough number beats no number, and it will get more accurate as the record fills in.
- Backfill older agreements as they come up. Every renewal is an opportunity to clean one record properly.
The bottom line
A termite bond is a dated asset with an obligation attached, and it behaves like one whether or not you manage it that way. Managed well, the book renews itself on a schedule, defends its own claims out of the treatment record, and holds the route density that makes every technician hour more profitable. Managed on memory, it expires quietly, a few percent at a time, and nobody notices until the calendar looks thin.
The companies that keep their books intact are not doing anything clever. They know what expires in the next sixty days, they invoice it before it lapses, and they can tell you in one number how much of last year's coverage came back.
Related reading: Pest control route density and profitability · Pest control recurring treatment scheduling · Warranty tracking for service businesses. For a complete machine-readable feature and pricing reference, see our LLM reference page.