Guide
The Promise Calendar: keeping every commercial preventive maintenance contract on schedule
McGuire Flanigan · Updated October 21, 2026 · 6 min read
A commercial preventive maintenance contract is a calendar of visits you promised, and the Promise Calendar keeps it: once a week, list every visit that's due or overdue grouped by site, draft each booking with the site contact and access notes, and have your dispatcher approve it before it's booked. Your software can generate the visits, but someone still has to book them. Below is the one-page checklist and the booking message.
The Promise Calendar in three steps
This is the checklist from our video on commercial maintenance contracts. Every contract is a calendar of visits you promised, and the visits that go wrong are usually the ones that never got booked.
- The due list. List every visit that's due or overdue, grouped by site, so a building with four rooftop units shows up as one problem.
- The draft. Draft each booking with the site contact and the access notes.
- The dispatcher's okay. Your dispatcher approves each booking before it's confirmed with the customer.
It's tempting to think your software handles all of this. It handles part. In ServiceTitan, recurring services generate recurring events that appear in the Follow Up screen, where they can then be booked into jobs. Generated is not booked. The Promise Calendar is the weekly check that closes that gap.
Who this is for and what you need first
The Promise Calendar is for HVAC, plumbing and electrical contractors with commercial maintenance agreements: offices, clinics, restaurants, storage, light industrial. A missed visit on one of these contracts isn't a scheduling slip to the customer. It's the exact thing they paid you for.
These agreements carry real money. FieldEdge's overview of service agreement programs puts a basic small commercial plan at about $500 to $1,000 a year and a fuller plan at $1,000 to $2,000, and larger buildings run higher. Prices vary by shop and market; the point is that each visit on the calendar is part of a paid promise.
Before you start, have:
- Every active contract in one list, with the site, the units covered, the visit frequency and the contract dates.
- The visit frequency per contract. If your software supports it, set the recurring visits on the agreement itself. ServiceTitan lets you set recurring visits on a service agreement's Scope of Work step, repeating by day, week, month or year.
- Site details on each location: the facilities contact, check-in point, key or roof access, parking and any hours the building restricts.
- One dispatcher who owns the check, once a week, same day.
1. The due list
Once a week, pull every maintenance visit that's due in the next 14 days or already past due. Then group the visits by site, not by unit. A medical building with four rooftop units is one trip, one contact and one access plan, so it should be one line on your list.
| Site | Units | Visit | Due | Status |
|---|---|---|---|---|
| Harbor Point Medical Plaza (example) | 4 rooftop units | Q4 PM | 12 days overdue | Not booked |
| Elm Street Dental (example) | 2 rooftop units | Q4 PM | In 5 days | Not booked |
| Riverside Self Storage (example) | 1 split system | Fall PM | In 9 days | Not booked |
The rows are examples. Sort overdue first, then by due date. Anything overdue gets booked this week, even if that means calling the site contact instead of waiting on a message.
What about frequency? ANSI/ASHRAE/ACCA Standard 180 sets minimum inspection and maintenance requirements for commercial building HVAC systems, and when it came out, ACHR News described it as the first standard of its kind for HVACR inspection and maintenance. If your contracts don't spell out what each visit covers, the standard is a reasonable place to start that conversation with the customer. The Promise Calendar itself just follows whatever your contract promises.
2. The draft
For each line on the due list, draft one booking. It has everything your tech needs to walk in and everything the site contact needs to say yes.
The booking message (copy and fill in):
Hi Tom, it's Lena at Arctic Air. Your quarterly maintenance for the four rooftop units at Harbor Point Medical Plaza is due. Can we come Tuesday, October 28, with a 7:00 to 9:00 AM arrival? Our tech will check in at security and pick up the roof hatch key at the front desk. If another day works better, just reply with it.
The internal booking note:
- Site and address
- Units and model numbers (from the agreement)
- Visit type (quarterly PM, filter change, coil cleaning, per the contract)
- Date and arrival window
- Site contact and phone
- Access: check-in point, keys, roof or mechanical room access, parking
- Parts or filters to load on the truck
If an AI agent drafts these, it reads the due list and the site records each week, fills in the message and the note for each site, and puts them in the dispatcher's queue. That's the same approval-first setup we use for every agent; the AI agents overview explains how the drafts and approvals fit together.
3. The dispatcher's okay
Nothing gets booked or sent until the dispatcher approves it. They're the one who knows that the 7:00 AM slot works only if the filters came in, or that Harbor Point's facilities manager is out on Fridays.
The dispatcher's checklist for each draft:
- Is the date one this crew can actually make, with the parts on hand?
- Are the access notes current?
- Is the site contact still the right person?
- Does this visit match what the contract promises (units, scope, frequency)?
Approve, fix or call. Then book it in your software so it shows up as a real job on the board.
What to watch out for
- Generated but not booked. The most common gap. Check that every event in your follow-up or recurring list has turned into a job.
- Stale site details. Keys change, contacts leave. Update the site record whenever a tech reports something different.
- One unit forgotten. When a site has several units, list them all in the booking note so the tech services every one.
- Contracts that ended. Remove a site from the calendar when its contract lapses, and flag it for a renewal conversation.
How to tell it's working
Run one count every Monday: the number of maintenance visits past due and not booked. It should be zero, or close to it, after the first month. A second count helps too: visits that were booked but rescheduled by your side. If that one climbs, the problem is capacity, not tracking.
There's also a reason customers care beyond the contract itself. A guide from the U.S. Department of Energy's Federal Energy Management Program estimates that operations and maintenance programs can save 5% to 20% on energy bills without major capital spending. That's the customer's side of the promise, and a missed visit takes it away.
If you'd like help seeing where an agent could watch your agreements, your free AI Operations Audit maps it, and the ServiceTitan AI integration guide covers what an agent can read there.
Questions operators ask
How often should commercial HVAC preventive maintenance happen?
- It depends on the equipment, the building and what the contract says. ANSI/ASHRAE/ACCA Standard 180 sets minimum inspection and maintenance requirements for commercial building HVAC systems, and many contracts are written quarterly or twice a year. Whatever the frequency, the Promise Calendar tracks the visits the contract actually promises.
Doesn't my field service software already schedule recurring visits?
- Many do the first half. ServiceTitan, for example, generates recurring events from a recurring service, and they show up in Follow Up to be booked into jobs. The Promise Calendar is the weekly check that every generated visit actually got booked.
What should a PM booking message include?
- The site, the units being serviced, the proposed date and arrival window, the on-site contact and the access details your tech needs (check-in point, keys, roof access, parking). The template below has all of them.
Can an AI agent book the visits on its own?
- In the setup we build, no. The agent drafts the booking and the message, and your dispatcher approves each one, because the dispatcher knows the crews, the parts and the customer.
See where AI fits in your operation
Thirty minutes on how the work actually moves. No pack of agents. No obligation to build. If we can help, we will show you the first paths. If we cannot, we will say so.
Sources
- HVAC Service Agreement Programs: Building Recurring Revenue Streams, FieldEdge
- Manage recurring services, ServiceTitan Help Center
- Recurring visit details for service agreements, ServiceTitan Help Center
- ANSI/ASHRAE/ACCA 180-2018 Standard Practice for Inspection and Maintenance of Commercial Building HVAC Systems, ICC (ASHRAE listing)
- New Standard Outlines HVACR Inspection, Maintenance Requirements, ACHR News
- Operations and Maintenance Best Practices Guide, U.S. Department of Energy (OSTI)
Keep reading
AI for dispatch in HVAC: what it does and what stays with your dispatcher
What AI can do on an HVAC dispatch board, what ServiceTitan's Dispatch Pro already handles, where a separate agent fits, and what stays with the dispatcher.
The Agent Job Card: an AI agent workflow template with three filled-in examples
The Agent Job Card is an AI agent workflow template with five lines (trigger, access, result, approval, record) and three filled-in examples to copy.
The Call Sort: choosing between an AI receptionist vs answering service, call by call
AI receptionist vs answering service for home service companies: sort routine calls to AI, emergencies to a person, and set after-hours rules ahead.