Colour printing: decide what the proof is actually proving

The screen is useful, but it is not the paper

A screen emits light. Printed colour is viewed through reflected light from ink or toner and the chosen material. Display brightness, room lighting and paper shade can all influence your judgement. A vibrant screen preview therefore cannot be treated as a contractual guarantee of a printed match.

For an everyday document, the important question may be whether diagrams remain distinguishable. For a brand launch, a particular corporate colour may need a more controlled comparison. State which colours matter and why. A logo on uncoated stationery can look different from the same design on a glossy leaflet even when both have been produced correctly.

Three approvals people often confuse

A content proof checks wording, placement and page order. A colour-managed proof can represent a specified printing condition when made and assessed appropriately. A production sample shows the real combination of process, material and finish for that job. Ask which one you are seeing and what approval is being requested.

A PDF viewed on an ordinary phone is suitable for checking a date or telephone number. It is a poor basis for a precise colour judgement. If the brand owner requires a defined tolerance, reference or physical sample, agree it before production. Do not introduce a new colour expectation after approving the order.

RGB and CMYK need a route, not a slogan

RGB artwork is not automatically unusable for printing, and selecting CMYK does not automatically make a file correct. The profiles, output intent, process and supplier's workflow determine the right conversion. Adobe's PDF export guidance describes how those settings are handled. Ask for the appropriate file requirements instead of converting everything to a random profile.

Photographs, vector logos and small black text can need different treatment. Avoid an unsupported blanket instruction to flatten every layer or rasterise all text. Retain useful vector detail where the workflow accepts it. Check transparency, spot colours, overprinting and image resolution with the production team if the artwork uses them.

Make the comparison repeatable

Keep an approved physical reference and identify the material it was printed on. Compare samples in consistent lighting; a warm restaurant interior and a cool office window can lead to different impressions. Finishes can also change perceived colour and contrast. A laminate or varnish should be part of the sample discussion.

For a Warrington organisation ordering stationery, a brochure and a sign, list the different outputs together. Decide where visual consistency is essential and where a practical match is acceptable. Record the agreed specification for repeat orders. “More blue than last time” is harder to act on than a labelled reference and a clear explanation of what changed.

Agree what happens when the reference cannot be matched

A colour reference may sit outside what a particular process and material can reproduce. The sensible response is to discuss an achievable target or a different route before approval. Do not request an absolute match to an unusually bright screen colour without a physical reference and an assessment of the available gamut.

Keep numerical measurements in context. A tolerance is meaningful only with a defined reference, measurement condition and acceptance method. A generic statement about colour accuracy does not establish those details. If the order has a formal brand requirement, involve the person authorised to interpret it and agree how a disagreement will be resolved.

For ordinary business documents, simpler checks can be appropriate. Important charts should remain distinguishable; photographs should serve the purpose; small black text should be clear. Avoid paying for a critical-brand proof when the actual requirement is merely readable internal information. Equally, do not substitute a casual screen approval for a colour-controlled packaging or identity requirement. The level of control should follow the consequence of a mismatch.