Skip to main content

The district data journey · Stage 1

Into the Data: Collecting and Gathering

Good data does not begin in a report. It begins at the moment a student, family member, teacher, or staff member records something the district needs to know.

Data enters a school district continuously—through enrollment, attendance, instruction, assessments, services, staffing, finance, transportation, meals, facilities, surveys, and many other daily activities.

Collection is more than data entry. It is where the district decides what a fact means, who is responsible for recording it, when it must be recorded, which system holds the authoritative record, and how accuracy will be confirmed.

  1. Define it
  2. Collect it
  3. Validate it
  4. Steward it

Where district data begins

Seeing collection as a districtwide activity helps departments find overlaps, gaps, and handoffs. Common sources fall into several connected families.

Students and learning

Enrollment, demographics, attendance, participation, courses, sections, teachers, grades, assessments, and academic progress.

Programs and student support

English learner information, special education plans and services, interventions, program participation, discipline, behavior, and school climate.

People and resources

Staff, credentials, assignments, vacancies, finance, purchasing, grants, contracts, facilities, and equipment.

District operations and community

Transportation, meals, emergency contacts, family communications, surveys, applications, consent records, and services delivered by community partners.

The collection question

Can the district trace an important data element from the person or event that created it, through each handoff, to the system and staff member responsible for maintaining it?

Data quality starts with people

The people closest to the source are often families and students, teachers and substitutes, school office staff, counselors and registrars, program coordinators, special education teams, human resources and business staff, administrators, technology teams, and service providers.

Each person sees only part of the data journey. Reliable collection depends on making responsibilities, definitions, timelines, and handoffs visible across those roles.

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, application question, or custom field, answer these questions together:

  • What decision, service, or requirement will this information support?
  • Is the information already collected somewhere else?
  • What does each field and allowed value mean?
  • Who owns the definition and approves changes?
  • Who enters, imports, or updates the information?
  • When must it be recorded and reviewed?
  • Which system is the authoritative source?
  • How will missing, late, or conflicting values be resolved?
  • Is the collection necessary, lawful, secure, and proportionate?
  • How long should the information be retained?

These decisions form the beginnings of a data dictionary, an ownership map, and a workable collection calendar. Even a simple shared record of the answers is better than relying on institutional memory.

Design a better collection process

Improvement does not always require a new system. Start with one high-value process and follow the information from its source to its final use.

  1. Map the path. Identify who provides the information, where it is entered, every system it passes through, and who uses it.
  2. Clarify the rules. Write plain-language definitions and instructions. Use required fields thoughtfully and controlled values when consistency matters.
  3. Prevent errors early. Add point-of-entry validation, duplicate-record checks, and clear ways to correct a mistake.
  4. Strengthen handoffs. Document timing and responsibility when information moves between schools, departments, vendors, or systems.
  5. Reconcile and learn. Compare connected systems regularly, review recurring errors, and give staff training that matches their actual responsibilities.

Keep the people providing data in view

Family- and student-facing forms should be accessible, mobile-friendly, understandable, and available in the languages the community needs. Collect only what the district can explain, protect, maintain, and use responsibly.

Warning signs

Collection problems often become visible long before a report or submission fails. Look for these signals:

What usually goes wrong?

  • Several departments collect the same information for different versions of the same purpose.
  • Staff rely on unofficial spreadsheets because the primary system or process does not meet the need.
  • Definitions vary by school, program, department, or vendor.
  • Information is recorded long after the event or entered only when a deadline approaches.
  • Responsibility changes without a documented handoff.
  • Errors are discovered only when a state submission, audit, or public request demands the data.
  • Critical process knowledge resides with one employee.
  • Staff collect information without knowing why it is needed or how it will be used.

Start small: choose one data element

Select one element that causes repeated corrections or confusion. Trace its full journey, name its owner, agree on its definition, document its authoritative source, and move one validation check closer to the point of entry.

The goal is not simply to collect more data. It is to create information that people can trust and use—without avoidable repair later.