Skip to main content

The district data journey · Stage 3

Beyond the Data: Reporting, Sharing, and Acting

Every report, file, dashboard, presentation, and notification turns internal records into information that another person or organization will rely on.

Data leaves operational systems in many forms: a CALPADS file, report card, LCAP table, dashboard, emergency contact list, board presentation, grant report, or response to a California Public Records Act request.

Each output carries obligations. It must be accurate enough for its purpose, understandable in context, accessible to its audience, reviewed for privacy and security, and approved or certified by the appropriate people.

  1. Prepare
  2. Review
  3. Release
  4. Respond

Many outputs, different obligations

Organizing outputs by purpose helps a district identify audiences, owners, review requirements, delivery schedules, and risks.

Students and families

Report cards, progress and attendance notices, assessment results, transcripts, eligibility communications, emergency notifications, portals, and student records.

Schools and district operations

Rosters, schedules, intervention lists, enrollment projections, staffing plans, budget monitoring, transportation and meal-service files, dashboards, and leadership reports.

State and federal accountability

CALPADS submissions and certifications, assessment files, civil rights and program reporting, special education reports, grants, fiscal reports, and accountability indicators.

Governance and public communication

LCAP metrics, School Accountability Report Cards, board materials, public dashboards and websites, research exchanges, and public-records responses.

Health, safety, and emergencies

Emergency contacts, mass-notification lists, reunification information, authorized health or accommodation information, and time-sensitive incident lists.

Partners and service providers

Approved data exchanges that support instruction, operations, evaluation, research, contracted services, or required reporting.

Match the process to the output

A file used during an emergency, an official state certification, and a public dashboard may begin with related data, but they require different timing, review, access, privacy, accessibility, and retention practices.

The output is not the source

Reports should be reproducible from authoritative records. A spreadsheet prepared for one deadline should not quietly become a new unofficial source system.

Before releasing or certifying an output, confirm:

  • Its purpose and intended audience
  • The authoritative source and responsible owner
  • The reporting population and time period
  • Inclusion, exclusion, calculation, and transformation rules
  • Suppression, confidentiality, and privacy requirements
  • Accessibility, format, and language needs
  • Required program, technical, leadership, or legal review
  • The version approved for release
  • The extraction date and, when relevant, refresh schedule
  • Where the final artifact and supporting documentation will be retained

Certification is a leadership act

A CALPADS certification or official public report should not be treated as a technical button click. Certification represents the district’s assertion that required records were submitted, known errors and warnings were reviewed, responsible program staff examined the results, and material discrepancies were resolved or documented.

A key principle: Technical staff can prepare and explain an output, but an authorized leader must understand and accept the representation made on behalf of the district.

Public-records responses

A request involving district data may require several people and systems. The work can include clarifying the request, identifying possible custodians, preserving responsive records, documenting searches, reviewing confidential information, applying authorized redactions, and producing records in a usable form.

Educational guidance—not legal advice

Public-records obligations are fact-specific. District staff should follow local procedures and coordinate with designated leadership or legal counsel when determining scope, exemptions, redactions, timing, and release.

Data teams should also avoid creating an ad hoc dataset that appears authoritative but changes definitions, combines unlike records, or removes context. When a new compilation is prepared, document its sources, logic, limitations, and review.

Emergency communication depends on data readiness

A mass-notification system is only as reliable as its source data and the process that keeps it current. Districts should regularly test:

  • Guardian and staff contact completeness
  • Preferred-language information
  • Student-to-household and release relationships
  • Integration schedules and failed transfers
  • Consent and opt-out handling
  • Message delivery failures and correction paths
  • Authorized access during an incident
  • Continuity during a power, network, or system outage

Testing should confirm more than whether a message can be sent. It should show whether the right message reaches the right people, in a form they can understand, when normal systems may be under stress.

Context makes an output responsible

A number rarely explains itself. Every public-facing report should help readers understand what is being measured, why it matters, who is included, the reporting period, and any important limitations.

  • Define the measure in plain language
  • Explain its purpose and relevance
  • Identify the population and reporting period
  • Describe exclusions, limitations, and uncertainty
  • Label results as preliminary or final
  • Use an accessible format and explain visual displays
  • Describe what the district is doing in response
  • Provide a way for readers to ask questions

A useful principle: Responsible reporting does more than publish a correct number. It gives people enough context to interpret the number fairly and understand what happens next.

Start small: trace one recurring output

Choose one report, file, dashboard, or notification. Document its audience, source, owner, business rules, review steps, privacy and accessibility checks, approval, release location, and retention. Then confirm that another person could reproduce it.

The goal is not simply to send data out. It is to create trustworthy information that people can understand, use responsibly, and act upon.