Every training coordinator has a version of this spreadsheet: one tab per cohort, one row per student, a column for every session, and a lot of manual checkmarks. It's not a bad system when a cohort has fifteen people and six sessions. It becomes a genuine liability somewhere around cohort three, when you're running multiple programs at once and the spreadsheet is the only record of who actually showed up.
Where it actually breaks
The failure point is rarely dramatic. It's a trainer who forgot to mark attendance for session four and now has to reconstruct it from memory two weeks later. It's a student who disputes their completion status and there's no timestamp, no record, just someone's recollection. It's the moment right before certificates go out, when someone finally cross-checks attendance against the completion requirement and finds three students who technically didn't qualify — after the invitations to the graduation ceremony already went out.
None of this is because anyone was careless. It's because attendance tracking in a spreadsheet has no guardrails. Nothing stops a gap from happening, and nothing catches it until someone goes looking.
What structured tracking changes
CertTrack's attendance and module-completion tracking exists specifically to remove the reconstruction step. Trainers mark attendance per session as it happens, module completion is tracked against the actual course structure, and by the time certification is due, eligibility is already known — not something to figure out under time pressure.
The bigger shift is what this makes possible after the fact. When attendance lives in a spreadsheet, answering "how many students actually completed 80% of sessions across all our Q1 cohorts" means opening every tab and counting by hand. When it lives in a real system, it's a query — the kind of number you can actually put in a funder report or a board update without a week of prep first.
