DataFlow Report Statuses Explained: What 'In Progress', 'Positive', 'Negative' and 'Insufficient Information' Mean, Why Reports Get Flagged, and Exactly What to Do Next (2026)
Your DataFlow case page shows a status — but not what it means for your licence. This guide decodes every status and report outcome, explains the most common reasons a component comes back negative or 'unable to verify', shows how regulators treat each one, and gives the step-by-step process for re-verification, appeals and fixing the underlying document.
DataFlow is a black box for most candidates: you pay, you upload, and weeks later a status changes. Understanding what those statuses mean — and what a negative or insufficient component actually does to your application — saves weeks of panic and, often, the application itself. This complements our complete DataFlow guide, which covers documents and timelines.
Case statuses (while verification is running)
| Status | Meaning | What you should do |
|---|---|---|
| Application received / Payment confirmed | Case created; documents not yet reviewed | Nothing; check that every document uploaded correctly |
| Document review / Pending documents | DataFlow's intake team found something missing or unreadable | Respond within the deadline — cases stall here for weeks when candidates ignore the email |
| In progress / Verification in process | Letters sent to your university, council and employers | Warn each issuing body that a request is coming; this halves the wait |
| Awaiting source response | One or more institutions have not replied | Chase the institution yourself — the registrar's or HR office's reply is the bottleneck |
| Report issued / Completed | The report has been sent to the regulator | Read every component outcome, not just the headline |
Report outcomes (per document)
A DataFlow report is not a single pass or fail. Each component — degree, transcript, licence, each experience letter, good standing — receives its own outcome:
- Positive / Verified: the issuing body confirmed the document is genuine and the details match. This is what you want on every line.
- Negative / Discrepancy: the issuing body responded and said the document is not genuine, or that a material detail (dates, title, grade, registration number) does not match their records.
- Insufficient information / Unable to verify (UTV): DataFlow could not get a usable answer — the institution did not reply, no longer exists, has no records, or replied ambiguously. This is not a finding of fraud, but regulators still cannot accept the document until it is resolved.
- Not required / Not applicable: the regulator did not ask for that component.
Why components come back negative
- Name or date mismatch between the document and the institution's register — a maiden name, a transposed date of birth, an initial instead of a full middle name.
- Experience letter overstated — HR confirms employment but different dates, a different designation or part-time status. This is the single most common negative in nursing files.
- Registration lapsed — the council confirms you were registered but the licence is not current.
- Unaccredited or unrecognised institution — the programme ran but is not on the recognised list.
- Genuinely fraudulent document — a bought certificate. Regulators share these findings, and the ban is permanent.
Why components come back "insufficient"
- The hospital or university never answered DataFlow's letters or emails.
- The employer closed, merged or lost its records.
- The institution replied to the wrong address, or asked for a fee DataFlow does not pay.
- The document you uploaded was a photocopy of a photocopy — unreadable to the verifier.
What regulators do with each outcome
| Outcome | Typical regulator response |
|---|---|
| All positive | Application proceeds to eligibility / exam |
| Positive core documents, one experience letter insufficient | Often proceeds if the remaining experience still meets the threshold; otherwise a request for re-verification |
| Degree, licence or good standing insufficient | Application on hold until resolved |
| Any negative with a plausible clerical cause | Chance to submit a corrected document and re-verify |
| Negative confirmed as fraud | Rejection and, in most GCC regulators, a permanent ban |
What to do next: the fix process
- Download the full report from your DataFlow account and read the verifier's comment for each flagged component — it usually names the exact discrepancy.
- Go to the source. Contact the registrar or HR office, ask what they told DataFlow, and obtain a corrected letter or an official records extract that matches your document.
- Open a re-verification request with DataFlow (a fee applies per component) and upload the corrected document plus any explanation — for example a marriage certificate for a name change, or a gazette notification for a hospital rename.
- Inform the regulator through its portal that a re-verification is in progress; DHA (Sheryan), SCFHS (Mumaris+) and QCHP all allow a note on the application.
- If the institution no longer exists, ask DataFlow about alternative verification — a ministry of education record, a provincial council extract, or a notarised affidavit; acceptance is at the regulator's discretion.
Re-verification typically takes two to four weeks. Do not open a brand-new DataFlow case for the same regulator; it costs more and creates two conflicting reports.
Preventing flags before you apply
- Match every name, spelling and date to your passport before uploading; fix discrepancies with an affidavit first.
- Get experience letters issued by HR on letterhead in the accepted format (format guide), and keep the HR contact email that DataFlow will write to.
- Renew home registration and obtain a fresh good-standing certificate (guide) within the last six months.
- Tell each institution to expect a DataFlow request and to reply from an official domain.
Broader rejection causes are in 10 reasons GCC applications get rejected.
Frequently asked questions
What does "insufficient information" mean on a DataFlow report?
The issuing institution did not provide a usable confirmation — it did not reply, had no records, or answered ambiguously. It is not a finding of fraud, but the regulator cannot accept the document until it is re-verified.
Can a negative DataFlow report be fixed?
Often, yes, when the cause is a clerical mismatch such as a name spelling, a date, or an experience letter with wrong dates. You obtain a corrected document from the source and request re-verification. A negative confirmed as fraud cannot be fixed.
How long does DataFlow re-verification take?
Usually two to four weeks per component once the corrected document is uploaded, depending on how quickly the institution responds.
Will one insufficient experience letter stop my licence?
Not necessarily. If your other verified experience still meets the regulator's threshold, most regulators proceed. If it does not, the application is held until the letter is re-verified.