7 DataFlow PSV mistakes that delay GCC licences — and how to fix them

Every GCC regulator — DHA, DOH, MOHAP, SCFHS, QCHP, NHRA and MOH Oman — makes your licence conditional on a clean DataFlow Primary Source Verification report. DataFlow does not judge your documents; it writes to the university, registrar or employer that issued them and asks whether the record is genuine. That single dependency is why PSV is the most variable stage of the whole process, and why the same handful of mistakes keeps costing applicants a month or more.

If you are new to the step itself, start with our DataFlow PSV explainer. What follows is the failure list.

1. Your name is not identical across documents

This is the most common applicant-side rejection by a wide margin. A degree that reads “Mohammed A. Hassan”, a passport that reads “Mohamed Ahmed Hassan” and a registration certificate with the maiden name are three different people as far as a verifier is concerned.

Fix: pick your passport spelling as the master, list every variation that appears anywhere in your file, and obtain an affidavit or a “one and the same person” letter from the issuing institution for each mismatch before submitting. Retrofitting one afterwards costs a resubmission.

2. Incomplete or unreadable scans

Cropped edges, phone photos at an angle, missing reverse sides. Many certificates carry the registrar’s signature, seal or serial number on the back — scan only the front and the case stalls on day one.

Fix: flat-bed scan, colour, 300 dpi, every page including blank reverses, whole page inside the frame, one document per file.

3. The Letter of Authorisation is signed wrongly

The LOA gives DataFlow permission to contact your institutions. It must be signed exactly as your name appears in the documents being verified, and dated. A nickname, an initial, an undated form or a signature that does not match the passport all bounce the file back.

4. Nobody at the issuing institution answers

The single biggest cause of open-ended delay is silence at the other end — a university department that has moved, a hospital HR desk that ignores foreign verification emails, a registrar with no archive of pre-digital records.

Fix: before you submit, call each institution yourself, confirm which office handles verification requests and get a current email address and named contact. Warn them a request is coming. If an institution has closed or lost its archives, ask the national regulator for a substitute certification and raise it with DataFlow at submission rather than after the report opens.

5. Employment letters that do not say enough

An experience letter must show your exact job title, full-time or part-time status, department, and precise start and end dates on official letterhead with a verifiable signatory. “Worked with us for two years” is not verifiable — and experience gaps are a frequent cause of a downgraded professional title.

6. Submitting under the wrong regulator or category

DataFlow cases are opened against a specific regulator and profession. Choose the wrong package, wrong title (GP vs. specialist) or wrong emirate and the report may not be accepted by the authority you actually need — and PSV fees are non-refundable.

7. Letting the report expire

Reports and eligibility letters have validity windows. Finish PSV, then spend six months job-hunting, and you can find yourself paying for verification twice.

What each mistake typically costs

All figures are indicative and vary by profession, country of qualification and regulator. Exact fees are quoted by DataFlow at submission.

A pre-submission checklist

• Passport spelling fixed as the master name; every variation documented.
• All certificates scanned front and back, in colour, fully in frame.
• Experience letters carrying title, dates, hours and a named signatory.
• Verification contact confirmed by phone at each institution.
• Non-English documents translated by an approved legal translator.
• Regulator, profession and title selected to match the job you are actually taking.
• Good Standing Certificates requested early — they are often the slowest item.

If your report has already come back negative

Do not open a fresh case blindly. Read the report line by line and separate the documents that failed for administrative reasons — no response, missing archive, unclear scan — from anything flagged as inconsistent. The first group is usually recoverable through a dispute or a targeted re-verification. The second needs advice before you touch it, because verification outcomes are shared between GCC regulators and a careless resubmission can turn a fixable delay into a permanent refusal.

Our licensing team reviews document sets page by page against the specific regulator’s criteria before anything is filed, prepares the DataFlow submission, and handles disputes where a report comes back short. Fixed-fee packages start at US$499. If you would rather have a document set checked first, send it to us for a free eligibility review.

FAQ