Applicants whose academic documents were issued in a language other than the one the institution teaches in face a set of mechanical requirements that are easy to get wrong: the translation must be complete, the copy may need to be certified, and the name on every document must match. None of these is a judgement about the applicant’s ability; they are checks that the office can read and trust the file. Getting them right is the difference between a file that moves and one that comes back for correction.
What a translation must satisfy
The translation requirement is about completeness and traceability, not about literary quality.
A complete translation covers every part of the document, not only the parts the applicant thinks matter. The transcript’s headings, the certificate’s formal wording, the grading scheme’s notes, and any stamps or annotations must all be rendered. A partial translation that omits a stamp or a footnote can leave the office unable to read a detail it needs.
The translator’s details should accompany the translation, where the institution requires them. The institution may ask for the translator’s name, qualifications, and contact, or for a statement that the translation is accurate. The applicant should supply what the institution’s rule names rather than assuming a format.
The translation is submitted with the original, not instead of it. The office reads the original as the authority and the translation as the aid; the applicant should keep the pair together so the office can check one against the other.
The translation should mirror the original’s structure, so the office can follow it line by line. Reformatting or summarising the content, even where the meaning is preserved, makes the office’s check harder and risks a return.
The applicant should use a translator acceptable to the institution where the rule names one, because an unacceptable translator’s work may be rejected regardless of accuracy.
Certified copy versus notarisation
These are different acts performed by different parties, and confusing them is a common reason documents are sent back.
A certified copy is a copy confirmed by an authorised person, often the issuing institution or a designated official, as a true copy of the original. The certifying step attests that the copy matches the original; it does not attest to the content’s meaning. The applicant obtains it from the body the institution recognises for this purpose.
Notarisation is a separate act performed by a notary public, attesting to the authenticity of a signature or document in a legal sense. It is not the same as a certified copy, and where the institution asks for a certified copy, a notarisation may not satisfy it, and vice versa.
The distinction matters because the institution’s rule names one or the other, and supplying the wrong one means the document is not in the required form. The applicant should read the rule precisely and obtain the exact act it names.
A certified translation is yet another act: the translation itself is certified as accurate, often by the translator or a recognised translation body. Where the institution requires certified translations, the applicant should confirm who may certify them, because the certifier is specified by the rule.
The applicant should not assume that notarising a translation makes it a certified copy, or that certifying a copy addresses a translation need. The three requirements, translation, certification, and notarisation, are independent and each is met on its own terms.
Name mismatches and how to reconcile them
Name differences across documents are among the most frequent causes of a returned file, and they are manageable with the right evidence.
Spelling variants, where the same name appears with different transliterations, are reconciled by a short statement from the issuing institution that the variants refer to one person, or by the civil document that shows the variant forms.
Name order, where one document puts the family name first and another last, is reconciled by a clear labelling of which is the family name on each document, so the office can align them. A consistent annotation across the file prevents the mismatch.
Former and current names, where a name changed through marriage or another event, are reconciled by the legal change document, such as a marriage or deed-poll record, showing the old and new names. The applicant presents this alongside the documents bearing each name.
Passport and academic-name differences, where the travel document and the certificate carry different forms of the name, are reconciled by the change document or an institutional letter, because the office must satisfy itself the files belong to one applicant.
The applicant should reconcile the mismatch with a document from the issuing institution or the relevant civil authority, not by annotating the certificate themselves, because a self-made note does not carry the weight the office needs.
Date formats and institution names
Two consistency points are small but repeatedly cause returns.
Date formats should be consistent and unambiguous across the file. A mix of day-month-year and month-day-year, or a numeric format that could be read either way, creates doubt about which date is which. The applicant should present dates in one clear format throughout, matching the institution’s preference where stated.
Institution names should be rendered consistently, especially where the name changed or where a transliteration varies. The applicant should use the name exactly as it appears on the certificate, and where a translation is needed, keep it consistent with the grading scheme and transcript so the office sees one institution, not several spellings.
Stamps and seals that carry dates or names should be translated and preserved, because they often carry the confirmation the office relies on. Omitting or loosely rendering them weakens the document.
The applicant should review the whole file for these consistencies before sending, because a single ambiguous date or name form can trigger a return that delays the whole application.
Why documents get returned
The technical reasons for a return are repetitive, and most are avoidable.
An incomplete translation, missing a stamp or note, forces the office to question whether the omitted part mattered. A complete translation prevents this.
The wrong certification act, a notarisation where a certified copy was required, puts the document in a form the rule does not accept. Reading the rule precisely prevents it.
A name mismatch without reconciliation leaves the office unable to confirm the files are one person’s. The change or institutional document resolves it.
Inconsistent dates or names across the file create doubt the office will not resolve by guessing. Consistent presentation removes it.
A translation submitted without the original leaves the office with no authority to check against. Keeping the pair together prevents the return.
The applicant who prepares the file against the institution’s stated requirements, rather than against a general habit, avoids most of these.
Gaps and how to close them
If a document requirement is not met, the responses follow the gap.
A missing or incomplete translation is closed by obtaining a complete translation from an acceptable translator, with the translator’s details as the rule requires.
A wrong certification act is closed by obtaining the exact act the institution names, whether certified copy or notarisation, from the recognised body.
A name mismatch is closed by the change document or institutional letter confirming the variants refer to one person.
An inconsistent date or name form is closed by re-presenting the documents in one clear, consistent format across the file.
An original not supplied with the translation is closed by sending the pair together, original and translation, so the office can verify.
What must be confirmed with the institution
The applicant should confirm the institution’s exact translation requirement, including who may translate and whether the translation must be certified, because the rule varies and guessing leads to rejection.
The applicant should confirm whether it requires certified copies or notarisation, and which body may perform the act, because the two are distinct and the wrong one fails.
The applicant should confirm how it wants name mismatches evidenced, so the right change or institutional document is obtained rather than a self-made note.
The applicant should confirm the date format and naming conventions it prefers, where stated, so the file is internally consistent.
The applicant should confirm the submission method and the contact for document queries, and should expect a reply within one business day from the admissions or records office.
Keeping the file internally consistent across submissions
A common reason for a returned file is not a single wrong document but an inconsistency between documents submitted to the same institution, or between the application and later verification. The applicant should treat the whole file as one set that must agree with itself. The name form, the institution name, and the date format used on the transcript, the certificate, the translation, and any letter should match throughout, because a mismatch in any pair raises the same doubt the office cannot resolve by guessing.
Where the applicant submits documents to several institutions, the consistency rule still holds within each submission, even if the translator or certifier differs between them. The applicant should keep a master record of the exact name spelling, the institution’s official name, and the date format used, and apply it to every document in every file. This discipline removes the small inconsistencies that trigger returns.
The applicant should also confirm, before sending, that the translation and the original say the same thing in the places that matter: the award title, the dates, the grades, and the issuing body. A translation that deviates even slightly from the original on these points forces the office to question which is correct. Reading the pair side by side before submission is the simplest check, and it prevents the most avoidable returns.
FAQ
Do I need a certified translation or just a translation? It depends on the institution’s rule. Some accept a plain translation; others require a certified translation from a named translator. Confirm the exact requirement rather than assuming.
Is a notarised copy the same as a certified copy? No. A certified copy is confirmed by an authorised person as a true copy of the original; notarisation is a separate legal act by a notary. Supply the exact act the institution names.
My name is spelled differently on my certificate and passport. What do I do? Provide the legal name-change document, such as a marriage or deed-poll record, or a letter from the institution confirming the variants refer to one person. Do not annotate the certificate yourself.
Can I translate my own documents? Only if the institution permits it; many require a translation from an acceptable translator, sometimes certified. Confirm who may translate before preparing the file.
Should I send the original with the translation? Yes. The original is the authority and the translation is the aid. Submit them as a pair so the office can verify one against the other.
Why was my document returned? Usually for a technical reason: incomplete translation, wrong certification act, unreconciled name mismatch, or inconsistent dates or names. Check the file against the institution’s stated requirements to find which.
This article is general planning information. It does not provide an official credential-equivalency, professional-registration, accreditation or admission decision. Verify current requirements directly with the relevant institution, regulator or professional body before acting.