LockedIn vs CLocked: School Phone Management Comparison (2026)

CLocked is a classroom launcher that originated in LAUSD with the goal of "teaching students purposeful phone use" by controlling which apps they can access during class. It's an interesting educational concept — but it's not phone-free enforcement. Here's how LockedIn compares.

With 43 states and D.C. with statewide school phone rules, schools need to understand the difference between guided phone use and actual enforcement. See also how LockedIn compares to other partial-restriction approaches like The Commons and Taplock.

What CLocked Actually Does

CLocked is a classroom launcher app that replaces the student's phone home screen with a curated set of teacher-approved apps:

• • App access control — Educators choose which apps students can use during class (calculator, Google Classroom, etc.)
• • "Learning tool" philosophy — Positions phones as tools to be managed, not banned. The idea is that students learn "purposeful phone use"
• • Emergency access — Phones remain available during emergencies since the device is never truly locked
• • LAUSD origin — Started in Los Angeles Unified, the nation's second-largest district, as a pilot program
• • Teacher-controlled — Individual teachers manage what's available during their class period

The philosophy is appealing: instead of banning phones, teach students how to use them responsibly. The problem? It doesn't work for enforcement. And the gap between "guided use" and "phone-free" is precisely what state legislatures are now targeting.

Why "Purposeful Use" Is Not Enforcement

CLocked's fundamental design treats the phone as a classroom tool that should remain accessible. That philosophy creates several critical enforcement gaps:

• • Students choose whether to comply — A launcher can present a curated home screen, but students can still exit the launcher, switch to other apps, or find workarounds. It's guidance, not enforcement. On Android, exiting a launcher requires minimal technical knowledge. On iOS, launchers have even less control over the system.
• • No OS-level locking — Phones remain fully functional underneath the launcher. The operating system is not restricted. Students can access notifications, texts, the camera, and any installed app by navigating around the launcher interface.
• • Per-classroom, not campus-wide — CLocked operates at the classroom level with individual teacher control. During passing periods, lunch, and before/after school, there is no enforcement. A truly phone-free campus needs all-day coverage triggered by campus boundaries, not individual class sessions.
• • No published bypass detection — If a student uses a decoy phone and keeps their real phone in their pocket, nothing in CLocked's published materials would catch it.
• • No published compliance reporting — CLocked does not publish a campus-wide enforcement dashboard or reports a school could show its board or state.
• • Teacher burden — Each teacher must configure and manage which apps are available for their class. This adds administrative overhead to every teacher's workflow rather than centralizing enforcement at the school level.

An Illustrative Scenario: The Launcher Problem

Consider a middle school that has deployed CLocked as its phone management strategy:

• • 8:00 AM — Students arrive. CLocked is not active yet because no teacher has started a session. Students scroll social media freely in the hallways and cafeteria.
• • 8:30 AM — First period starts. The math teacher activates CLocked, showing only the calculator and Google Classroom on students' launcher screens. But two students have already exited the launcher via notification shortcuts and are texting under their desks.
• • 9:25 AM — Passing period. CLocked session ends. All phones are fully unrestricted for 5 minutes. Students check social media, respond to texts, and share content.
• • 9:30 AM — Second period. The English teacher forgot to start a CLocked session. Phones are unrestricted the entire period.
• • 12:00 PM — Lunch. No CLocked sessions active. A student records a fight and uploads it to Snapchat before the administration even knows it happened.
• • 2:30 PM — The district asks for documentation of phone-free policy compliance. The school has no centralized data to provide.

With LockedIn at the same school: phones lock on campus during school hours — before first period, during passing periods, at lunch. No teacher setup required. The admin dashboard shows who is locked in, and the school has per-student records to share with the district.

LockedIn: Enforcement That Actually Works

LockedIn takes a different approach — lock the phone at the OS level, campus-wide, with no teacher involvement:

• • OS-level device 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.
• • Automatic geofencing — Phones lock on campus during school hours and unlock after school: automatically at Screen Time schools, or with a triple-click (a tap on Android) at Guided Access schools, where a student who doesn’t lock in is flagged. No daily distribution or collection.
• • 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.
• • Live admin dashboard — See every student's compliance status from one screen. Centralized at the school level, not fragmented across individual teachers.
• • 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.

CLocked vs LockedIn: Feature Comparison

Deployment and Implementation

The deployment models reflect the fundamental philosophy difference between the two tools:

• • CLocked setup — Students install the app. Each teacher configures which apps are available for their class. Teachers must remember to start and stop sessions. Ongoing management happens at the classroom level, creating inconsistent enforcement across different teachers and periods.
• • LockedIn setup — Students download the app. The school configures campus geofences and scheduling once through the admin dashboard. Enforcement is automatic and campus-wide. No per-teacher configuration. Setup takes about a day, and schools are live within a week.

The difference in ongoing staff burden is significant. CLocked adds work to every teacher's daily routine. LockedIn removes phone enforcement from teachers entirely, letting them focus on teaching.

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 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.

CLocked doesn't prevent phone use (students can exit the launcher), generates no enforcement records, and only operates during individual teacher-initiated sessions. LockedIn enforces the policy on campus for the whole school day and keeps per-student records of lock status and flagged workarounds.

The "Purposeful Use" Philosophy vs Policy Reality

CLocked's "purposeful phone use" philosophy represents a genuine pedagogical perspective: phones are powerful tools, and students should learn to use them intentionally. This is a reasonable educational goal.

But there's a growing body of evidence — and a wave of state legislation — arguing that the school day is not the right time for this experiment. Research consistently shows that even the presence of a phone reduces cognitive performance, and that teenagers lack the prefrontal cortex development needed for reliable self-regulation around highly addictive devices.

The legislative trend is clear: states are requiring enforcement, not education-first approaches. Schools that deploy CLocked's "purposeful use" model may find themselves non-compliant with their state's mandate within a year. LockedIn is designed from the ground up for the enforcement-first reality that these laws demand.

Frequently Asked Questions

Can students exit the CLocked launcher?

Yes. CLocked operates as a launcher overlay on the phone, not an OS-level restriction. Students with basic technical knowledge can navigate around the launcher to access other apps, notifications, and system functions. LockedIn locks the phone at the operating-system level, so there is no launcher to exit: the apps the school blocks stay locked, and deleting the app is flagged.

Does CLocked work during lunch and passing periods?

No. CLocked is teacher-initiated and operates during individual class sessions. Between classes, during lunch, and before/after school, phones are fully unrestricted. LockedIn uses campus geofencing to enforce phone-free policy from the moment a student enters campus until they leave — covering every period, passing period, and lunch automatically.

Is CLocked enough for state phone ban compliance?

No state law requires a particular tool, but CLocked is a guidance tool without OS-level enforcement, campus-wide coverage, or records of who complied, so it leaves a school policy largely unenforced. LockedIn enforces the school's policy on campus and keeps per-student records your board can review.

Does CLocked put more work on teachers?

Yes. Each teacher must configure which apps are available for their class and remember to activate and deactivate CLocked sessions. This adds daily administrative overhead. LockedIn operates at the school level with automatic geofencing — teachers have zero phone-management responsibilities.

Can CLocked and LockedIn be used together?

There's no practical reason to run both. LockedIn locks the phone during school hours, which makes a classroom launcher largely redundant. Schools considering CLocked for its educational philosophy can achieve phone-free enforcement with LockedIn and pair it with any standalone digital citizenship curriculum.

Administrator summary: CLocked vs LockedIn (launcher experience vs OS lock)

Launcher and “school mode” experiences improve what students see first when they open a phone. They do not remove the underlying OS affordances that drive misuse: quick settings, alternate browsers, screenshots, and messaging paths that never touch the launcher surface.

LockedIn is not a different skin on the same problem — it is an OS-level lock tied to the school day: at Screen Time schools the apps the school blocks lock automatically on campus, and at Guided Access schools the phone stays on the LockedIn screen. The dashboard flags common workarounds by student name, such as a second "decoy" phone or a deleted app. If your policy language requires phones to be off or stored away, no app meets that on its own, and a launcher is the furthest from it.

CLocked vs LockedIn: launchers change the home screen, not the phone

Launcher products answer a real classroom annoyance: students disappear into icons the moment the bell rings. A school-branded first screen can steer attention toward LMS tiles and approved resources. What launchers cannot do is erase the underlying operating system affordances that determined students in minutes: control center toggles, alternate browsers, screenshots, split-screen tricks, and quick routes back to messaging that never “opened the banned app” in a way a launcher can see.

That matters because your policy language is usually blunt—“phones away” or “no personal device use”—while launcher enforcement is inherently partial. Partial enforcement creates unequal classrooms: strict teachers win skirmishes, lenient teachers become accidental safe harbors, and students learn which hallways and which periods are “free.” Districts trying to build culture need consistency more than they need another colorful icon grid. Consistency is what OS-level locking buys: the same factual device state for every student, with exceptions handled as documented accommodations rather than hallway negotiation.

Another practical issue is measurement. Launchers can show engagement with the launcher. They do not automatically produce the compliance evidence phone-ban statutes increasingly expect: time ranges where personal smartphones were restricted, with student-level granularity and exportable summaries. LockedIn is designed for that measurement layer because it treats compliance as infrastructure, not as a UI nudge.

• •Teacher workload: prefer systems that remove debate rather than systems that add “please open the school screen” reminders.
• •Cheating: treat camera + browser + messaging as one risk surface, not three separate policy clauses.
• •Secondary devices: ask how the vendor helps you catch the old phone in the backpack trick.

None of this says launchers are useless. Many districts keep an LMS-first experience on school-owned iPads while still needing a BYOD answer for phones. The mistake is believing a launcher is a phone-ban platform. If your board believes that, you will underfund the real fix and overburden teachers when reality returns two weeks into the semester.

STEM classrooms illustrate launcher limits quickly: students use calculators, reference PDFs, and collaboration tools while still needing a genuinely distraction-free environment during checks for understanding. A launcher can organize tiles; it cannot remove the parallel social channel that competes for working memory. That parallel channel is why “phones away” policies failed for a decade: the phone was still a socially hot object even when the home screen looked school-themed.

Discipline data often hides the launcher problem because incidents get coded as “defiance” rather than “tool category mismatch.” When districts re-code incidents after OS-level locking, they sometimes discover a large fraction of phone conflict was not moral defiance but predictable friction from partial tools. Better tools change the story teachers tell about students.

From a parent-night perspective, launchers also sound like spyware-adjacent surveillance to some communities unless messaging is extremely careful. OS-level locking is easier to explain as a time-bound pause tied to school hours, similar to how gyms lock lockers: not because we do not trust you forever, but because this place has rules while you are here.

Pilot design matters. If you test a launcher, log how many interventions teachers still perform per class period. Then pilot OS-level locking and compare. The delta is often the story that convinces union partners because it is measured in minutes returned to instruction, not in vendor promises.

Assessment integrity is another lens. Launchers may reduce obvious tab-hopping during a quiz, but they do not remove the phone as a covert camera or as a second-screen coordination tool for answers. High-stakes testing teams already think in those threat models; daily instruction deserves the same realism. OS-level locking removes many cheating affordances because the handset is not a live general-purpose computer during the assessment window—without turning teachers into forensic investigators.

Fine arts and performance programs sometimes worry about phones as cameras for legitimate reasons. The district answer should not be “ban cameras forever”; it should be “cameras are unavailable during locked instructional time, and events have explicit adult-supervised capture rules.” LockedIn aligns with that pattern: instructional hours are protected, while after-school creativity can still exist on family terms.

If you want a district-grade pocket strategy, pair honest category choices with honest procurement: LockedIn for student-owned phones during school hours, and keep classroom tools for classroom tools. For a broader category tour, read school cell phone solutions compared.

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 GoGuardian — Chromebook filters vs student phone lock
• → LockedIn vs LanSchool — classroom management vs campus 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)