4. The Annual Data and Compliance Calendar
School data work does not follow the instructional calendar neatly. Many deadlines occur immediately after school opens, near winter break, shortly after the new year, during spring planning, or after students and many employees have left for summer.
A realistic compliance calendar must show more than final due dates. It must show when source data becomes available, when departments must review it, when corrections must be made, when leadership approval is needed, and whether qualified staff will actually be working.
The calendar should answer five questions
For every obligation:
- When does the source data become available?
- When must it be entered or corrected?
- When should internal review begin?
- What is the external deadline?
- Who must be available to complete and approve the work?
A better calendar structure
Do not build this as a single list of state deadlines. Use fields such as:
- Reporting activity
- Governing agency or requirement
- Data period
- Source system
- Source-data owner
- Person preparing the submission
- Reviewer
- Certifier or approver
- Internal opening date
- Internal review date
- Correction deadline
- External deadline
- Dependency or prerequisite
- School-break conflict
- Backup employee
- Status
- Last verified date
- Official source link
The annual rhythm
July and August: close one year while opening another
Typical work includes:
- Finalizing prior-year records
- Summer enrollment and withdrawals
- New-year system configuration
- Calendars, terms, courses, and sections
- Staff assignments
- Student rollover and promotion
- Data integration testing
- User-access review
- Beginning-of-year forms
- Emergency contact verification
- Training new and returning staff
The central problem is overlap: the prior year is not finished while the new year is already generating data.
September and October: stabilize the opening of school
Typical work includes:
- Enrollment and demographic review
- Attendance reconciliation
- Program participation
- English learner records
- Staff and course assignments
- Special education coordination
- Census-day preparation
- Initial state-reporting extracts
- Correction of rollover and scheduling problems
This is often when local operational urgency and state reporting collide.
November and December: validate before the break
Typical work includes:
- Resolving submission errors
- Reviewing certification reports
- Coordinating corrections with schools and departments
- Confirming program and enrollment records
- Completing required approvals
- Preparing for deadlines that occur during or immediately after the winter closure
The calendar should expose deadlines whose work must be completed before employees leave.
January and February: certify, reconcile, and begin planning
Typical work includes:
- Completing winter reporting and certifications
- Responding to anomalies discovered in fall data
- Midyear attendance and academic monitoring
- Staffing and enrollment projections
- Accountability and program reporting
- Preparing data needed for budget and LCAP development
- Reviewing access and integration changes
A January deadline often represents work that had to begin in November.
March and April: connect operations, accountability, and planning
Typical work includes:
- State testing preparation
- Accountability-data review
- LCAP metrics and stakeholder information
- Program evaluation
- Course and staffing planning
- Graduation-status review
- End-of-year reporting preparation
- Verification of data needed before staff leave
May and June: close the year deliberately
Typical work includes:
- Completion and graduation records
- Final grades and credits
- Attendance closure
- Program exit and completion records
- End-of-year state submissions
- Special education and service records
- Report cards and transcripts
- Data archival
- Summer-program setup
- Documentation of unresolved issues
This is the time to capture staff knowledge before summer departures.
Do we have to work during winter and summer break?
The honest answer is: sometimes, but it should not happen by accident.
Some submission windows, corrections, certifications, enrollment processes, emergency responsibilities, and year-end activities continue while schools are closed. Whether an employee must work depends on the actual reporting calendar, the employee’s work year and assignment, collective bargaining agreements, local calendars, staffing decisions, and district procedures.
The page should not normalize uncompensated or improvised break work. Instead, it should encourage districts to:
- Identify break-period obligations before the year begins.
- Establish internal deadlines earlier than external deadlines.
- Assign year-round or extended-day responsibility where necessary.
- Budget for additional days, overtime, or substitute coverage when appropriate.
- Cross-train a backup employee.
- Ensure reviewers and certifiers will be available.
- Avoid making one employee the only person who can complete a submission.
- Document secure remote-access and emergency procedures.
- Conduct a post-cycle review when a deadline repeatedly requires crisis work.