The mosdos policy: what schools require, and how enforcement actually works

The takanah letter is a genre by now: the school's standards stated, the parent's signature required, the consequences named. And every principal who has run one knows the genre's quiet crisis — the letter governs the compliant and is invisible to everyone else. The honor system works exactly on the families who least needed governing; the devices that mattered were configured the morning of the device check and restored by supper. A policy that cannot be verified is a policy that selects for honesty among those it least worries about, while teaching the rest that the school's standards are theater. The mosdos that solved this did not write sterner letters. They changed what a policy is.

Why the honor system fails structurally

• Inspection doesn't scale and shouldn't. The rebbi examining phones is a role nobody wants: technically outmatched by any motivated teenager, halachically and pedagogically miscast, and auditing a utility drawer where the vault app looks like a calculator. Spot checks catch the unlucky, not the noncompliant.
• Settings-level compliance is costume. Anything a parent configures, a teen can unconfigure and reconfigure — the peeling ladder applied to the school's requirements: the device checked in September and the device carried in February share only a case.
• The policy burden lands on the wrong desk. Honor-system enforcement makes every rebbi a monitor and every parent-school conflict a he-said case. The school's actual expertise — chinuch — gets spent on forensics.

“A school rule that cannot be verified does not produce compliance. It produces a curriculum in how compliance is performed — taught schoolwide, by the students, to each other.”

kolbo.life

What verified policy looks like

The working model, now running across the mosdos that adopted platform-level standards:

1. The policy is a configuration, not a description. "Devices must meet the school standard" becomes a named tier — the categories, hours, and app posture defined once — that a device either is enrolled in or is not. The standard stops being an essay and becomes a state, per the same architecture-versus-adjective test families run on products.
2. Verification is a glance, not a search. The school's dashboard shows enrollment and integrity — this device, on the standard, currently — the institutional oversight model, without any rebbi ever handling a student's phone. The check that took an inspection morning takes a screen.
3. Tamper events surface themselves. The device that leaves the standard reports it — to the parents first, the school per the agreed protocol — converting the February problem into a same-week conversation. Detection, as everywhere, is the honest form of enforcement.
4. The policy travels home. Because the standard is device-level, it holds on Sunday exactly as on Tuesday — which is what the takanah letter always claimed and could never see. The school-home seam becomes one standard with two dashboards, not two regimes with a gap between them.

The partnership clauses that keep it kosher

Verified enforcement concentrates power, so the mature mosdos pair it with explicit governance: scope discipline (the school sees policy state, never content — enrollment and integrity, not messages and photos; the privacy-by-scoping principles bind institutions harder than parents); the parents remain the device's owners — the school's tier is a floor the family may exceed, never a ceiling it may not question, with the teen's own ladder running above the school floor at the family's discretion; a graduation posture — the policy's rungs age with the grades, because a twelfth-grade policy identical to a seventh-grade one teaches that standards are about control rather than development; and a real appeals lane — the family with a documented need (the work-tier teen, the medical case) gets a scoped exception through a named process, because a scoped exception is an allowlist entry rather than a blanket waiver, and a policy without a lane breeds the workarounds it forbade.

Frequently asked questions