Company IDs and Employee Credentials

A company ID looks like a small thing until you count what depends on it. It gets a new hire past the guard on the first day, identifies your staff to clients and delivery drivers, stands in for a signature on gate logs and equipment releases, and — on the day someone resigns — is supposed to stop working. In most small and mid-sized companies here, those jobs are split across a designer's file, an outside printer and a spreadsheet nobody fully trusts. The gaps between the three are where mismatched cards, long waits for replacements, and still-valid IDs belonging to people who left last year quietly accumulate.

A company ID is a credential, not a souvenir

Treat the card as a credential and the requirements get clearer. A credential has to be issued deliberately to a specific person, trace back to a record that says it is current, be verifiable by someone who does not know the holder, and be revocable the moment the relationship ends. A printed rectangle with a photo on it satisfies only the first of those, and only on the day it is handed over.

That is why ID problems are rarely design problems. A company can have a beautiful card and still be unable to answer the question a client's security guard actually asks: is this person still employed here, today? Answering it requires the card to point back to a live record rather than stand on its own. ERPat's Company Tag module is built around that idea — the card is the visible end of an issuance record, and the record is what carries the authority. Templates, printing, revocation and verification then stop being four separate chores and become four stages of one lifecycle.

Designing the card once, then reusing it

Most ID inconsistency comes from the card being redrawn. A new batch goes to a different printer, someone rebuilds the layout from scratch, the logo shifts a few millimetres, and now three generations of cards are in circulation with no clean way to tell a current one from an old one at a glance.

Custom card templates in Company Tag make the layout a reusable asset instead. You define the design once — front and back, logo placement, which fields appear, and where the photo and QR code sit — and every card generated from it comes out identical. The variable parts are drawn from the employee's record rather than retyped, so a name spelled correctly in HR is spelled correctly on the card.

Templates are also the right place to decide how much personal information a card should carry. An ID needs enough to identify the holder and reach someone in an emergency; it does not need every detail your HR file holds. Under the Data Privacy Act, the safest card is the one showing only what its purpose requires — and a template makes that a decision you make once, not one you re-argue per card.

Issuance as a record, not an errand

The moment a card is handed over is the moment worth capturing. Issuance in Company Tag creates a record tied to the employee: which card they hold, when it was issued, and from which template. That sounds bureaucratic until the first time someone reports a lost ID, or a card surfaces in a drawer and nobody can say whose it was or whether it still counts.

A proper issuance record also makes replacements manageable. Cards get lost, damaged, or reissued after a legal name change or a transfer between branches. Each of those is a new issuance and, ideally, a revocation of the one before it, so a person's card history reads as a sequence rather than a pile.

It gives HR an answer to a question that comes up during audits and client accreditations, too: how many active IDs are in circulation, and does that number match headcount? If it does not, the difference is precisely the list of cards you need to chase.

Printing a whole batch in one pass

Printing IDs one at a time is fine when you hire one person a month. It stops being fine during an onboarding wave, a branch opening, or an annual reissue, when the work is dozens of near-identical cards and a queue at whoever owns the printer.

Batch printing generates the whole set from the same template in a single run: select the employees, generate, print. Because every card comes from one template and one data source, alignment and formatting stay consistent across the batch — no card is a slightly different one-off because it was made on a different afternoon by a different person.

The quieter benefit is scheduling. Batch generation lets ID production sit inside onboarding as a step you can plan around a start date, rather than an errand that gets remembered on the new hire's first morning, when it is already too late to do anything about it.

Revocation is the half most companies skip

Ask a company how it issues IDs and you will get a clear answer. Ask how it revokes them and you usually get a shrug and a hope that the guard remembers the face. Revocation is where the real exposure sits: a resigned employee's card, a lost ID that was never reported, a contractor's temporary card that outlived the contract.

Company Tag treats revocation as a first-class step in the same lifecycle as issuance. Marking a card revoked changes its status in the record, and that status is what any later check reads. It pairs naturally with the digital half of the credential: the Security module governs accounts, sessions and role-based access, so an exit means ending the session and disabling the account as well as invalidating the card. One departure, two credentials, both closed the same day.

What the QR code is actually for

A printed card can be copied. Laminate, a photo and a logo are not hard to reproduce, which is why a card checked only by eye proves very little — the person checking is really trusting that your design is difficult to fake.

QR verification changes what is being checked. Instead of judging the card, the verifier scans it and reads the status of the record behind it. A current card resolves as current; a revoked one does not. That is the difference between trusting an object and confirming a fact, and it is exactly why revocation discipline matters — a QR check is only as truthful as the record it reads.

It earns its keep where your people are not personally known: client sites, warehouse gates, deliveries, multi-tenant buildings, and any branch where the guard on duty rotates. It also gives you something concrete to show during client accreditation, which increasingly asks how you verify your own staff.

Getting the lifecycle in order

If you are starting from a drawer of assorted cards, do not start with the layout. Start by listing who currently holds an active ID and comparing that list against your active roster — the difference between the two is your actual problem. From there the sequence is straightforward: build the template once, issue against it so every card has a record behind it, print in batches that follow your hiring calendar, and put revocation on the clearance checklist beside the laptop and the company phone. The design is the easy part. The lifecycle around it is what makes a company ID mean anything.