The DOT medical card in your driver's wallet has an expiration date printed on it. So does the boiler inspection certificate framed in the mechanical room, the applicator license riding in the spray rig, and the certificate of insurance your sub handed over in March. Every one of those dates was read exactly once — on filing day — and then the document went into a drawer where dates cannot be seen.
Deadlines live inside documents nobody reopens
This is the same pattern in every trade: an obligation is proven by a piece of paper, the paper carries a date, and the paper gets filed. A contractor license renewal, a commercial driver's medical certificate — issued for two years at most, often less when the examiner writes conditions — a boiler certificate that attaches to one specific vessel at one specific address, a general liability policy, the stack of insurance certificates from every sub on the job. The dates exist. They are simply distributed across a filing cabinet, a glovebox, a wallet, and an email attachment from fourteen months ago, and no calendar anywhere holds them all. The renewal you remember at 4:50 on the Friday it lapses was never forgotten. It was just never written down anywhere that talks.
Extraction, mechanically
The system starts by gathering the paper. Every license, card, certificate, permit, and policy gets scanned or photographed, run through text recognition, and the dates, document numbers, and holder names get pulled into structured records. Each calendar entry keeps a link back to the image of the source document, so anyone who doubts a date can look at the actual paper in two clicks — provenance, not trust. A person verifies every extracted date once, during setup, and that pass matters: text recognition on a clean PDF is close to perfect, but a creased medical card photographed in a truck cab can read an 8 as a 3, and a silently wrong date in a compliance calendar is worse than no calendar at all. Anything the software isn't confident about gets flagged for manual entry rather than guessed at. From then on, new documents enter the same way: photograph it, confirm the extracted date, filed.
Escalation, not repetition
A reminder that fires once and dies is a snooze button. The design here is a ladder that gets louder. At ninety days out, a routine notice goes to the office manager, and it carries the substance of the renewal, not just the date — this license needs continuing education hours completed first, this vessel needs an inspection scheduled before the certificate can reissue, this driver needs a physical booked. At thirty days, if nobody has marked it handled, the notice repeats and copies a second person. At fourteen days, still unacknowledged, it goes to the owner directly and says so. Acknowledgment is the load-bearing feature: a reminder that can be marked "handled — renewal submitted 3/12" stops firing and leaves a record. Reminders that can't be answered become noise, noise gets ignored, and ignored reminders are how the original problem happened in the first place.
Where this bites hardest
A fleet operator carries the sharpest version: every driver's medical certificate runs on its own cycle, and an expired card discovered at a roadside inspection puts that driver out of service on the spot — the truck sits, the load sits, and the customer hears about it. Mechanical contractors carry certificates per boiler, per site, each on its own inspection clock. Agricultural and pest operations hold applicator licenses with continuing-education requirements that have to be completed before the renewal window, which means the real deadline is earlier than the printed one. And anyone who works as a subcontractor lives with the mirror image: your insurance certificate's expiry sits in the general contractor's compliance software, which flags it automatically and holds your pay applications until a current one arrives. The GC has this system pointed at you. This is the same system pointed at your own drawer.
This schedules obligations. It does not define them.
The line needs stating plainly, because it is easy to blur and dangerous when blurred. This system tracks the dates on documents you already hold. It has no opinion about whether your operation needs a permit it doesn't have, whether a regulation applies to you, or whether the legislature changed a renewal cycle last session. Those are questions for your attorney, your insurance agent, or your compliance officer, and nothing here substitutes for them. If the state moves a deadline, the calendar doesn't know until a person tells it. What you get is logistics: a complete, dated, escalating picture of the obligations you already carry, with the receipts attached. What you do not get is advice, and any vendor who blurs that line for you is doing you harm.
The other limits
The inventory is manual and it is the price of admission. Obligations nobody gathers don't exist to the system, so the first week is a person going through the cabinet, the gloveboxes, and the inbox. Renewal itself remains human work — the system buys you sixty days of warning, it does not fill out the form, sit the physical, or schedule the inspector. And dates that depend on events rather than paper — an inspection due twelve months after the last one — only stay correct if the completion gets recorded when it happens, which is a habit, not a feature.
Where to start
Give it one afternoon and one folder: every document in the business with an expiration date on it, gathered in one place. In practice most owners find at least one date closer than they thought before any software enters the picture — and that discovery is free. The pile in the folder is the entire input. If the pile is small and the dates are far off, you don't need this yet, and it's better to know that too.