Reviewing Diploma Name Change Evidence

Protocol status

A diploma name change is reviewable when the request, the authority for the change, the updated student record, and the credential file can be matched in order, with no gap between an approved name and the name actually printed.

This page describes a review design and its proposed controls. It does not report an executed sample, measured outcomes, or evidence that the controls improved performance.

Review protocol

Planned review sequence

1. Define the population from a fixed diploma order file for a declared conferral term. Include every candidate whose diploma name differs from the primary name on the student record, and record the count. Also record the total order count so the changed-name subset can be read in context. State the extract date, the vendor file version, and the source system.
2. Record the name printed on the diploma, the name on the student record, and the name the student confirmed. Keep these as separate fields. A difference between the printed name and the confirmed name is the primary exception; a difference between the confirmed name and the record may be authorized or may be an error.
3. Identify the policy basis for the change. Institutions differ on legal names, preferred names, accents, suffixes, transliterations, and the order of family and given names. Record the policy version and the category that applies. A change with no policy category cannot be reviewed for consistency.
4. Trace the request channel and the date. Record whether the student confirmed the name through the official portal, a signed form, or another approved method. A verbal request relayed by a staff member is weaker evidence and should be coded as such. The review should not treat an email signature as identity verification.
5. Check the authority for the change. A registrar may approve a correction, a legal name change may require documentation, and a preferred-name designation may follow a separate process. Record who approved the change, the date, and the scope. Do not infer approval from the fact that the file was updated.
6. Verify that the student record was updated before the diploma file. Record the effective date of the record change and the date the vendor file was produced. A file that leads the record creates a credential that the institution cannot reproduce from its own system. If the two dates are reversed, flag the case for review.
7. Examine the supporting evidence category without copying unnecessary identity documents. Record whether the required document was present, the reviewer, and the date. The review does not need to retain a copy of a marriage certificate or a court order in its working file; it needs to know that the authorized office reviewed it.
8. Test special-character handling. Sample names with accents, apostrophes, hyphens, suffixes, and non-Latin scripts, and compare the printed file to the approved name. A vendor system that strips a character can change a name even when the record is correct. Record the character-level difference and the vendor response.
9. Compare the vendor order file to the candidate list and the degree audit. Record duplicates, missing rows, candidates with a hold, and names that appear in two programs. A name can be correct and still be attached to the wrong credential if the row mapping is wrong. Sample at least one case with a hold and one with a late award.
10. Review the confirmation and reprint history. Record whether the student was asked to confirm the printed name before the order, the date of confirmation, and any later correction. A reprint caused by an institutional data error should be distinguished from one caused by a student change after the deadline.
11. Check the delivery and release record. A corrected name is not complete if the credential was already mailed under the old name or if a hold prevents release. Record the mailing date, the tracking reference, and any return. Do not disclose the name change in a general status message.
12. Test the vendor file join before sampling. Confirm that the candidate identifier, the degree-audit record, the name-change approval, and the order row share a reliable key. Record duplicate rows, missing candidates, and names that appear in two programs. Report the match rate. A name that is correct but attached to the wrong row is still a credential error.
13. Pilot the field list on one program or conferral group. Record the cases where the policy category was unclear, the approval could not be located, or the vendor had already produced the file. Use one field list for the full sample, amended only before the review starts. Keep the pilot separate so the final counts use one method.
14. Define decision rights for a disputed name or a late correction. Name who can approve a reprint, waive a fee, or change a credential after release. Record the authority and the date. The assistant can prepare the evidence and the vendor request, but should not decide whether a name request should be granted.
15. Review the student-facing confirmation message. Check whether it showed the exact name and delivery address that would be printed, the deadline to request a change, and the office to contact. A confirmation that only says your diploma is on file does not give the student a chance to catch an error.
16. Set the reporting audience and cadence. The registrar needs exception counts, the vendor needs a corrected file, and the privacy office needs to know what identity evidence was retained. Report aggregates and de-identified examples. Set a named follow-up owner and a date for the next credential review.
17. Check the name-policy change log for the period. If the rule for legal names, preferred names, or special characters changed, record the effective date and the candidates notified. A name that looks inconsistent under the current rule may have been correct when the file was produced. Report those cases separately.
18. Document the sample selection record. State the frame, whether the review is a census or a sample, and how replacements were handled. Keep the selection file. A review that examines only the names someone remembered will miss the quiet vendor truncation that affects many records.
19. Test the correction trail. For any credential that was reprinted or reissued, record the original name, the corrected name, the approver, the vendor request, and the date. Confirm that the student record and the vendor file agree after the correction. A reprint that leaves the source record unchanged will reproduce the error.
20. The review reports file integrity and does not decide whether a name change should be approved, whether an identity document is authentic, or whether a fee should be waived. Those decisions belong to the registrar and the policy owner. The review reports whether the approval and file integrity can be reconstructed.
21. Report the population, the changed-name subset, the policy categories, the record-to-file order, the special-character exceptions, and the limits. Retain the order file version, the policy references, and the review notes under the records schedule. The protocol measures documentation and file integrity; it does not decide whether a requested name should be approved or whether a legal document is authentic.

Operational implications

The printed name, the record name, and the student-confirmed name are three separate fields.

A policy category is needed before a name difference can be judged consistent or exceptional.

The request channel and identity evidence should be recorded, not inferred from a familiar sender.

Approval authority should be named; a file update is not proof that the right office approved it.

The student record should be updated before the diploma file is produced.

Supporting identity documents can be reviewed without being copied into the working file.

Special characters need a dedicated sample because vendor systems can silently alter them.

A correct name attached to the wrong credential row is still a credential error.

Confirmation and reprint history separate an institutional error from a late student change.

A name correction is incomplete while delivery or release is still blocked.

The review measures record and file integrity, not the merits of a name request.

The policy date is part of the evidence for whether a printed name was correct at the time.

Unmatched order rows should be reported rather than excluded from the credential count.