The job bag on the feeder
It is a paper envelope with a printed sheet stapled to the front and handwritten notes added by three people. Stock: 150 silk. Somebody has written 'customer wants uncoated now' in pen near the bottom, and somebody else has crossed out the delivery date. The press operator reads the printed part, loads silk, and runs.
Two hours later, finishing picks it up, reads the handwritten note, and asks why it is on silk. Nobody is sure whether the change was confirmed or just discussed.
The spec gets copied too many times
A job's specification is typed at estimate, retyped or edited at order, printed on the job ticket, then amended by hand as the customer changes their mind. Every copy is a chance for a mistake, and the most recent change is the one most likely to live only in pen.
- Estimate, order and ticket are separate documents that can disagree.
- Changes after the ticket is printed are handwritten, if they are recorded at all.
- Different stations read different parts of the ticket, and nobody reads all of it.
- Operators cannot easily tell whether a note is confirmed or a question.
- There is no record of who changed the spec, or when.
What a wrong ticket costs
A job run on the wrong stock is a reprint, with the material, the press time and the finishing wasted, and the replacement squeezed into a schedule that was already full. Wrong finishing, wrong quantity or the wrong delivery address cost in the same way. Beyond the reprints, press operators and finishers lose time walking to the office to ask what a note means, and supervisors spend their day answering questions instead of running the floor.
Digital job tickets from one source
- The approved order in your MIS, or in the order system we build, becomes the single source of the specification. Nothing is retyped.
- Each station gets its own view on a screen or tablet: the press sees stock, colours, sheet size and quantity, finishing sees folds, lamination and binding, dispatch sees packing and addresses.
- Changes are made on the order by the account handler, not by pen. A change that lands after a station has started alerts that station and the supervisor.
- Operators confirm key details before starting, such as the stock actually loaded, by scanning the pallet label or picking from a list.
- Each station records completion, quantities and any spoilage, so the ticket becomes a history of the job.
- A printed ticket can still travel with the work if you want one, with a barcode that opens the live version.
| Station | What it sees | What it confirms |
|---|---|---|
| Press | Stock, colours, sheet size, quantity | Stock loaded, run complete |
| Finishing | Folds, trim, lamination, binding | Operations done, counts |
| Dispatch | Packing, addresses, delivery date | Packed and shipped |
| Office | Whole job and its history | Changes approved |
A calmer press floor
The spec an operator sees is the spec the customer approved, including the change made at eleven this morning. Questions go down because the answer is on the screen. When something does go wrong, the history shows where, which makes the fix about the process rather than about blame. Supervisors get a live picture of which jobs are where without walking the floor with a clipboard.
The office benefits as well. When a customer rings to add a second delivery address or knock the quantity down, the account handler changes the order once and can see which stations have already seen the old version. That is the conversation that used to happen by shouting across the floor, and it is the one most likely to be missed on a busy afternoon.
Is this happening on your floor?
- Job bags carry handwritten changes.
- You have run a job on the wrong stock or with the wrong finish.
- Operators walk to the office to check what a ticket means.
- Nobody can say who changed a spec after the ticket was printed.
- Your estimate, order and ticket do not always agree.