An admissions officer receives an application for a learner who may already have attended the school. If staff create a second record before checking, attendance, academic history and reports could be split between two files.
That is a risk to test, not proof that a particular school or software has duplicate data. The safe review starts with a search, distinguishes a possible match from a confirmed one, and gives uncertain cases to an authorised registrar. The example below is fictional: it uses no real learner name, identifier or school history.
Search before creating another record
Find where the school first receives an application and who can search its existing learner records. Before creating a new entry, use the identifiers and source documents the school has approved for this purpose. Do not decide that two records belong to the same person from a name alone; names may be shared, spelled differently or entered in a different order.
Use the minimum information needed for the comparison. A search log can refer to a document type or verification reference without copying the document itself. Keep access to identifiable records within the school’s approved roles and processes.
The school should define its own matching rules before a demonstration. Which fields may be compared? What counts as a close match? Who can see the source document? Which role can approve a correction? If those decisions are unclear, pause the test and ask the school’s authorised owner to set them. The software should not silently turn a local policy question into an automatic identity decision.

Send a possible match to the authorised registrar before changing either record.
Separate a possible match from a confirmed match
Use three review outcomes so an uncertain case is not mistaken for a finding:
| Review outcome | What the admissions team does next |
|---|---|
| No candidate found | Record the search context and continue through the school’s normal admission process. |
| Possible match | Hold creation or correction at the agreed checkpoint and refer the case to an authorised registrar. |
| Confirmed match | Follow the school’s approved transfer, correction or merge process; record which record was retained and how the decision can be traced. |
| False match | Keep the learners’ records separate and record the reviewer’s decision so the same case is not needlessly reopened. |
These are management outcomes for the review log, not promised status labels in any product. The matching fields, confidence threshold and authority to change a record must come from the school’s process.

Keep source documents in the school-approved intake channel and limit extra copies while a registrar checks a possible match.
Test both the match and the correction path
A software demonstration should include more than a clean example where the same identifier appears twice. Give the team fictional test records and ask it to show:
- a record that clearly matches under the school’s approved rules;
- a similar name that belongs to a different learner;
- a partial match with a missing or inconsistent identifier;
- an authorised registrar reviewing the source evidence;
- a user without authority attempting to change or combine records;
- the school’s approved correction or transfer path, if a match is confirmed; and
- the original record references and decision history after that action.
Ask what the system flags, what a user must decide and what it will not decide. If the presenter cannot show the match rule, authority check or history, record that item as “not demonstrated”. Do not label it a product defect or a confirmed feature until the system owner has investigated it.
Keep a duplicate-review log
Use record references rather than learner names in the review log. Keep source documents in the school’s approved location; the log should note what was checked, not become an unapproved second copy of the student file.
| Log field | What to record |
|---|---|
| Candidate record references | The two or more records being compared |
| Matching fields checked | Only fields approved for the school’s review |
| Source document checked | Document type or verification reference, not an unnecessary copy |
| Review outcome | Possible match, confirmed match, no match or false match |
| Decision and next action | Hold, continue, refer, use the approved transfer path or correct under authority |
| Reviewer and date | The person who made the decision and when |
| Correction reference | The system or process reference for an approved change, if one occurred |
| Next owner | The person responsible for any unresolved case |
For example, a test record might show “ADM-041 / ADM-118; school-approved identifier agrees; source document checked; registrar review pending.” Those are fictional references, not learner records. Do not turn this example into a required matching rule or a national identifier standard.
Ask Academia Pro to show what happens to a learner’s history
Academia Pro’s public product page describes student records and says a learner transferring between Academia Pro schools keeps academic history. It does not describe duplicate warnings, matching criteria, registrar review permissions or merge history. Chwezi’s software services page is a general company overview, not proof of those specific behaviours.
Bring an approved fictional case to a product walkthrough. Ask the team to show a possible match, a false match and the authorised decision path. If a record is corrected or merged, ask to see which reference remains, what happens to linked attendance and academic history, who made the change and where the decision can be reviewed. Record what is standard, what needs configuration, what is manual and what remains unresolved.
If the system cannot demonstrate a traceable correction, agree on a controlled manual process before staff use it for real admissions. Do not assume that a record can be safely merged just because the product retains academic history during a transfer.
Sources and scope
- Academia Pro, School management software, accessed 31 October 2026. The public page describes student records and continuity of academic history when a learner transfers between Academia Pro schools. It does not establish duplicate detection or merge behaviour.
- Chwezi Core Systems, Software development and systems implementation, accessed 31 October 2026. General public service scope, not evidence of a particular identity-matching capability.
- The decision path, fictional references and duplicate-review log are editorial synthesis. Identifiers, admission procedures, data access and record-correction authority must be set by each school for its own country and operating context.
Common questions
- Does a matching name mean the applicant is already in the school system?
- No. Names can be shared, spelled differently or recorded in another order. Compare the school-approved identifiers and source documents, then have an authorised person decide whether the records refer to the same learner.
- Should staff merge records when software flags a possible duplicate?
- Not automatically. A warning identifies a case for review; it does not prove the records belong to one learner. Keep the records unchanged until the school has verified the match and the authorised correction path is clear.
- Does Academia Pro automatically detect or merge duplicate learners?
- Its public product page describes student records and continuity of academic history when a learner transfers between Academia Pro schools. It does not establish duplicate detection, matching rules or merge history. Ask the product team to demonstrate those cases.