Who Writes This Site: The Editorial Desk, and How We Verify
Every page here carries one byline: the editorial desk. No stock headshot, no “Senior Immigration Expert, 10+ years”. This page states who writes this site. It covers the first-hand experience behind the desk, and how a figure gets checked before it publishes. It also names the one commitment we have not met yet: a named reviewer.
Who writes this: the editorial desk, and what that means today
Cycle 1 is desk-attributed, on purpose. A small team of UAE residents writes and checks every page, and no individual human byline appears yet. This audience scans for fake credentials. A fabricated “immigration expert” with a stock photo would cost us the exact trust we are trying to earn.
We would rather show you an honest desk than an invented person. The audience already told us which one works. A dated timeline from a real resident earns trust; “10+ years on the market” and “thousands of happy clients” do not. Our attribution policy runs on one rule: no ghost bylines. That is also how articles are assigned. Each one goes to a desk writer and is read by a second person before it publishes.
The machine-readable byline matches the human one. Our JSON-LD names an Organization as the author, never a Person, because there is no real named person to attach yet. When named expert contributors are confirmed, this page splits into one page per author. Each gets a real profile block and real sameAs profiles. Not before that.
First-hand experience the desk actually has
The people writing hold the same documents the reader holds — Indian and Pakistani passports among the team, the same Emirates ID, the same residency renewals, the same VFS Global, TLScontact and BLS queues in Dubai and Abu Dhabi. The desk has filed its own Schengen, UK and US applications, and been refused too.
That shared history is why the site mirrors the profile block. The audience introduces itself the same way in every forum post. So do we, when we write about our own files.
Passports on the team: Indian and Pakistani, among others. UAE residency and tenure: years in the UAE with files going back to the 2000s. The queues: VFS Dubai and Abu Dhabi, biometrics done in person. Travel history: prior Schengen and UK applications, including at least one refusal — which is why the refusal pages exist at all.
We sat in those queues, so we know what the newer risk looks like. Consulates now flag recognizably AI-generated itineraries and cover letters — one applicant was told theirs “looked template-like”. We write for the person that pattern already burned. So we do not publish copy you could paste into an application.
How a page gets verified before it publishes
Primary source first, every time. We open the ICP or GDRFA service card, u.ae, or the consulate page for the exact product a page covers. We never lean on a blog that quotes it. Every figure then carries its own check date, not one page-level “last updated”. This review process is the same one behind the methodology block you see on the fees page.
| Step | What the desk does |
|---|---|
| Open the primary source. | The ICP or GDRFA card, u.ae, VFS or the consulate — for the exact product named, not the market word for it. |
| Date every figure. | Each number carries the day we checked it. News figures carry their publication date inline. |
| Print contradictions. | Where ICP, GDRFA and Amer disagree, we show both versions, both dates, and name who says what. We never average and never pick a winner silently. |
| Flag what we did not open. | If we took a figure from a source's published text without opening it ourselves, we say so and cite it by its exact card title. |
| Treat absence as a finding. | "We found no security deposit on any ICP or GDRFA card as of 20 July 2026" is a full answer, not a gap. |
| Publish a dated correction. | When a reader catches an error, we re-check the source and post a dated correction, crediting the reader if allowed. |
The full sourcing rules and the correction log sit on the editorial-policy page. If two of our numbers ever disagree, that is the block that tells you which one moved and when.
The named-reviewer commitment (and why it is not done yet)
No named human reviewer is attached in cycle 1, and we will not pretend otherwise. Visa content is YMYL. A wrong answer can cost a refusal, a fine, or a family’s residency. So it needs a named reviewer with real, checkable author credentials. We do not have one to name yet.
We will not invent one to fill the slot. In this market, readers actively hunt for fake authority. A fabricated expert is a terminal risk — worse than an honest gap. So the reviewer role stays open, and this paragraph is the visible IOU.
Here is what closes it. A licensed UAE advisor, or a resident who has been through these queues, agrees to attach a real name. That name comes with a real profile block and verifiable sameAs profiles. Then this page splits into per-author pages with Person schema. That reviewer’s name appears on every YMYL page they check. Until then the byline is the desk and the schema stays Organization. These are open contributor roles, stated as debt, not filled with fiction.
Are you that person — a licensed advisor, or a resident who wants to stand behind what you know? Or did you find a figure of ours already out of date? Write to us at contact. Who we are as a company sits on the about page; the terms we use are defined in the glossary.
We are not affiliated with the UAE Government, u.ae, ICP, GDRFA, MOFA or any Amer centre. We are a Dubai-based visa information publisher. We quote no price of our own, we take no case, and we process no applications. For an official decision on your visa, contact ICP, GDRFA or the relevant consulate directly.
Found a figure that's out of date, or a receipt that contradicts us?
WRITE TO US