Education operations stall when students and staff must ask for what the file already knows.

How it shows up

• Enrolment, documents, and exceptions live in different offices.
• Students email for status that a portal could have shown, if it were true.
• Staff re-enter the same person into the next system in the chain.
• A special program is run beside the SIS because the SIS almost fits.

Why it matters

Core systems were bought for records. The path from admissions to completion, including exceptions, was left to coordinators.

If nothing changes

• Administrative load grows with headcount even when teaching load does not.
• Students experience the institution as a series of closed doors.
• Exceptions, which are common, have no path.

When it is working

The student (or the file) carries status. Staff work exceptions. Standard records stay in the SIS. The path around them is designed.

Problems we commonly work on

• People keep asking for status because they can't see it
• Work held together by spreadsheets, email and memory
• The same information is entered more than once

Possible systems

• A case path for the programs that leak
• Honest self-service status
• Integration rather than a second student system

Signals worth watching

• Status emails per student
• Time to complete an exception
• Duplicate records across systems

Integrations

• SIS
• Document workflows
• Identity if it already exists

Roles this hits

• Sales and service
• Operations
• Owners and executives
• Technology
• Finance

Selected work

Comparable files are walked through in a working session. We do not invent percentages for the website.