Buckfield budget workshop flags unclear tuition and special‑education costs in RSU 10 draft

Members of the Town of Buckfield school budget committee met Nov. 19 to pore over a draft RSU 10 budget and repeatedly flagged tuition and special‑education lines they said need clearer breakdowns and supporting counts.

The committee, working from a shared Google Doc, spent much of the meeting asking district staff to identify which students are covered by lines labeled “elementary tuition,” “private school tuition” and other span‑cost entries. Speaker 2, who led a primer on federal K–12 grants, summarized the district’s grant mix — Title I, Title II and Title V — and warned that formula and competitive grants are allocated differently and can affect where positions and services are coded.

Why it matters: several large lines lack school‑level or student‑level provenance, complicating the committee’s ability to measure the local share of tuition and the district’s immediate cash needs. The committee wants counts, account‑code mapping and the district’s rationale before finalizing local appropriations.

Committee members repeatedly pointed to three specific categories of concern: out‑of‑district tuition and superintendent agreements, special‑education staffing and contracted services, and the technology and software licensing budget. Speaker 1 said the group found a line labeled “elementary tuition” that appears to total in the hundreds of thousands and asked staff to confirm whether that reflects students sent to other districts or a district‑wide allocation.

The meeting recorded a specific private‑tuition figure discussed aloud: “$56,003.23,” which members tied to private school tuition for grades 9–12, but they said the underlying student counts and the way the total is split among Hanover, secondary and elementary lines were not clear. Committee members also noted small per‑pupil 'span' charges (discussed as approximately $9.50–$9.90) used to allocate district overhead across grade spans; those administrative shares did not reconcile on the committee’s printout.

On special education, the committee discussed whether to employ a full‑time director and assistant or to outsource the director role. Members raised that IEP‑related work (meetings, evaluation, required participants) drives workload and that some districts contract psychologists or specialists rather than sustain full‑time staff. Speaker 2 recommended collecting a five‑year average of out‑of‑district placements to smooth planning rather than relying on a single year’s snapshot.

Technology and software also drew attention. The packet included a roughly $78,000 technology/software line (described in the meeting as covering budgeting and payroll systems and recurring license fees) and several tech‑coordinator salary/benefit entries. The committee asked for a software inventory and whether RSU 10’s bulk contracts (if any) would continue to cover remote‑site schools after reorganization.

Process and next steps: the committee agreed to compile a written list of questions and to ask district staff (identified in the discussion as Leah and Chad) for an Excel export keyed by account codes so members can filter 900‑series (system‑wide) versus school‑specific lines. Kristen and Speaker 1 will assemble questions and schedule a follow‑up meeting. The group did not take any final votes during the session.

Quotes: “We need to know how many kids from our district go to these other schools,” Speaker 1 said when pressing on the tuition lines. Speaker 2 added, “Formulas can be awarded to state agencies, or directly to school districts,” explaining why funds and coding can differ.

The committee plans to request student‑level counts for out‑of‑district placements, a line‑by‑line mapping of account codes, and clarification of which positions are funded by which federal titles. Those documents will inform further budget decisions and any proposed reductions or reallocations.