Certification expiry tracker
A lapsed card rarely gets noticed on the day it expires. It gets noticed when an inspector, a GC safety rep, or an owner's site orientation asks to see it. Then a forklift operator can't run the...
The problem
A lapsed card rarely gets noticed on the day it expires. It gets noticed when an inspector, a GC safety rep, or an owner's site orientation asks to see it. Then a forklift operator can't run the telehandler, a laborer gets walked off the roof of a commercial array, or the whole crew waits while someone finds a replacement.
The records are usually scattered. OSHA 10 and 30 cards sit in a folder at the office. Forklift certifications are on a wallet card in someone's truck. First aid and CPR cards live in a photo on a foreman's phone. Expiry dates are in nobody's head until they are already past.
A superintendent running three crews can't carry forty-odd dates around. A spreadsheet helps, but only if someone opens it. The agent's job is to open it every day so you don't have to.
How the agent workflow works
The agent works from one roster: a shared spreadsheet or simple database with a row per worker and a column per credential. Each row holds the credential type, the issue date, the expiry date, and a link to a scan or photo of the card.
What it reads. Each morning it reads the roster. It also reads two other inputs: the crew schedule, so it knows who is assigned to which job in the coming weeks, and any new card photos dropped into a shared folder or sent to a dedicated email address.
What it produces. For new card photos, it extracts the name, credential type, and dates, then drafts a roster entry. Nothing goes into the roster until a person confirms it. For the daily check, it sorts credentials into groups: already expired, expiring inside your chosen warning window, and expiring soon after that. Most superintendents pick a long window for cards that need a class to renew and a shorter one for cards that can be renewed online.
It then drafts a short message for each flagged worker or foreman: which card, which date, and who to talk to about booking renewal. It also drafts a summary for you, listing flagged items by job. If someone with a card expiring next month is scheduled to run equipment on a job that starts after that date, the agent marks it as a conflict.
The human checkpoint. The agent sends nothing on its own. You or an office admin reviews the summary, edits the drafted messages, and approves them. You also confirm every roster entry the agent extracted from a photo. Renewals are booked by a person, and a card is marked renewed only after someone sees the new one.
What you need to set it up
- A single roster, in a spreadsheet or a simple database the agent can read and write to.
- An AI agent tool that can run on a daily schedule, read files, and draft messages. Many general-purpose agent platforms can do this.
- A shared folder or email address where foremen drop card photos.
- Access to the crew schedule, even if it is only a spreadsheet.
- A messaging or email channel for the approved notices.
Setup time is mostly data entry. Expect several hours to build the first roster from existing cards, plus an hour or two to configure the daily check and tune the warning windows. The ongoing subscription cost is whatever the agent tool and storage already cost you, as there is nothing special to buy.
Where it breaks
Bad photos. Wallet cards get scuffed, laminated glare hides dates, and handwritten expiry dates get misread. This is why every extracted entry needs a human check.
Cards that don't show an expiry date. Some credentials show only an issue date, and the validity period depends on the issuer or the employer's own rules. The agent can't guess that. You must tell it the rule for each credential type, and you must correct it when a rule changes.
Stale rosters. If a new hire never gets added, or a sub's crew rotates without notice, the agent is faithfully watching an incomplete list. It catches only what it is shown.
Schedule conflicts depend on schedule quality. If the crew schedule is loose or lives in text messages, the agent's warnings about upcoming assignments will be wrong or missing.
Warning fatigue. If the window is too wide, foremen start ignoring the messages. Tune it, and watch whether renewals actually happen.
Finally, the agent tracks dates. It doesn't verify that a card is genuine or that a training provider was legitimate.
The bottom line
This workflow won't replace your safety program, but it removes the most avoidable failure in it: a card that lapses because nobody looked. The agent does the daily looking and the drafting. You do the approving and the booking.
Start with one crew and one credential type, such as forklift cards. Get the roster accurate, check that the warnings arrive early enough to act on, then add the rest.
Related use cases
- Two-week lookahead, built not typed Management
- Change-order first draft Management
- Schedule scenario planning, run before you commit Management