Skip to main content
Meta Typing Club
Education

One Typing Standard: The Sprawl Fight Worth Picking First

Meta Typing Club12 min read
One Typing Standard: The Sprawl Fight Worth Picking First

Districts kept access to an average of 2,982 distinct edtech tools in 2024-25, close to nine percent more than the year before. Typing is the category to consolidate first, because nobody defends a fourth typing app the way they defend a reading program, and four apps mean four privacy reviews, four support paths and no district-comparable data.

TL;DR: Start rationalization where the pedagogy is uncontested. Consolidating typing onto one district standard buys comparable progress data, one data privacy agreement instead of four, and one support path, at the cost of a migration window and a grandfathering promise you have to keep. The license savings are the smallest part of the win.

What sprawl actually costs you, line by line

The license line is the one your finance office sees and the smallest number in the file. Everything expensive about running four typing tools is invisible to the general ledger.

The three costs nobody invoices you for

Privacy review comes first. The Student Data Privacy Consortium values agreement work at an average legal fee of $250 per hour with a minimum of one hour for the district and one for the vendor, and that is per agreement, per year of amendments, per renewal. Four typing vendors is four of those, for one instructional outcome. Support is second: four password reset paths hitting your help desk in the first two weeks of September, when the queue is already at its annual peak. Comparability is third, and it is the one that stings in a cabinet meeting. Four tools report on four scales, so the question of whether third graders across the district are on pace has no answer that survives a follow-up.

And the licenses you are already paying for

GovTech, reporting a Penn Center for Learning Analytics analysis of 48 districts, found a median 70 percent of student software licenses completely unused and 97.6 percent not used to the level intended. EdSurge's April 2026 reporting on district rationalization calls the survivors zombie licenses, which is exactly what they feel like when you find them in a renewal file.

Sprawl is not a spending problem, it is a comparability and review-hours problem, and only the second one gets audited.

Why typing is the fight you can win

Try consolidating your reading curriculum and you will spend a year in meetings with people who have professional identities attached to the answer. Typing has almost none of that. An EdWeek Research Center survey found 69 percent of school and district leaders say keyboarding is taught somewhere in their district, and 84 percent say it happens in grades 3 through 5, which means the practice is common and the ownership is thin.

The standards picture explains why nobody is guarding the territory. Common Core names keyboarding once at grade 3, in W.3.6, as using keyboarding skills, with no measurable expectation attached until a year later. A category with a real instructional need, a common practice and no defended methodology is the softest target on your rationalization list.

Pick the category where consolidation costs you a migration window instead of a philosophy war.

The audit that fits on one spreadsheet

Before any recommendation, build the inventory. Four steps, and none of them require a vendor conversation.

  1. Pull every typing product with a live login in any building, including the free ones teachers found themselves, from your single sign-on logs rather than from your purchase orders.
  2. Pull 30-day active users against seats held for each one. Held seats without logins are your negotiating position.
  3. Pull the data privacy agreement for each product and check its state. In Illinois, SOPPA requires a written agreement before covered information is transferred and public posting of each executed agreement within 10 business days; in New York, Education Law 2-d requires the parents bill of rights to accompany every contract with a third-party contractor receiving student data. Any product without one is a finding you can act on this week.
  4. Ask each principal one question: which of these does your staff actually teach with, and who would be upset if it went away?
ColumnWhere it comes fromWhat it decides
Seats held vs 30-day activeVendor console or SSO logsWhich contracts do not get renewed at all
Buildings and grade bandsYour inventory plus principal repliesWho needs a migration window and who does not
Signed agreement and template usedYour DPA file or state registryWhich product is a compliance finding today
Export format for student progressVendor documentationWhether teachers lose history in a migration
Renewal date and notice periodContractThe calendar your whole consolidation runs on

Districts that do this on a schedule get compounding returns. Joliet Public Schools, in the same EdSurge reporting, reviews usage data annually and eliminates tools with low adoption or redundancy rather than waiting for a budget crisis to force it.

Consolidating without a teacher revolt

The teacher who built a beautiful rotation around a product you are about to cancel is not being difficult. She is protecting work she did on her own time, and she will decide how the rest of her building talks about your department for the next two years.

Four commitments hold that together. Grandfather to the end of the school year, so nobody loses a class mid-sequence. Migrate at the fall start, never in February. Name one champion teacher per building, ideally the person with the loudest attachment to the tool being retired, and give her the first accounts and the first look at the reports. Publish an exception route in writing: a building that wants to keep a different product submits an instructional reason and gets an answer within two weeks, and yes, sometimes the answer is yes.

The pain is real and worth naming out loud. East Moline School District 37 described the pre-consolidation state as teachers going to four different places to run a lesson. Teachers feel sprawl before technology directors quantify it, which means the case for consolidation is often already made in the staff room.

Announce the migration date and the exception route in the same email, or your consolidation becomes a rumor with a villain.

What one standard buys that four cannot

Set expectations honestly with your cabinet. The savings that justify the work are operational, and the dollar line is real but modest.

What changesFour toolsOne standard
Progress dataFour scales, no district viewOne scale, comparable across buildings and grades
Privacy reviewFour agreements, four renewal cyclesOne agreement, one amendment thread
Help deskFour reset paths and four vendor escalation contactsOne path, one documented escalation
Teacher trainingRepeated per building, never at scaleOne session that transfers when staff move buildings
BudgetSmall duplicate lines nobody ownsOne negotiated rate with a known renewal date

Notice which row is last. If you sell this to a superintendent as a savings project you will be asked for a number that is too small to impress anyone, and our breakdown of the real total cost of a district-wide typing program shows why the interesting money is in staff hours rather than licenses. Sell it as the first district-comparable dataset you have ever had on keyboarding, tied to the grade-band benchmarks your curriculum office can defend.

The best argument against me

Standardizing concentrates risk. One vendor with your whole district on it can degrade its product, raise its price at renewal, or fail, and your leverage on renewal day is whatever you wrote into the contract two years earlier. A building running its own tool has an exit; a district standard does not.

That objection partly wins, and the answer is contractual rather than rhetorical. Write a data export clause naming the format and a deadline. Take a three-year term rather than five. Keep the documented exception route alive so at least one building is running an alternative and your team stays fluent in it. And keep the annual usage review, because a standard that stops being used is worse than sprawl: it is sprawl with a policy attached.

Where Meta Typing Club fails your own test

We sell a typing platform, and a post from a typing vendor arguing that districts should standardize on one typing platform is self-serving by construction. So here is what your rationalization checklist would flag about us, verified against our own code rather than our marketing.

There is no Clever, ClassLink, OneRoster, LTI or SAML integration anywhere in the product. Rostering means a CSV upload per school or a teacher or parent creating each student account, and at district scale that is real setup labor you would have to plan for, which our note on why new platforms die in rostering rather than in the demo treats as the failure mode it is. The dashboard reports words per minute only, so a benchmark table written in characters per minute needs converting. Districts and school networks receive a quote; an independent teacher evaluating on their own account pays nothing and has no student limit, which is not a pilot and not a way around your review. An adult can delete their own account in Settings, and a child account is deleted by the parent, teacher or school that created it. Our public School Agreement states that student data is stored and processed in the United States, but our subprocessors are not published, so demand a signed agreement, a named subprocessor list, a written retention period and an inventory of what a child account stores, from us and from every finalist.

The flip side is worth your attention. Because there is no roster sync, no child email is required, and no age or date of birth is collected, a first phase can run on neutral class identifiers with the name mapping held inside the school.

A vendor that cannot tell you where it fails your checklist has not read your checklist.

Key takeaways for the rationalization file

  • Districts kept access to an average of 2,982 edtech tools in 2024-25, up close to 9 percent year over year.
  • A median 70 percent of student software licenses went completely unused in the Penn Center analysis of 48 districts, and 97.6 percent were not used to intended levels.
  • Each duplicate vendor carries its own agreement work, valued by the Student Data Privacy Consortium at $250 per hour with a 1-hour minimum for each side.
  • Typing is the low-controversy first cut: 69 percent of leaders report keyboarding is taught somewhere, and Common Core names it once, at grade 3.
  • Run a 5-column inventory: seats versus 30-day active users, buildings, agreement status, export format, renewal date.
  • Protect the rollout with 4 commitments: grandfather to year end, migrate at the fall start, name a champion per building, publish an exception route with a 2-week answer.
  • Expect the operational wins first; the license savings are the smallest line in the case.
  • Meta Typing Club has no rostering integration, reports WPM only, and gives districts a quote; a teacher's own account is free with no student limit, as one teacher's evaluation.

Questions technology directors ask before they start

How many typing tools is normal for a district our size?

There is no published typing-specific benchmark, so use the total as a proxy: an average of 2,982 tools per district in 2024-25, with individual students and teachers interacting with an average of four integrated tools each. If more than one typing product has live logins in a single building, you already have a consolidation case.

What does the privacy review actually cost us?

The Consortium's own model applies $250 per hour with a one-hour minimum for each district and each vendor per agreement, which is the only public primary-source figure. Your real cost is higher, because the hour it models does not include your team's review, the amendment cycle or the annual reconfirmation.

Can we import our student roster?

Only as a file. There is no Clever, ClassLink, OneRoster or LTI connection, but a school can upload a CSV file with OneRoster-style column names or add students one by one, and a teacher or parent can create accounts. That is a genuine cost at scale, and it is also why a first phase can run without child email addresses or dates of birth.

What happens to student data in the products we drop?

Export before the license lapses, not after. Ask each retired vendor in writing for the export format, the retention period after termination and the deletion confirmation, and file those with your agreement records. Districts in states with posting requirements will need that paper trail anyway.

How do I handle the building that refuses to move?

Give it a written route rather than a fight. An instructional reason, a two-week answer, an annual review of the exception. Most exception requests evaporate once teachers see comparable data across buildings, and the ones that survive usually teach you something about your standard.

What is the per-student price?

A district rollout is quoted, while a single school sees published yearly prices, USD 250 for School Plus and USD 500 for School Pro. Ask for a quote naming the term, the seat count, the renewal date and the price at renewal, and put that document in front of your cabinet before anyone commits to a standard.

How long does a migration window need to be?

One school year, structured as a spring decision, a summer setup and a fall start. Retiring products keep running until June for classes mid-sequence. The one deadline worth defending is that no new building adopts a fifth product during the window.

Where to start this month

Pull the login inventory before you pull the contracts, because the tools nobody bought are the ones nobody reviewed. Rank your duplicate categories by how much of a fight each one will be, and put typing at the top, where the instruction is agreed and the ownership is loose. If we are one of the products you evaluate, read our structured keyboarding lessons against your grade bands first, then check whether your next device refresh is also a keyboarding decision, then ask us for the written quote and the privacy artifacts in the same email. Consolidation that begins with an inventory ends with a recommendation; consolidation that begins with a vendor demo ends with a fifth tool.

#edtech sprawl#app rationalization#technology director#district typing standard#student data privacy#software consolidation
Share:

You Might Also Like