Book a discovery call

13 Residential construction · United States Shipped

A certificate tracker for about 110 subcontractors, repaired and audited

No chase went out to a subcontractor without a person approving it first.

Part of Six tools built inside a live construction-tech platform

Before
Certificates chased by hand by email and phone before each one expired
After
Certificates read on arrival, chases queued, every outgoing message approved by a person before it sent
110 active subcontractors tracked
The work, before and after
Before and afterBefore: Certificate expires, then Chased by email, then Chased by phone. After: Certificate arrives, then Dates read, then Chase queued, then Person approves, then Message sent. Result: 110, active subcontractors tracked.BEFORE2 OF 3 PAIN POINTSAFTER2 OF 5 AUTOMATEDCertificateexpiresChased by emailChased by phoneCertificatearrivesDates readChase queuedPerson approvesMessage sent110active subcontractors trackedBefore and afterBefore: Certificate expires, then Chased by email, then Chased by phone. After: Certificate arrives, then Dates read, then Chase queued, then Person approves, then Message sent. Result: 110, active subcontractors tracked.BEFORE2 OF 3 PAIN POINTSAFTER2 OF 5 AUTOMATEDCertificate expiresChased by emailChased by phoneCertificate arrivesDates readChase queuedPerson approvesMessage sent110active subcontractors tracked
21
live projects
Every
chase approved by a person before it sent
How the system runs
Input
  • Certificate by email or upload
ArrAI
Read, track, chase
Output
  • Chase queued
  • Send held for approval

01 What changed

  • Nothing went out to a subcontractor without a person seeing it first
  • Certificates were read and queued for a chase, not tracked on a list
  • The builder ended the workstream in August, once wrap insurance covered most projects
The full story The problem, how we approached it, and what we built

A home builder tracked subcontractor insurance certificates through a tracker inside its software platform. Our role was repair and audit: keeping intake, reading and the chase queue working, with every outgoing message held until a person released it. The builder ended the workstream in August, once wrap insurance covered most of its projects.

Built for
Office manager and project coordinators
Engagement
Custom home builder
Sector
Residential construction
Region
United States
Year
2026

02 The problem

Every subcontractor on every project carried an insurance certificate with an expiry date. A lapsed certificate on a live site is a real liability.

The platform already had a tracker for this. It needed someone to keep it reading certificates correctly and to check what it was about to send.

03 The approach

We repaired the intake for certificates sent by email or uploaded, the reader that pulls out dates and coverage, and the queue that decides who to chase and when, then audited what it produced.

Every send waited on a named person's approval. In August the builder ended the workstream, because wrap insurance now covered most of its projects.

04 What we built

  • Repairs to certificate intake by email and upload
  • Audit of the reader that extracts carrier, coverage and expiry
  • Chase queue checked across 21 live projects
  • Release step kept on: every outgoing message held until a person approved it

Want this kind of result mapped for your business?

Book a discovery call