No-Show & Make-Up Session Tracker: Stop Missed Training Becoming a Permanent Gap
Turn each session's attendance into a worklist of who missed it, capture the reason, route them to a make-up session, and track required no-shows until they actually complete — with your coordinator approving every plan and closure.
A web tool where you import attendance, AI flags every registrant who didn't show, you capture the reason and assign a make-up session, your coordinator approves the plan, and the tool tracks required no-shows until they truly complete — escalating overdue ones and exporting a no-show + make-up status CSV.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- An attendance export or sign-in sheet (CSV)
- Your upcoming session schedule
- Claude Code or any AI coding agent
The problem this kills
You run a training session for 30 people. Twenty-four show up. Six don't. The roster gets filed, the day moves on — and those six no-shows quietly vanish into the gap between "we offered it" and "they actually completed it." Some of those misses don't matter. But some were mandatory — the compliance refresher, the safety certification, the harassment-prevention course — and nobody is tracking them down.
Three months later an auditor asks for proof that everyone completed the required training, and you discover that "we ran the session" is not the same as "everyone took it." Now you're reconstructing who missed what from old sign-in sheets and email threads, chasing people who left months ago, and hoping you catch every gap before it becomes a finding.
You don't need a learning management system to fix this, and you don't need to be a developer. You need a tool that refuses to let a required no-show close until the person has actually completed a make-up.
What you'll build
A simple internal web tool. After each session you import the attendance (from your tracker or a sign-in sheet) and the tool compares it against who was registered — anyone registered who didn't attend becomes a no-show on a worklist. For each one you capture a reason, mark it excused or unexcused, and — if the training is required — assign a make-up session from your upcoming schedule. Your coordinator reviews each no-show, approves the reason and the make-up plan, and the tool then tracks it until the person actually attends the make-up. Required no-shows cannot be closed without an approved make-up completion. Repeat no-shows and overdue required ones get escalated instead of slipping. At any point you export a clean no-show + make-up status CSV for your records or your auditor.
What's inside the Implementation Plan
The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how you run sessions today, where your roster and attendance live (your LMS, a spreadsheet, a paper sign-in sheet), exactly how your courses and employees are named and ID'd, which trainings are required versus optional, how you decide excused versus unexcused, your typical and peak class sizes, and your messy edge cases — and then it tailors the data model, the rules, and every later step to your answers. This is not a generic template; the agent reflects a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through the attendance import, the no-show detection, the reason-and-make-up capture, the coordinator review-and-approve screen, the completion tracking, the escalation logic, and the email reminders — each step with a ready-to-copy prompt. There's also a fallback so you can build the whole thing today even with no API to your LMS.
The governance it includes (this is the point)
This is compliance-grade tooling, so it ships with the controls a training team needs: login so only your team can use it, row-level security so you only ever see your own organization's data, a complete audit trail of who flagged, approved, and closed which no-shows and when, a hard human-approval gate so no make-up plan or closure is recorded until your coordinator signs off, and duplicate guards keyed on employee + original session so the same miss can't be tracked or closed twice. Required no-shows are locked open until an approved make-up completion exists — so a mandatory miss can never be quietly marked done.
Who it's for
Compliance coordinators, training managers, L&D admins, and safety officers who own mandatory training and are tired of discovering gaps only when an auditor asks. If you can describe how your shop decides what's required and what counts as completed, you can build this.
You've got this — start with the plan, paste the first prompt, answer the interview, and you'll see your first no-show worklist take shape the same afternoon.