A Cleared Visitor Can Still
Take the Wrong Child.
Most visitor systems tell you who is at the door. Tool For School tells you whether they are allowed to leave with a specific student — and produces the audit trail to prove you followed protocol.
How It Connects to Custody and Dismissal
Sex offender registries. ID scanners. Visitor badges. Schools invest in all of it. And a custody-restricted parent can walk right through every single layer of it, because none of those systems know what the custody order says.
Tool For School Building Access is not a visitor log. It is the enforcement chain that connects identity verification, custody rules, dismissal authorization, and release confirmation into one unbroken record — from the moment someone arrives at your front door to the moment a child walks out of it.
If something goes wrong, you will need to show exactly what your system knew, who made each decision, and what protocol was followed. This is that system.
The Problem
Your Front Office Should Never Have to Remember Custody Rules
Memory is not a safety system. Neither is a binder.
A parent arrives at 1:45 PM for an early pickup. Their ID scans clean. The sex offender registry comes back clear. A badge prints. Staff waves them through. Nobody checked whether this parent has an active custody restriction for this child. That information was sitting in the SIS. Nobody looked. Nobody had time to look.
A grandfather arrives who has been picking up his granddaughter every Tuesday for two years. Staff recognize him. They stop checking ID because it feels like an insult. Nobody knows he was added to the district deny list six months ago after an incident at another school.
A custody-restricted parent learns to arrive during the chaotic 15 minutes at the end of the school day. Staff are managing twenty things at once. A judgment call gets made. The child leaves with someone they should not have left with.
These are not failure stories about bad staff. They are failure stories about systems that ask humans to remember things humans should not have to remember. The liability is not just the incident. The liability is not being able to show what your system knew, what it checked, and what it decided. Building Access gives you that record.
The Solution
Identity. Custody. Screening. Release.
One Connected Record.
Every step is deterministic. Every decision is logged. No step can be skipped.
Visitor Arrives
Staff opens Building Access on the front desk tablet. If the district uses Verkada, the visitor's image appears on screen automatically when they press the intercom button outside. The check-in flow opens pre-populated with the entry point and timestamp. If the visitor presses intercom and walks away, that event is still logged.
Identity Verified
Staff scans the visitor's driver's license barcode using the tablet camera. Name, date of birth, and state are extracted in under 2 seconds. No proprietary scanner required. Manual entry is available as a fallback. Every check-in records how identity was captured — barcode scan, manual entry, or digital wallet — and that method is part of the permanent record.
Guardian Resolution
The system matches the captured identity against the SIS guardian snapshot. If the visitor matches a guardian record, they are resolved as a known contact and their linked students are identified. If they do not match any record, they are flagged as an unresolved visitor. Resolution method and confidence level are logged.
Screening — Five Checks, In Order
Every visitor goes through the same five checks regardless of who they claim to be: guardian authorization, active custody restrictions, school and district ban list, incident flags, and sex offender registry via offenders.io covering all 50 states with daily sync. All five checks run. All five results are logged. The full screening record is retained regardless of outcome.
Decision — Three Outcomes
Green: visitor is cleared, badge is issued, visit is logged. Yellow: admin review required — a notification goes to the school admin with the specific flag reason, admin approves or denies. Red: access blocked — staff see the reason, the visitor does not, and the blocked attempt is permanently logged.
Downstream Workflows
For early pickups: a dismissal request is created automatically in the Dismissal module. The student's teacher is notified. A child release record is created. Physical handoff must be confirmed by staff before the pickup is marked complete. The chain from arrival to release is one unbroken audit record.
Screening
Five Checks. Every Visitor. Every Time.
No check can be skipped. No result can be edited after the fact.
Guardian authorization
Is this person listed as an authorized contact for the student they are here to see?
Custody restrictions
Does an active custody restriction exist for this person and this student today?
Ban list
Does this person appear on the school-level or district-level ban list?
Incident flags
Has this person been flagged by a school or district administrator for a prior incident?
Sex offender registry
Does this person appear in the national sex offender registry via offenders.io — all 50 states, U.S. territories, and tribal databases with daily synchronization?
Three Possible Outcomes
The system decides. Staff execute.
Visitor passes all five checks. Badge is issued. Visit is logged with full screening record.
A flag requires a human decision. Admin is notified with the specific reason. Visit stays pending until admin approves or denies.
Access denied. Staff see the reason. The visitor does not. The blocked attempt is permanently logged.
Registry Logic
A Registry Match Is Not Always a Block
Tool For School applies different logic for an unknown visitor versus a resolved guardian — because the legal exposure is different in each case.
Most visitor management systems treat a sex offender registry match as a binary outcome. Match equals block. That is the right answer when the visitor is a stranger with no connection to any student. It is the wrong answer — and a legal liability for your district — when the visitor is a custodial parent who is on a registry but has no court order restricting their school access.
Unresolved visitor with a registry match
Immediate block. The visitor has no established relationship to any student and appears on the national registry. Entry is denied. A supervisor is notified. The visitor is not told why. The blocked attempt is logged in full.
Resolved guardian with a registry match
Admin review, not an automatic block. The system notifies the school admin and flags the specific match. Admin checks whether an active custody restriction or court order already restricts this person's access. If a custody restriction exists, that restriction is the block reason. If none exists, an administrator or SRO is present for the interaction and makes the final call.
Deny Lists
Your Deny Lists Work Across the District.
Your Incident Flags Follow a Person.
One flag entered by one administrator protects every school in the district — automatically.
School-level ban list
Managed by school admin. Applies to all check-ins at that school. A name added by a single administrator is enforced on every subsequent visit without any staff needing to know who is on it.
District-level ban list
Managed by district admin. Applies across every school in the district. A person removed from one campus for a serious incident is automatically flagged at every other campus in the district on their next visit.
Incident flags
Elevates a visitor to admin review without necessarily blocking — useful for prior concerns without a current active restriction. Incident flags can have expiry dates, severity levels, and reason codes. Every create and clear action is logged with actor, timestamp, and reason.
Audit Trail
When Something Goes Wrong, You Need to Show What the System Knew
Every access event produces a permanent, append-only audit record. Nothing is editable after the fact.
Identity capture
Method (barcode scan, manual, digital wallet) and confidence score for every check-in.
All five screening results
Every flag triggered or cleared, logged in full, regardless of the final outcome.
Every decision recorded
Who made each decision and when — staff, admin, system. No anonymous actions.
Override documentation
Override requests and approvals with the exact reason selected, actor name, and timestamp.
Teacher notifications
Notifications sent and acknowledgments received, with timestamps.
Physical handoff
Handoff confirmation and checkout time — the chain does not close until staff confirm release.
Visit logs retained
Audit logs retained
Records cannot be edited or deleted
Access to the log is itself logged. Every time a staff member, admin, or district user views the audit log, that access is recorded with actor, timestamp, and scope.
Integrations
If Your District Has Raptor or Verkada,
This Makes It Custody-Aware.
Tool For School does not replace your physical security investment. It adds the enforcement layer your physical security system cannot provide.
Raptor
Raptor handles ID scanning hardware, badge printing, and sex offender registry screening. Tool For School adds custody enforcement, ban list management, dismissal workflow integration, child release records, and the full audit trail. Both systems run simultaneously.
Verkada
Verkada handles cameras, intercoms, and door access control. Tool For School connects via a webhook registered in Verkada Command — a two-minute setup. When a visitor presses the intercom, the check-in flow opens automatically. After screening clears, Building Access sends a door release signal back to Verkada.
Starting from scratch
A front desk tablet and a standard badge printer is everything you need for Phase 1. Any modern iPad or Android tablet handles ID scanning via the built-in camera. Standard badge printers from Brother or Zebra work without additional configuration. No proprietary hardware, no vendor lock-in.
| Capability | Raptor | Verkada | Tool for School |
|---|---|---|---|
| ID scanning and badge printing | Yes | Yes | Yes |
| Sex offender registry | Yes | No | Yes — national, daily sync |
| Ban lists and deny lists | Yes | Limited | Yes — school and district level |
| Incident flags | No | No | Yes |
| Custody restriction enforcement | No | No | Yes |
| Guardian vs. stranger screening logic | No | No | Yes |
| Dismissal workflow integration | No | No | Yes |
| Child release records and handoff | No | No | Full append-only audit trail |
| Works with existing hardware | No — proprietary | No — proprietary | Yes |
High-Risk Interactions
The Two Parent Interactions With the Highest Risk and the Thinnest Paper Trail
Building Access turns both into documented, auditable workflows connected to dismissal and attendance.
Early Pickup
When a guardian clears screening for an early pickup, Building Access creates a dismissal request in the Dismissal module automatically. The student's teacher receives a notification and has 3 minutes to acknowledge. If there is no response, the request escalates to the front office queue and the attendance office.
Staff confirm physical handoff before the pickup is marked complete.
For siblings, one parent check-in handles all students. Each student gets a separate child release record. Each teacher gets a separate notification. The pickup is not marked complete until every child's handoff is confirmed.
Late Drop-Off
When a parent arrives late, staff capture a structured reason: medical appointment, transportation delay, family issue, school appointment, weather, or other. The event is linked to the school's operational calendar and attendance window.
An attendance review entry is created automatically in the attendance office queue. No attendance code is assigned by the system — that decision belongs to authorized attendance staff.
When a parent later disputes an unexcused absence, the record is there: identity, reason, exact arrival time, and calendar context in one retrievable record.
Rollout
Live in Days. No Hardware Procurement Required.
Three phases. Each independently useful. No phase depends on hardware you do not already have.
Core Access Control
Front desk tablet + badge printer
- ✓ Visitor check-in and ID scanning
- ✓ Guardian resolution against SIS
- ✓ Five-layer screening including sex offender registry
- ✓ School and district ban list management
- ✓ Incident flag management
- ✓ Badge printing
- ✓ Full append-only audit logging
Parent Event Workflows
Requires Dismissal module
- ✓ Early pickup with dismissal integration
- ✓ Child release records
- ✓ Late drop-off with attendance review
- ✓ Teacher notifications with escalation
- ✓ Calendar correlation
Physical Security Integration
Verkada or kiosk hardware
- ✓ Verkada webhook for automatic arrival detection
- ✓ Door release signal after screening clears
- ✓ Kiosk self-service for vestibule deployments
- ✓ Digital wallet identity (Google Wallet, Samsung Wallet)
- ✓ District-level analytics
FAQ
Building Access FAQ
Common questions from schools evaluating this module.
We already have Raptor. Do we have to replace it? ▾
We use Verkada. How does this integrate? ▾
What is on the ban list and who manages it? ▾
What happens when a custodial parent is on the sex offender registry? ▾
What if a visitor is in the registry but we want to let them in anyway? ▾
How long are records kept? ▾
Who can see screening results? ▾
Does this replace our SIS? ▾
See Building Access in Your School
15-minute demo. Real workflows. We walk through an actual visitor check-in from arrival to release.