Skip Navigation

Appendix E—Data Governance Supplementary Materials

Sample Data Governance Committee Mission Statement, Goals, and Objectives

(Adapted with permission from Chatis Consulting)

Example Data Governance Committee Mission

The Data Governance Committee supports the _______ Department of Education’s mission of helping teachers teach and children learn by promoting the appropriate use of data to inform decisionmaking; and ensuring data quality, accountability, and timeliness.

Examples of Data Governance Committee Goals

  • Improve data quality.
  • Increase accountability for data accuracy.
  • Eliminate redundancy in data collection.
  • Improve understanding of data within the department and among districts.
  • Increase data use in program and policy decisions.
  • Improve capability and timeliness of data reporting.

Examples of Data Governance Committee Objectives

  • Identify the owner of every data element.
  • Define all data elements.
  • Document all data processes.
  • Standardize data processes from year to year.
  • Reduce manual manipulation of data.
  • Identify the official source of data for all external reporting.
  • Eliminate redundant data collections that are not the official source for external reporting.
  • Allow districts to review their data before they are reported externally.
  • Communicate all data decisions/changes to districts.
  • Reduce the collection of, and reliance on, aggregate data.
  • Increase the use of student-level data for external reporting.

Sample Data Stewards Working Group Guidelines

(Adapted with permission from Chatis Consulting)

Process for addressing critical data issues

  1. Identify the data steward responsible for the issue and its resolution (one person).
  2. Determine whether a small working group of relevant data stewards should be created to address the issue.
    • Does the issue directly affect the data quality or work of more than one program/ subject area in the organization?
    • Note: Even if a working group is formed, only one data steward should be accountable for the issue.
  3. Plan first meeting of the working group.
    • Clearly define (and document) the source of the problem—not the symptoms. This includes all aspects of the issue: communication (internal and external), definitions, technology, etc. A reporting problem is almost never just a reporting problem: its source is earlier in the data process. (Note: If the issue is complex, additional research and time could be require to fully identify it; this time spent at the beginning of the process is well worth it to fully understand what you are trying to address.)
    • Determine the goals of addressing the problem; what exactly does the group want to achieve? (These goals should be aligned with the Data Governance Committee's goals).
  4. Create a mini-project plan for addressing each aspect of the problem and for achieving the established goals.
    • Include main steps, including due dates and who must be involved in, or responsible for, each.
    • Assign action items at the end of each workgroup session, including responsible staff member and due date.
    • Determine whether any part of the issue is not within the purview of the Data Governance Committee. If so, the responsible data steward should bring the issue to the Data Governance Committee chair.
    • Provide monthly updates to the Data Governance Committee for inclusion on the critical-data issues log.
  5. Once a preliminary “business” solution has been developed (i.e., you know what you want to do), coordinate with technology staff to get their input and determine how it can be implemented.
  6. Document all decisions made and implemented solutions thoroughly, and save to a common online area accessible by all Data Governance Committee members.
  7. Communicate these decisions and implemented solutions to the Data Governance Committee, all applicable program areas, LEAs, and any other staff directly affected by the issue. Be especially clear if the solution requires certain staff members to change how they work.
  8. Retire the issue from the critical data issues log, celebrate! Then move on to the next issue.
Sample Critical Data Issues Log