LockedIn vs LanSchool: Classroom Management vs Phone-Free Campus (2026)

LanSchool (now owned by Lenovo) is one of the longest-running classroom management tools in K-12 education. It lets teachers monitor student screens, limit websites, control apps, and manage school-owned devices during class sessions. But LanSchool was built for laptops and Chromebooks — not personal phones. Here's how LockedIn fills the gap.

This comparison is especially relevant as 43 states and D.C. have statewide school phone rules. Districts already running LanSchool on their Chromebooks are discovering they need a separate solution for the phones in students' pockets. See also how LockedIn compares to other classroom management tools like GoGuardian and MDM platforms like Mobile Guardian.

What LanSchool Does

LanSchool has been a staple of K-12 classroom management since the 1990s, evolving from a local-network tool into a cloud-based platform (LanSchool Air). Its core features focus on giving teachers control over school-owned devices during class:

• • Screen monitoring — Teachers view all student screens as thumbnails in real-time, catching off-task behavior on school-owned devices
• • Blank screens — Capture attention by blanking all student devices at once during instruction
• • Web and app limiting — Block distracting websites and applications during class sessions
• • Keystroke monitoring — Alerts for inappropriate content typed on managed devices
• • Multi-device support — PCs, Macs, Chromebooks, iPads, and Android tablets
• • Cloud or local hosting — LanSchool Air (cloud) or LanSchool Classic (on-premise) deployment options
• • Screen sharing — Push teacher's screen to all student devices for demonstrations

These are valuable capabilities for keeping students focused on school-owned devices during class. LanSchool is particularly popular in districts that want teacher-level control rather than IT-administered filtering. But every one of these features applies to school-owned devices in classroom sessions. A student's personal iPhone in their pocket? LanSchool can't see it, can't control it, can't lock it.

The Gap: Classroom Scope vs Campus Scope

LanSchool is excellent for managing classroom devices that the school owns and controls. But the phone-free campus challenge is fundamentally different in two key ways:

• • Doesn't lock student phones — LanSchool manages school-owned devices. A student's personal iPhone is entirely outside its scope. LanSchool has no capability to detect, monitor, or restrict personal phones.
• • Requires device enrollment — LanSchool needs its agent software installed on managed devices. Schools can't install software on student-owned phones without MDM enrollment, which creates the same privacy and legal issues described in the Mobile Guardian comparison.
• • Classroom-scoped, not campus-scoped — LanSchool works within classroom sessions. When a teacher starts a class, LanSchool monitors the devices in that class. But it doesn't manage phones in hallways, cafeterias, bathrooms, locker rooms, or during passing periods. Phone-free campus policies need enforcement everywhere, not just in classrooms.
• • Teacher-initiated, not automatic — LanSchool requires teachers to start and manage classroom sessions. If a teacher forgets to activate LanSchool, or if a substitute teacher doesn't know how to use it, there's no monitoring that period. Enforcement depends on consistent teacher action.
• • No phone bypass detection — No view of a second phone or a deleted app on a student's personal device.

An Illustrative Scenario: The Classroom vs Campus Problem

Consider a high school with 1,000 students and a 1:1 Chromebook program managed by LanSchool Air:

• • Period 1 — 8:00 AM — Ms. Rodriguez starts her LanSchool session. She can see 30 Chromebook screens. Her students' 30 personal phones are invisible — three students are texting under their desks right now.
• • Passing period — 8:50 AM — LanSchool session ends. Students flood the hallways scrolling social media on their phones. No monitoring, no enforcement. LanSchool doesn't operate outside of classroom sessions.
• • Period 2 — 9:00 AM — A substitute teacher covers Mr. Chen's class. The sub doesn't know how to use LanSchool. No classroom monitoring at all this period — and phones are completely unmanaged as usual.
• • Lunch — 12:00 PM — 1,000 phones are active in the cafeteria. No LanSchool session running. Students are filming TikToks, cyberbullying over group texts, and sharing inappropriate content via AirDrop.
• • End of day — The principal needs to show the district that the school's phone-free policy is working. LanSchool can report on Chromebook usage during class sessions. It has zero data on phone usage anywhere on campus.

With LockedIn at this same school: every student's personal phone locks on campus during school hours. Enforcement is campus-wide — classrooms, hallways, cafeteria, and everywhere in between. No teacher action required. No gap during passing periods. The substitute teacher's class is just as phone-free as every other class. The principal has per-student compliance records to share.

LockedIn: Campus-Wide Phone Enforcement

LockedIn is purpose-built for the problem LanSchool doesn't address — locking student-owned personal phones campus-wide:

• • OS-level phone locking — At Screen Time schools, the apps the school blocks lock automatically on campus and stay locked until the last bell; at Guided Access schools, students lock in with a triple-click (a tap on Android) and the phone stays on the LockedIn screen, and a student who doesn’t lock in is flagged. Students can always call home or 911.
• • Campus-wide, not classroom-scoped — Works in hallways, cafeterias, bathrooms, and everywhere on campus — not just during class sessions.
• • No teacher action needed — Phones lock on campus via geofencing (automatically at Screen Time schools; a triple-click at Guided Access schools). Teachers don't need to start sessions, remember to activate anything, or manage phone policies.
• • No device enrollment — Students download an app. No IT infrastructure, no agent software, no device provisioning.
• • Workaround flags — Flags a second “decoy” device until an administrator approves it, plus deleted apps, faked or switched-off locations, and use of blocked apps, by student name.
• • Compliance reports — Per-student lock status and flagged workarounds, on record for your board or a state agency (see state phone-free school laws).
• • Emergency campus-wide unlock — One tap turns on Emergency Mode, which unlocks every phone on campus and runs an I’m safe / I need help roll call. Students can always call home or 911.

LanSchool vs LockedIn: Feature Comparison

Can You Use LanSchool and LockedIn Together?

Yes — and the combination covers both device types comprehensively. Like GoGuardian and Mobile Guardian, LanSchool and LockedIn solve different problems:

• • LanSchool for classroom management on school-owned Chromebooks and laptops — screen monitoring, web filtering, app control during lessons
• • LockedIn for locking the personal phones in students' pockets — campus-wide (at most schools on its own; at Guided Access schools students lock in on arrival), with workarounds flagged

Together, they cover every device in the building — school-owned and student-owned. LanSchool keeps students focused on their Chromebooks during class. LockedIn ensures their phones are locked everywhere on campus. There are no conflicts between them — they operate on completely different device types and at different scopes.

State Phone Ban Compliance

As of October 12, 2026, 43 states and D.C. have a statewide law, executive order or board policy requiring public schools to restrict student phones or adopt a phone policy. These laws focus specifically on personal phones, not school-owned laptops. These laws require schools to adopt a policy that restricts student phones; a few (such as North Carolina, New York and Maryland) also require the policy to be filed or enforcement data to be reported. None requires a particular enforcement tool.

LanSchool can demonstrate that school-owned Chromebooks are managed during class — but it has zero data on student phone usage. A LanSchool report showing Chromebook monitoring says nothing about whether the phone policy is enforced. LockedIn keeps per-student records of phone lock status across the campus, all day.

Setup and Deployment Comparison

The deployment experience reflects the different scope and approach of each tool:

• • LanSchool setup — Requires agent installation on every school-owned device (via group policy, Google Admin Console, or manual installation), teacher account creation, class roster configuration, and training for each teacher on how to use the platform. Ongoing management requires teachers to actively start and manage sessions each period. Substitute teachers need access and training.
• • LockedIn setup — Students download the app. The school configures campus geofences and scheduling through the admin dashboard. No agent installation, no teacher training, no session management. No teacher action is required. Setup takes about a day.

The operational difference is critical: LanSchool requires consistent teacher engagement every class period. LockedIn needs no daily reminders: the dashboard is for following up on flags. Phone enforcement doesn't depend on whether a teacher remembers to start a session.

Frequently Asked Questions

Does LanSchool work on student-owned phones?

No. LanSchool requires its agent software to be installed on managed devices, which is only possible on school-owned hardware. It cannot lock, monitor, or manage student-owned personal phones. LockedIn is specifically built to lock personal student phones at the OS level without requiring device enrollment or agent installation.

Can LanSchool block phones during class?

LanSchool can blank screens and restrict apps on school-owned Chromebooks and laptops during a class session. But it has no capability to interact with student-owned phones. A student's personal phone is completely invisible to LanSchool. Campus-wide phone enforcement requires a dedicated phone management tool like LockedIn.

Is LanSchool enough for state phone ban compliance?

No. State phone ban laws target student-owned personal phones, not school-owned laptops. LanSchool can report on Chromebook usage during class sessions, but it provides no data on phone usage. Schools subject to phone ban mandates need a dedicated phone management solution like LockedIn to generate the enforcement documentation these laws require.

What happens if a teacher forgets to start a LanSchool session?

If a teacher doesn't start a LanSchool session, there's no classroom monitoring that period — on any device type. LockedIn's phone enforcement is automatic and doesn't depend on teacher action. Phones are locked campus-wide via geofencing regardless of whether any teacher has started any session.

Does LockedIn replace LanSchool?

No — they serve different purposes. LanSchool manages school-owned Chromebooks and laptops during classroom sessions (screen monitoring, web filtering, app control). LockedIn locks student-owned phones campus-wide. Most schools benefit from running both to cover all device types.

Administrator summary: LanSchool vs LockedIn (classroom screens vs campus phones)

LanSchool gives teachers superpowers on lab and 1:1 images they manage. It does not travel home in a pocket on a data plan the district does not pay for. That is why “LanSchool phone management” is a category error — and why districts still need a phone answer after LanSchool is perfectly deployed.

LockedIn complements classroom management products instead of fighting them: different agent, different consent story, different compliance artifact — phone lock logs instead of screen thumbnails.

LanSchool vs LockedIn: classroom screens vs student pockets

LanSchool’s historical strength is right there in the name: the classroom as a managed space where teachers can guide attention on devices the school can see. That is valuable for labs, 1:1 programs, and testing windows. It is not a replacement for the phone in the hoodie pocket that never joins the LanSchool session. When districts search “LanSchool phone management,” they are usually expressing a hope that classroom software can stretch to BYOD enforcement. Hope is not a plan.

Phones distort instruction even when laptops behave. A student can appear “on task” on a Chromebook while coordinating a side conversation on a phone that never touches the school’s management plane. Teachers sense the mismatch as uncanny: the room looks compliant yet feels online. LockedIn removes that uncanny valley by addressing the pocket device directly, with the same campus-wide seriousness districts apply to attendance and tardy bells.

Procurement teams should avoid forcing a single vendor to pretend to be two vendors. Let LanSchool (or any classroom tool) win on teacher workflows for school-owned screens. Let LockedIn handle OS-level phone restriction for personal phones. The district wins when each category is funded for what it can truthfully do.

Athletics and activities illustrate the pocket problem bluntly. A student can leave a “locked” Chromebook in a locker while living the school day entirely on a phone for scheduling, maps, group coordination, and social identity. Coaches and club sponsors feel this constantly: the policy says phones away, but reality says phones run the logistics layer. LockedIn aligns logistics with policy by locking the phone’s distracting apps during the school day—without removing the physical phone families still want for pickup coordination after dismissal.

Instructional coaches sometimes ask whether phone bans harm “digital learning.” The answer is discipline-specific: schools still use laptops, CAD tools, science probes, and creative software where appropriate. The ban targets the pocket supercomputer whose primary design goal is engagement, not education. LanSchool can remain part of the educational device story; LockedIn becomes part of the boundary story that protects that educational work from being undercut six inches below the desk.

When you train principals, give them a single dashboard habit: start the day by scanning phone compliance the same way they scan attendance. That ritual makes phone bans real in the building culture—because adults are paying attention to the same object students know matters. LanSchool dashboards cannot complete that ritual for BYOD phones; LockedIn can.

Graduation and awards season is a useful stress test for any phone strategy: emotionally charged days, lots of photo desire, and packed schedules. Partial phone policies explode then, because everyone has a “special reason” and adults do not want to be villains on camera day. A campus lock with a documented unlock drill is calmer: the default is consistent, and exceptions are rare, explicit, and fair—rather than a patchwork of favors that students remember as injustice.

Deans of students often describe “phone drama” as a top-three time sink. If your goal is to return adult attention to coaching, counseling, and teaching, remove the device layer that manufactures hourly drama. LanSchool cannot do that for BYOD phones; it was not built to. LockedIn can—without asking deans to become phone technicians.

School resource officers and safety teams also benefit when fewer students are walking hallways with live cameras and live feeds; it reduces the “broadcasting” instinct during tense moments. That is not the only reason to lock phones, but it is a real operational benefit leaders notice quickly.

• •Teacher training: keep classroom tool training separate from phone-ban training to reduce cognitive overload.
• •Evidence: pair LanSchool session logs (where applicable) with LockedIn lock timelines for a complete day-in-the-life picture.
• •Equity: ensure phone enforcement does not depend on which teacher is technically strongest.

If you write a pilot, include a middle school and a high school. Phone dynamics differ by age band, and your enforcement stack should feel fair in both.

The public story remains simple: we support teaching on district devices, and we remove personal phone distraction during instructional hours. That is coherent enough for a press release and true enough for an audit.

Learn more about LockedIn and read LockedIn vs GoGuardian for another “classroom tool vs phone” framing.

More LockedIn vs competitor comparisons

Searching for a phone-free school, school phone management, or K-12 phone ban alternative? Each guide below targets the competitor by name so you can compare LockedIn to the product families administrators evaluate alongside district policy.

• → LockedIn vs Bark for Schools — content monitoring vs OS phone lock
• → LockedIn vs Brick — Brick phone / Brick Mode vs district enforcement
• → LockedIn vs CLocked — classroom launcher vs OS phone lock
• → LockedIn vs GoGuardian — Chromebook filters vs student phone lock
• → LockedIn vs Mobile Guardian — MDM vs BYOD student phones
• → LockedIn vs NutKase Phone Pouches — Velcro pouch vs OS lock
• → LockedIn vs Off The Device — airplane mode nudges vs OS lock
• → LockedIn vs Phone-Free School App — manual School Mode vs geofenced lock
• → LockedIn vs Pinwheel — kid-safe phones vs lock any student phone
• → LockedIn vs Pocket Points — rewards app vs mandatory enforcement
• → LockedIn vs Securly — web filter vs OS-level student phone lock
• → LockedIn vs Taplock — geofenced app limits vs OS phone lock
• → LockedIn vs The Commons App — distraction-free app vs OS phone lock
• → LockedIn vs TRUCE Family — MDM app block vs OS lock (no MDM)