Compliance Expiry Tracker | FluidGrids Use Cases

You know the exact spreadsheet. One row per certificate, license, and compliance document — ISO, SOC 2, fire safety, food safety, insurance, vendor DPAs, professional registrations — each with an expiry date and an owner who is not, at this moment, thinking about it. Nobody opens that sheet until an auditor, a regulator, or a customer asks whether something is still valid. And by then the honest answer is sometimes: it lapsed three weeks ago, and nobody was reminded in time.

FluidGrids turns that dormant sheet into an active control. A schedule node fires every morning at seven. A Google Sheets node reads your registry exactly where it already lives — you keep owning the source of truth, the workflow just wakes up and reads it. A code node walks every row and computes days-to-expiry, cleanly skipping any cell it can't parse so one bad date never derails the whole sweep. In seconds, 240 tracked items become a clean list of the handful that need something today.

Then the reminders get smart about urgency. A switch node routes each item into a tier by how close the deadline is — 90 days, 60, 30, 7 — and the tone scales with the risk. The 90-day ISO renewal earns a calm Slack heads-up: start planning. The 30-day fire-safety license gets a firmer Slack-and-email nudge: begin the paperwork now. The 7-day driver medical fans out across Slack, Gmail, and WhatsApp with the owner's manager looped in, because at seven days a single muted channel is how a lapse happens. Attention scales with proximity instead of every alert looking identical and getting ignored equally.

But a reminder you can dismiss is still a reminder you can dismiss. So the last node books the renewal onto the owner's calendar — a dated event, titled for the item, with the registry link and expiry date in the body, placed a sensible lead time before the deadline. The nudge stops being a notification and becomes a commitment the owner and their manager can both see. The renewal is now scheduled, not merely mentioned.

The agent never renews anything itself, and that restraint is the point. This is a govern control: it computes, it escalates, it books, and it hands the decision to the accountable human at exactly the right moment. What it does own is the evidence. Every morning's sweep is pinned to an exact workflow version in run history — what was checked, who was alerted, on which channels. And because edits live as drafts until you deliberately activate them, the 07:00 sweep keeps running untouched while you refine a rule, with one-operation rollback if a change misbehaves.

The day an auditor asks how you make sure nothing lapses, you don't describe a process you hope people follow. You show them one that ran, escalating and on record, for every single item under your name.