Library Daily Opening and Closing Checklist
Use this Library Daily Opening and Closing Checklist to standardize opening, closing, cash handling, and facility security tasks for library staff. It helps the shift lead verify readiness, reduce missed steps, and leave a clear handoff record.
Trusted by frontline teams 15 years of frontline software
Built for: Public Libraries · Academic Libraries · School Libraries · Municipal Services
Overview
This template is a daily opening and closing checklist for library operations. It is built for the routine steps that must happen before service begins and after the building is secured: security walk, systems startup or shutdown, cash drawer setup and reconciliation, patron services readiness, and facility lockdown.
Use it when the same tasks repeat every day and you need a reliable way to assign ownership, confirm completion, and capture exceptions. It works well for branches with rotating staff, split shifts, or multiple service points because each checklist item can be verified independently and marked complete, blocked, or needing follow-up. The checklist format also helps separate blocking issues, such as a failed alarm or inaccessible cash drawer, from non-blocking issues that can be routed later.
Do not use this template as a catch-all for every branch task or as a policy document. It is not the right fit for one-time projects, long maintenance jobs, or broad operational plans. It also should not replace incident reports, facilities logs, or cash control procedures where those are required. The best use is as a repeatable daily runbook that leaves the next shift with a clear, auditable handoff and fewer missed steps.
Standards & compliance context
- Use the checklist as an operational control that supports local cash-handling procedures, not as a substitute for required financial records.
- If your branch handles public access, emergency exits, or alarm systems, keep the security walk aligned with local fire and life-safety requirements.
- Where staff handle patron data or public computer access, the startup and shutdown steps should reinforce basic privacy and workstation security practices.
- If a step affects safety or access control, treat the failure as blocking until the responsible DRI confirms the issue is resolved or formally accepted.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Create separate opening and closing task instances, then set the recurrence_config to daily with the correct days_of_week for the branch schedule.
- Add 5 to 15 checklist items that each start with a verb and describe one independently verifiable action, such as verifying doors, starting systems, or reconciling the drawer.
- Assign one DRI per checklist item or per task type so staff know exactly who completes the security walk, cash steps, and patron readiness checks.
- Run the opening checklist before service begins and the closing checklist after the last patron leaves, marking each item complete, blocked, or non-blocking as appropriate.
- Review any failed verification step at the end of the shift, create follow-up work for facilities or IT when needed, and note anything that should change in the next recurrence.
Best practices
- Keep each checklist item atomic so one person can answer yes, no, or N/A without interpretation.
- Separate opening and closing into different task instances when the branch needs different owners, timing, or verification steps.
- Reserve critical priority for safety, security, or compliance blockers such as an alarm issue or an unsecured cash drawer.
- Use normal priority for routine readiness checks so important exceptions stand out instead of being buried.
- Record failed steps immediately and attach the follow-up action before the shift ends, not after memory fades.
- Include a clear verification step for doors, alarms, public computers, self-check stations, and cash reconciliation.
- Avoid compound items like 'check the desk and restock supplies' because they hide partial completion and make audits harder.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this library opening and closing checklist cover?
It covers the daily tasks a library team needs to complete before doors open and after the last patron leaves. Typical items include a security walk, systems startup or shutdown, cash drawer setup and reconciliation, patron service readiness, and facility lockdown. It is meant to be a shift checklist, not a policy manual, so each item should be directly verifiable.
Who should run this checklist each day?
Usually the shift lead, circulation supervisor, or opening and closing DRI runs it, with support from the staff member assigned to the desk or facility walk. If your library has separate front-desk and facilities responsibilities, split the checklist so each person owns the items they can verify. The key is to assign one clear DRI per checklist item so nothing is assumed.
How often should this template recur?
This template is designed for daily recurrence, typically once for opening and once for closing. If your branch has split shifts, you can duplicate it into separate morning and evening runs with distinct recurrence_config values. Avoid using it as an ad-hoc note, because the value comes from consistent execution and a repeatable handoff.
Is this checklist useful for compliance or audit purposes?
Yes, it can support internal controls by documenting that required opening and closing steps were completed. It is especially helpful where cash handling, patron safety, or facility security are involved. It should not replace formal incident reports, inventory logs, or any required regulatory record, but it can complement them as a verification step.
What are the most common mistakes when using this template?
The biggest mistake is writing compound checklist items, such as combining cash count, drawer setup, and receipt verification into one line. Another common issue is marking everything critical, which makes priority less useful for actual safety or service blockers. Teams also sometimes forget to include a closing verification step for doors, alarms, and systems shutdown.
Can this template be customized for different library branches?
Yes, and it should be. Branches with self-check kiosks, meeting rooms, makerspaces, or after-hours returns may need extra checklist items, while smaller branches may need fewer. Keep the items atomic, use normal priority for routine steps, and reserve critical for anything that affects safety, security, or compliance.
How does this compare with an informal opening and closing routine?
An informal routine depends on memory, which makes missed steps more likely when staff rotate or the branch is busy. A checklist template turns the routine into a repeatable task type with clear ownership, a visible status, and a consistent record. That makes it easier to spot recurring issues and hand off between shifts.
Can this checklist connect to other systems or workflows?
Yes. Many libraries link it to incident reporting, facilities work orders, cash reconciliation logs, or IT service tickets when a verification step fails. If a step is blocking, the checklist can trigger a follow-up task; if it is non-blocking, staff can note the issue and continue while it is routed for later action.
Related templates
Ready to use this template?
Get started with MangoApps and use Library Daily Opening and Closing Checklist with your team — pricing built for small business.
