When Government Verification Becomes the Citizen’s Problem
John Snow’s passport renewal has been flagged — not because of anything he did, but because of how his father’s name is spelled.
His driving licence lists his father as “Johnny.” His previous passport, issued by the same passport authority, lists him as “Johnny Jonathon Snow.” Nothing about his father has changed. John hasn’t requested a correction, filed an affidavit, or claimed a new relationship. He has simply submitted two government-issued documents that describe the same person with different amounts of detail.
The passport office calls this a discrepancy. It isn’t. It’s a formatting difference — and it’s about to cost John a trip to a government office, a fresh set of documents, and weeks of waiting for a renewal that should have been routine.
This happens to people constantly, in every country with fragmented record-keeping. It’s worth asking why — and who should be responsible for fixing it.
The Citizen Doesn’t Design the Form
Consider something as basic as a name.
In some cultures, a full name traditionally includes the given name, the father’s name, and the family surname. Over generations, conventions shift. A child may go by only a given name and surname, while the father’s name continues to appear in certain records in its longer form.
Government forms compound this. One application asks for:
First Name + Middle Name + Last Name
Another asks for:
Surname + Given Name
A third provides only:
First Name + Last Name
Yet another has a separate field for the father’s name — but prints only part of it on the final card.
The citizen doesn’t design any of this. When a department issues an ID, it decides how its database stores the information and how the card displays it. The citizen has no say. Years later, when that same document is submitted elsewhere, the citizen is the one told: the names don’t match.
An administrative problem has just become a citizen’s problem.
A Difference in Presentation Is Not a Difference in Identity
Go back to John Snow. His father’s name is Johnny Snow — but Johnny’s own documents record his full name as Johnny Jonathon Snow. John’s driving licence, issued years ago, simply shortened this to “Johnny.”
Now John applies to renew his passport. His previous passport — issued by the very authority processing this renewal — already records his father’s name as Johnny Jonathon Snow.
John hasn’t requested any change. He hasn’t declared that his father acquired a new name. He has submitted a government document that displays the same information slightly differently than another government document does.
If the renewal process flags this as a discrepancy, the honest question is: what exactly has changed?
The person hasn’t changed. The father hasn’t changed. The relationship hasn’t changed. The information the passport authority already accepted hasn’t been altered by anyone. Only the presentation is different — and treating every presentational difference as a substantive one creates administrative work without making the record any more accurate.
Discrepancies Are Not the Same as Variations
A good verification system should be able to tell these apart:
Father: Johnny Snow
Father: Michael Snow
versus:
Father: Johnny
Father: Johnny Jonathon Snow
The first pair may point to two different people. The second is almost certainly one identity, recorded at two different levels of detail. The purpose of verification is to catch genuine risk — not to reject anything that isn’t character-for-character identical. Modern systems should be capable of making that distinction automatically.
Asked to Prove What the Government Already Knows
Here’s the deeper problem. The passport authority already accepted “Johnny Jonathon Snow” once, when it issued John’s previous passport. That record exists in their own system.
If that same detail is treated as requiring fresh verification on renewal — with no new reason to doubt it — John is being asked to prove, again, something the government itself already established.
Verification makes sense when there’s a reason to believe something has changed, or that earlier information was wrong. When neither is true, repeat verification is just procedural repetition dressed up as diligence.
The right question to ask, every time, is: what new fact makes this verification necessary? If the honest answer is “another government document used a different format,” the burden being placed on the citizen deserves a second look.
Databases That Don’t Talk to Each Other
Citizens experience “the government” as a single entity. In practice, it’s dozens of departments, each with its own database, built independently over decades: one for driving licences, one for passports, one for electoral rolls, one for property records, one for welfare records.
The same person can exist across these systems under several slightly different representations of the same identity. From the citizen’s chair, this is close to impossible to manage. No one can reasonably be expected to ensure that every government database uses identical spelling, ordering, abbreviations, and naming conventions for their family.
Get Meet Vekaria’s stories in your inbox
Join Medium for free to get updates from this writer.
If consistency across records matters, the responsibility for creating it should sit with the institutions running the databases — not with the individual caught between them.
The Burden Isn’t Evenly Distributed
For a department, asking for “one more document” looks like a small administrative step. For a citizen, it can mean:
- finding an old document
- obtaining a certified copy
- visiting another office
- scheduling an appointment
- travelling to a government centre
- taking time off work
- paying document or travel costs
- waiting for manual processing
- responding to objections
- submitting written explanations
- waiting weeks or months for something that should have taken minutes
That’s not the cost of photocopying a page. That’s the transaction cost of an ordinary life being put on hold. A mechanism that saves one government employee five minutes but costs thousands of citizens several hours each is not an efficient system — it just moves the cost somewhere less visible.
Fast-Track Services Make the Problem Obvious
The absurdity is sharpest when an application qualifies for expedited processing but gets diverted into manual review over a minor documentary variation. The citizen experiences this as punishment for something they didn’t cause.
They followed the rules. They submitted government-issued documents. They requested no change and concealed nothing. They simply ran into two records of the same fact, formatted differently by two different offices. The system then manufactures a discrepancy between its own records — and hands the cost of resolving it to the citizen. That’s the wrong direction of accountability.
Verification Should Be Risk-Based, Not Format-Based
The answer isn’t to eliminate verification. It’s to make it proportionate.
High-risk discrepancy: a genuinely different name, date of birth, parent, nationality, or other core identity attribute. This deserves scrutiny.
Low-risk variation: a different name order, a dropped middle name, an abbreviated parent’s name, punctuation, spacing, or transliteration differences. This should be resolved through automated matching against existing records or a simple declaration — not a lengthy manual process.
The Government Has Better Tools Than the Citizen Does
A citizen has a handful of documents in a folder. The government has databases, historical filings, prior applications, issuing-authority records, and the ability to cross-check between its own departments.
When two government documents look different, the state — not the individual — is in the better position to determine whether that difference means anything. Instead of saying:
“Your documents don’t match. Prove they refer to the same person.”
the system should be capable of asking itself:
“These documents differ in presentation. Do our own records show they refer to the same person?”
That question, asked internally instead of outsourced to the citizen, is the difference between a citizen-centric government and a document-centric bureaucracy.
Verify What Matters
Verification is valuable when it prevents fraud and protects the integrity of public records. It loses its legitimacy the moment the procedure becomes more important than the purpose behind it.
A citizen shouldn’t have to repeatedly prove that two government-issued documents describe the same person, simply because two departments chose different ways of recording the same information. An unchanged fact shouldn’t become a new problem just because it arrived on a different form. The goal is to establish identity — not to enforce typographical uniformity across every card the state has ever printed.
Government Should Own the Problem It Creates
If departments build different forms, different databases, and different display conventions, inconsistencies are inevitable. That’s a structural reality, not a citizen failure — and it shouldn’t automatically become the citizen’s burden to fix.
Citizens should absolutely be expected to provide truthful information and cooperate with legitimate checks. But they shouldn’t be made to repeatedly patch over fragmentation that exists entirely within the government’s own machinery.
Good governance isn’t only about catching fraud. It’s also about not manufacturing friction for the honest majority who never triggered a real risk in the first place. Every unnecessary verification step consumes someone’s time. Every avoidable document request creates another queue. Every discrepancy generated by the system’s own inconsistency turns a routine service into an ordeal.
The measure of an efficient government isn’t how many documents it can demand from its citizens. It’s how intelligently it uses the information it already has.
