Budget storylines

This page turns the budget evidence into reportable story packages. It starts from the claim a reader might make, then points to the first proof table, district examples, outside records, interview checks, follow-up surfaces, and the counter-reading that should travel with the story.

NJDOE User-Friendly Budgets, 2025-26 latest year. Real movement uses CPI-U and 2025 dollars across loaded UFB years where labeled. How this budget data works

Statewide story angles

These generated angles turn the current UFB findings into assignment-ready leads. Each row starts with the statewide signal, keeps the proof surface and concrete district examples nearby, and names the shortcut that should not become the story.

The angles are generated from the same statewide briefing, question routes, and lead sheets as the report. They are not causal findings; they are the first reporting packages the current UFB evidence can support.

Budget mechanism explainer

Before reading a district as expensive, squeezed, underfunded, or wasteful, choose the mechanism the evidence is actually testing. This table keeps the headline claim, benchmark, denominator, money basis, proof links, outside records, and blocked overread together.

This explainer is table-led because each mechanism crosses mixed units: NJDOE comparative cost, operating revenue shares, CPI-U movement, nominal proposal rows, source-family dollars, service-load counts, tax bases, reserves, and side files. It is an assignment desk, not a causal model.

Mechanism coverage ledger

Before choosing a story route, size the machines. This ledger shows how much of the statewide UFB load each overlapping mechanism touches: districts, operating scale, UFB on-roll, published cost position, real per-student movement, examples, proof paths, and shortcuts to block.

Rows are overlapping reporting screens, not additive categories. A district can appear in several mechanisms, so district counts, operating scale, and on-roll shares should size the reporting route, not sum to a statewide total. Published comparative cost is NJDOE's row; real movement uses CPI-adjusted loaded-year anatomy where available.

Fiscal mechanism map

The explainer names the possible machines. This map shows where the current UFB data points first: local-cap exposure, aid exposure, category or service-load cost engines, denominator movement, one-time bridges, live proposal shocks, and side-file exceptions. Mechanisms can overlap, so the rows are reporting routes rather than exclusive labels.

The mechanism map is generated from latest-year UFB rows, CPI-adjusted loaded-year movement where labeled real, General Fund operating revenue shares, proposal columns, source-family signals, service-load rows, balance/reserve context, and side files. It identifies what to investigate; it does not prove statutory cap exhaustion, aid entitlement, deficit, waste, adequacy, service quality, or cause.

News judgment filter

Not every true budget signal is the story. This filter separates ordinary background, such as nominal budget growth, from reportable signals that need a fair comparison, source basis, examples, and a blocked shortcut before writing.

Money-path bridge

A budget story should not force the reader to infer how payer-side evidence, spending categories, proposal timing, and comparison frames connect. This bridge keeps those signals in the same row before a claim becomes prose.

The bridge is not an accounting schedule. It keeps operating revenue, proposal rows, pupil-cost categories, service-load rows, source families, and side files separate while showing which evidence must travel together.

Claim safety ledger

The same number can support a careful sentence or a misleading one. This ledger names what the UFB rows can safely establish, what outside reporting must still check, and which conclusion should not be written from the budget data alone.

Story readiness ladder

The claim safety ledger controls wording. This ladder controls readiness: which budget sentences can be published from UFB with caveats, which are only reporting leads until local records are checked, and which conclusions should be blocked from UFB alone.

Vizier's generic form router suggested part-to-whole forms for readiness states, but this stays table-led because the job is not counting claim states. The reader needs the safe sentence, missing evidence, proof path, and blocked overread in the same row.

Reader stakes map

A budget story should answer what a resident can understand, compare, or ask next. This map starts each lane with the reader's stake, then keeps the first UFB signal, proof surface, and blocked inference in the same row.

Vizier suggested visual forms for part-to-whole or geography tasks, but this map is neither a composition nor a county map. It stays table-led because each lane crosses dollars, shares, tax bases, denominators, side files, proof links, and counter-readings.

Structural squeeze screen

Some budget stories follow a structural squeeze pattern: local revenue dependence, costs that do not move like a simple 2% line, denominator pressure, and one-time support or category clues that have to be verified locally. This generated screen looks for that pattern statewide without calling it a deficit, levy-cap violation, cut, or cause.

The screen is a reporting queue, not a diagnosis. UFB can show local-revenue dependence, real per-student arithmetic, funding mix, category/source-family clues, service-load rows, and planned fund-balance or reserve support. It cannot prove deficits, cuts, levy-cap mechanics, adequacy, efficiency, or cause without board records, levy worksheets, audits, staffing detail, contracts, and interviews.

Story packages

Each row is a generated reporting package. The examples are starting points for local reporting, not final judgments about district performance.

District story scorecard

The story packages below are broad. This scorecard shows where the district-level signals are actually concentrating and what comparison frame has to travel with each lane.

Rows are sorted by the strongest generated district signal in each lane, then by how many districts land in that lane. It is an assignment-desk layer, not a rating of districts or a causal model.

Cross-signal budget tensions

A budget story can fail when one true signal is read alone. This generated tension finder packages the strongest cases where cost position, tax basis, real movement, proposal movement, reserves, side files, service load, student need, or category signals have to be read together.

Use these rows as reporting prompts, not as proof that the paired signals cause each other. The table keeps mixed units visible rather than collapsing them into one score.

Reporting handoff

The UFB evidence can identify the story lead, but local reporting has to finish it. This table turns each generated package into records to pull, interview checks, proof surfaces to keep open, and the unsupported shortcut to block.

County story map

County pages are often the fastest path from statewide evidence to a local assignment. This map shows which county frame is likely to matter first.

How to work a budget story

The strongest budget reads move from claim type to fair comparison, timing, denominator, and source-row proof.

What this story desk cannot prove

• It does not replace reporting. The page chooses evidence packages from UFB rows, but board documents, contracts, staffing, enrollment, facilities, and local policy still need checking.
• It does not rate districts. Cost, tax, reserve, placement, or salary signals are prompts for explanation, not quality scores.
• It keeps mixed units separate. Proposal dollars, CPI-adjusted movement, shares, rates, side-file rows, and source-line examples should not be collapsed into one number.
• It uses the loaded local warehouse. Generated output bakes in the current NJDOE UFB warehouse and links only to districts with matching public slugs where available.