Draft resolutions, ordinances, and model bills at every level of government — offered as starting points for public conversation about how School Contact becomes the law of the land.
The fragmented state of school communication is not merely an administrative inconvenience — it is a public safety vulnerability. These four scenarios illustrate the concrete, life-or-death cases that make School Contact legislation a matter of urgency, not preference.
A man arrives at Lincoln Elementary claiming to be a child's uncle. The office has no way to verify he is an authorized contact. There is no verified parent communication channel. The child is released. Hours later, an Amber Alert is issued.
With School Contact, every authorized guardian has a verified @parents.email identity linked to the child's record. An unverified contact cannot claim authorization — the registry confirms or denies it instantly. Any pickup attempt from an unverified identity triggers an automatic alert to the verified parent.
A shooting begins at 9:14 AM at a high school. By 9:17, parents are calling the main office line — which is now unreachable. District social media posts conflicting information. Parents drive to the school. Roads become gridlocked. First responders are slowed.
With School Contact, a single authenticated district-level message from 333·[email protected] reaches every verified parent of every enrolled student simultaneously — with a timestamp, a verified sender identity, and a read receipt. No phone tree. No social media chaos. No impersonation possible during the crisis.
A Category 4 hurricane makes landfall in South Florida. Forty thousand students are displaced overnight. Families relocate to Georgia, Tennessee, and Texas. In the weeks that follow, receiving schools have no way to verify who these children are, what grade they are in, or who their authorized guardians are. Enrollment processing takes weeks. Some children fall through the cracks entirely.
With School Contact, every displaced student arrives at the receiving school with an active, nationally verified identifier. The new school queries the registry and retrieves the full verified record — enrollment history, grade level, authorized contacts — in seconds. No paperwork. No delay. No lost children.
A registered sex offender creates a fake teacher email address — indistinguishable from a real district address — and sends messages to students. Current law has no mechanism to distinguish a verified teacher address from a fraudulent one. By the time the fraud is detected, dozens of students have received and responded to messages.
With School Contact, no message claiming to come from a teacher address (111) can be delivered to a student domain unless it is verified against the national registry. A fraudulent address is rejected at the infrastructure level — before it ever reaches a student's inbox. The attempted contact is logged, timestamped, and reported automatically.
School boards are the front line. A board resolution cannot compel state or federal action, but it does three powerful things: it signals community readiness to legislators, it creates a formal record of local support, and it begins the policy conversation at the place where children, parents, and educators actually meet.
This resolution formally expresses a school board's support for the principles of the School Contact Initiative and directs district leadership to evaluate readiness for participation in a Phase 2 pilot program.
This resolution is intentionally non-binding on state or federal actors and requires no budget appropriation. It is a statement of intent and a formal directive to begin the internal evaluation process.
This board policy establishes the local framework for the @parents.email domain — requiring every enrolling family to provide a verifiable mobile phone number that becomes their School Contact guardian identity. It directly addresses the abduction and unauthorized pickup vulnerability.
This policy connects to existing school safety protocols and can be implemented independently of state or federal legislation — it is within the Board's existing authority to govern enrollment procedures.
This protocol amendment requires the district to replace or supplement its current emergency notification system with one that uses verified School Contact identifiers — ensuring that emergency messages during lockdowns, active threats, or natural disasters go only to verified parents, from verified district senders, with tamper-proof timestamps.
County governments and county offices of education (COEs) occupy a critical middle layer — they coordinate between individual districts and the state, they often manage special education, alternative programs, and court-ordered schools, and they are the first level at which cross-district coordination becomes possible.
A county-level committee brings multiple school districts to the same table — enabling shared infrastructure costs, coordinated pilot programs, and a unified voice when advocating to the state legislature. This is often how technology standards propagate in public education: one county proves it works, then the state adopts it.
This ordinance creates a county-level civil penalty — distinct from criminal law, which requires state or federal action — for anyone who knowingly uses a spoofed or impersonated school communication address to contact a minor. It provides a local enforcement mechanism while broader state and federal legislation is developed.
State legislatures set the framework within which every school district in the state operates. A state law mandating participation in a verified educational communication system — or even mandating a readiness study — transforms the School Contact Initiative from a voluntary pilot into a durable piece of public infrastructure. States also have the authority to create criminal penalties, allocate funding, and negotiate interstate compacts.
This is the core state-level bill. It establishes the legal requirement for verified identity in K–12 communication, creates the state's participation in the national registry, funds the rollout through a combination of state appropriations and federal e-Rate matching, and establishes criminal penalties that complement the federal framework.
Note: The specific felony classification, sentencing ranges, and cross-references to existing statutes must be tailored by each state's legislative counsel to conform to that state's criminal code structure.
This bill directly addresses the natural disaster and mass displacement scenario. It authorizes the Governor to enter into an interstate compact — a formal agreement between states — requiring mutual recognition of School Contact student identifiers, so that a child displaced from one state is immediately enrolled and recognized in another without administrative delay.
This bill creates a statutory right — not just a policy option — for parents to hold a verified @parents.email identity. It also creates a corresponding duty for schools to recognize and respond to verified parent communications, and prohibits any district from treating a verified parent identity as grounds for restricted access to their child's school records.
Federal legislation provides the national standard, the funding mechanism, and the teeth. The FCC controls numbering plan administration. The Department of Education controls Title I, IDEA, and e-Rate funding. Congress controls the criminal law that applies across all 50 states. Federal action transforms a patchwork of state pilots into a unified national infrastructure.
This is the foundational federal bill. Without FCC action to reserve the area codes, any state or local implementation lacks the national interoperability that makes the system's benefits possible. Without a national registry, transfers across state lines remain manual. Without e-Rate funding eligibility, the cost falls entirely on districts.
This bill provides the federal criminal law framework — establishing that misuse of student domain identifiers is a federal offense, not merely a state civil matter — and formally integrates the School Contact alias system into the existing COPPA compliance framework so that educational technology vendors have a clear, legally recognized path to compliant implementation.
Infrastructure at national scale requires national funding. This bill provides the appropriations mechanism — ensuring that participation in School Contact is not a financial barrier for under-resourced districts, which are often the communities most vulnerable to the safety failures the system addresses.
Effective deterrence requires clear, graduated penalties that increase with the severity of the violation and the vulnerability of the victim. The following framework is proposed for adoption across local, state, and federal levels — with each tier enforcing the provisions within its jurisdiction.
| Violation | Tier | Proposed Penalty | Severity |
|---|---|---|---|
| Contacting a student domain (444/555/777) without verified school affiliation | Federal / State | Up to 5 years imprisonment + $10,000 fine per violation | Felony |
| Contacting a student domain with sexual, grooming, or predatory content | Federal | Up to 10 years imprisonment; aggravating factor under existing child exploitation statutes | Federal Felony |
| Impersonating a verified teacher (111) or staff member (222) in contact with a minor | State / Federal | Up to 5 years imprisonment + $10,000 fine; permanent loss of any educator credential | Felony |
| Impersonating an authorized guardian (@parents.email) for unauthorized student pickup | State | Up to 3 years imprisonment + $5,000 fine; mandatory registry flagging | Felony |
| Unauthorized access or false signal to the National School Contact Registry | Federal | Up to 10 years under Computer Fraud and Abuse Act; $50,000 fine | Federal Felony |
| Using a spoofed domain designed to mimic a School Contact address | County / State | $500–$5,000 civil fine per transmission; criminal referral if pattern of conduct | Civil / Criminal |
| School district failure to use verified infrastructure for declared emergency notifications | State | Loss of state emergency preparedness certification; withholding of state safety funds | Administrative |
| EdTech vendor sharing student alias token data in violation of COPPA amendment | Federal | FTC civil penalties up to $50,120 per violation per day under existing COPPA enforcement | Civil |
| School employee sharing a student's full administrative address with unauthorized third party | Local / State | Termination of employment; $1,000–$10,000 civil fine; criminal referral if intentional | Administrative / Civil |
| First-time technical non-compliance by participating district (missed deadline, incomplete registry) | State | Written notice + 90-day cure period; no penalty if cured within 90 days | Administrative |
Note on proportionality: This framework is designed to concentrate the most severe penalties on adult actors who exploit the system to target children — not on schools, districts, or families navigating a new compliance requirement in good faith. Administrative and civil penalties for institutional actors are calibrated to be corrective, not punitive. Criminal penalties for predatory contact are calibrated to be severe enough to constitute a genuine deterrent.
The School Contact Initiative cannot reach its full potential without the cooperation of the telecommunications industry. Area codes are administered through the North American Numbering Plan — and carriers are the infrastructure through which every call, text, and data connection flows. We are asking the nation's telecommunications companies to become active partners in protecting children.
Once the FCC formally reserves area codes 111, 222, 333, 444, 555, 777, and 999 for educational use, we ask every carrier — wireline, wireless, and VoIP — to treat communications originating from or directed to these codes with the same care they currently apply to emergency service numbers. Calls and messages claiming to originate from a reserved educational area code but not verifiable against the National School Contact Registry should be flagged, blocked, or routed to a carrier-level review process — just as fraudulent calls on other reserved codes are today.
Area codes 444, 555, and 777 identify K–12 students. When a device registered to one of these student identifiers attempts to access a service that requires age verification — creating a social media account, purchasing a game with mature content, or visiting an adult platform — the carrier's infrastructure knows, before any data is exchanged, that the requesting identifier belongs to a minor. We propose that carriers surface this information to platforms through a standardized API, enabling age verification that is both accurate and privacy-protective: the platform receives only a binary confirmed-minor signal, not the student's identity.
The School Contact Initiative is not asking carriers to build new infrastructure from scratch — we are asking them to apply existing numbering plan enforcement mechanisms to a new category of protected users. We invite the major carriers — AT&T, Verizon, T-Mobile, and the CTIA — to participate in the technical standards development process alongside the FCC and the Department of Education. Early participation means early influence over how the standards are written. We want the industry to be a co-author of these protections, not a late-stage compliance obligation.
A note on voluntary cooperation: While the legislative proposals in this page contemplate eventual FCC rulemaking that would make carrier cooperation mandatory for reserved educational area codes, the School Contact Initiative is actively seeking voluntary cooperation commitments from carriers in advance of any rulemaking. Early carrier partners who adopt these standards voluntarily will be publicly recognized as leaders in child digital safety — and will have shaped the standards rather than been subject to them.
The School Contact Initiative does not tell parents whether or when to give their child a smartphone. That is entirely your decision as a family. What the system does is ensure that when your child uses any connected device for school — or anywhere else — they carry a verified identity that protects them in ways no existing system currently can.
Whether you buy your child a phone at age eight or age sixteen is a parenting decision, and School Contact does not change that. What School Contact does is separate the question of device ownership from the question of identity. Your child's area code and numeric identifier are assigned at enrollment — not at purchase. The moment they enroll in kindergarten, they have a student ID. Whether that ID is accessed from a smartphone, a school tablet, a smartwatch, or a library computer is entirely up to your family.
Think of it the same way you think about a Social Security number or a library card. Your child has one whether or not they carry a device. The device is just one of many ways to use it.
The numeric identifier assigned to your child at kindergarten enrollment stays with them through high school graduation. It is permanently linked to your verified @parents.email guardian identity — which means you are always connected to your child's school record, their communications with teachers and staff, and any alerts the system generates.
You do not need a new account for each school year, a new app for each district, or a new login for each platform the school uses. Your verified phone number is your access point — and it is connected to your child's record for as long as they are enrolled.
COPPA requires parental consent for data collection from children under 13. KOSA and similar state laws impose duties of care on platforms with minor users. But every one of these laws relies on platforms knowing who is a minor — and today, they don't. A student identifier in the School Contact registry gives platforms the verified signal they need to enforce the age requirements they already claim to follow. Parents who have watched their 10-year-old navigate around an age gate will understand exactly why this matters.
The Entertainment Software Rating Board rates games for audience appropriateness — but the ratings are only as effective as the age verification behind them. An M-rated game requires the buyer to confirm they are 17 or older. Online, that confirmation is a checkbox. With a verified student identifier, a platform distributing mature-rated content can receive a confirmed-minor signal before account creation — giving parents and developers a meaningful enforcement mechanism for ratings that today are largely advisory.
Several states have passed laws requiring adult content platforms to verify user ages. Those laws have faced legal challenges and enforcement gaps — in part because the verification mechanisms available are either privacy-invasive (requiring ID uploads) or easily defeated (requiring self-attestation). A School Contact confirmed-minor signal is neither: it is privacy-protective, it is accurate, and it is impossible to override by simply typing a different birthdate. It does not prove an adult is an adult — but it does prove a student is a minor, which is the protection that has been missing.
School Contact is not a parental control app. It does not monitor your child's messages, restrict their browsing, or report their activity to you. What it does is make the platforms your child encounters online responsible for using accurate age information when they already claim to — closing a loophole that has existed since the first age gate appeared on the internet. Your conversations with your child about responsible use of technology remain exactly as important as they have always been. The system just stops the platforms from pretending they have no way to know.
These proposals are starting points — not finished law. If you are a school board member, a state legislator, a parent advocate, or a policy researcher, we want to hear your reactions, your amendments, and your concerns.