Library Program Attendance Log

This template works for story times, maker programs, teen events, adult workshops, outreach visits, and one-off special programs. It is built around attendance by age group, staffing, and grant linkage, so it fits programs where you need both headcounts and basic program context. If your event has a very different structure, you can rename the program type field or add conditional logic for extra details.

Complete it for each program session, ideally right after the event while attendance and staffing details are still fresh. If a program runs in a series, log each session separately so trends in attendance, age mix, and deviations are easier to review. A single entry per session also makes internal reporting and grant documentation cleaner.

The staff member who ran the program, the presenter, or the person assigned to track attendance should complete it. The attestation section gives you a clear record of who submitted the log and when, which helps with audit trail and follow-up questions. If volunteers help count attendees, a staff member should still review the final totals before submission.

Yes. The grant-funded fields let you connect attendance records to a specific grant, funding stream, or outcome area. That makes it easier to show which programs were supported by which funds and to summarize participation for reporting. If a program is not grant-funded, the form still works as a general attendance log.

Use the age_unknown field rather than guessing or forcing staff to collect personal details. This keeps the form aligned with data minimization and avoids unnecessary PII collection. If your library uses a different age breakdown, you can customize the age group fields to match your reporting needs.

It can replace or supplement a sign-in sheet when you only need aggregate counts rather than names. That is often better for privacy and faster for high-volume programs. If you need individual contact information for follow-up, keep that in a separate form so attendance tracking stays focused on the minimum necessary data.

The most common issues are forgetting to total the age group counts, leaving the program type too vague, and skipping the deviation or notes fields when something changed. Another frequent problem is recording attendance after the fact without a clear method, which can lead to inconsistent counts. A quick end-of-program review helps prevent those errors.

You can add branch-specific program types, local grant names, or extra fields for outreach location, registration count, or materials used. If your system needs more detail, use conditional logic so extra fields only appear when they apply. That keeps the form shorter and easier to complete while still capturing the information your reports require.

Yes, the fields are structured so they can map cleanly into spreadsheets, dashboards, or a library management workflow. Program date, branch, age group totals, and grant fields are especially useful for filtering and trend analysis. If you export the data regularly, keep field names consistent across branches to avoid cleanup work later.