Queue management is one of those things that looks trivial until you have twenty people waiting and a colour job sitting in front of nine photocopies. The problem is rarely that people are slow. It is that nobody decided, in advance, what order things should go in — so every decision is made under pressure by whoever is nearest the machine. This guide is a set of rules you can write on a wall and a routine that keeps the counter moving.
Why queues fail
A queue is not a list. It is a set of rules about what happens next. When those rules are not written down, every decision becomes a judgement call made in a hurry, and the person making it is usually also serving a customer.
- Everything is urgent. If every job can jump the queue, the queue has no meaning and customers stop trusting any order you give them.
- The big job blocks the small ones. A 300-page colour print started ahead of nine single-page photocopies feels to the waiting customers like you do not respect their time.
- Waiting on the customer is not the same as first in. Someone who is standing right there and has a one-page job should not be behind someone who left twenty minutes ago.
- Reprints are started as new jobs. The specification is lost, and the second attempt is often wrong too.
The most common queue failure is a single colour job started in the middle of a stack of black-and-white work. It blocks everything, and the fix costs nothing: separate the queues.
The four rules
Write these down. They are not complicated, and they are not negotiable in the moment.
| Rule | What it means | Why |
|---|
| One rule, in writing | The order is decided before the day starts, not during the rush | Judgement calls made under pressure are inconsistent, and customers notice |
| Small and waiting beats large and waiting | A customer standing at the counter with a one-page job goes before someone who left | Perceived fairness is about people, not pages |
| Colour never blocks monochrome | Separate queues or separate machines | A colour job takes five times as long per page and holds the machine |
| A reprint is the same job, not a new one | Restore it rather than starting again | It keeps the original specification and it keeps the customer informed |
Setting up the queue
- Order by arrival. Every counter should be able to answer "how many jobs ahead of me" with a number.
- Mark jobs that are urgent. A visible flag beats a verbal instruction that the next person on the counter cannot hear.
- Mark jobs where the customer is waiting. Different from urgent — they are standing there.
- Move waiting-on-the-customer jobs to the front as they arrive, and do not let them accumulate.
- Keep bulk jobs in their own lane. A coaching institute order is not competing with a passer-by for the next twenty minutes.
A daily routine that keeps it clear
The queue self-manages until it does not. These five habits prevent most of the decay.
- Start of day: clear yesterday's completed jobs and check for anything a customer collected but did not confirm.
- Every hour: look at the pending list and ask whether anything has been waiting too long for a reason that is not capacity — usually a missing specification or a file that will not open.
- Before starting a long job: tell the customer how long it will take and give them a way to know when it is ready. A customer told "about twenty minutes" is far less likely to ask than one who was never told anything.
- End of day: clear the queue completely, and check for jobs that were never collected. These are your abandoned orders, and they are a measurable loss.
- Weekly: count reprints and abandoned jobs. Both should be falling. If they are not, the specification is not being captured properly.
That end-of-day step is the one most counters skip, and it is where the real data is. A queue you never clear is a queue you never learn anything from, and abandoned jobs are pure loss that never appears anywhere on the books.
When the queue is genuinely too long
Sometimes a queue is long because there is more work than capacity, and no amount of ordering fixes that. The options are limited and worth knowing.
| Option | When it makes sense | The trade-off |
|---|
| Add a second machine | One machine is genuinely saturated in a specific window every day | Only after ruling out routing problems. An idle second machine is pure cost |
| Extend opening hours | Demand clusters at specific times rather than being spread | Only works if the extra hours are actually busy, and if the lease permits |
| Add a thermal printer | Small chits, admit cards and passes are blocking the main queue | Cheapest useful addition on most counters |
| Turn work away | Peak weeks where you cannot meet deadlines anyway | Hard to do and unpopular, but a missed deadline is worse than a refusal |
| Raise the minimum charge | Lots of tiny jobs that consume counter time | Plausible because the labour is nearly identical for a one-page and a ten-page job |
A counter that says "I cannot print 300 pages by tomorrow" keeps its reputation. A counter that accepts it and delivers at midnight has spent its own evening and will do it again next week.
What software helps with, and what it does not
Being clear about this prevents buying the wrong thing.
- Software helps: capturing the specification before the customer arrives, showing a position in the queue, separating job types, and letting a job be restored rather than re-entered.
- Software does not help: making a bad price good, creating customers, or making a 300-page job take less time. Those are pricing, marketing and equipment decisions.
- Software does not help if the rules are not written down. A system that offers perfect priority management is useless if nobody has decided what the priority is.
Common mistakes
- Sorting by document name rather than by arrival. Alphabetical order is not a queue, and customers will notice.
- Letting the loudest customer set the order. A demand does not become more urgent because it is repeated.
- Printing large jobs first because they are easy to start. They block everything, and the small jobs pile up behind them.
- Never telling anyone an estimate. Silence reads as being ignored.
- Auto-sending every job the moment it lands. Convenient for bulk work, and a jam then blocks the machine for everyone.
Where to go next
If the queue is long because files arrive with no specification attached, that is the channel problem rather than the workflow — our guide to ending the WhatsApp queue covers why the old arrangement produces exactly this symptom. For the setup side, our contactless counter guide covers capturing specifications at upload and training staff. And for the economics of a long queue, our guide to making a photocopy shop profitable explains why adding volume is not always the answer.