A library staff schedule needs to answer two questions at once: who is working, and who is covering each service point? A full roster can still leave Reference short for half an hour or assign the same colleague to two desks.
Start with the service your library needs to provide. Then build the working hours and assignments around your team’s availability, qualifications, leave and workload. The sequence below works as a planning exercise whether you are reviewing a spreadsheet or preparing a schedule in FacilitySight.
01 / Start with the service
Define what needs cover, and when.
List the desks and other assignment points for each branch. For every one, record the time windows, required headcount and relevant qualifications. Include opening and closing responsibilities, programs and duties that do not happen at a public desk.
Make changes within the day explicit. The children’s desk may need different coverage while a program is running. A branch’s opening hours may also differ from the hours staff are working behind the scenes.
| Planning field | Question to answer |
|---|---|
| Branch and desk | Where does the work happen? |
| Coverage window | What is the exact start and end time? |
| Required people | How many colleagues are needed during each part of that window? |
| Qualifications | What must someone be prepared or authorized to do? |
| Other duties | Which tasks can happen alongside the desk, and which need separate time? |
Library traffic patterns can help inform these decisions, alongside service priorities and staff knowledge. Counts do not automatically determine the right staffing level.
02 / Get the inputs right
Available, scheduled and qualified mean different things.
- Availability
- When a colleague could work. A person can be available for more hours than they are scheduled.
- Working pattern
- The regular hours or rotation used to prepare shifts. Alternating Saturdays belong here; a one-off change belongs with the relevant dates.
- Qualifications
- The desks and branches a colleague can cover. Keep these records current and review missing information before making an assignment.
- Approved leave
- An absence that affects the plan. Keep requests awaiting a decision distinct from approved time off.
Review contracted or expected hours and desk-hour targets as well. Someone may be available and qualified without being the best choice for another assignment after considering their existing workload.
FacilitySight keeps availability alongside recurring working hours and supports desk and branch qualification records. Managers review suggested colleagues with that context before choosing coverage. See coverage and skills.
03 / Build the day
Place assignments inside working hours.
Prepare the shifts first, then place the desks, programs, other duties and breaks within them. Reuse the familiar parts of a week, but review the new dates before treating the copied plan as ready.
A colleague working 9 am–5 pm might cover a morning desk, take a break, support a program and return to a different service point. A single 9–5 row describes their hours; it does not show whether every service point is covered.
- Check whether an assignment falls outside someone’s working hours.
- Look for overlapping assignments and breaks that remove required cover.
- Review the precise intervals where assigned headcount falls below the requirement.
- Check whether moving someone solves one gap but creates another.
In FacilitySight, recurring patterns create working hours; desk assignments can be authored or copied separately. Coverage compares the assigned people with the requirements set by the manager.
04 / Prepare for changes
Follow an absence through the whole plan.
A leave approval may affect several desks, a program and a closing duty. Review all affected assignments before choosing a replacement. Keep full- and partial-day absences precise so a short appointment does not become an unexplained whole-day change.
- Confirm the dates and hours of the absence.
- Identify the affected assignments and their coverage requirements.
- Review suitable colleagues against availability, qualifications and workload.
- Check the wider schedule after making the change.
- Publish the revised plan so the team has one version to work from.
Keep PTO balances explainable too. Opening balances, accrual or grants, approved leave, adjustments and eligible refunds should make the closing balance understandable. In FacilitySight, pending requests do not reserve PTO; approval records the leave debit. Read the scheduling and PTO details.
05 / Review together
Check the week before the team depends on it.
Review both the desk view and the person view. The desk view shows gaps. The person view reveals an uneven workload, difficult handovers or time placed against the wrong assignment.
- Required coverage and any unresolved gaps are visible.
- Leave, availability, qualifications and dated changes have been considered.
- Working hours, breaks and desk-hour targets have been reviewed.
- The team knows which published schedule to use and how to raise a change.
FacilitySight lets managers prepare a draft before publishing. Staff can see their published schedule, request leave, review PTO balances and history, and manage availability where employee editing is enabled. Printed schedules and read-only personal calendar feeds provide other ways to share the week.
06 / Keep the records clear
A schedule is the plan. Time entries record worked hours.
“Library staff tracking” can describe several different needs. Be specific about whether you want scheduled desk coverage, recorded hours, PTO balances or progress on a task. Each needs a different record.
For a library time clock, define how staff clock in and out, who reviews missed punches, and how someone requests a correction. Preserve the reason and history for a change so a manager can understand what happened. A missing clock-out should be reviewed; it should not silently become an assumed departure time.
FacilitySight’s time-clock workflow uses a phone, desktop or shared PIN kiosk and a manager review queue for missed punches and correction requests. Keep those time records separate from scheduled coverage. Anonymous people counters do not identify which employees are present.
If a particular payroll or HR connection is part of your requirements, confirm it with the team before including it in an implementation plan. Review connections and requirements.
07 / Prepare the next week
Bring one real week to the conversation.
You do not need to describe every possible scheduling problem. A week with a difficult handover, a leave request or a program is a useful place to start.
- Branch opening hours and service-point coverage requirements.
- Recurring staff hours, rotations and dated availability.
- Desk and branch qualifications.
- Approved leave and your PTO policy.
- Programs, breaks, closing duties and known coverage gaps.
- The way staff receive schedules and request changes today.
Staff Scheduling and Work Items can be used without people-counting hardware. Explore library staff scheduling or review pricing and purchasing.
Talk through your library schedule