The Accreditation Deadline Nobody Tracked
The move in short
Agent — An agent that runs every Monday, reads the accreditation register in the lab information management system and the certification document store, extracts all renewal and submission deadlines within the next 90 days, cross-references each against the current status field, identifies any where preparatory work has not been logged, and sends the compliance officer a sequenced action horizon — deadline, responsible person, required submission artefact, and days remaining — plus a direct calendar invite for any deadline newly entering the 30-day window.
The Company
Ferrum Environmental Testing runs a commercial laboratory in Brno. They test soil, water, and air samples for industrial clients, construction companies, and public authorities across the Czech Republic and Slovakia. About 78 people work there, split between the lab floor and a small technical and administrative team. Their whole business rests on holding the right accreditations — without them, a client can't submit Ferrum's results to a regulator, and the contract dies.
The Pain
Lucie is the compliance officer. She's responsible for keeping all twelve accreditations and client-mandated certifications current. Each one has its own renewal cycle, its own documentation requirements, and its own body that wants submissions in a specific format by a specific date.
Right now she manages this across a shared Google Calendar that three people have edit access to and nobody really maintains, plus a folder of email reminders she's set herself over the years. Some of those reminders fire six weeks before a deadline. Some fire two weeks before. A few have drifted because the renewal date shifted one year and she updated the deadline but not the prep reminder.
What actually happens is that she spends part of most Mondays going through the calendar, the document store, and her inbox, trying to work out what's actually due, whether anyone's started the prep work, and whether the right person knows they're responsible. She's never missed a hard deadline, but she's come close a couple of times, and the close calls take up a lot of her mental space.
The Move
You'd set up an agent that runs every Monday morning. It connects to Ferrum's LIMS and the certification document store. It pulls every renewal or submission deadline in the next 90 days, checks the status field on each one, and looks at whether any preparatory work has been logged against it.
Then it sends Lucie a single structured list. Each item shows the deadline, who's responsible, what document or submission is actually required, and how many days are left. Anything where prep work hasn't been logged gets flagged. For any deadline that's newly entered the 30-day window since last Monday, it generates a calendar invite directly to Lucie and the responsible person.
She doesn't have to go looking. Monday morning she opens one message and she already knows what needs attention this week. The accreditations that are in good shape don't even take up her time.
Tools like Make or n8n can handle the scheduling and the connections. The logic itself isn't complicated — it's just reading fields, comparing dates, and checking whether a status has been updated.
The blind spot
The reason this doesn't get built is that Lucie is managing. Nothing has actually broken. So it feels like a nice-to-have rather than a fix for a real problem, and nobody gets around to scoping it.
The pattern
The same approach works in a few other situations:
- A professional services firm with multiple client SLAs and a junior account manager checking renewal dates manually each week
- A food manufacturer tracking supplier audit certificates across 30-plus ingredients, all with different expiry dates
- An HR team managing work permit renewals for international employees across several jurisdictions