What good ownership looks like for school management, ERP, and SIS

Ownership is more than administration

Ownership means that someone is accountable for the meaning, quality, access, use, and review of a record or workflow. It is not simply the person who enters data or answers the first support question.

Ask who will own the student record, permissions, family questions, fee corrections, training, and go-live decision. If one person owns everything, define a backup and separate operational work from approval before adding complexity.

Give each workflow a named owner

Select a workflow that causes repeated work or visible confusion. Map it from trigger to outcome, including the exception that consumes the most time. Name the person who can define the expected result, approve a change, and decide when an exception needs escalation.

• Admissions to enrollment
• Student records to class roster
• Fees to payment and receipt
• Attendance or assessment to family visibility

Make ownership visible in the data decision

Define the source of truth for students, guardians, classes, dates, fees, and staff. Profile a small sample for duplicates, missing values, stale contacts, and unclear ownership. The U.S. Department of Education data governance checklist treats quality, access, security, lifecycle, and disposal as connected responsibilities.

Do not use a shared spreadsheet as an easy answer if it broadens access or creates a new copy of sensitive data. GOV.UK procurement guidance recommends data protection by design and default, minimum necessary data, access control, security measures, and clear end-of-contract responsibilities.

Document the smallest acceptable migration. A school does not need to move every historical note on the first day if doing so increases risk or delays validation. It does need a clear rule for what remains in the old system, who may consult it, how long it is retained, and how the accountable owner checks the new record.

Make support and review part of ownership

Request task-based training, documentation for common exceptions, a support route, escalation expectations, and a plan for term-start pressure. Ask what the vendor needs from the school and what happens when the school cannot provide a specialist. Support should return useful context to the accountable owner instead of creating an untracked queue.

A workflow is ready when its owner can explain the expected result, correct an exception, show who may access it, communicate the change, and identify the condition that would pause the next phase. Review the ownership map whenever the school changes roles, campuses, or systems.