Starting at the front desk: how visitors arrive

• Tell me about a typical morning at your front office during arrival and morning drop-off.
• Walk me through your current visitor sign-in process from when someone arrives to when they are cleared to enter.
• When a new visitor signs in, who usually verifies their photo ID or relationship to a student?
• How many visitors does a single front desk typically manage on a heavy day? Options: Fewer than 10, 10 to 30, 31 to 60, 61 to 100, More than 100
• Describe any moments that cause lobby congestion or make front office staff feel rushed.

Where paper fails you

• Imagine a parent dispute or an emergency requires an accurate roster right now, how confident are you that handwritten logs would hold up? Options: Very confident, Somewhat confident, Not confident
• Tell me which visitor categories are most likely to saunter past the sign-in undetected, and why.
• Name who typically notices first when an unscreened contractor or volunteer is in the building.
• On average, how often do you discover a mismatch between sign-in records and who was actually in the building at dismissal? Options: Daily, Weekly, Monthly, Rarely, Never
• What single failure in your current sign-in process would make you halt a rollout of any new system?

When speed matters: balancing fast check-in and strict screening

• Suppose check-in took an extra 30 seconds per visitor, would your front office halt the process or absorb the delay for better screening? Options: Halt or revert, Absorb the delay, Unsure
• At what times of day do you see the most pressure to speed check-in and why?
• Call out the staff roles most likely to push back if check-in slowed the line. Options: Front office lead, Principal, Security staff, Other
• Estimate how many visitors per hour your busiest lobby processes during peak times. Options: Fewer than 10, 10 to 30, 31 to 60, More than 60
• If a proposed solution cannot process visitors within your busiest 90th percentile time, would that rule it out? Options: Yes, rule out, No, we would evaluate trade-offs, Need to test first

Guardrails for custody, contractors, and volunteers

• Have you ever had a custody hold or restriction missed by your current process, and what happened next?
• List the systems or documents that contain your custody and restriction flags today.
• Identify the point person responsible for approving volunteer and contractor access.
• List the volunteer and contractor types that require pre-registration versus those allowed to sign in on arrival.
• What single data gap, for example missing custody flags or contractor insurance records, would stop this project from moving forward?

The legal, community, and political pressure points

• Imagine a community member demands proof of who was in a building during an incident, could you produce that report without legal review? Options: Yes without review, Yes with review, No
• Identify the approvals this rollout needs from district leadership, unions, or legal counsel. Options: Superintendent, School board, Legal counsel, Union representative, Facilities director, Other
• Please list the role responsible for final sign-off on security tools and the associated budget.
• Describe the privacy or student data handling concerns your counsel raises most often.
• What threshold of parental or board concern would force you to pause or accelerate this project? Options: Minor complaints, Formal board inquiry, Legal threat, State investigation, Other

The other options you are weighing

• What vendors, incumbent systems, or internal projects are you actively considering instead of an outside visitor-management partner? Options: Current paper process, Existing vendor or incumbent, In-house build, Other vendor, Undecided
• If you stayed with your current approach, what would have to be true about it for you not to change?
• Has anyone proposed building a solution in-house, and who would be expected to own that effort? Options: Yes, IT would build, Yes, operations would own, No internal proposal, Other
• Rank the evaluation criteria that matter most in selecting a visitor-management partner. Options: Screening coverage, Check-in speed, SIS integration, Badge printing quality, Reporting and rosters, Price, Support and SLAs
• If the incumbent can match your top two criteria today, what would still make you choose a new platform?

What must be true before we can start building

• Are there any integration blockers, such as lack of SIS access or closed access-control APIs, that would prevent work from starting? Options: SIS access unavailable, Access control APIs closed, Badge printers not networked, Contractor data unavailable, No blockers identified, Other
• Select the systems that must integrate at launch. Options: Student information system (SIS), Access control system, HR/contractor database, Badge printers and kiosk software, Directory/AD, Other
• Point to the person or role in IT or data who will own credentials and API access, and note whether they have bandwidth this quarter.
• Estimate the cleanliness of the student and staff data that would feed custody alerts: mostly clean, some cleanup needed, or large gaps. Options: Mostly clean, Some cleanup needed, Large gaps require major cleanup
• Where are the physical constraints we should know about, such as badge printer locations, locked lobbies, or limited floor space?
• Is there a hard date or regulatory deadline that, if missed, would cancel or restart the project? Options: No fixed date, Board or community timeline within 30 days, Regulatory or state deadline within 90 days, Other

Acceptance criteria and the pilot that proves it

• If the pilot does not produce a clear reduction in unscreened entries or a verified check-in time under your target, would you stop evaluation? Options: Yes, stop evaluation, No, iterate and retest, Undecided
• Select the measurable success signals you'd want validated during a pilot. Options: Reduction in unscreened entries, Average check-in time under target, Accurate custody alerts, Badge printing reliability, Emergency roster accuracy, Front office adoption rate, Clear on-demand reporting
• Who will sign off on pilot acceptance and what specific data will they require?
• How long a pilot period do you see as sufficient to make a go or no-go decision? Options: 1 week, 2 weeks, 4 weeks, 8 weeks, Other
• Should the pilot prove the numbers, what internal step would move this to a signed contract quickly?
• What single internal objection could still block you from moving to procurement even after a successful pilot?

Next steps and quick wins

• If we could deliver one quick win in 30 days that reduces lobby congestion, which would matter most to you? Options: Pre-registered volunteers, Fast-track badge printing, Queue management at peak arrival, Automated custody alerts, Other
• Point to the next stakeholder we should engage to validate requirements.
• What documents or diagrams would accelerate scoping work, for example floor plans, current sign-in logs, or an SIS access plan? Options: Floor plans, Current sign-in logs, SIS access plan, Badge printer locations, Contractor/volunteer lists, Other
• Would a live lobby observation or a remote video walkthrough be possible in the next two weeks? Options: Yes, on-site observation, Yes, remote walkthrough, Not possible in two weeks
• Who should be on a short implementation readiness call from your side? Options: Principal, District safety director, IT lead, Front office lead, Facilities manager, Legal counsel
• Do you have a preferred contract timeline that, if met, would cause you to prioritize this project above others? Options: Within 30 days, Within 60 days, Within 90 days, No firm timeline, Other

• Solution Experience Session

• Confirm the current state and its cost
• You confirm the demonstrated workflows would eliminate the manual sign-in gaps and produce reliable rosters during an emergency.
• Provide a test-run configuration and simulated visitor data for your busiest school to validate throughput and badge printing before the follow-up session.
• Proof: Screening and watchlist match using your scenario
• You verify the screening accuracy and badge workflow meet your check-in speed requirements to avoid lobby congestion.
• Share the list of custody-restricted students and any existing watchlist rules to seed the custody alert and watchlist tests.
• Proof: Fast check-in and badge issuance under peak load
• Deliver a draft integration dependency checklist for SIS and access control endpoints, including required credentials and data fields, for buyer review.
• You agree on the remaining technical evidence and acceptance criteria needed to move toward procurement and rollout.
• Identify the typical peak arrival window and average check-in counts per hour for the schools in scope to size kiosk and staffing recommendations.
• Proof: Custody alerts and emergency roster generation
• Confirm fit: does this match your need?
• Decide evidence and next steps

• Solution Experience Session
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• Lobby Kiosk Installation
• Visitor Screening Against Public Registries
• Custom Watchlist Upload and Management
• Photo ID Capture and Badge Printing
• Time-Stamped Entry and Exit Logging
• Student Information System Integration
• Access Control Door Release Integration
• Volunteer and Contractor Pre-Registration
• Recurring Visitor Profile Setup
• Emergency Roster Generation
• District-Level Reporting Dashboard Deployment
• Mobile Check-In for Events
• Ongoing Screening Database Updates
• Front Office Staff Training and Onboarding

Lobby Kiosk Installation

• How many school buildings require a kiosk installed in the main office lobby? Options: 1-3, 4-10, 11-25, 26+
• Which physical entrances at each school need kiosk coverage (main office only, main + visitor entrance, gym/auditorium event entrance)? Options: Main office only, Main office + main visitor entrance, Include event entrances (gym/auditorium), Other
• Where will each kiosk be powered and networked (power outlet location, wired Ethernet jack, Wi-Fi SSID and VLAN)?
• Who will coordinate on-site access and keys for installers during the scheduled install window?
• When are your preferred install windows for each site (school hours only, evenings, summer break dates)? Options: During school hours, Before/after school, Evenings/weekends, During scheduled break (summer/holiday)
• What acceptance criteria will confirm a kiosk installation is complete at each school (for example: kiosk boots to production, prints test badge, connects to SIS lookup)?

Visitor Screening Against Public Registries

• Which public registries must the screening check include for your district (state sex offender index, multi-state central registry, county-level lists)?
• How frequently do you require nightly or real-time screening updates against the public registries? Options: Real-time/near real-time, Nightly, Weekly, Monthly
• Which visitor attributes from the kiosk should be matched to registry records (full name, date of birth, alias, photo)? Options: Full name, Date of birth, Alias/AKA, Uploaded photo
• What threshold or match rules do you prefer for flagging an alert (exact name + DOB match, fuzzy name with DOB, fuzzy name only)? Options: Exact name + DOB, Fuzzy name + DOB, Fuzzy name only, Custom rules
• Who in your district reviews registry alerts that the system generates (front office, safety director, school resource officer)? Options: Front office staff, School safety director, School resource officer, Other
• Describe how you want registry alerts surfaced in the lobby workflow (hold for staff review before badge, allow badge with custody alert, immediate deny with staff call)? Options: Hold for staff review, Allow badge but flag custody alert, Prevent check-in and notify staff, Other

Custom Watchlist Upload and Management

• What types of custom watchlists do you maintain that need system upload (custody-restricted guardians, banned visitors, contractor blacklists)?
• Which file format do your watchlist exports currently use for bulk upload (CSV with columns, Excel, API endpoint)? Options: CSV (name, DOB, reason), Excel spreadsheet, API feed, Other
• How often will your team update custom watchlists (ad hoc, daily, weekly, monthly)? Options: Ad hoc, Daily, Weekly, Monthly
• Who is authorized to add or remove names from your custom watchlists, and how should those role permissions map to the system?
• Provide the minimum fields you will include in a watchlist record for upload (e.g., first name, last name, DOB, reason, source document ID).
• Indicate any legal or privacy constraints on sharing watchlist data across schools (court orders, gag orders, restricted distribution). Options: No constraints, Restricted by court order, Restricted to district admins, Other

Photo ID Capture and Badge Printing

• Which badge format do you require for visitors (CR80 credit-card size, paper temporary badge, laminated badge)? Options: CR80 (plastic) badge, Standard badge paper (single sheet), Laminated badge, Other
• Which badge printer models are currently available at each site or planned to be provided to installers?
• How many badges per day do you expect at the busiest school to size printer supplies and stock (estimate peak daily badges)? Options: Less than 50, 50-150, 150-500, 500+
• Where should visitor photos be stored and for how long according to your retention policy (on-device cache, central database, retention period in days)?
• Who may approve exceptions to photo capture (parents declining photo, known volunteers) and what alternate badge treatment is acceptable? Options: Principal approval, District safety director, No exceptions, Other
• Which badge elements must appear on the printed badge for your acceptance (photo, name, visit reason, expiration timestamp, school logo)? Options: Photo, Name, Visit reason, Expiration timestamp, School logo

Time-Stamped Entry and Exit Logging

• How should entry and exit times be recorded for multi-door campuses where visitors move between buildings? Options: Log per kiosk by building, Single district-level log, Log only on initial check-in and final check-out, Other
• Which identifier should the system use to correlate a visitor's check-in and check-out events (badge ID, name + DOB, temporary QR code)? Options: Badge ID, Name + DOB, Temporary QR code, Other
• What maximum acceptable clock skew is allowed between kiosk timestamps and district server time for records to be valid (seconds or minutes)? Options: Under 5 seconds, Under 1 minute, Under 5 minutes, Custom
• Where do you want exit events captured if staff forgets to scan out (manual front office check-out, mobile check-out, automated after set idle time)? Options: Manual front office, Mobile check-out, Auto after idle period, Other
• Describe any reporting requirements tied to time-stamped logs for drills or audits (CSV export, timestamped PDF, integration to SIS attendance reports). Options: CSV export, Timestamped PDF, SIS attendance export, Other
• Specify retention period for entry/exit logs for compliance or investigative needs (90 days, 1 year, 7 years, other). Options: 90 days, 1 year, 7 years, Custom

Student Information System Integration

• Which Student Information System (SIS) or vendor does your district use and what version or API endpoint is available for integration?
• Which SIS data elements must be shared to enable custody and restriction alerts (student ID, guardian name, custody indicator flags, emergency contact relationships)?
• How will we receive access to SIS data for integration: secure API credentials, SFTP nightly export, or scheduled CSV push? Options: Secure API (recommended), SFTP export, Scheduled CSV push, Other
• Who in your district will approve SIS data access and complete the necessary release/ROIs for integration?
• What measurable acceptance criteria will validate SIS integration (for example: custody flags sync within 15 minutes, 95% student-guardian match rate)?
• List any data privacy or FERPA-related constraints we must follow when storing or displaying SIS-derived alerts at the kiosk.

Access Control Door Release Integration

• Which door controller manufacturers or protocols are in use at your sites (provide controller model or protocol such as Wiegand, OSDP, or REST API)?
• Which specific doors do you want integrated for remote release from the kiosk workflow (front office main entrance, courtyard gates, gym exterior doors)?
• What authorization rule should trigger a door release from a successful visitor check-in (staff approval, auto-release for pre-registered visitors, staff PIN entry)? Options: Staff approval required, Auto-release for pre-registered, Staff PIN on kiosk, Other
• Who will provide access to the door controller systems for testing and what credentials or on-site support window is required?
• Describe any forced-entry or lockdown behaviors integration must support (prevent release during lockdown, log attempted releases during lockdown). Options: Prevent release during lockdown, Log attempted releases, Allow override by safety director, Other
• Indicate your desired SLA for verifying a door-release integration in staging before production go-live (functional tests completed within X days). Options: 3 business days, 5 business days, 10 business days, Custom

Volunteer and Contractor Pre-Registration

• How do volunteers and contractors currently apply to work on campus (paper form, online form, third-party vendor)? Options: Paper form, Online district form, Third-party vendor, Other
• Which pre-registration fields are mandatory for volunteers/contractors (full name, DOB, company, background check ID, insurance certificate)?
• Do you require background check verification before issuing a badge for contractors or volunteers, and what vendor or certificate type is acceptable? Options: Yes, vendor certificate, Yes, district background check, No, review on arrival, Other
• Who owns the approval workflow for pre-registered contractors (site admin, district procurement, facilities manager)? Options: Site admin, District procurement, Facilities manager, Other
• Provide the expected turnaround time you require from submission to approval for pre-registered volunteers and contractors. Options: Same day, 1-3 business days, 3-7 business days, Custom
• Indicate whether pre-registration should auto-generate a QR check-in code or a printable temporary badge for the contractor/volunteer. Options: Auto QR code, Printable temporary badge, Both options, Neither

Recurring Visitor Profile Setup

• Which categories of recurring visitors do you want profiles for (after-school tutors, recurring contractors, district staff, volunteers)? Options: After-school tutors, Recurring contractors, District staff, Volunteers, Other
• How long should a recurring visitor profile remain active before requiring re-verification (30 days, 90 days, 1 year)? Options: 30 days, 90 days, 1 year, Custom
• What fields must be included in a recurring visitor profile to speed check-in (photo on file, vehicle plate, company, recurring schedule)?
• Who can create or edit recurring visitor profiles within the system at each school? Options: Front office staff, Principal, District admin, Other
• Describe any approval or background-check revalidation required when converting a pre-registered visitor into a recurring profile. Options: No revalidation, Background check required, Supervisor approval required, Other
• Indicate whether recurring profiles should allow scheduled recurring check-ins (automatic sign-in on approved days) and which visitor categories may use that. Options: Allow for tutors, Allow for contractors, Allow for staff only, Disable scheduled auto sign-in

Emergency Roster Generation

• Which real-time roster exports do you need for emergency response (CSV with current occupants, PDF roster by room, API feed to emergency system)? Options: CSV current occupants, PDF roster by room, API feed to emergency system, Other
• How often must the emergency roster update during a drill or incident (real-time stream, every 30 seconds, every minute)? Options: Real-time stream, Every 30 seconds, Every minute, Every 5 minutes
• Who should be authorized to pull or receive emergency rosters (principal, district safety director, first responders)? Options: Principal, District safety director, First responders, Other
• Provide the fields required on an emergency roster for your incident command (visitor name, badge ID, check-in time, assigned room or last-known location).
• Where should emergency roster exports be staged for rapid access (local kiosk, district cloud storage, secure API endpoint)? Options: Local kiosk cache, District cloud storage, Secure API endpoint, Other
• Specify any integration needs to your emergency notification or mass-notification system for automated roster delivery.

• Subscription Agreement / Order Form
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Service Level Agreement (SLA)
• Data Processing Agreement (DPA)
• Public-Sector Procurement & Security Addendum
• Acceptance & Go-Live Certificate
• Change Order Agreement
• Ongoing Screening Update Schedule

• Go-live Health Check
• First Outcomes Measurement
• Acceptance Gate Review
• Quarterly Success Review

• Publish the quarterly performance summary to the shared channel for ongoing issue tracking.
• Confirm the incumbent wind-down path, archive location for legacy sign-in data, and the timeline to close any fallback habits.
• Agree remediation actions and target close dates for any failed criteria.
• Publish the acceptance record with pass/fail per criterion and the buyer's named signatory.
• Archive legacy sign-in records to the agreed storage location and confirm access permissions.
• Create remediation tickets for failed criteria with closure deadlines and required verification steps.
• Schedule a targeted verification check once remediation items are complete to confirm acceptance closure.
• Metrics and trend review
• Confirm emergency roster accuracy and badge print success rate remain at or are moving toward Solution Scope targets.
• Reduce the count of overdue tickets and ensure priority enhancement requests have clear next steps.
• Agree focused adoption or training activities for the coming quarter to close observed gaps.
• Close or update all tickets older than 30 days and publish their current status.
• Prioritize the top three enhancement requests and create implementation tickets with expected delivery quarters.
• Schedule a front-office refresher training session and distribute updated quick-reference guides.
• Re-confirm success criteria and ownership
• Confirm each acceptance criterion has a named owner for remediation or verification.
• Validate that all critical integrations (SIS, printer, access control) show recent successful activity.
• Produce a prioritized list of open issues with target resolution dates.
• Publish the go-live issues log with priority and target resolution dates.
• Enable or verify SIS data access and confirm sample records sync successfully.
• Perform an on-site badge printer check and document printer location and paper stock.
• Run a watchlist sync and report any recent alert matches or sync errors.
• Present first-period outcome data
• Determine whether average check-in time and weekly active front-office users are trending toward Solution Scope targets.
• Identify root causes for any metric gaps and agree specific remediations with deadlines.
• Capture operational quality issues requiring configuration or hardware adjustments.
• Adjust kiosk placement or signage to improve check-in throughput by the agreed date.
• Update badge template and run a print-quality verification test.
• Refine watchlist rules or screening thresholds and schedule a re-run of recent records for verification.
• Produce a follow-up data extract for the agreed remediations to validate changes at the acceptance gate.
• Restate acceptance criteria and numeric targets from Solution Scope
• Produce a documented pass or fail for each acceptance criterion recorded in Solution Scope and capture the buyer's formal acceptance decision.
• Present outcome data against each criterion
• Open tickets and enhancement backlog
• Deployment and integration validation
• Root-cause diagnosis for metric gaps
• Operational quality checks
• Early adoption and usage signals
• Document pass/fail and capture formal acceptance
• Adoption and training needs
• Incumbent system wind-down and data archiving
• Open issues, defects, and blockers
• Agree next-quarter operational priorities
• Agree corrective actions and timeline
• Agree remediation items and closure timelines
• Immediate remediation plan