AHA Roster and Skills Checklist Automation

Yes, because the roster is mostly information the booking already holds. When a student books, you capture their name, their email, the course, the session date, the location, and the instructor assigned. A roster asks for those same fields. So the sensible move is to fill the roster from that record instead of asking a human to copy it across. What software cannot do is judge accuracy. If a student booked under a nickname, or attended and was never marked, or failed a skill, only the instructor in the room knows. That is why this ends with a review and a signature rather than an automatic submission. The tool does the typing. You do the checking.

Stop treating the roster as a separate document and start treating it as a view of the booking. One record per student per session, entered once at booking, printed into whatever paperwork the class needs. Rosters and skills checklists both read from that record. When a student cancels Thursday, the roster generated Friday no longer has them on it, because there is one source rather than three copies drifting apart. Our own CPR business runs around 137 bookings a month. At that volume the retyping is not a small annoyance, it is a recurring evening job, and it is the exact job a computer should have.

You are, and we will not pretend otherwise. The training center and the instructor of record carry the obligations to the AHA: what was taught, who attended, who passed the skills check, and what gets submitted. This tool fills forms from your booking data. It does not certify anything, it does not submit on your behalf, and it does not accept responsibility for whether a record is correct or accepted. The instructor reviews every generated document and signs it. That step is not a formality we tacked on, it is the point at which a filled form becomes your record. Any vendor telling a training center it can hand over that responsibility is selling something it cannot deliver.

A roster is about the class. A skills checklist is about one student. So the checklist is generated per enrolled student, with their name, the course, the date, and the instructor already filled in, and the skill lines left for the instructor to mark in the room. That split matters in practice. The roster can be produced the moment enrollment closes. The checklists get printed for class day and come back marked, one per person. Generating them individually also means a late add gets a checklist without anyone rebuilding a packet by hand.

The paperwork regenerates from the current bookings. This is the failure mode that makes hand-typed rosters expensive: the sheet was accurate on Wednesday, three things changed on Friday, and nobody wanted to retype the page. So class starts with a document that quietly disagrees with the room. When the roster is generated rather than maintained, the version you print on class morning reflects who is actually enrolled that morning. If someone walks in unbooked, that is still a human decision and a handwritten line, and the instructor's signature covers it.