What you will learn
- What library programmes need from booking, beyond a headcount
- How recurring programmes, series, and one-off events differ
- How waiting lists, cancellations, and no-shows are handled
- How children's programmes handle safeguarding and guardian bookings
- How programme data informs next season's planning
What the project is
Libraries are programme venues as much as lending collections. A branch may run storytimes, homework help, digital skills classes, author talks, and book clubs in a single week, each with its own capacity, audience, and booking needs. Managing those through paper lists or general event tools fragments the programme and leaves librarians without attendance data.
The platform unifies it. Readers browse the programme by branch, age group, and topic, book themselves and their children, manage cancellations, and receive reminders, while librarians see bookings, waiting lists, and attendance per programme.
Core features
Programme listings are the core: events by branch, age group, topic, and date, with capacity, booking windows, and accessibility information. Booking handles individuals, families, and groups, with waiting lists that promote automatically when places free up. Attendance capture at the door, by name search or check-in, turns bookings into data, and programme reporting shows attendance, no-show rates, and waiting list demand per programme type.
- Programme listings by branch, age group, topic, and date
- Bookings for individuals, families, and groups
- Waiting lists with automatic promotion when places free up
- Attendance capture at the door with name search
- Reminders and cancellation handling for bookers
- Programme reporting: attendance, no-shows, and demand
How it is built
Start with listings and booking for one programme type, such as classes, and prove booking, waiting lists, and attendance end to end. Recurring series follow, then children's safeguarding features, designed with children's librarians, once the core is running reliably.
- Define programme types, capacities, and booking rules with librarians.
- Build listings and booking for one programme type.
- Add waiting lists, cancellations, and reminders.
- Add attendance capture and programme reporting.
- Add recurring series and children's safeguarding features.
Technology considerations
Booking simplicity decides adoption. Readers book rarely and will abandon long forms, so booking should need minimal steps, with family members addable without separate accounts. Waiting list promotion must be time-limited: a promoted place held indefinitely blocks the next person, so promotion should expire and move on automatically.
Children's data needs extra care. Guardian bookings, emergency contacts, and age verification must be accessible only to authorised staff, with retention rules for after the programme ends.
Challenges to plan for
The main challenge is no-shows. Popular programmes fill with bookings that never attend, blocking others. Reminder messages, easy cancellation, and no-show tracking that informs future booking rules, such as limits after repeated no-shows, help, but they must be applied fairly and explained plainly.
- No-shows blocking places in popular programmes
- Waiting lists that stall because promoted places are never claimed
- Children's bookings without guardian information
- Programme data that nobody reviews, so weak programmes repeat
Who it is for, and its limits
This platform fits public libraries running regular programmes, library systems coordinating programmes across branches, and academic libraries running workshops and training sessions.
It does not create programme quality; it administers bookings and attendance so librarians can judge quality from data. Programme content and delivery remain librarian work. Costs and timelines vary with branch count and programme variety, so confirm with a quote before budgeting.
Learning from the first season
Review the first season's programme data with librarians before planning the next: which programmes filled, which had waiting lists, which suffered no-shows, and which drew audiences the library had not reached before. That review turns booking data into programming decisions, such as repeating a workshop that filled twice, moving a popular class to a larger room, or retiring a programme that consistently under-attends despite promotion.
Share a short version of that review with the community, through the programme pages or a newsletter, so readers see that their bookings and attendance shape what the library offers. A library that visibly responds to demand earns the trust that makes the next season's bookings stronger, and it gives librarians evidence for funding conversations about programme space and staffing.
Frequently asked questions
How do readers find programmes?
By browsing listings filtered by branch, age group, topic, and date, with capacity and booking windows shown for each event.
What happens on a waiting list?
When a place frees up, the next person is promoted with a time-limited offer. If they do not claim it, the place moves to the next person automatically.
Can families book together?
Yes. Family bookings let one person book several members, including children, with guardian information captured where required.
How are no-shows handled?
Attendance capture records them, reminders and easy cancellation reduce them, and repeated no-shows can inform future booking rules, applied fairly and explained plainly.
Does the platform show which programmes work?
Yes, through reporting on attendance, no-show rates, and waiting list demand per programme type, which informs next season's planning.
Can I book for someone else?
Yes, for family members and, where the programme allows, for others, with the booker's contact details used for reminders and cancellations.