More Dates Than Anyone Counts
Ask someone what dates appear on a driver's license and you will hear two: date of birth and expiry. A card typically carries four or five, along with a small revision code and an audit reference that most holders have never consciously read.
None of these are decorative. Each records a specific event in the card's life, and reading them together is how a trained examiner decides whether the document in front of them is internally coherent. This guide walks through what each field records, where the revision marks hide, and which combinations do not make sense.
Issue Date Versus Expiry Date
The issue date records when this particular piece of plastic was produced, not when the person first became licensed. Those are different events, and conflating them is a common misreading. Somebody licensed at seventeen who replaced a lost card last month holds a card with a very recent issue date and a long driving history behind it.
Expiry is usually calculated from issue by a fixed term set in state law, commonly four, five, or eight years, and in many states it is pinned to the holder's birthday. That pinning is what produces the useful cross-check: if the expiry day and month do not match the date of birth in a state that aligns them, something is wrong. State-by-state terms are covered in driver's license expiration and renewal by state.
The Dates You Were Not Looking For
Beyond the obvious two, several other dates appear depending on jurisdiction.
- An original issue or first licensed date, recording when driving privileges began.
- Under-21 milestone dates, printed as the day the holder turns 18 and 21.
- A duplicate or revision date, showing when the current copy replaced a previous one.
- A card production date encoded in the barcode that need not match anything printed.
The milestone dates are the most visible of these, and their placement and wording vary considerably, as set out in under-21 markings and age lines on licenses.
Revision Marks and Design Generations
Somewhere on most cards, usually in tiny type near an edge or tucked into the artwork, sits a revision code identifying which design generation the card belongs to. It might be a two-character year code, a letter, or a short alphanumeric string.
Its purpose is administrative: it tells the issuer and any examiner which specification the card was produced against. That matters because states redesign every several years, so multiple valid designs circulate at once, and knowing which specification applies determines which security features should be present. A card whose revision mark and feature set disagree is a card worth a second look.
Audit Numbers and Inventory References
The audit number, sometimes called an inventory control number, is a serial identifying the physical blank rather than the person. It is assigned to card stock as it moves through production, and it links a finished document back to a batch, a facility, and a time window.
It is the field most often confused with the document discriminator, which is a different thing entirely: the discriminator identifies a record in the issuing database, while the audit number identifies a piece of plastic. The distinction is drawn out in what is the document discriminator on a license, and the numbering schemes themselves in inventory control numbers on ID cards.
How These Fields Cross-Check Each Other
Individually each date is unremarkable. Together they form a web of relationships that has to hold, and this is where careless documents come apart.
Expiry must follow issue by a term the state actually uses. The design generation implied by the revision mark must match the artwork and the feature set. The printed issue date should be consistent with the production data in the barcode. And the milestone dates must agree arithmetically with the date of birth. Any single mismatch is the kind of internal contradiction that a careful reader notices well before any equipment is involved.
Why Reading Them Is Worth the Effort
These fields reward attention precisely because they are boring. A forger concentrates on the portrait, the hologram, and the barcode, since those are what everyone talks about, and treats the small print as filler to be copied from whatever sample was to hand.
That is why a mismatched revision code or an impossible expiry term shows up so often, and why examiners are taught to read the quiet parts of a card first. The rest of the data on the front is decoded in the fake ID verification hub.
Frequently Asked Questions
What is the difference between the issue date and the original issue date?
The issue date is when this specific card was produced, including after a replacement or renewal. The original issue date records when driving privileges first began, so a long-standing driver can hold a card issued last week.
Where is the revision mark on a license?
Usually in very small type near a border, in a corner, or worked into the background artwork. It identifies which design generation the card was produced against, which in turn determines the features it should carry.
What are audit numbers used for?
They identify the physical card blank rather than the holder, linking a finished document back to a production batch and facility. That traceability is how issuers investigate stock that has gone missing.
Is the audit number the same as the document discriminator?
They are different. The discriminator points at a record in the issuing database, while the audit number points at a piece of card stock. Both are serials, but they answer separate questions.
Why would an expiry date look wrong?
Because most states set a fixed term from issue and many align expiry to the holder's birthday. An interval the state does not use, or a day and month that disagree with the date of birth, is an internal contradiction.
Do these dates appear in the barcode too?
Issue and expiry generally do, and some jurisdictions add production data that is not printed anywhere on the front. Comparing the printed dates against the encoded ones is a routine consistency check.