How to prevent duplicate student records

Duplicates are how board entries, fee balances, and attendance percentages quietly rot.

Duplicates are how board entries, fee balances, and attendance percentages quietly rot. Do this against the calendar you will go live on, not a generic weekday grid.

named fee heads families can see on a receipt Named facts: working days, one student record, publish gates. Named owners still have to keep the holiday master, the roster, and the family view aligned in this place, because a brochure paragraph will not survive the first mid-year joiner or the first board week.

Marketing CRM names that never match the register.
Deleting history to “clean” a duplicate.
named fee heads families can see on a receipt Named facts: working days, one student record, publish gates.

Search before create

Name, guardian, previous admission number.

If you skip this step, the first parent receipt or the first exam week will rewrite the process in a corridor.

Duplicates are how board entries, fee balances, and attendance percentages quietly rot. Named owners still have to keep the holiday master, the roster, and the family view aligned in this place, because a brochure paragraph will not survive the first mid-year joiner or the first board week.

Name, guardian, previous admission number.
Schoolyi keeps a student profile across years. Merge policy stays a named school owner.
Named facts: working days, one student record, publish gates.

Transfers are not new children

Joining date on the existing profile when it is the same person.

If you skip this step, the first parent receipt or the first exam week will rewrite the process in a corridor.

Joining date on the existing profile when it is the same person.
Schoolyi keeps a student profile across years. Merge policy stays a named school owner.
Named facts: working days, one student record, publish gates.

Named merge owner

Software should not auto-merge as a slogan.

If you skip this step, the first parent receipt or the first exam week will rewrite the process in a corridor.

Software should not auto-merge as a slogan.
Schoolyi keeps a student profile across years. Merge policy stays a named school owner.
Named facts: working days, one student record, publish gates.

Certificates from the live file

Or the TC will disagree with the register.

If you skip this step, the first parent receipt or the first exam week will rewrite the process in a corridor.

Or the TC will disagree with the register.
Schoolyi keeps a student profile across years. Merge policy stays a named school owner.
Named facts: working days, one student record, publish gates.

Where this usually breaks

Marketing CRM names that never match the register. Deleting history to “clean” a duplicate.

A second spreadsheet for the “real” list is the usual failure.

Schoolyi keeps a student profile across years. Merge policy stays a named school owner. Named owners still have to keep the holiday master, the roster, and the family view aligned in this place, because a brochure paragraph will not survive the first mid-year joiner or the first board week.

Marketing CRM names that never match the register.
Deleting history to “clean” a duplicate.
Schoolyi keeps a student profile across years. Merge policy stays a named school owner.

How Schoolyi fits

Schoolyi keeps a student profile across years. Merge policy stays a named school owner.

Open /features/people after you can describe the awkward case. This page is a playbook, not a feature grid. Named facts: working days, one student record, publish gates.

No. A person decides. Named owners still have to keep the holiday master, the roster, and the family view aligned in this place, because a brochure paragraph will not survive the first mid-year joiner or the first board week.

Playbook: /how-to/prevent-duplicate-students
Product: /features/people
Book a demo with your awkward case, not a slide deck

Questions

Auto-merge? No. A person decides.

Re-admissions? Usually the same profile with a new joining date.

Twins? Two records, linked family. Do not collapse them. Named facts: working days, one student record, publish gates. Named owners still have to keep the holiday master, the roster, and the family view aligned in this place, because a brochure paragraph will not survive the first mid-year joiner or the first board week.

Auto-merge? No. A person decides.
Re-admissions? Usually the same profile with a new joining date.
Twins? Two records, linked family. Do not collapse them.

Bring this playbook to a demo

Write the awkward case before you watch slides: a mid-year joiner, a concession after invoicing, or a working-day exception. Schoolyi keeps a student profile across years. Merge policy stays a named school owner. Named facts: working days, one student record, publish gates. the academic calendar the school actually uses

Schoolyi is the operations system for that walkthrough — one student record, one academic calendar, publish gates on results, receipts that match finance. Score statutory filing and hardware as not met unless the deployment actually has them. named fee heads families can see on a receipt the boards the campus reports to

Duplicates are how board entries, fee balances, and attendance percentages quietly rot. Name, guardian, previous admission number. Named owners still have to keep the holiday master, the roster, and the family view aligned in this place, because a brochure paragraph will not survive the first mid-year joiner or the first board week.

Open /features/people
Book a demo with the awkward case
Named facts: working days, one student record, publish gates.

How to prevent duplicate student records