06-reference/research

k12 abm district count fiscal cycle dpa verification

2026-10-28·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
k12abmb2govstudent-privacyverification

Verifying the K-12 ABM hypothesis table: district count, fiscal cycle, DPA gates

The question

"Verify the K-12/B2Gov ABM hypothesis table (~13,000 districts, July fiscal cycle, state DPA gates) before it goes into a phData training deck"

Context: [[2026-10-22-abm-k12-edtech-training-pattern]] labels its own district-count, fiscal-calendar and DPA claims as "Ray's general-knowledge synthesis... not web-checked." This brief pins each to a primary source or marks it unverified. Only three claims in that note are load-bearing enough to verify; the rest of the table (public board minutes, peer-district proof, funding-source framing) is pattern description, not checkable fact.

Verdicts - (V) verified with citation, (P) partially verified / definition-dependent, (U) unverified:

Claim as written in the 10-22 note Verdict Corrected statement
"about 13,000 US school districts" as the ABM account universe (P) 13,303 operating regular school districts (NCES CCD SY2023-24) - but 19,186 operating public education agencies total, incl. 4,212 independent charter LEAs. The ABM denominator is ~19,200, not ~13,000.
"most districts' fiscal year starts July 1" (P) July 1 is the common start but is neither universal nor always state-level: Tex. Educ. Code §44.0011 lets each board pick July 1 or Sept 1; Alabama systems appear to run Oct 1 - Sep 30 (state DOE budget form, read as a search summary only).
"most districts" as a quantified national share (U) No published national census of district fiscal-year start dates found. Do not state a share.
DPA is often its own gate in the buying committee (V) True, but the gate is mostly contractual (SDPC NDPA + state variants, Fla. Admin. Code R. 6A-1.09550), not statutory.
"some states require a signed one before student data moves (Illinois 105 ILCS 85 §15(4); California Educ. Code §49073.1)" (P) - Illinois (V), California wrong IL SOPPA §15(4) is a genuine pre-transfer gate (nonpublic schools excluded). Cal. Educ. Code §49073.1 is not: it obligates the LEA to ensure its contract contains nine terms, remedy = void on failure to cure. Drop California from that sentence.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The headline correction is the denominator, and it changes the lesson rather than just the number. The note's thesis - K-12 is the cleanest ABM market because the account universe is finite and fully known - gets stronger with the right figure, not weaker. The real universe is roughly 19,200 operating public education agencies, of which 13,300 are regular districts and 4,200 are independent charter LEAs. That is still finite, still fully enumerated in a free federal dataset, still tractable for a tiering exercise. But "13,000" quietly deletes the charter segment, which in an ABM motion is a distinct tier with a different committee shape, a faster cycle and often no central-office CTO. Teaching a marketing team to build a Tier-1/2/3 account list off 13,000 regular districts and then wondering why the charter pipeline is invisible is exactly the kind of error an ABM training should be inoculating against. The correct framing for a deck: name the denominator and its definition, then show that choosing the definition is the first ABM decision, not a footnote.

The fiscal-calendar row needs a mechanical rewrite, not a number fix. "Most districts' fiscal year starts July 1" is unsourceable as a quantified claim, and Texas §44.0011 shows why: the start date is a board-level choice between July 1 and September 1, so two neighboring Texas districts can sit on different cycles. Alabama runs its whole system October to September. The teachable version is better anyway: the fiscal year is a per-account attribute you look up, same as the superintendent's name, and it is published in every district's adopted budget document. That converts a shaky generalization into an agent task, which is where the note was already heading in its "agents in production" section. An agent that reads a board packet can read the fiscal-year dates off the budget cover page.

On DPAs, the substantive fix is to stop describing one mechanism and start describing two. Statutory gates are rare and narrow: of the five states verified in [[2026-09-02-scribble-works-school-phase-state-law-plan]], only Illinois SOPPA §15(4) actually conditions the data transfer on a signed agreement, and even that excludes nonpublic schools. Contractual gates are near-universal and are what a vendor actually experiences: the SDPC National Data Privacy Agreement and its state variants, plus state rules like Fla. Admin. Code R. 6A-1.09550 that push privacy terms into district contracts. For a training deck the distinction is operational. If the gate were statutory you would build a 50-state compliance matrix; because it is mostly contractual and consortium-standardized, the play is to complete one NDPA with an Exhibit E General Offer and treat that signed package as a reusable credential across an entire state alliance. That is a far more interesting ABM insight than "privacy is a gate," and it is the kind of thing that makes a vertical-ABM session concrete.

Calibration note for whoever builds the deck: every number above is a public federal or state figure, and the two statutory readings are from primary text pulled 2026-10-28. The one thing that stays unverified is the national distribution of fiscal-year start dates. Do not round it into "most districts."

Why this is in the vault

[[2026-10-22-abm-k12-edtech-training-pattern]] is the reuse outline for the next marketing-team ABM training, and it self-labels its central table as unverified. This brief is the gate between that hypothesis table and live training content: it supplies the citable district count and its definition, kills the unsourceable "most districts start July 1" quantifier, and corrects the CA §49073.1 mischaracterization that the 10-22 note introduced while citing a vault brief that had it right. It also tightens the public-market half of [[project_credibility_for_phdata_sales]]'s "agents in production" demo, since the agent task becomes per-district attribute extraction rather than a stated generality.

Open follow-ups

Related

Sources

Vault:

Web (all retrieved 2026-10-28): Read directly this session (full page text):

Seen only as a search-result summary, not fetched in full - treat as one step removed: