Skip to content

The phone policy runs itself. You handle the exceptions.

Phones lock when students arrive on campus and unlock after the last bell. Your dashboard names the students who need a follow-up, and keeps the records that show your board the policy is working.

Book a demoSee the launch week
The dashboard mid-morning: counts at the top, the students who need a follow-up below. Sample school and student names.

Only the students who need you.

Students who are locked in are counted, not reported. What reaches you is a short list with names on it, each flag in the dashboard’s own words, with the reason and the fix.

Alerts go to the administrators you choose, usually a dean or assistant principal. Teachers stay out of it.

  • A decoy phone

    A phone flagged as a decoy doesn’t count as the student’s until you approve it. Until you approve or reject it, the dashboard marks it.
    Dashboard alert: Fake Device

  • An app that went quiet

    A phone that hasn’t checked in for about two school days is flagged as a possible uninstall. The flag clears itself if the app checks in, and becomes App Uninstalled once the removal is confirmed.
    Dashboard alert: Possible Uninstall

  • A faked or switched-off location

    A phone that turns off the app’s location access is flagged as Location Issues, and so is an iPhone with Location Services off. On Android, a faked GPS position is flagged as Mock Location.
    Dashboard alert: Location Issues

  • Blocked apps in use

    If a locked phone shows steady use of apps your school blocks, a violation is filed after the school day ends. A single reading never counts against a student.
    Dashboard alert: Using Blocked Apps

  • An app never installed

    The student gets a reminder email every school day. From your launch date, each school day without the app is a violation, filed to your inbox automatically.
    Dashboard alert: Never Installed

Exceptions you decide. Opt a student without a phone out from their row on the dashboard, with a note on why, or leave them off the roster, and nothing changes for them. At most schools a student with a medical need goes on a 504 plan from their row: LockedIn then blocks only social media, games and entertainment for them, so a glucose monitor keeps working. At schools that use Guided Access, you exempt the student from one rule instead, such as keeping Bluetooth on for a glucose monitor.

Your rules, in your words, every time.

Write your consequences once, as steps. Each violation reaches the dean with the student’s step on it, and the follow-up email is written from your words, so every student hears the same rule the same way.

Writing and enforcing a phone policyDraft your policy with the free generator

Your consequences

An example

  1. First violationThis is a warning. Fix it today.
  2. Second violationYour phone stays in the front office until 3pm.
  3. Third violation and every one afterWe call home and set up a meeting with a parent.
The last step covers every violation after it. Each violation reaches the dean with the student’s step on it, and the follow-up email is written from these words.

What you can show your board.

Most state laws require a phone policy and leave enforcement to the school. LockedIn enforces yours and keeps the records that show it’s working.

Where a law requires phones to be stored away, as Kansas’s does, LockedIn enforces and documents your policy alongside that storage rather than replacing it.

Look up your state’s lawPrepare the board presentation

On the dashboard’s Statistics tab

Compliance
For any period you pick, beside the period before it.
Hours locked in
The measured time phones were actually locked during school hours.
Violations
Totals for the period, and the hour of the day with the most.
App adoption
How much of your roster has installed the app.
Each violation
In the dean’s inbox with the student’s name, the reason, and any notes your team adds.

One tap from you unlocks every phone.

In an emergency, a phone in a pouch is out of reach when a student needs it most. With LockedIn, an administrator releases every phone on campus from the dashboard, and each one becomes a way to reach your team.

  1. 01

    Start it in one tap.

    Pick lockdown, evacuation, shelter in place or medical, add a message, and every phone on campus unlocks and shows it.

  2. 02

    Every student answers.

    Two buttons on every phone: I’m safe, or I need help. A help request reaches your admins with where the student is.

  3. 03

    Your team sees everyone.

    A live map shows who’s safe, who needs help and who hasn’t answered yet, and admins can chat with any student who asked for help.

The confirmation an administrator sees before every phone unlocks. Sample school.
  • Drills run the same way
  • Phones lock again when it ends
  • Location only while it’s on, erased when it ends
  • Every action logged, with a record you can export

LockedIn doesn’t replace 911, and students can always call it.

When parents and IT ask.

You’ll be the one answering. Each answer here comes from our privacy policy, so you can repeat it word for word.

The page to send familiesSecurity detailsPrivacy policy

  • Can my child reach me?

    Always. Students can call home or 911. At most schools the Phone app is never locked; at schools that use Guided Access or screen pinning, a student can step out of LockedIn at any time, and the dean sees that they did. Everyday messages go through the front office, and your school decides about texting.

  • What can it see?

    During school hours, whether the phone is on campus and whether it’s locked, plus a few device signals that give away a workaround. No coordinates, and no location after school unless you declare an emergency. Never texts, photos, browsing, or which apps a student opens. Activity records are deleted after 90 days.

  • Does the school control the phone?

    No. There’s no device-management profile, so the school never takes control of a family’s phone.

  • Who owns the data?

    Your school. LockedIn acts as a school official under FERPA, under your direct control, and can sign state-standard agreements such as the SDPC National Data Privacy Agreement.

  • Is it secure?

    AES-256 encryption at rest and TLS in transit, multi-factor sign-in for admins, and data hosted in the United States. SOC 2 Type II attestation is in progress; LockedIn is not yet attested.

Live within a week.

Setup takes about a day. The rest of the week goes to the launch, because a phone policy succeeds or fails on how it starts, and we’re with you for all of it.

Priced per student, per year, with a written quote for your enrollment. Start with a pilot in one grade or one campus if you like. Title I schools can apply for subsidized or fully covered access.

How pricing worksApply as a Title I school

Your launch week

An example timeline

  1. 01Kickoff call: we map your campus boundary and bell schedule with youLockedIn and your teamDay 1
  2. 02Roster sync from Clever, Veracross, Blackbaud or OneRoster, or a CSV uploadLockedInDays 1–2
  3. 03A 30-minute training for the deans and front office who will see the alertsLockedInDays 2–3
  4. 04The family letter goes home, with our parent FAQ attached Start from our letterYour teamDays 3–4
  5. 05Students install the app and sign in with their school emailStudentsDay 5
  6. 06Launch week: we watch the dashboard with you and fix what comes upLockedInWeek 1

Guides for administrators.