Key Takeaways
- Choose colours for defined roles and actual applications.
- Test combinations, not isolated swatches.
- Screen values do not guarantee an identical printed result.
- Document approved pairings, exceptions and ownership in the brand guidelines.
A useful brand palette is a set of decisions people can apply consistently, not simply a row of attractive swatches. It needs to work on the website, documents, social assets and physical materials the business actually uses. Start with those applications and the brand brief, then choose and test the colours.
This is the practical production companion to our colour psychology guide. That article explains why universal claims about colours and emotions are a weak foundation. Here the question is how to turn a direction into a readable, repeatable system that suppliers and team members can use.
1. List the first applications
Choose the first five places the palette must work. For one business that could be a website, proposal, vehicle, uniform and business card. For another it might be packaging, product labels, shelf displays, email and a shop sign. The list should reflect real expenditure, not imaginary future channels.
Note constraints beside each application. A small embroidered mark, a long text document and a large backlit screen need different treatment. Include existing materials you intend to retain so the new direction can be assessed alongside them.
Identify the person who will approve the final decision. Gather input from relevant people, but avoid an undefined vote in which every preference has equal authority and the brief disappears. The approver needs a clear set of criteria to apply.
2. Define colour roles
Start with the primary identity colour and the neutrals needed for backgrounds and text. Add an accent only where it has a clear purpose. A secondary palette may support diagrams, product ranges or campaigns, but should not become an unlimited collection of alternatives.
Write the roles in plain language. For example: main background, body text, primary action and supporting highlight. This makes the system usable by someone who did not attend the design presentation. It also helps identify a missing role before a developer invents one.
Keep functional states separate where appropriate. Errors, warnings, success messages and selection indicators need understandable behaviour. They should fit the visual system without being mistaken for ordinary decorative accents.
3. Compare complete directions
Apply each candidate palette to the same real content. Use a service-page section, a proposal cover and a small social asset rather than comparing swatches alone. Hold the wording and layout reasonably consistent so the discussion stays focused.
Check how the company name reads, where attention goes and whether the offer remains clear. A dramatic background may work for a campaign but become tiring across a long document. A pale accent may look elegant at presentation size while disappearing in small text.
Record the reason for accepting or rejecting each direction. “The action is hard to distinguish on mobile” is actionable. “It does not feel right” needs further explanation. The decision should survive beyond the designer's verbal presentation.
4. Build a contrast matrix
List approved foreground and background pairs. Check body text, headings, links, button labels and important states at their intended sizes. The W3C minimum-contrast guidance gives the text requirements; do not assume that any two brand colours are suitable together.
Also review non-text contrast for relevant interface components and graphics. These checks concern the actual role of an element, not merely its decorative appearance. A palette sheet should show which pairs are approved for which uses.
Do not round an almost-passing result into a pass. If a combination fails, alter the tone, change the role or provide a suitable alternative. Keep the original identity colour for decorative use if that is appropriate rather than forcing it into unreadable text.
5. Check meaning without relying on colour alone
Look at charts, selected controls, form errors and product variants. Ask whether someone can understand the information when colours are difficult to distinguish. Labels, icons, patterns and text can provide additional cues.
For example, a selected delivery option should have an identifiable state beyond a subtle background tint. An error needs an explanation, not only a red outline. A product swatch should have a name so the customer knows what they selected.
Test these decisions in the interface, not just the guidelines. A theoretically compliant palette can still be implemented poorly. Include the states in design handover and verify them again when the website is built.
6. Prepare screen and print specifications
Record digital values and the intended colour space with the assets. For print, work with the supplier on the appropriate specification, process and material. A hexadecimal value is useful for a website but is not a promise that every printer and substrate will reproduce the same appearance.
Request proofs for important physical applications. Check the actual paper, finish, fabric or sign material where practical. Lighting and production method can affect the result, so a laptop preview is not sufficient approval for an expensive print run.
Keep approved proof references and note any production-specific alternative. A supplier should not have to guess which version is authoritative. If a metallic effect is important, distinguish a real production finish from a flat colour that only suggests it on screen.
7. Test difficult situations
Try the identity on photography, dark backgrounds and small formats. Check a monochrome document and a low-cost office print. Review a long heading and a dense table as well as a spacious cover page. These tests expose practical weaknesses early.
Decide where the identity needs a reversed or single-colour version. The logo durability guide covers reproduction constraints in more detail. A flexible system has deliberate variants; it does not rely on each supplier improvising a solution.
Use the same approach for social templates. A palette that works on one short headline may fail with a longer message or a busy photograph. Build enough flexibility to handle the business's real content while retaining a recognisable style.
8. Document the system with examples
Give the team a concise reference containing roles, values, approved pairings and examples. Include a few important mistakes to avoid, such as using an accent for body text or placing the logo on an unsuitable background. Explain exceptions rather than hiding them.
Connect the palette with typography, imagery and layout rules. The visual identity systems guide explains why these decisions need to work together. Separate files without usage guidance often produce inconsistent results even when every file is technically correct.
Name the owner of the guidelines and keep a version date. When a new application requires a change, update the reference rather than circulating an unexplained extra swatch. Retire obsolete assets from the normal working folder while retaining an appropriate archive.
A simple palette acceptance record
For each approved combination, record its role, the application checked and any restriction. Add the supplier proof reference for important physical materials and the person who approved it. Include an example with ordinary business content rather than only a styled cover. When a future application falls outside the tested set, mark it for review instead of assuming approval extends to every possible use. This small record makes the palette easier to maintain and keeps production decisions from being lost in email conversations.
A documented application example
The Cornwall Flooring and Home Co. identity shows one visual direction applied to signage, cards, social assets and clothing. The useful evidence is the connected delivery and the guidelines that support it. We do not infer a sales or recognition uplift from the palette.
For your own project, request the same practical breadth: show the identity where the business will use it and explain the production decisions. A smaller, well-tested system is more useful than a large palette that nobody knows how to apply.
Our brand identity design service develops the system, and brand guidelines make it usable after handover. Share your current assets and first applications to discuss a clear palette brief and approval process.
Frequently Asked Questions
How many colours should a brand palette contain?
There is no mandatory number. Start with the roles the business needs and add colours only when they serve a clear purpose. A small documented palette is usually easier to maintain than a large set of unexplained options.
Can every brand colour be used for text?
No. Suitability depends on the foreground and background combination, text size and role. Record approved pairings and alternatives instead of assuming that every colour in the identity works in every context.
Will the same colour code look identical in print?
Not necessarily. Production method, colour management, material and finish matter. Agree specifications with the supplier and approve suitable proofs for important applications rather than relying only on a screen preview.
Should the website and printed materials match exactly?
They should feel like the same identity, but may need deliberate production-specific values or variants. Document those choices so differences are controlled rather than accidental.
What should we receive at handover?
Usable assets, colour roles and values, approved combinations, production notes, examples and a clear guideline owner. Include the decisions needed for future suppliers to reproduce the identity consistently.
