Why legalisation order decides your timelines
Incorrect sequencing (translating before legalising, or mixing originals) triggers DataFlow/PSV addenda and regulator holds. A neat pack—legalised first, translated second, one colour PDF per document—keeps licensing and credentialing moving.
Apostille or consular? (plain English)
Apostille (Hague Convention countries): a single government stamp confirms authenticity for international use.
Consular legalisation (non-Hague routes): multi-step chain (your foreign ministry → destination embassy/consulate).
Rule of thumb: check your document’s country of issue. If it’s Hague, use Apostille; if not, use the consular chain.
Which documents typically need it (signals, not promises)
Education: degree + transcript (sometimes internship/attendance letters).
Registration: Good Standing / Certificate of Current Professional Status.
Civil status for family sponsorship: marriage and birth certificates.
Police clearance: often legalised; follow your visa track’s rule.
(Clinical letters of service/employer references are usually verified via DataFlow/PSV rather than legalised.)
The correct sequence (copy/paste)
Name hygiene first
Ensure every issuer account shows your passport-exact name (all middle names).
Legalise
Hague country → Apostille.
Non-Hague → foreign ministry + UAE/KSA/Qatar embassy (as applicable).
Sworn translation(after legalisation)
Into English or Arabic per pathway; attach translator credentials if asked.
Combine to one colour PDF per document
Order: Original → Apostille/attestations → Sworn translation.
File name:
Surname_Name_Degree_[University]_YYYY.pdf.
Map to the right portal bucket
DataFlow/PSV: degree under Education, Good Standing under Licence/Registration, civil docs under Visa/Sponsorship.
Track validity windows
Some items (Good Standing, police clearance) expire; diary refresh dates now.
Packaging that prevents holds
Scan at 300–400 dpi, in colour; seals and QR/verifier links must be readable.
Avoid photos of documents; use a flatbed scanner where possible.
Keep one PDF per item (do not merge different documents).
Add a one-line note in the portal if your issuer sends directly (e.g., NMC → DataFlow).
Common pitfalls—and calm fixes
Translated before legalised → redo translation after legalisation.
Name mismatch (missing middle names) → request reissue before legalisation.
Mixed PDFs (degree + transcript + marriage in one file) → split into one file per document.
Low-quality scans → rescan in colour; re-upload; add a note for the reviewer.
Wrong bucket in portal → move to the correct field; resubmit with a short clarifying line.
Quick role notes
Ready checklists
Before you start
Passport-exact name confirmed on university/regulator profiles
Hague status of document’s country checked
List of documents mapped to portal buckets (Education/Licence/PSV/Visa)
Legalise & translate
Apostille or consular chain completed
Sworn translation completed after legalisation
Colour scans checked for seals/QRs
Upload & track
One PDF per item; filenames clean
Buckets correct; short note added if issuer sent directly
Refresh dates diarised (GSC/police clearance)