1. Into the Data: Collecting and Gathering
Data enters a school district continuously. It arrives through enrollment forms, classroom attendance, assessments, staff records, program applications, service logs, discipline records, transportation systems, food services, special education processes, surveys, and dozens of other activities.
Collection is not merely data entry. It is the point at which the district decides what a fact means, who is responsible for recording it, when it must be recorded, and how its accuracy will be confirmed.
When information is incomplete or misunderstood at the point of entry, someone must repair it later—often during a deadline, audit, certification, emergency, or public records request.
Where district data begins
Organize collection sources into understandable families:
- Students and enrollment
- Attendance and participation
- Courses, sections, teachers, and grades
- Assessments and academic progress
- English learner information
- Special education plans and services
- Discipline, behavior, and school climate
- Programs, interventions, and supports
- Staff, credentials, assignments, and vacancies
- Finance, purchasing, grants, and contracts
- Transportation, meals, facilities, and operations
- Family communications and emergency contacts
- Surveys, forms, applications, and consent records
The people closest to the source
- Families and students
- Teachers and substitutes
- School office staff
- Counselors and registrars
- Program coordinators
- Special education teams
- Human resources and business staff
- Site and district administrators
- Technology and data-system staff
- Community partners and service providers
A key principle:
Data quality is created throughout the organization. It cannot be inspected into existence by the data office at the end of the process.
Define before collecting
Before creating another spreadsheet, form, or custom field, ask:
- What decision or requirement does this information support?
- Is the information already collected somewhere else?
- What does each value mean?
- Who owns the definition?
- Who enters or imports it?
- When must it be entered?
- Which system is the authoritative source?
- How will missing or conflicting values be resolved?
- Is collecting it necessary, lawful, and proportionate?
- How long should it be retained?
Designing better collection processes
Discuss practical improvements such as:
- Clear field definitions and plain-language instructions
- Required fields used thoughtfully
- Controlled values instead of inconsistent free text
- Validation at the point of entry
- Duplicate-record prevention
- Documented handoffs between departments
- Regular reconciliation between systems
- Training tied to actual staff responsibilities
- Accessible, translated family-facing forms
- Privacy-conscious collection that avoids unnecessary data
Warning signs
Include a simple “What usually goes wrong?” section:
- The same information is collected by several departments.
- Staff use unofficial spreadsheets because the primary system is difficult to use.
- Definitions vary by school or program.
- Data is entered weeks after the event.
- Responsibility changes without a documented handoff.
- Errors are discovered only when a state submission fails.
- Important knowledge resides with one employee.
Staff collect information without knowing why it is