Public Computer Usage and Sign-In Log (Library)
Track public computer sessions, station assignments, time limits, and policy acknowledgments at the library desk. Use it to manage waitlists, document extensions, and keep a clear audit trail for each patron session.
Trusted by frontline teams 15 years of frontline software
Built for: Public Libraries · Community Learning Centers · Municipal Services
Overview
This Public Computer Usage and Sign-In Log (Library) template tracks each patron session from check-in to closeout. It includes fields for patron identification, station assignment, scheduled and actual end times, time-limit extensions, usage purpose, printing volume, acceptable use acknowledgment, and staff-only incident notes.
Use it when your library needs a simple audit trail for shared computer access, especially when stations are limited and sessions must be timed. The template helps staff assign terminals, manage waitlists, document policy acceptance, and note technical problems without relying on memory or scattered paper slips. It is also useful when you need to show who used a station and when, while keeping the form focused on operational needs.
Do not use this template as a general patron registration form or a broad customer profile. If you do not need contact_email, leave it out or make it optional. If your library does not track minor consent separately, remove that field rather than collecting unnecessary PII. The form works best when required fields are limited, time fields use proper date and time inputs, and conditional logic hides irrelevant consent or incident prompts until they apply. That keeps the log fast at the desk and easier to review later.
Standards & compliance context
- Limit collection to the minimum necessary fields under GDPR Article 5 by avoiding unnecessary PII such as extra contact details.
- If the form is public-facing or kiosk-based, make sure labels, focus order, and validation support WCAG 2.1 AA accessibility.
- For minors, use a clear guardian consent field only when your library policy requires it, and keep the prompt specific to the session purpose.
- If the log is used to document accommodations or sensitive incidents, keep staff notes restricted and avoid collecting more personal data than needed.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Patron and Session Identification
This section identifies who used the station and on what date, while keeping personal data limited to what the library actually needs.
-
Date
Date of the computer session.
-
Patron Name or Library Card Number
Enter your full name or library card number. A library card number is preferred to minimize PII collection.
-
Patron Type
Select the patron category. Children under 13 must have a guardian present per library policy.
-
Email Address (Optional)
Optional. Provide only if you wish to receive a session receipt or reservation confirmation. Not shared with third parties.
Station Assignment and Session Timing
This section is the operational core of the log because it shows which computer was used, for how long, and whether the session stayed within policy.
-
Computer Station Number
Select the station number assigned by staff or the self-service kiosk.
-
Session Start Time
Time the patron began using the computer terminal.
-
Scheduled Session End Time
Calculated end time based on the standard time limit (typically 60 minutes). Staff will set this at sign-in.
-
Allocated Session Duration (Minutes)
Standard session length is 60 minutes. Extensions may be granted by staff if no patrons are waiting.
- Time Extension Granted?
-
Extension Duration (Minutes)
Enter the number of additional minutes granted. Requires staff authorization.
-
Actual Session End Time
Time the patron actually vacated the station. Completed by staff at session close.
Usage Purpose and Activity Type
This section helps staff understand why the station was used and whether printing or other resource-heavy activity affected the session.
-
Primary Purpose of Session
Select the best description of your session’s primary purpose. Used for anonymous usage statistics only.
- Please Describe (Other Purpose)
-
Number of Pages Printed (if applicable)
Enter total pages printed during this session for billing or quota tracking.
Acceptable Use Policy Acknowledgment
This section documents that the patron saw and accepted the rules before using a public terminal, which is important for consistent enforcement.
-
Acceptable Use Policy Agreement
The full Acceptable Use Policy is available at the reference desk and posted at each terminal. Use of library computers constitutes agreement with this policy.
-
Guardian Consent for Minor
Required only when patron type is ‘Child (under 13)’. Guardian must remain present during the session.
Staff Use Only — Session Close and Incident Notes
This section captures the closeout record, exceptions, and service issues so staff can review what happened without mixing it into the patron-facing workflow.
-
Session Closed By (Staff Name or ID)
Library staff member who confirmed session end and station clearance.
- Session Close Status
-
Incident or Policy Violation Description
Required if session status is ‘Policy Violation’. Include nature of violation, staff response, and whether patron privileges were suspended.
- Technical Issue Description
- Waitlisted Patron Notified of Available Station?
- Additional Staff Notes
How to use this template
- 1. Set the required fields to match your desk workflow, including log_date, station_number, session_start_time, scheduled_end_time, and aup_acknowledged.
- 2. Add conditional logic so minor_guardian_consent appears only when patron_type indicates a minor, and show extension_minutes only when extension_granted is checked.
- 3. At check-in, staff enter the patron details, assign a station, record the planned session length, and confirm the acceptable use policy before the session begins.
- 4. During the session, staff update any extension, printing_pages, or technical issue notes as soon as they occur so the record stays accurate.
- 5. At closeout, staff record actual_end_time, session_status, and any incident_description or waitlist notification, then save the entry for later review.
Best practices
- Use date and time pickers for log_date, session_start_time, scheduled_end_time, and actual_end_time instead of free-text fields.
- Keep contact_email optional unless your library has a specific follow-up reason for collecting it.
- Show minor_guardian_consent only when the patron is a minor, and label the field clearly so staff know when it applies.
- Record extensions immediately when they are granted, not after the patron leaves the station.
- Separate patron-facing fields from staff-only notes so incident details do not clutter the sign-in flow.
- Use a multi-select or controlled list for primary_usage_type if your library tracks common activities such as job search, schoolwork, email, or printing.
- Document technical_issue_description in plain operational terms, including the station number and what staff did next.
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 computer sign-in log cover?
It records the patron, date, station number, session timing, usage purpose, and whether the acceptable use policy was acknowledged. It also includes staff-only fields for session closure, incidents, and technical issues. Use it to manage public computer access without over-collecting information.
Should every patron be required to fill out all fields?
No. Keep required fields limited to what you need to assign a station, enforce time limits, and document policy acknowledgment. If your library allows anonymous or minimal sign-in, avoid collecting contact_email unless there is a clear operational reason. That supports data minimization and reduces friction at the desk.
How often should this log be used?
Use it for every public computer session, including extensions and early terminations. If a patron moves to a different station, create a new entry or clearly note the reassignment so the audit trail stays accurate. Consistent use matters more than long narrative notes.
Who should complete the staff-only closeout fields?
A staff member who actually ends or reviews the session should complete session_closed_by, session_status, and any incident or technical issue notes. This keeps the record reliable and makes it easier to resolve disputes about time limits, waitlists, or equipment problems. Patron-facing fields should stay separate from staff-only notes.
How does this template handle minors and guardian consent?
The minor_guardian_consent field is there for libraries that require a parent or guardian acknowledgment for minors. If your policy does not require it, make the field conditional so it only appears when the patron_type indicates a minor. That is cleaner than showing every consent field to every patron.
What are the most common mistakes when using this log?
Common issues include leaving time fields blank, using free-text notes instead of structured fields, and forgetting to record extensions. Another frequent problem is collecting more PII than needed, such as unnecessary contact details. Clear validation and staff training help prevent those gaps.
Can this log be customized for printing or internet-only sessions?
Yes. You can add a conditional field for printing requests, or narrow primary_usage_type to the activities your library tracks most often. If you only need internet access tracking, remove unused activity options so the form stays short and easy to complete. Progressive disclosure works well here.
How does this compare with a paper sign-in sheet or ad hoc notes?
A structured log is easier to search, review, and audit than scattered paper notes. It also reduces missed fields because validation can prompt staff to enter the station, timing, and closeout status before saving. That makes it more dependable for daily operations and incident follow-up.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
See how the Kansas City Chiefs unified communication for 600+ event staff with a branded app, achieving 90% adoption and reaching every employee on game day.
-
AI employee self-service assistants cut HR and IT support time with instant answers, automated routing, and better employee experience.
-
A vendor-agnostic checklist covering architecture, frontline access, AI, compliance, and payroll to evaluate any scheduling platform.
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
Ready to use this template?
Get started with MangoApps and use Public Computer Usage and Sign-In Log (Library) with your team — pricing built for small business.
