5 Edtech Contract Clauses to Read Before Your Board Votes

Read five clauses before you vote: renewal and escalation, student data control and deletion, per seat versus site pricing, termination rights, and indemnification. Those five decide what the district owes and what happens to children's records. Run them against every vendor in the packet, Meta Typing Club included, before the consent agenda reaches a vote.

TL;DR: A trustee has no duty to understand an entire vendor agreement and every duty to understand what the board is approving. Five clauses carry most of the risk. If the packet arrived last night, read term and renewal first, then the data section, then termination. Treat a vendor's refusal to answer plainly as its own kind of answer.

The Vote You Are Actually Taking

The agenda item says software. The document says something else: a term, a renewal mechanism, a data flow, a price that moves, and an exit that may not exist.

LearnPlatform by Instructure reported that districts accessed an average of 2,982 distinct edtech tools in 2024-25. Most never reach a board agenda. The handful that do arrive as a line item and a signature block.

A reasonable trustee can disagree with the position this piece defends: a board should decline to approve any edtech agreement whose operative terms live on a web page the vendor can rewrite without notice. You cannot approve a document that does not hold still.

Renewal and Escalation: The Clause That Votes for You Next Year

Start at the back. Renewal language runs about two sentences and does more work than the rest of the contract combined.

The pattern to find is an evergreen term: the agreement renews automatically unless one party gives written notice inside a window, often 30 to 60 days before the anniversary. That window is the whole clause, and it assumes someone at the district is tracking a date on a document signed by a colleague who may have left.

Then read what the price does on renewal. "Then-current list price" means the vendor sets it. A capped escalator, a fixed percentage or a published index, lets the board forecast it.

Do not expect a federal backstop. The Federal Trade Commission's Negative Option Rule was vacated in its entirety by the Eighth Circuit on July 8, 2025, and Cooley's summary describes it as a rule aimed at consumer subscriptions rather than institutional purchasing. On renewal terms, the contract your board approves is the protection your board gets.

Student Data: Control and Deletion

Under the FERPA school official exception, a vendor may hold education records only if it performs a service the district would otherwise staff itself and stays "under the direct control of the agency or institution with respect to the use and maintenance of education records". Redisclosure limits at 34 CFR 99.33(a) come with it.

Direct control is not a feeling.

The Future of Privacy Forum's read is that contractual policies are how a district establishes it. So the question on the page in front of you is narrow: does the agreement put the district in control of how records are used and kept, in operative language rather than a recital? Ask your board attorney whether that wording holds up in your state.

State law adds teeth. California's Student Online Personal Information Protection Act, at Business and Professions Code section 22584, bars targeted advertising to students, profiling outside K-12 school purposes, and the sale of pupil information, and requires deletion of covered information on the school's request. Many states have statutes in that mold, coverage varies, and counsel should say which binds your district.

Your agreement's deletion and retention language carries more weight than it did two years ago. The Federal Trade Commission declined to finalize the proposed provisions on ed tech and the role of schools when it amended the COPPA Rule. The rule was published April 22, 2025 with a year to comply, putting the compliance date in 2026, and it closed the reading under which "reasonably necessary" retention meant forever.

Your State May Already Have a Standard Agreement

Districts do not have to draft data terms one at a time. State alliances built the Student Data Privacy Consortium's National Data Privacy Agreement, and the current version standardizes the terms above. Put it in front of every vendor, Meta Typing Club included. A vendor that will not sign the data privacy agreement your state alliance already uses has told the board something the sales deck never would.

Per Seat or Per Site

Pricing structure is where a good product becomes a bad purchase. The question is not the number at the bottom of the quote but what makes it move.

Question	Per seat	Site or building license
You pay for	Named or active students	A building, grade band, or district
Price moves on	Enrollment counts and mid-year adds	Nothing until renewal
Reconciliation risk	True-up invoices if counts exceed the license	Low
Waste risk	Seats nobody activates	Buildings that never adopt
Ask for	Count date, pro rata adds, no retroactive true-up	Written definition of the covered site

Waste is not hypothetical. Trade coverage of LearnPlatform's 2019 analysis, drawn from 11 math and literacy tools across schools serving roughly 70,000 learners, reported that 27 percent of licenses were never activated. That study is narrow and old, and also the only published figure of its kind we could verify.

Ask for activation reporting in the contract itself, not as a favor. A typing platform can report active students and minutes practiced per building without much effort. Meta Typing Club does that through teacher class dashboards. That is a claim about our own product rather than an industry norm, and it is worth saying plainly that we currently charge nothing at all, while our terms reserve the right to add paid features later, which is exactly the kind of reservation this section tells you to read in any vendor agreement. The license shape decides which risk the district carries: seats nobody activates, or buildings that never adopt.

Termination

A board can vote to stop paying a vendor. Stopping the vendor from holding the records is a separate clause.

Look for whether the district may terminate for convenience and on how many days' notice, whether a non-appropriation clause releases the district if the board does not fund the line, and what happens to student records afterward: return, delete, certify, by when.

Numbers beat adjectives here. Termination for convenience on 30 days' written notice is language a board can hold someone to. "As mutually agreed" is not, and neither is deletion "promptly". A contract that lets you leave but keeps the data has not really let you leave.

Indemnification and the Breach You Did Not Cause

Trustees skip this clause and lawyers read it first. Indemnification decides who pays when something goes wrong that neither party wanted, and the two words that matter are "mutual" and "cap."

A one-way clause in which the district indemnifies the vendor, with nothing reciprocal for a breach of the vendor's own systems, puts the cost of the vendor's failure on the district's general fund. A cap set at twelve months of fees is fixed to what the district spends, while notification cost scales with the student records exposed. Nothing ties those two numbers together.

We could not find published data on typical liability caps in K-12 edtech agreements, and we will not invent a number. Ask for one sentence in writing: data breach and privacy claims sit outside the liability cap.

What a Clean Agreement Looks Like

Clause	Red flag language	What clean looks like
Term and renewal	Renews automatically at then-current list price	Fixed term, renewal by district action, capped escalator
Incorporated terms	Subject to the terms posted at our website, as updated	Terms attached as an exhibit; changes need a signed amendment
Student data	Vendor may use aggregated data for product and marketing purposes	District owns the records; no advertising or profiling
Deletion	Data deleted per vendor retention policy	Deletion within stated days of request, with written certification
Liability	Cap equals fees paid, no exceptions	Mutual indemnity, data breach carved out of the cap

None of this is peculiar to typing software; a reading platform and a keyboarding subscription get read the same way. The Department of Education's Student Privacy Policy Office publishes a model terms of service checklist with warning signs written for educators rather than attorneys. Clean language is the difference between the contract the board approved and a document that changed after the vote.

But That Is Staff's Job

The strongest argument against everything above is that trustees reading contracts is a governance failure, not a win. Boards set policy and approve budgets; staff and counsel review terms. A trustee redlining indemnification language from the dais slows procurement and takes on a role the board cannot hold.

Most of that is right, and we concede the operational half outright.

Where the objection fails is on the record. The board authorizes the obligation, and the five items here are governance questions in legal clothing: how long are we committed, what happens to children's records, what moves the price, how do we leave, who pays if it goes wrong. A trustee who can answer those five has done the board's work, not the lawyer's.

Key Takeaways

• Renewal decides more than price. An evergreen clause with a 30 to 60 day notice window commits the district by default, and "then-current list price" hands next year's budget to the vendor unless a capped escalator is named.
• The FERPA school official exception requires direct control over education records, and the agreement is where a district establishes that.
• Many states have SOPIPA-style student privacy statutes and coverage varies, so counsel should confirm which one binds your district and whether the agreement mirrors it.
• The amended COPPA Rule left the proposed edtech and school-authorization provisions unfinished and tightened retention, with compliance due in 2026.
• A termination clause that returns the money but not the records is unfinished. Look for a day count and a written certification.
• Per seat pricing carries true-up risk; site licensing carries adoption risk. Trade coverage of a 2019 LearnPlatform analysis put unactivated licenses at 27 percent.
• A cap set at twelve months of fees cannot scale with the records exposed in a breach. It needs a carve-out.

Trustee Questions, Answered

The packet reached me at nine last night and we vote at six. What do I read first?

Term and renewal, then the data section, then termination. Those three fit on about two pages and cover the obligations that outlive the current board. Pricing and indemnification can wait for the follow-up with staff: a bad price is fixable next cycle, a bad data clause is not.

Can I ask to table an item because I have not read the agreement?

Your board's own rules govern that, and this is not legal advice, so check with your board attorney or parliamentarian. Worth knowing: a request to table for document review is a normal governance motion, not an accusation against staff, and far cheaper than an amendment eighteen months later.

The vendor says the terms are standard and non-negotiable. Is that true?

Sometimes, for small purchases. Frequently not for anything district-wide. State alliances publish a common data privacy agreement so districts stop drafting one at a time, and a vendor signing it elsewhere can sign yours. Ask which standard agreements the vendor has already signed.

Our attorney reviewed it. Is that enough for me to vote yes?

It covers the legal exposure. It does not answer whether the term matches the pilot or whether anyone at the district still owns the renewal date. Counsel reviews risk against the law. The board decides whether to carry the commitment at all, and that is a budget judgment.

The tool is free for teachers. Does a free product still need an agreement?

If it touches student records, yes. FERPA's direct control requirement and state student privacy statutes attach to the data, not to the invoice. We found no published ranking of how student data most often leaves a district, but the mechanism is plain: no purchase order means no contract review, and no one reads the terms.

Does approving the purchase also bind us to the vendor's online terms?

That depends on the drafting, which is the point. If the signature page incorporates online terms by reference, the board has approved documents it never saw and the vendor may update them later. Ask for those terms as an attached exhibit before the vote.

What should the minutes say so this vote holds up in two years?

Record the term length, the total not-to-exceed amount, the renewal mechanism, and that a data privacy agreement was executed. A successor board reading that entry can tell what was authorized without reconstructing it from invoices, and staff can tell when the notice window opens.

Before the Next Consent Agenda

Nothing here is legal advice, and Meta Typing Club is a typing platform rather than a compliance authority. Run the five clauses against us the same way you would run them against any other vendor in the packet, and start with what you can open tonight: our terms of service and privacy policy are public pages. What no vendor's public pages carry, ours included, is the district agreement itself: the renewal mechanism, the deletion window, the liability cap. Those live in the document a vendor sends you, which is why you want it in hand before the vote. More writing for school leaders sits on the Meta Typing Club blog. A trustee who reads five clauses has done more diligence than most edtech purchases ever receive.