Industry guide

Managed IT diligence for private schools.

Schools hold student records, family financial information, and, for younger students, data with its own federal protections. Schools hold years of records on minors, parents expect discretion as a matter of trust, and online services used by children carry federal privacy obligations that flow through the school's technology choices.

What binds you

The frameworks

FERPAThe frameworkStudent-record privacy duties where federal funding applies.
COPPAThe frameworkFederal limits on collecting data from children under 13 through online services.

The industry question

How are student records access-controlled, and how are the online services children use vetted?

It belongs on the checklist, in writing, next to the other 18.

The method

The bench, applied

Observe

The tactics

Lock-in contracts, stripped quotes, and exit traps, documented in the industry's own words with checkable sources.

See the tacticsAdapt

The standard

Fourteen marks of a fair managed IT agreement, stated plainly and provider-neutral.

See the standardProtect

The benchmark

The four-step method and the 18 questions to ask in writing, with a printable checklist.

Use the benchmark

Your state

Private Schools, state by state

The same diligence with your state's verification layer: the breach statute, the entity search, the regulator.

Choose your state

Educational reference, not legal advice. Frameworks are summarized at the framework level; confirm specifics for your situation with counsel or the primary source.