How to prevent duplicate student records

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

A second profile splits the fee balance, the attendance percentage, and the certificate. Search before you create. Do this against working days on one student record, with publish gates, not a generic weekday grid. Named facts: working days, one student record, publish gates. Name the owner before the first family sees a receipt.

No. A person decides.

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

Search before create

Name, guardian, previous admission number. Search name, guardian, and any previous admission number before creating a student. A marketing name that never matches the register becomes a duplicate on enrollment day.

For preventing duplicate student records, “Search before create” still has to survive a mid-year joiner and a working-day exception on one student record. Refuse this shortcut: Marketing CRM names that never match the register. Auto-merge? No. A person decides. Named facts: working days, one student record, publish gates.

“Search before create” for preventing duplicate student records fails when this is skipped: A second profile splits the fee balance, the attendance percentage, and the certificate. Search before you create.

Usually the same profile with a new joining date.

Search before create
Marketing CRM names that never match the register.
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. A transfer of the same person is a joining date on the existing profile, not a new child.

For preventing duplicate student records, “Transfers are not new children” still has to survive a mid-year joiner and a working-day exception on one student record. Refuse this shortcut: Deleting history to “clean” a duplicate. Re-admissions? Usually the same profile with a new joining date. Named facts: working days, one student record, publish gates.

“Transfers are not new children” for preventing duplicate student records fails when this is skipped: A second profile splits the fee balance, the attendance percentage, and the certificate. Search before you create.

Two records, linked family. Do not collapse them.

Transfers are not new children
Deleting history to “clean” a duplicate.
Named facts: working days, one student record, publish gates.

Named merge owner

Software should not auto-merge as a slogan. A named owner merges. Do not auto-merge, and do not delete history to make the list look clean.

For preventing duplicate student records, “Named merge owner” still has to survive a mid-year joiner and a working-day exception on one student record. Refuse this shortcut: Marketing CRM names that never match the register. Twins? Two records, linked family. Do not collapse them. Named facts: working days, one student record, publish gates.

“Named merge owner” for preventing duplicate student records fails when this is skipped: A second profile splits the fee balance, the attendance percentage, and the certificate. Search before you create.

No. A person decides.

Named merge owner
Marketing CRM names that never match the register.
Named facts: working days, one student record, publish gates.

Certificates from the live file

Or the TC will disagree with the register. Certificates and transfer documents come from the live file. If they disagree with the register, the duplicate already won.

For preventing duplicate student records, “Certificates from the live file” still has to survive a mid-year joiner and a working-day exception on one student record. Refuse this shortcut: Deleting history to “clean” a duplicate. Auto-merge? No. A person decides. Named facts: working days, one student record, publish gates.

“Certificates from the live file” for preventing duplicate student records fails when this is skipped: A second profile splits the fee balance, the attendance percentage, and the certificate. Search before you create.

Usually the same profile with a new joining date.

Certificates from the live file
Deleting history to “clean” a duplicate.
Named facts: working days, one student record, publish gates.

How this playbook changes for a real campus

preventing duplicate student records still starts from the holiday master, not a borrowed weekday grid. A second profile splits the fee balance, the attendance percentage, and the certificate. Search before you create.

Working days, one student record, and publish gates are the checks. Receipts have to match finance before families see a result.

Marketing CRM names that never match the register. Deleting history to “clean” a duplicate. Named facts: working days, one student record, publish gates.

Usually the same profile with a new joining date.

Search before create
Named facts: working days, one student record, publish gates.
the boards the campus reports to

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. Named facts: working days, one student record, publish gates.

preventing duplicate student records still fails when this is skipped: A second profile splits the fee balance, the attendance percentage, and the certificate. Search before you create. Saved marks stay drafts until the school publishes them.

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

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 for preventing duplicate student records. This page is a playbook, not a feature grid. Name the owner in the demo. Named facts: working days, one student record, publish gates.

That walkthrough still uses the holiday master the school will go live on and the fee heads families can see on a receipt.

No. A person decides.

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. Named facts: working days, one student record, publish gates.

A second profile splits the fee balance, the attendance percentage, and the certificate. Search before you create. Named facts: working days, one student record, publish gates. Ask these before the demo.

Twins? Two records, linked family. Do not collapse them. Named facts: working days, one student record, publish gates.

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

A second profile splits the fee balance, the attendance percentage, and the certificate. Search before you create. Schoolyi keeps a student profile across years. Merge policy stays a named school owner. Named facts: working days, one student record, publish gates. Book the demo with that owner in the room.

Score statutory filing and hardware as not met unless the deployment actually has them. Publish gates still decide what families see.

Search before create

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