Recertification Workflow

The problem this kills

Recertification is one of those things that quietly turns into a fire drill. Someone's forklift cert lapses on the 30th, nobody noticed until the 28th, and now you're scrambling to book a refresher, chase the retest, and reissue paperwork before they're legally allowed back on the floor. Multiply that across dozens of people and cert types, each on its own cycle, and "compliance tracking" becomes a spreadsheet you're afraid to trust.

The real damage isn't just the scramble. It's the gaps: people working on an expired cert, refreshers that got scheduled but never confirmed, retests that quietly failed and got renewed anyway, and no clean record of who approved what. When an auditor asks "show me the proof this person was current the whole time," you want a history, not a guess.

What you'll build

A recertification pipeline tool that runs the whole cycle for you:

• Detects who's due based on each cert's renewal cycle, with grace-period handling and a clear "expired while in recert" flag.
• Schedules and tracks the refresher and retest for each person, so nothing sits in limbo.
• Verifies completion (refresher done + retest passed) before anything moves forward.
• Holds a human gate: the training lead reviews eligibility and approves the renewal. Failures route to remediation, not renewal.
• Issues the new certificate with a fresh expiry date, updates the register, and keeps the full history of prior cert periods.
• Exports a renewed-certs CSV in the exact columns your system of record expects.

It works even if you have no integration with your HR or LMS system: import your register from a Google Sheet or CSV, and export a clean CSV back out.

What's inside the Implementation Plan

The plan is a single file you paste into an AI coding agent. It builds the tool with you, step by step, and each step ends with a ready-to-copy prompt.

It opens by interviewing you about your business. Before it writes a single line, the plan has the agent ask about your current recert process, the cert types and cycles you track, the exact field names and codes in your register, your typical and peak volumes, your real approval and grace-period rules, and your messy edge cases. It reflects a short tailored spec back to you for a thumbs-up, then shapes the data model, validations, and every later step around your answers. This is your tool for your certs, not a generic template.

From there it walks through accounts and setup, the data model, the due-detection logic, the scheduling and tracking screens, the approval gate, certificate issuance, the register update, and the CSV export and verification.

The governance it includes (this is the point)

Compliance tooling that can't prove itself is worthless. This plan bakes in:

• Login so only your team can use the tool.
• Row-level security so each organization only ever sees its own data.
• A complete audit trail of who did what and when: who scheduled, who marked complete, who approved the renewal.
• A hard human-in-the-loop approval gate before any cert is renewed. The tool drafts eligibility; a person reviews and approves; only then is the new certificate issued.
• Duplicate guards so the same employee + cert type + cert period can't be processed twice.

Who it's for

Compliance and training leads who manage recurring certifications that must be renewed on a cycle, and who are tired of tracking it all in a spreadsheet that nobody fully trusts. You don't need to be a developer. If you can describe your process clearly and paste a prompt, you can build this.

You've got this. Paste the first prompt and let the interview tailor it to your business.