# CSKE Wilbraham Financial Reporting — Site Storyline Review

**Review date:** August 17, 2026  
**Revised portal:** v3.2.0  
**Database checkpoint:** August 16, 2026 at 22:26 EDT  
**Status:** Independent prototype; not a Town of Wilbraham system or recommendation

## Executive assessment

The attached reports contain most of the right evidence and many of the right editorial rules. The problem is not a lack of analysis. It is that resident education, whole-picture technical analysis, database documentation, process explanation, and Finance Committee method have been asked to coexist in the same reading experience.

That produces three failures:

1. **The reader has to choose a report before understanding the central financial question.**
2. **Valid numbers with different scopes, periods, and meanings appear close enough to look interchangeable.**
3. **The decision and its consequences arrive after the evidence machinery instead of organizing it.**

The revised architecture assigns each audience one question and one route. The resident reads the current budget first and the choices ahead second. The connected-data exploration, annual workflow, and decision method then provide increasing depth. Sources, definitions, and complete long-form conversations support all five routes rather than competing as a sixth storyline.

## Assessment of the attached reports

### 1. Debt and Taxes Resident Guide v0.5.0

#### What is strong

- It begins with questions residents actually ask: spending, taxes, one home, Proposition 2½, schools, debt, and affordability.
- It defines terms before asking a resident to draw a conclusion.
- Its strongest number sequence is sound and relatable:
  - FY2021–FY2025 Town spending plan: $48,322,189 to $56,595,042, up $8,272,853 or 17.1%.
  - FY2021–FY2025 actual levy: $40,826,000 to $47,337,000, up $6,511,000 or 15.9%.
  - HWRSD FY2022–FY2026 budget: $50,281,358 to $57,289,029, up $7,007,671 or 13.9%.
- It correctly explains that Proposition 2½ does not cap a budget, assessment, tax rate, or one home's bill at 2.5%.
- It separates Town and HWRSD debt and reaches the evidence-supported conclusion that repayment evidence exists while complete affordability evidence does not.
- It includes “where residents can act,” which turns information into civic use.

#### What impedes the story

- The page is still too long for the intended resident experience. A resident reaches many charts, caveats, alternative time windows, and definitions before completing the basic path.
- The guide leads with historical trends while the resident now needs the FY2027 voted plan as the current anchor.
- The FY2021–FY2025 and FY2022–FY2026 Town budget windows are both valid, but presenting them in the same main route creates avoidable period switching.
- Detailed debt instruments, evidence-state teaching, glossary entries, reconciliation mechanics, and raw extracts belong behind the main walkthrough.
- One household example is correctly disclosed as non-typical, but any prominent anecdote still risks becoming the perceived Town-wide household result.

#### Editorial decision

Keep the question-led structure, plain definitions, Proposition 2½ explanation, historical direction, and clear affordability boundary. Compress the main resident route around the FY2027 General Fund and move the full historical guide to an archive link.

### 2. Whole-Picture Town Decision Guide v0.3-2.8

#### What is strong

- It recognizes the correct governing idea: major decisions should be tested as one portfolio, not as isolated proposals.
- It identifies the current large commitments and the forward choices—HWRSD, Wilbraham Middle School, BUC buildings, capital, debt, and staffing.
- It preserves the four BUC scenario families rather than silently inventing alternatives or a ranking.
- It correctly distinguishes enrollment from rated and functional school capacity.
- It has strong analytical axes for service purpose, expense nature, fund, accounting presentation, facilities, debt, recurring capacity, grants, and affordability.
- It introduces the right whole-picture affordability concept: recurring balance, annual timing, capital sustainability, and household/service consequence.
- It protects dated capital evidence from being presented as a current price.

#### What impedes the story

- It asks a resident, analyst, department head, and committee member to read the same enormous page.
- The most important forward choices appear before and after large technical sections, so the decision thread is easy to lose.
- Multiple accounting views are useful to analysts but read like competing versions of “the budget” without a strong audience contract.
- The grant inventory, parcel portfolio, long account tables, glossary, and evidence maps interrupt the public narrative even though they are valuable supporting material.
- The phrase “whole picture” becomes a reason to include everything rather than a discipline for selecting the evidence needed for the current question.

#### Editorial decision

Retain the report as the deepest evidence conversation. Its main entry should be an invitation for the Town Administrator, staff, boards, committees, and interested residents to see the breadth already available, explore questions that were previously difficult to ask across separate records, and identify the exact Town context that would deepen the next answer. The domain map, stable reporting contracts, and gaps still matter, but they support curiosity and collaboration rather than leading with database machinery.

### 3. Reporting Writer Training Packet v0.1.0

#### What is strong

This packet contains the clearest editorial standard of the three attachments. Its recommended sequence should govern future reports:

1. decision question;
2. owner and timing;
3. current baseline;
4. comparable measures;
5. material changes and drivers;
6. cross-domain effects;
7. alternatives;
8. affordability and implementation;
9. uncertainty and evidence gaps; and
10. next gates and source drill-through.

It also provides the right section anatomy: plain question, direct answer, a few scoped numbers, why they matter, boundaries, drill-through, and next evidence.

Its most important controls are:

- resident, decision, and technical views must use the same facts;
- budget is not actual;
- appropriation is not spent;
- levy is not audited property-tax revenue;
- original principal is not outstanding debt;
- assessed value is not market or sale value;
- missing is not zero; and
- affordability must include recurring balance, timing, long-term capital sustainability, and household/service effects.

#### What should change in its use

The training packet should be the production standard behind the site, not a public storyline. Residents should experience its discipline without having to read its terminology, schema practices, or QA curriculum.

## Revised five-story architecture

### Journey 1 — Current budget: “What are residents supporting now?”

**Audience:** residents and new readers  
**Anchor:** FY2027 final-voted General Fund, $57,018,471  
**Primary conclusion:** HWRSD assessment and debt total $33,094,675, or 58.042% of that General Fund; the $23,923,796 remainder already supports every other General Fund purpose.

The page then separates:

- spending authority from actual spending;
- the FY2027 General Fund from the $66.372 million FY2027 multi-fund Expense Control scope;
- the budget from the property-tax levy;
- the Town-wide levy from a household bill;
- Town debt from HWRSD debt; and
- one-time reserves from recurring capacity.

It ends with the correct limitation: the current evidence does not establish an amount available for new commitments.

### Journey 2 — Choices ahead: “What may have to change?”

**Audience:** residents following the coming budget and building choices  
**Opening problem:** “keep property taxes from increasing” has several possible meanings.

The page distinguishes:

- no operating override;
- staying below the maximum levy;
- holding the Town-wide levy flat; and
- holding each household bill flat.

It then places these choices on one portfolio timeline:

- next HWRSD budget and Wilbraham allocation;
- Wilbraham Middle School capacity and capital;
- the four BUC scenario families;
- capital, debt, and maintenance;
- staffing and recurring services; and
- household timing and distribution.

The BUC scenarios remain unranked. The $1,558,190 deferred-maintenance measure, $453,115 inflated projection, and $768,400 partial FY2027 allocations are shown as separate, non-additive measures.

### Journey 3 — Connected data: “What could Wilbraham understand when its records are connected?”

**Audience:** Town administration, staff, boards, committees, analysts, report writers, and interested residents  
**Opening principle:** start with a Town question, then let connected records and Town knowledge deepen the answer.

The purpose is to provide a glimpse of what is possible—not to inspect Town work from outside or teach staff how the Town operates. The reader is invited to help explain how records, business rules, and operational context fit together. That help improves the analysis and turns institutional knowledge into a reusable decision record.

The page maps:

- Annual Town Meeting authority and budget versions;
- Town accounting;
- HWRSD and schools;
- debt and securities;
- assets, facilities, projects, and the 2021 capital assessment;
- GIS and parcels;
- grants and funding;
- audits and continuing disclosure;
- scenarios and decision inputs; and
- source, evidence, and conformance controls.

It also exposes the stable `reporting_*_v1` contracts and the two most material empty mappings as focused invitations for help:

- `map_atm_budget_line_town_account`: 0 approved rows;
- `map_grant_award_business_subject`: 0 approved rows.

The full whole-picture report remains available as a connected-data conversation, with the detailed technical evidence preserved underneath it.

### Journey 4 — Annual workflow: “How does financial work move, and where does FinCom fit?”

**Audience:** residents, committee participants, staff, and proposal sponsors  
**Primary conclusion:** FinCom is an advisory checkpoint inside a larger chain; it does not originate, authorize, or implement every action.

The six durable handoffs are:

1. frame available room;
2. build comparable requests;
3. review baseline and changes;
4. reconcile and deliberate;
5. publish advice and support the public decision; and
6. monitor, transfer, close, and learn.

The page separates operating, HWRSD, capital, CPA, debt/Proposition 2½, and reserve/free-cash branches and shows when residents can ask the most useful questions.

### Journey 5 — Financial decision review: “How should FinCom test one proposal?”

**Audience:** Finance Committee members and other reviewers  
**Primary conclusion:** later numerical precision cannot repair an undefined decision, unreliable baseline, unreconciled funding bridge, or incomplete alternative.

The eight gates are:

1. define the decision;
2. establish the baseline;
3. control every measure;
4. reconcile money and future obligations;
5. test affordability;
6. compare complete alternatives;
7. show consequences, value, and risk; and
8. make advice accountable.

Each gate now has a question, required evidence, output, and stop condition.

## The recommended “+?”

The most useful addition is not another peer report. It is a **Future Financial Obligation Statement** that travels with every material proposal.

It should preserve:

- decision identity and version;
- opening appropriation or authorization;
- stabilized recurring change;
- debt, contract, staffing, benefit, maintenance, renewal, replacement, regional, and exit obligations;
- economic substance—real improvement, structural change, risk reduction, measurement-only change, deferral/cost shift, or unresolved;
- implementation owner, milestones, actual results, review trigger, and closeout.

This statement connects the annual workflow to the decision method and prevents the first-year price from becoming the whole story. The database is not yet complete enough to populate a live obligation total; the page explicitly preserves that boundary.

## Sitewide editorial contract

Every future section should contain, in this order:

1. the resident or committee question;
2. a direct answer—or “not yet determinable”;
3. no more than a few controlling numbers;
4. period, entity, fund, stage, and denominator beside those numbers;
5. why the answer matters;
6. what the answer does not mean;
7. the next evidence or action; and
8. a source or technical drill-through.

The main narrative should never require a reader to understand database table names. The connected-data route should never hide the business meaning behind table counts—or make a missing connection sound like a criticism of the people who understand the underlying work.

## What remains unresolved

The revised site improves the story; it does not manufacture missing evidence. The following remain necessary before a current affordability or option-ranking conclusion:

- a reconciled multi-year Town and HWRSD recurring forecast;
- FY2027 and future levy/revenue bridges and household distributions;
- current BUC use, condition, operating cost, legal constraints, complete option scopes, transition, proceeds, funding, and lifecycle cash flows;
- Wilbraham Middle School rated and functional capacity, room/schedule use, grade-level enrollment, and current forecast;
- current consolidated Town and allocated HWRSD debt service, exclusions, retiring debt, and capital schedule;
- a completed/open/superseded/current-condition bridge for the 2021 capital study;
- approved cross-domain mappings for voted budget to Town accounts and grants to business subjects;
- service outcomes and consequences for material budget changes; and
- confirmation of the current official annual calendar and live decision procedures.

## Implementation in portal v3.0.0

- Rewrote the landing page around five connected questions.
- Rebuilt the current-budget resident journey around the FY2027 voted plan.
- Rebuilt the choices-ahead journey around tax-policy meaning, BUC, Middle School, and the combined commitment stack.
- Replaced the technical-report front page with a complete database domain and readiness map.
- Rebuilt the annual workflow around FinCom's advisory lane and the separate financial branches.
- Rebuilt the decision workbench as a static, printable eight-gate method.
- Reframed sources and definitions as a supporting layer.
- Preserved every former long-form page as an archived drill-through file.
- Added the August 16 schema catalog and captured live schema to the deployable package.

## Long-form editorial revision in portal v3.1.0

The six supporting long-form pages were no longer left as untouched archives. Each received a page-by-page editorial pass that:

- replaces “walk-down,” “how to use this report,” and system-centered headings with reader questions;
- opens with the human decision or resident concern rather than the reporting method;
- places direct answers before definitions, controls, and caveats;
- uses “why this matters” and “what we still need to know” as recurring transitions;
- keeps tables, calculations, evidence labels, source boundaries, and technical drill-through intact;
- relabels links from “archived reference” to “complete long-form conversation”; and
- adds a shared reading layer that improves line length, heading balance, callouts, and mobile readability.

The short five-journey architecture still provides the front door. The long-form pages now feel like a deeper conversation on the same story rather than a manual attached to it.

## Connected-data journey revision in portal v3.2.0

Journey 3 now has a clearer audience and purpose:

- show Town administration and other readers the breadth and depth of information already available;
- demonstrate the kinds of cross-domain questions that were difficult or impossible to ask when records lived in separate documents;
- create interest in what additional sources and relationships could make possible;
- invite Town staff to help explain records, business rules, and operational context; and
- show how technology and data can add deeper due diligence, analysis, explanation, traceability, and documentation without replacing institutional knowledge or judgment.

The page now leads with possibilities and questions before schema counts, pipelines, or reporting contracts. Missing information is framed as a focused invitation—“which source, mapping, assumption, or working rule would carry this answer farther?”—rather than as a deficiency. Potentially accusatory wording was removed sitewide; the replacement vocabulary emphasizes evidence, completeness, reviewability, clarity, and preserved meaning.

## Resident entry progression in portal v3.2.1

The homepage no longer asks a new reader to interpret four large totals before choosing a reason to stay. Its opening progression is now:

1. reassure the reader that every number and report is not required;
2. invite one familiar question;
3. offer the two resident journeys first;
4. introduce the one-minute financial picture only after the reader has a purpose;
5. explain the nesting among the four visible numbers; and
6. offer sources and deeper methods only when the reader wants them.

The $66.372 million cross-fund scope now has its own supporting drill-down. The page begins with the one relationship a resident needs first—the $57.018 million General Fund is already inside the larger number—then explains the six fund families, the amounts outside the General Fund, the relationship to the school and levy figures, and the remaining reconciliation work. The total is explicitly provisional for economic interpretation because transfers, carryforwards, reimbursements, pass-throughs, related authorizations, and possible overlap are still under review.

The resident-facing vocabulary now uses “option,” “approach,” “obligation,” “standard,” or “expected result” according to context. This reduces political or moral overtones and keeps attention on what is actually being defined or tested.