A student can appear in the student information system without contributing 1.00 full-time equivalent (FTE) to a state funding report. A short schedule, a withdrawal entered after the count date, or a transfer assigned to the wrong resident district can change the report even when the SIS headcount looks reasonable. The useful control is a documented, student-level bridge from the count-day SIS snapshot to the numbers submitted for apportionment.
This guide uses Washington’s 2026–27 P-223 process as a concrete example. Its count dates, 1,665-minute divisor, forms, and deadlines are Washington rules, not a national formula. Districts elsewhere should substitute their own education agency’s current enrollment and attendance rules. For the broader funding context, see how state aid and attendance accounting connect.
Why an SIS enrollment count is not the P-223 total
Washington’s Office of Superintendent of Public Instruction (OSPI) says enrollment reported on Form P-223 helps determine general apportionment and several program allocations. Form P-223H separately supports special education funding. September through December apportionment payments rely on budgeted enrollment in the F-203; beginning in January, monthly payments rely on actual year-to-date average enrollment reported to OSPI. That makes a monthly reporting error both a compliance problem and a cash-flow forecasting problem. The 2026–27 OSPI Enrollment Reporting Handbook explains these funding links and the supporting records districts must retain.
Three numbers should be kept distinct: the people in the SIS, the students eligible to be claimed on the applicable count day, and the sum of their reportable FTE. A student who is eligible but attends part time may add one to headcount and less than one to FTE. Program-specific counts may require a different form or evidence. An enrollment dashboard that presents only active records cannot prove any of those totals by itself.
Set the count-day snapshot before calculating FTE
Washington’s WAC 392-121-119 generally sets the count date at the fourth school day of September and the first school day of October through June. An individual school’s or grade’s calendar can determine its count date when calendars differ; Running Start has a different October–August pattern. OSPI’s handbook gives a September example in which a school opening on September 8, 2026 counts on September 11 while other district schools opening September 1 count on September 4. A districtwide date hard-coded into an export would miss that distinction.
Before the count, have the registrar or SIS owner freeze a reproducible extract with student ID, school, grade, enrollment and exit dates, resident district, program flags, course schedule, and attendance or participation evidence. Store the extraction time and the calendar used for each school. A later SIS edit should be traceable as a change to the original snapshot, not silently replace it. For related system design issues, see how districts integrate SIS and ERP data.
Test eligibility before the arithmetic
The OSPI handbook requires enrollment in an eligible course of study and participation on or before the count day, subject to the applicable exclusions. Its audit guidance calls for evidence of participation by September’s count date and attendance within the preceding 20 consecutive school days for October through June. A student who has withdrawn, transferred, dropped out, or met another exclusion should not remain in the claim merely because an SIS status was left open. The handbook also distinguishes choice transfers from interdistrict agreements when deciding which district may claim a nonresident student. Ask the enrollment specialist to resolve these exceptions with the underlying records; do not infer eligibility from an “active” flag alone.
Convert schedules to FTE with a visible calculation
For ordinary classroom instruction, WAC 392-121-122 uses 1,665 enrolled minutes per week as the full-time benchmark. A partial FTE is weekly enrolled minutes divided by 1,665, subject to the state’s other limits. Meals are excluded; qualifying class-change time may be included. OSPI says regularly scheduled late starts or early releases must be reflected in the weekly minutes. Its handbook directs districts to round student FTE to two decimal places and provides an FTE calculator tool on the current enrollment reporting page.
Illustrative reconciliation: Suppose 24 eligible students each have 1,200 reportable weekly classroom minutes on the October count date. Each contributes 1,200 ÷ 1,665 = 0.72 FTE after rounding. Their combined reportable FTE is 17.28, although the headcount is 24. If an SIS export instead defaults each student to 1.00, the file overstates the group by 6.72 FTE. The reviewer should trace the weekly minutes to the published bell schedule and each student’s course schedule, then correct the source calculation and document the adjustment. This example is arithmetic only; it is not a dollar estimate of state aid.
That basic formula should not be pasted across every program. Washington’s handbook describes separate rules for alternative learning experience, Running Start, Open Doors, and other arrangements. A student with more than one setting may also face combined FTE limits. Keep the program code and its rule beside the student-level calculation so a reviewer can see why a value differs from ordinary classroom FTE.
Build a monthly bridge that a second person can review
- Lock the inputs. Save the original SIS roster, school calendars, bell schedules, transfer records, and count-day attendance or participation evidence. Note the report month and extract timestamp.
- Apply eligibility tests. Mark withdrawn, transferred, long-absent, and other exception records for documented review. Record the reason, decision maker, and evidence rather than deleting the row.
- Calculate at student level. Derive FTE from the applicable schedule or program rule. Retain the minutes or other inputs, rounded student FTE, grade, school, and resident district.
- Aggregate by reporting field. Reconcile headcount and FTE by school, grade, and program to the P-223 lines. Reconcile special education headcount separately to P-223H, with the required IEP, evaluation, and service evidence.
- Explain every difference. Compare the district totals with the previous accepted month, the current SIS dashboard, and the budget forecast. Keep a short exception log for timing, status, schedule, and program changes.
- Approve and submit. Have a reviewer who did not prepare the file sign the bridge. Retain the submitted version and the accepted reports with the supporting records.
OSPI’s 2026–27 Enrollment Reporting User Guide says the electronic P-223 application runs validations on P-223 and P-223S submissions. Its edits compare October–June P-223 and P-223H district totals with the prior accepted month and may require a correction or an explanatory comment. These system checks are useful, but they do not replace the student-level bridge: a plausible district total can still hide a student claimed under the wrong program or school. The handbook says EDS enrollment reporting is separate from CEDARS reporting.
What to retain for audit and budget review
The OSPI handbook’s documentation section calls for signed monthly reports, enrollment and withdrawal dates, schedules supporting FTE, school or program FTE calculations, student rosters, daily attendance, and relevant nonresident agreements. For P-223H, it identifies evidence of an active IEP, a current evaluation, and qualifying services. Organize a monthly folder so a reviewer can move from the submitted 1251 or 1735 report to the aggregate bridge and then to a selected student’s source documents without reconstructing an old SIS state.
Finance should also use the reconciled result in its forecast. Label each month as budgeted, submitted, or accepted; do not mix those states in a trend chart. When a count changes, show the FTE variance and the reason before changing projected aid. Washington’s January shift to actual year-to-date average enrollment makes this especially relevant to midyear cash planning. The related district revenue forecasting guide covers the wider budgeting process.
Common mistakes and a final pre-submission checklist
The recurring errors are simple to describe: treating headcount as FTE; using one count date for schools with different calendars; counting a student whose participation or attendance evidence is missing; overlooking a withdrawal or transfer; and accepting an automated validation as proof of the underlying roster. A second risk is quietly changing a prior month without following the state revision process. OSPI’s 2026–27 handbook lists October’s original P-223 and P-223H due date as October 19, 2026 and explains how later revisions are routed. Confirm the current handbook and district calendar before relying on any deadline.
- Is the count date correct for every school, grade, and program?
- Can each claimed student be tied to eligibility and count-day evidence?
- Do student schedules and program rules support every partial FTE?
- Do headcount and FTE reconcile separately to each submitted form?
- Are unusual month-to-month changes explained and independently approved?
- Are the signed reports, extract, calculations, and source records retained together?
A defensible enrollment report is a traceable calculation, not merely a successful upload. When the SIS snapshot, eligibility decisions, FTE math, submitted forms, and forecast all connect, district staff can correct errors sooner and explain the reported numbers to both finance leaders and auditors.