Order statuses: building a clear workflow in a print shop
An order status says where a job stands right now and who owns the next step. A print shop should start with six to nine statuses, named so they answer the customer's question, such as "waiting for proof approval" or "in finishing", and give each status one owner and one next action.
Why do statuses matter in a print shop?
Every job in a print shop passes through several pairs of hands: whoever takes the request, whoever prepares the proof, whoever prints, whoever cuts and folds, and whoever hands it over. The customer sees none of this and asks the only question they care about: where is my order? If the answer lives in one person's head, every such call interrupts whoever holds the information, or ends with "let me check and call you back".
Clear statuses turn the answer into something anyone on the team can see in a second. They do a second thing that is less obvious: they show where jobs get stuck, because a job that sits for days in the same status is a job someone has forgotten.
Which statuses should you set up for a print job?
There is no single right set, because every print shop works a little differently. Here is an example of seven statuses for an ordinary job, which you can adapt. The owner column shows example roles; in a small shop it is sometimes the same person.
| Status | What it means | Owner | Next step |
|---|---|---|---|
| Quote | The customer asked for a price and the job is not yet approved | Whoever takes the enquiries | Send the quote, and follow up on the date you agreed |
| Waiting for proof approval | The quote was accepted and the proof went to the customer | Whoever prepares the proof | Get approval or corrections from the customer |
| Approved for print | The proof is approved and the files are ready | Whoever plans the work | Schedule the print run and check the materials are in stock |
| Printing | The job is on the press or in its queue | The press operator | Finish printing and pass it to finishing |
| Finishing | Cutting, folding, binding, lamination or packing | Whoever runs finishing | Check the result and mark the job ready |
| Ready for pickup or delivery | The job is packed and waiting for collection or a courier | Whoever hands jobs to customers | Arrange pickup or delivery and tell the customer |
| Delivered | The customer has the job | Whoever handed the job over | Make sure payment and the invoice are handled, then close |
A job waiting for files from the customer, or for material ordered from a supplier, needs a status of its own; otherwise it looks as if someone is working on it. Put it where it fits best in the sequence and name it after what you are waiting for, for example "waiting for customer files".
What rules of thumb keep statuses working?
- One status, one owner, one next action. If you cannot say who owns a job in that status and what they should do, the status is not defined well enough.
- Few statuses beat many. With fifteen statuses nobody knows which to pick, and updates stop. Six to nine are enough for most businesses, and you can add one when you see a real need.
- Give statuses names that answer what the customer asks. "Waiting for proof approval" and "ready for pickup" answer the question directly. Internal names like "stage 3" are understood only by whoever invented them.
- Avoid "in progress". It is the status everyone picks when they do not know what to write. It names no owner and no next step, so it hides exactly the jobs that are stuck.
- A status describes the state, not who is working. "Printing" is a status. "Danny is on it" is an owner. Record that separately.
- Update the status when the job moves. Not at the end of the day or the end of the week. A status that is updated late is a status you cannot rely on.
What do you do with a stuck order?
A stuck order is one that has not moved for several days for no known reason. Decide in advance what "several days" means for each status: a quote sitting for a week is a different matter from a proof waiting two days for approval. When you spot a stuck job, ask three questions:
- Who owns it now, and what is their next step?
- Are you waiting for the customer, a supplier or someone on the team?
- What has to happen today to get it moving, and if the answer is a call to the customer, who makes it?
If the job is waiting for the customer, call. One call today beats finding out a week from now that the deadline has passed.
What does a five-minute morning review look like?
The simplest way to keep order: five minutes every morning, before the work starts. Go through the open list in this order:
- Jobs due today or tomorrow: is each one in a status that fits the time left?
- Jobs that have not moved for several days: who owns them, and what will move them?
- Proofs waiting for the customer: is it time for a reminder?
- Jobs ready for pickup or delivery: does the customer know?
Five minutes like this save a lot of "where is my order?" calls, because most of the time you already know the answer before the customer asks.
How do you roll statuses out with a team?
- Sit down with the people who actually work on the jobs and write down the stages a job goes through, from the first request to handover. The statuses come from that list.
- Give each status an owner and a next step. If two people think they own the same status, or nobody owns it, fix it now.
- Start with the jobs that are open today, not with the archive. There is no need to type in old orders.
- Agree one rule everyone knows: whoever moves a job updates its status at that moment.
- After two weeks, check which status nobody uses and which one has become a parking lot for everything. Merge, split or rename.
Where do people usually trip up?
- Too many statuses, so everyone picks whatever they like.
- Updating from memory at the end of the day, so the status no longer reflects reality.
- A status with no owner: everyone sees it and nobody feels it is theirs.
- Never checking. Statuses nobody goes over turn within weeks into a list nobody trusts.
- Waiting for a perfect setup before starting. Begin with a simple set and fix it as you go.
Where does Dougri fit?
In Dougri for print shops the business defines its own statuses, from nine preset colours, and you can name them exactly as shown here. On Solo you can start from a ready template and adapt it. The order list shows each order's status, and orders that changed since you last looked are marked, so you can see what moved without asking. You can add tasks to an order, each with an owner and a due date, and whoever works on a task taps Start when they begin and Complete when they are done. From Team you can assign work across people. It works in the browser on a phone.
One thing to know: Dougri does not send customers automatic status messages. You send the update to the customer yourself, but this time you know what to say. You will find the plans and prices on the pricing page, and what the system does for a print shop on the print shop software page.