Questions Schools Ask
Thoughtful questions deserve thoughtful answers.
Every school is different.
These are some of the questions we hear most often as schools explore whether Ona Pass is the right fit.
If your question isn’t answered here, we’d be happy to discuss it during a Pilot Pre-Flight.
Getting started
- How long does implementation usually take? For a pilot school, administrator setup typically takes about 20–30 minutes. Most Teachers & Staff learn the primary workflow in about four minutes. Many teams issue their first real passes within the first day once roster data is verified.
- How much preparation is required? Less than many schools expect. You need a modern browser, trial keys, a verified staff roster, and a small team ready to participate. We provide onboarding guidance; you do not need a separate training day before the pilot begins.
- Can we begin with one department? Yes. A focused pilot often starts with a team of about ten staff—which may be a grade level, department, or mixed group that creates and receives passes regularly. Starting small is intentional.
- Do we need district approval before starting? It depends on your district’s procurement and technology policies. Many schools begin with a single-campus pilot while keeping purchasing and IT informed. If your LEA requires advance approval, we are happy to join that conversation during a Pilot Pre-Flight.
Everyday use
- How quickly can a pass be created? Most staff complete pass creation in about five seconds once familiar: choose a student, pick a destination, send. The New Pass sheet stays on the page they already have open.
- How much training do Teachers & Staff need? The primary workflow—create a pass, see who is out, act on Passes To You—typically takes about four minutes to learn. A short walkthrough or quick-start guide is usually enough for daily use.
- What happens if someone forgets? The workflow is designed to stay forgiving. Staff can search for students as they type, enter a name that is not in the roster when needed, and return to the same notebook page throughout the day. Forgetting a step should not require calling the office.
- Does Ona Pass replace our existing procedures? Not automatically. Ona Pass supports your pass routines with a clearer record—your school still defines when passes are appropriate, how long students may be out, and how staff respond. Many schools use a pilot to see how digital passes fit alongside existing expectations.
Technology
- What devices are supported? Ona Pass runs in modern web browsers on desktop, laptop, and tablet—typically Chrome, Safari, Edge, or Firefox. See the IT overview for pilot deployment scope.
- Does every student need a device? No. The pilot experience is staff-facing. Teachers & Staff create and manage passes; students do not need accounts or apps for typical pilot use.
- How is data protected? Ona Pass collects only the fields the pass workflow requires and separates staff and administrator access by role. We document our FERPA-aware framing, data minimization approach, and honest preview/pilot status on the Security & Privacy page. Your technology and legal teams should review that material before pilot participation.
- How difficult is implementation for IT? For a pilot, implementation is intentionally limited: browser access, standard HTTPS traffic, no local install, and documented demo or scoped school onboarding. Production rollout at district scale requires a separate review—we describe current scope honestly on the IT page rather than implying enterprise readiness that is not yet available.
Pilot Program
- What happens during a Pilot Pre-Flight? See What is a Pilot Pre-Flight? on the Pilot Program page for the full process and checklist.
- Who should participate? A mix of staff who regularly create passes and staff who receive students, plus an administrator who can verify roster data and observe campus activity. About ten staff is a typical pilot scope—enough to evaluate real use, small enough to manage support.
- How do we evaluate success? Look for practical signals: Are passes being created during normal class time? Do staff follow a consistent workflow? Is movement easier to understand? Are support requests manageable? Would staff choose to continue? We encourage schools to define their own review questions rather than relying on login counts alone.
- What happens after the pilot? Your team decides what comes next. Expansion to additional staff or schools should follow evidence from the pilot—not a predetermined timeline. If the workflow does not fit, ending the pilot is a valid outcome. See the Pilot Program page for scope and timeline details.
Questions behind the questions.
Many questions about software are really questions about change.
Schools want to know whether a new system will respect teachers’ time, support students, and fit naturally into the school day—not add another layer of work that nobody asked for.
Those are the same questions we asked ourselves while building Ona Pass. Will staff actually use it? Will it protect instructional time? Will it create more reporting work for administrators? Will it feel like surveillance, or like a clearer record of routines schools already have?
We try to answer those questions honestly here and during a Pilot Pre-Flight. If the honest answer is “it depends on your school,” we say so—because a good partnership starts with clear expectations, not confident guesses.
Explore related perspectives
Different roles ask different questions. These pages go deeper on the workflows and decisions that matter to each team.
Teachers & Staff
Staff Notebook — create passes, see who is out, receive inbound students
Student Services
Shared visibility into movement and consistent pass workflows
District / LEA Leadership
Consistency, governance, and evidence-based expansion
Pilot Program
Scope, timeline, and onboarding for a focused school evaluation
Still have a question?
Every school has unique routines and priorities.
Schedule a Pilot Pre-Flight to ask questions, discuss your current workflow, and decide together whether Ona Pass is the right fit.