The 38-second version of the gap below, straight from ServiceTitan's own Forms, e-signature, and vendor-contract documentation.
Not on its own. By ServiceTitan's own published documentation, Forms collects checklists, photos, PDFs and customer signatures, and e-signature is scoped to service agreements sent to customers. Neither documented workflow classifies an incoming document, reads an expiration date off it, or alerts anyone before a certificate of insurance lapses. Here is the part that makes the gap impossible to wave away: ServiceTitan's own vendor contract requires exactly that discipline from the businesses it works with — a certificate of insurance within ten days of signing, thirty days' written notice before any cancellation. ServiceTitan enforces this on its own vendors. It does not hand contractors the equivalent tool to enforce it on theirs.
This is not a knock on Forms or e-signature. Both do a real job well: capturing what happened on a job site and getting a customer's name on a service agreement without a clipboard. The question this post answers is narrower — what happens to the paperwork that isn't a service agreement: a subcontractor's certificate of insurance, a signed lien waiver, a permit, a manufacturer warranty registration — and who catches it when a certificate quietly expires.
What does ServiceTitan's Forms feature actually track?
Per ServiceTitan's own Forms documentation, the feature is built for field data collection: technicians fill out checklists, attach photos, generate PDFs, and capture customer signatures on service agreements during a job. That is genuinely useful for standardizing what a tech documents on site.
What the documentation does not describe is any classification layer sitting behind that capture. A completed form is a completed form. Nothing in ServiceTitan's own published workflow reads what type of document arrived, extracts a date buried inside it, or routes it to a specific department or folder based on what it actually is.
Does ServiceTitan's e-signature feature cover certificates of insurance?
No. ServiceTitan's own how-to guide scopes e-signature specifically to service agreements: you add a signature link, email it to a customer, and get notified "when a customer views or signs an agreement." That is the entire documented alert surface — a customer-facing signature event on one document type. There is no vendor or subcontractor document category in that workflow, and no mention of expiration-date alerting for anything.
If ServiceTitan doesn't track COI expiration, why does ServiceTitan itself require it?
Because when ServiceTitan is the one holding the risk, it treats certificate-of-insurance compliance as non-negotiable. ServiceTitan's own Standard Vendor Terms and Conditions require any vendor it contracts with to furnish a certificate of insurance within ten (10) days of signing the agreement, naming ServiceTitan as additional insured, with at least thirty (30) days' prior written notice before any coverage cancellation.
Read that against the product ServiceTitan sells contractors. ServiceTitan requires proof-of-insurance discipline, with real deadlines and real notice periods, from the businesses that work with it. It does not build the tracking, matching, and expiration-alerting layer that would let a contractor enforce the same discipline on its own subcontractors, inside the same system. The company knows this risk is worth a contractual deadline. The product it ships doesn't watch the calendar for you.
What does a lapsed COI actually cost a contractor?
There is no single authoritative number here, and this post will not pretend there is. A couple of compliance-software vendors that publish content on COI tracking put the cost of a claim involving an uninsured subcontractor somewhere in the $75,000 to $150,000 range, citing unspecified "construction industry data." We could not independently verify a primary source behind that figure, so treat it as directional, not a guarantee for any specific job.
What is verifiable is the mechanism, not the dollar figure: a general contractor, a bonding company, or ServiceTitan itself can require current proof of insurance before releasing payment or continuing a relationship. A certificate that lapsed three weeks ago and nobody noticed is exactly what triggers that hold — on a job that is otherwise finished and waiting to be paid.
What do existing "AI document management for contractors" tools actually offer?
Two kinds of pages currently answer some version of this question, and neither closes the actual gap. Generic AI-document-management content describes, in purely educational terms, an AI system that can "ingest COIs, extract policy limits, and flag deficiencies" — useful as a concept, but it names no platform, offers no buyer-decision framing, and never mentions ServiceTitan or field service at all. On the other side, dedicated certificate-of-insurance trackers exist as standalone compliance software: real expiration reminders, but built to run independently, with no documented integration to a contractor's job data, customer records, or ServiceTitan folder structure.
| Capability | ServiceTitan Forms + e-sign | Standalone COI tracker | Top Builder AI Documents agent |
|---|---|---|---|
| Field checklist / photo capture | Yes — Forms | Not built for this | — (sits on top of ServiceTitan's own capture) |
| Customer e-signature on service agreements | Yes — documented workflow | No | — (not a replacement for this) |
| Classifies an incoming document by type | Not part of the documented workflow | Manual entry, by design | Yes — automatic classification |
| Matches a document to the right customer/job | No | No ServiceTitan integration | Yes |
| Tracks certificate-of-insurance expiration dates | No | Yes — standalone | Yes — inside your existing workflow |
| Routes the document to the owning department/folder | No | No | Yes |
| Flags e-signature and expiration items needing a human | No expiration alerting | Expiration reminders only | Yes — both, in one queue |
How does Top Builder AI's Documents agent close this gap?
The Documents agent classifies each incoming document by type, matches it to the correct customer and job, routes it to the owning department and the right ServiceTitan folder, and flags anything that needs a person: an e-signature still pending, a certificate of insurance approaching its expiration date, or a document it cannot classify with enough confidence to file automatically.
What does this look like on one incoming document?
The example below is illustrative, built to show the mechanism, not a client result.
| Source | Subcontractor emails a renewed COI PDF |
| Classification | Certificate of insurance |
| Match | Matched to that subcontractor's vendor record |
| Extracted expiration date | Read from the document, logged against the vendor |
| Routing | Filed to the ServiceTitan vendor folder |
| Next action, automatically scheduled | Flagged again 14 days before expiration |
Does this replace ServiceTitan Forms or e-signature?
No. Forms is still how a technician documents a job site, and e-signature is still how a customer signs a service agreement — both real, useful, and unaffected. The Documents agent sits alongside them, watching every document that lands in the office regardless of source, classifying and routing it, and catching the expiration dates and pending signatures that a tool built for field data collection was never designed to watch for.
How does this connect to the rest of the back office?
A lapsed subcontractor certificate is a real-money problem the moment a general contractor withholds payment or a bonding company asks for current proof of coverage — which lands on the Financial agent's desk, not just a filing cabinet. Catching an expiration two weeks out, instead of discovering it the day a payment gets held, is what connects a paperwork agent to the numbers the rest of the back office is already tracking. Documents is one of eight agents in Top Builder AI's back-office stack; the full back-office overview covers how they work together.
- No automatic compliance decisions. The agent classifies, matches, routes, and flags. Whether a lapsed certificate holds a payment or gets a grace period is a call a human makes.
- No silent misfiling. A document it cannot confidently match to a customer or job is flagged needs-human, not filed on a guess.
- No invented dates or figures. Expiration dates come from the document itself; nothing is estimated or assumed.
- Delivered as a configured install, not a blind signup, so it is set up against your real document flow and ServiceTitan folder structure from day one.
See what's actually expiring in your document pile right now
Most shops have never run this check. A fit call walks through what a real classify-match-route pass finds in your own inbox.
Book a fit call →