Library Program Attendance Log

This template captures the core details needed to document a library program: submitter information, branch location, program date and time, program type, target audience, attendance by age group, staffing, outcomes, and follow-up notes. It is designed to produce a clean record for internal planning and funder reporting. If your library needs more detail, you can add fields for registration source, room capacity, or partner organization. Keep the form focused on what you will actually use so it stays quick to complete.

The best practice is to complete it immediately after the program while attendance and engagement details are still fresh. Some branches also enter a draft before the event and then update the counts after the session ends. If you run recurring programs, use one submission per session rather than one monthly summary so the record stays auditable. That makes it easier to reconcile totals later.

The person who ran the program or the staff member responsible for attendance tracking should complete it. If a volunteer or presenter is collecting counts, a staff reviewer should still confirm the final submission. The attestation field helps show that the record was reviewed for accuracy. For multi-branch systems, assign one owner per branch to avoid duplicate or missing logs.

The age-group counts, program type, and outcomes fields give you the data points funders usually ask for in narrative and numeric reports. Because the template separates attendance by age group, you can summarize participation without manually re-reading notes. The outcomes and challenges fields also help explain what happened beyond the raw headcount. That makes reporting faster and more consistent across branches.

No attendee-level PII is required in this template, which supports data minimization. It records aggregate counts instead of names, birth dates, or contact details, so it is better suited for public program tracking than registration management. If you add optional follow-up contact fields, include clear consent language and only collect what you need. For anonymous programs, keep the form aggregate-only.

Yes. The template is meant to be adapted to your library’s reporting categories, so you can rename program types, add a multilingual program flag, or adjust age bands to match your funder’s definitions. If you change the age groups, keep the categories mutually exclusive so totals are easy to validate. Avoid adding too many optional fields unless they support a real reporting need.

This template works well with spreadsheet exports, dashboards, and branch reporting workflows. You can connect it to calendar tools for event metadata, or to a reporting system that rolls up attendance by branch, program type, or month. If your library uses a separate registration form, keep this log as the post-event attendance record rather than duplicating registration data. That reduces errors and keeps the workflow simple.

A common mistake is entering only the total attendance and skipping the age-group breakdown, which limits reporting value. Another is using free-text notes to store counts or dates that should be structured fields. Some teams also forget to record materials distributed or follow-up needed, which makes it harder to act on the session later. Clear required fields, validation, and a final review step help prevent those gaps.