Guides

Running enrolment week without a queue

The enrolment-week queue is not a staffing problem. Almost everyone standing in it is missing one of two things — a usable photograph or a clean record — and both can be sorted weeks before anyone walks in. This is the plan we have settled on after twenty-five years of running intakes for New Zealand institutions.

The queue is a symptom, not the problem

Walk along an enrolment queue and ask people why they are in it. You will hear the same two answers, over and over: the system has no photograph of them fit to print, or it has no record for them — or two records, or a record with somebody else's details attached. The printer is almost never the constraint. Most of what happens at that counter is a data fix, performed one person at a time, in front of an audience.

A counter is the most expensive place there is to fix data. The person doing the fixing has a queue watching them, no time to check anything with anyone, and a live printer beside them ready to commit the mistake to plastic. The same fix done three weeks earlier is an email nobody remembers sending.

So the whole approach follows from one idea: anyone who arrives with a photograph and a record already in order does not need to queue at all — their card is printed before they arrive. The queue is only for genuine exceptions, and a queue of exceptions is short.

The timeline

Plan backwards from card-in-hand

Fix the finish line — a card in every hand on day one — and work backwards. The dates below are the latest we would leave each step.

  1. Four weeks out — load the roll. Import cardholders from your student management system or directory. Do it this early because the import is what surfaces the problems: duplicates, blank names, half-finished enrolments. Four weeks gives you time to fix them at the source.
  2. Three weeks out — invite photographs. Email everyone a link. They upload from a phone, and automated screening rejects the unusable shots immediately, with a reason, so people can retry while there is still time.
  3. One week out — chase the gaps. By now you have a precise list of who is still missing a photograph or a complete record. Chase that list, not the whole intake.
  4. The week before — print the bulk run. Not the morning of. Print, sort and box the cards ready to hand out, with time in hand for a ribbon change or a fault.
  5. Enrolment week — exceptions only. Cards are handed out on arrival. The counter deals with the handful of genuine walk-ups.

Photographs before arrival

Most of the queue is photographs, so this is where the leverage is. Invite people by email with a personal upload link — a phone camera in daylight produces a perfectly printable photo. The point of automated screening is not to be fussy; it is to reject the unusable ones on the spot with a plain reason — too dark, face too small, sunglasses on — while the person still has weeks to try again. A rejection at the counter is a queue. A rejection three weeks out is a second attempt the same afternoon.

The rules worth enforcing are the ICAO 9303 ones — the passport-photo standard, which exists because it is what keeps a face recognisable on a small printed card. We have written them up in plain language in our guide to the photo rules.

One record per person

A card is only as good as the record behind it. Feed the roll from the system that owns it — your SMS or directory — rather than from a spreadsheet fork that starts drifting the day it is exported. Then let the import do its job: it is exactly where duplicates, blank preferred names and incomplete enrolments should surface, while each one is a five-minute fix in the source system.

Every record you resolve four weeks out is a person who never stands at your counter in week one. That trade — minutes at import against queue-time on day one — is the entire economics of this plan.

Capacity

Do the printing arithmetic honestly

A retransfer card printer produces roughly 60–120 single-sided cards an hour, depending on the model, and printing both sides costs you more again. Take the low number, not the brochure number. Three thousand cards at eighty an hour is nearly forty hours of printing — a week of steady running for one machine, before loading, cleaning and the odd jam. That arithmetic is why the bulk run happens the week before, and never the morning of day one.

Consumables are part of the same sum. A ribbon prints a fixed number of cards, so count your ribbon panels against the size of the run before you release it — running out halfway through is an operational failure, not a surprise.

  • Print the bulk run the week before. Enrolment week is for exceptions, not production.
  • Count ribbon panels against the run, and keep a spare ribbon in the room.
  • Keep a cleaning kit in the room and use it on schedule — most print-quality faults are dust.
Day one

The day-of playbook

If the weeks before went to plan, enrolment week itself is calm. Three roles cover it.

A short counter, for walk-ups only

Counter mode issues or replaces one card while the person waits — the late enrolment, the lost card, the name that changed yesterday. It is for genuine exceptions, not for working through the intake.

One person on data fixes

Somebody with access to the source system, seated away from the counter, fixing the record properly so the card prints right the first time. The counter refers to them; they do not hold the queue.

Spoils accounted for

Misprints happen. Mark the card spoiled and reprint through the same path, so the count of cards printed matches the count of cards issued and nothing goes missing quietly.

Checklist

The enrolment-week checklist

  • Roll imported from the SMS or directory four weeks out; duplicates and blanks fixed at the source
  • Photo invitations emailed three weeks out, with automated screening rejecting unusable shots with a reason
  • Gap list — missing photographs, incomplete records — chased one week out
  • Bulk run printed, sorted and boxed before day one
  • Spare ribbon and a cleaning kit in the print room
  • Counter mode tested end to end with one live card
  • One named person on data fixes, away from the counter
  • Spoiled cards recorded and reprinted, not quietly binned

Where CardOffice fits

Everything above can be run on determination and spreadsheets — we know, because we did it that way for years. CardOffice exists to make it the default. Cardholder management loads the roll from Entra ID, Google Workspace, your SMS database or a spreadsheet, surfaces duplicates and gaps at import, and handles the photo invitations, phone uploads and ICAO 9303 screening. Card printing runs the bulk batch, tracks ribbon and cleaning, switches to counter mode for walk-ups and accounts for every spoil — or, if you would rather not own a printer that week, we print the run in our card room and courier it overnight.

Planning an intake?

Tell us your numbers and your dates and we will talk the plan through against your own systems — what to import from where, and whether to print the run yourself or have us print it. No obligation, and no sales script.

Book a consultation