Recurring Service Schedule Template
Free recurring service schedule template (Excel): set a cadence per account (monthly, bi-monthly, quarterly, or custom) and the sheet computes each next-due date on a rolling year grid. No signup.
How next-due dates are computed
Set a cadence per account and the sheet counts forward from the last service date to the next-due date, using a fixed interval in weeks:
Monthly = 4 weeks
Bi-monthly = 8 weeks
Quarterly = 13 weeks
Custom = your own number of weeks
next due = last service + interval-in-weeks Week-based intervals give a deterministic, drift-free next-due date (a calendar "month" is anywhere from 28 to 31 days). All four intervals live in one place — the workbook's Settings sheet — so you can retune them once and every account follows.
The rolling year grid answers a different question — "which months does this account get serviced?" — so it uses a calendar rule, not the week interval: monthly marks every month, bi-monthly every other, and quarterly marks the calendar quarters from the anchor month (e.g. a January-anchored account is marked Jan, Apr, Jul, Oct). A custom-weeks account marks whatever months its interval lands in across the year. On-hold accounts keep their row but show no marks.
This is a planning aid, not a system of record. It schedules nothing automatically and sends no reminders — there is no stored account database, no dispatch, and nothing is saved. Everything lives in the file you download.
The cadence you set here is the input to several other questions. Whether a recurring plan beats one-off visits at your prices is tested by the recurring plan comparator; on a facility account the visit frequency feeds straight into the commercial account pricing, which builds the monthly figure from facility type, square footage and how often you show up. Each visit the grid calls for is then recorded in the pesticide application log worksheet, and a day's worth of due accounts is sequenced by the route day planner.
Sources
- Pest Control Service Checklist Template. Connecteam. Retrieved .