Printing & Design / August 14, 2026
Colour Management Before the Press
Colour becomes manageable when the file, proof, substrate and output condition are named together.
01
A colour promise needs a condition
“Make it match the screen” is not a production condition. A brief should say what is being compared, on which surface and under which proof or output condition. ISO guidance treats colour data and printing conditions as part of the production conversation.
That precision is helpful to marketing teams because it turns a subjective review into a defined approval step.
02
Keep the approval trail short
One approved reference, one named condition and one person responsible for sign-off is usually clearer than a long chain of screenshots. Record the substrate and finish alongside the proof so a later reprint has a chance of being comparable.
Colour and condition questions decide how a facsimile reads as well: the plate-to-press reading of a printed map carries the same approval trail into reproduction work.
03
Define the colour condition
A brand colour is not a floating number that looks identical everywhere. The file, ink or toner, substrate, proof, viewing light and measurement condition all shape the result. Begin by naming the physical reference and the output condition the team will approve, then state which visual difference is acceptable when the same colour crosses several materials.
This step turns a vague request to match the screen into a production question. A screen emits light; paper reflects it. The approval needs a physical sample when the printed object, not the monitor, is what a customer or operator will see.
04
Compare proof types carefully
A contract proof is useful when its condition and relationship to the press output are defined. A calibrated soft proof can speed review and catch layout or colour-management errors, but it cannot show the exact touch, gloss or absorbency of the final stock. A press sheet shows the production route but can be expensive if the specification is still moving.
Choose the proof that answers the risk. Use a soft proof for early content and separation checks, a representative hard proof for colour decisions, and a press approval when the run, substrate or brand consequence justifies it. Calling every PDF a proof removes the distinction that makes approval useful.
05
Make approval reproducible
Attach a small approval record to the job: file version, stock, finish, proof condition, viewing light, date and named approver. Include a neutral area, a brand colour and a photographic or flesh-tone area when relevant. Keep the reference with the production files so a reprint is compared with the same evidence rather than a remembered screen.
A retail team might approve a deep blue on coated stock, then need the same identity on an uncoated event card and a vinyl sign. The right response is not to force one appearance everywhere. Define the priority, create a controlled adaptation and record which physical sample governs each use.
06
Find the approval errors
The classic error is reviewing a print under a warm office lamp while comparing it to a cool display. Another is changing the stock after sign-off without reopening the colour decision. Unmanaged conversions, missing profiles, over-saturated images and a late transparency flattening can also make a correct intention leave the file in a different condition.
Do not solve disagreement by asking for more screenshots. Trace the file, proof, substrate and light. If the references do not share a condition, the team has a communication problem before it has a colour problem. A short, named approval trail is easier to correct than a long thread of opinions.
07
Know what standards cannot decide
ISO/TC 130 guidance helps describe printing conditions and colour communication, but it does not choose a brand priority, a local paper, a particular device or an acceptable business trade-off. Inks, screens, batch variation and viewing environments still create limits. Confirm current profiles and tolerances with the printer responsible for the output.
The source note for this article points to ISO/TC 130 guidance and the Printroom's editorial synthesis. The method is deliberately cautious: a standard supports the condition, while the signed sample and the use case decide what the business should accept.
Source trail
ISO/TC 130 guidance; editorial synthesis. Read the editorial method for the difference between a standard, an archive observation and practical synthesis.