UNIFIED RECORDS
A person’s story.
Connected, with context.
Connect identity, enrollment, learning and operations with a shared record and clearly defined access.
List existing student, finance and learning records. Identify stable keys and the team accountable for each field.
START WITH THE QUESTION
Why does a simple change become a round of emails?
A student joins a new program. A guardian changes a phone number. A scholarship is approved. When every department holds its own copy, someone must reconcile the differences. A shared institutional record gives each update an owner and every connected team the context it needs.
Explore unified institutional records in practice.
Choose a perspective to see what changes.
One identity, a new academic chapter
An accepted applicant becomes an enrolled student without creating a second identity. Admissions history remains connected to the new academic record.
Academic and finance teams use the confirmed enrollment as their starting point.
- Learner
- Alex Morgan · ST-2048
- Program
- Year 9 · Science pathway
- Enrollment
- Confirmed for autumn term
- Record owner
- Registrar
WHAT MAKES IT USEFUL
Identity, enrollment, and relationships in one context.
Identity before duplication
Agree which identifier belongs to a person and which belongs to an application, enrollment or staff appointment. Review potential duplicates before merging histories.
Relationships that explain context
Connect guardians, teachers, programs, campuses and services to the person. A relationship has a purpose, a period of validity and an access boundary.
Changes with an accountable owner
Identify who can create, correct, approve and retire each record. A connected view is useful only when teams understand which information is authoritative.
FROM DISCUSSION TO DAILY WORK
Agree how a record becomes trustworthy.
- 1
Map the sources
List existing student, finance and learning records. Identify stable keys and the team accountable for each field.
- 2
Reconcile the identity
Resolve duplicates, missing relationships and conflicting values before import. Preserve source references for review.
- 3
Confirm the handover
Test enrollment, contact changes and progression with the people who own the receiving workflow.
Unified institutional recordsMap the sources → Confirm the handoverSEE HOW THE WORK CONNECTS
Unified institutional records
Why does a simple change become a round of emails?
- 01
Map the sources
List existing student, finance and learning records. Identify stable keys and the team accountable for each field.
- 02
Reconcile the identity
Resolve duplicates, missing relationships and conflicting values before import. Preserve source references for review.
- 03
Confirm the handover
Test enrollment, contact changes and progression with the people who own the receiving workflow.
Illustrative workflow · Shape the details around your institution.
CONFIGURE WITH INTENTION
Define record ownership and change authority.
- Institutional identifiers and duplicate review rules
- Program, campus and enrollment relationships
- Required fields, record ownership and amendment approvals
- Historical retention and export requirements
QUESTIONS TO RESOLVE
Questions about unified institutional records.
Use these questions to make the evaluation specific to your institution.
Does every department see the same information?
Departments share an identity and agreed context, while the information and actions available to each role remain limited by responsibility. A teacher’s classroom view and a finance officer’s account view serve different purposes.
What happens to records from our existing systems?
Migration begins with a source inventory and mapping exercise. Decide which historical records to import, which to retain in an archive and how reconciled totals or sample records will be accepted before cutover.
Can one person have more than one relationship?
That is an important scenario to review: a staff member may also be a guardian, and a learner may attend multiple programs. Model the relationships separately so that one role does not silently grant another role’s access.
YOUR INSTITUTION. YOUR CONTEXT.
Bring the record your teams keep recreating.
Start with a real workflow, the people involved and the outcome you need.