Brand Standards
These brand standards define how ICO should appear across every touchpoint — website, decks, portals, proposals, and print. The goal is a brand that stays consistent, sharp, and unmistakably ICO.
The strategic core of the ICO brand
Overview
Brand position
Brand promise
Core belief
| Brand leaders | Need confidence that the program reflects the brand correctly and feels considered, elevated, and on-brand. |
|---|---|
| Operators | Need clarity, speed, consistency, and a partner who understands rollout, logistics, and long-term program management. |
| Ownership / procurement | Need a solution that is scalable, rational, and easier to manage without sacrificing quality or presentation. |
| Wearers | Need uniforms that feel right in the role, look professional, and support a better day-to-day experience on the job. |
| What ICO delivers | A better uniform experience through stronger product choices, clearer program logic, and more thoughtful brand execution. |
|---|---|
| How ICO is different | ICO combines creative authority and operational rigor in one partner. Most companies lean heavily toward one side. ICO has to do both. |
| What the client gets | A program that looks more intentional, feels easier to run, and performs more consistently over time. |
System over fragments
How ICO should sound
What it isn't: "We provide comprehensive end-to-end apparel solutions."
Short sentences. Clear meanings. No filler language used just to sound impressive. ICO should say what it does in plain terms, without hiding behind corporate language, abstractions, or unnecessary setup. If a sentence can be shorter, make it shorter.
What it isn't: "ICO tries to help brands find a better apparel solution."
State what ICO does without hedging. Do not use 'we try to', 'we aim to', or other language that weakens authority. ICO should sound assured because the business knows what it does well. Confidence here means clarity and conviction, not sales exaggeration.
What it isn't: "We make uniforms fun!"
ICO has personality without being playful. The tone can be dry, sharp, and slightly understated, but it should never become jokey, flippant, or self-conscious. Think intelligent editorial confidence rather than lifestyle branding or startup cleverness.
What it isn't: "We handle everything for everyone, everywhere."
The language should reflect that ICO is not just creative, but executable. It should sound like a partner who can actually build, roll out, and manage a program at scale. The tone should balance taste with competence.
What it isn't: "We deliver transformative, best-in-class wardrobe ecosystems."
Prefer concrete language over inflated claims. Name the thing, explain the value, and stop. If the copy starts sounding grander than the actual idea, it is probably off-brand. Precision builds more authority than hype.
What it isn't: "Hey! We’re so excited to partner with you!"
ICO should sound like a real person with judgment, not a committee or a chatbot. That does not mean slangy, overly friendly, or conversational for its own sake. The tone should feel warm through clarity, not informality.
Logo rules that scale
Approved logo variants
Full lockup — black
Default on light backgrounds for websites, decks, documents, and most formal brand applications.
Full lockup — white
Use on dark fields where the full identity needs to read clearly and feel deliberate.
Short mark — black
For more casual touchpoints like tags and collateral when the client or wearer already knows ICO.
Short mark — white
Use the short mark on dark applications only when the context is already familiar and the full lockup is not needed.
| Contrast | Always use the variant that reads immediately. Low-contrast use is off-brand. |
|---|---|
| Colour | Black or white only. No exceptions for campaigns, portals, or co-branded applications without explicit approval. |
| Full vs. short mark | Use the full ICO Uniforms lockup by default. Use the short ICO mark only in more casual applications such as tags or collateral where the audience already knows the brand. |
| Clear space | Maintain breathing room around the mark equal to the height of the 'I' in ICO. Do not crowd it with text or busy image edges. |
| Minimum size | Digital: 80px wide minimum. Print: 20mm wide minimum. |
| Stretching | Never distort, skew, outline, add shadows, or otherwise stylize the mark. |
Strong contrast, room to breathe
Choose the variant that reads immediately. Give the mark clear space. Use it at a considered size.
Do not improvise
Avoid low contrast, effects, recolours, or decorative treatments. The logo is not a design element — it is a mark.
A neutral system with one warm accent
| Light mode default | Cream (#F4F4F2) is the default page background. It should carry the majority of the experience because it feels softer, more editorial, and more premium than pure white. |
|---|---|
| When to use white | White (#FFFFFF) is for cards, inset modules, and moments that need sharper contrast inside a light layout. Do not build whole pages in white unless there is a specific reason. |
| Text on light backgrounds | Use Ink (#141414) for headlines and primary text, Mid Grey (#676767) for body copy, Hairline (#E8E8E8) for borders, and Cool Stone (#9A8F84) only for labels and accents. |
| Dark mode usage | Dark sections should use #181818 as the background. Use them intentionally for contrast, emphasis, and pacing — not as the default environment for the whole brand. |
| Text on dark backgrounds | Use #F4F4F2 for headlines and high-priority text. Supporting copy should be rgba(244,244,242,0.72) or lighter-toned neutral text, not the same value used on light backgrounds. |
| What to avoid | Do not place Mid Grey body copy on dark backgrounds, do not use pure black as a field colour, and do not introduce tinted or coloured backgrounds outside the approved system. |
| Eyebrow labels | Always Cool Stone (#9A8F84) at 10px, weight 500, ALL CAPS, tracked at 0.22em. |
|---|---|
| Body text | Mid Grey (#676767) for supporting copy. Never pure black (#000000) for body — use Ink (#141414) only for headlines and primary text. |
| Light backgrounds | Default to Cream for page fields and White for contained cards or modules. The contrast between the two should stay subtle, not stark. |
| Borders & dividers | Hairline (#E8E8E8) throughout. Never use a coloured border. 1px only — never thicker except for the active nav indicator (2px Cool Stone). |
| Dark sections | Background #181818 (slightly off-black, not pure black). Text #F4F4F2 for headlines and rgba(244,244,242,0.72) for supporting copy. |
| Accent restriction | Cool Stone never appears as a headline, never as a background, and never used decoratively. It is a functional colour for labels and interactive states only. |
| No additional colours | Do not introduce new colours. Photography provides all the richness. A pitch deck that feels like it needs a colour accent is a deck that needs better photography. |
Let the system breathe
Black headlines on cream, grey body copy, hairline borders, stone eyebrow labels. Photography provides colour. The palette stays neutral.
Do not add colour
Do not introduce additional accent colours, gradient backgrounds, or coloured section backgrounds. Every colour addition dilutes the system.
How colour enters the system without becoming the brand
Core principle
| Use it for | Image-led storytelling, product spotlights, campaign moments, lookbooks, landing pages, and collateral where colour helps unify photography and layout. |
|---|---|
| Do not use it for | Core UI, navigation, standard informational pages, dense decks, tables, forms, or any part of the system that should remain neutral and purely functional. |
| What it is | A contextual application method that borrows hue from photography or product. |
| What it is not | Not a secondary brand palette, not a campaign colour system, and not a licence to add arbitrary accent colours. |
Sampling examples
Primary source
Sample from the dominant product tone so the colour reads as a continuation of the garment.
Secondary source
Use the environment only when it supports the mood without overtaking the product.
Tonal shift
A slight shift in luminosity can create depth while still feeling sourced from the image.
One hue at a time
Keep the composition on one sampled hue so the page stays controlled and editorial.
Layout examples
Architectural field
Colour appears as a grounded surface, not a floating accent shape.
Flush to the image
The sampled block meets the image cleanly so both elements read as one composition.
Grid-locked field
The colour block aligns exactly to the same spacing logic as the rest of the layout.
Return to neutral
A colour-led moment resolves back into cream, white, hairline, and stone.
| Dark fields | Use Cream (#F4F4F2) for headlines and supporting text on dark sampled backgrounds. |
|---|---|
| Light fields | Use Ink (#141414) for headlines and Mid Grey (#676767) for body copy on light sampled backgrounds. |
| Mid-tone exclusion | If a sampled colour sits in the true mid-range and cannot support readable text contrast, use it only as a visual surface without typography on top. |
| Priority | Legibility beats colour fidelity. If the exact sampled tone fails, adjust slightly or move the text elsewhere. |
Type on colour examples
Dark field
Cream typography on a dark sampled background keeps the text clear and controlled.
Light field
Ink headlines and Mid Grey body copy are still the default on light samples.
Mid-tone exclusion
A true mid-tone can be used as a visual surface, but the type should move elsewhere.
Legibility first
If the exact sampled tone fails, adjust the tone slightly rather than sacrificing readability.
The litmus test
Two typefaces. Strict rules.
| Hero headline | Cormorant Garamond · Regular 300 · clamp(52px, 6.8vw, 108px) · line-height 1.0 · Used once per page maximum. |
|---|---|
| Section heading H2 | DM Sans · Weight 300 · clamp(28px, 3.5vw, 48px) · tracking -0.01em · line-height 1.05. Default all-DM-Sans treatment for page and section headlines. |
| Card heading H3 | DM Sans · Weight 400 · 18–22px · tracking 0 to -0.01em. Regular weight (not light) for legibility at smaller sizes. |
| Body large | DM Sans · Weight 300 · 16px · line-height 1.8 · color #676767. Hero subcopy, section intros, scale section subtext. |
| Body standard | DM Sans · Weight 300 · 14px · line-height 1.8 · color #676767. Card descriptions, process steps, proof facts. |
| Eyebrow / label | DM Sans · Weight 500 · 10px · tracking 0.22em · ALL CAPS · color #9A8F84 (Cool Stone). All section labels, nav items, department tags. |
| Button / CTA | DM Sans · Weight 500 · 11px · tracking 0.14em · ALL CAPS. Pill shape for primary, outlined pill for secondary, underline for tertiary. |
| Pull quote | Cormorant Garamond · Regular 300 by default, italic only for emphasis · clamp(20px, 2vw, 30px) · line-height 1.3. Testimonials only. Always in quotation marks. |
| Mixed-line pairing | When Cormorant appears inline with DM Sans, use the approved serif swap at 1.25em with -0.03em tracking so it reads at the same optical scale and keeps the line continuous. |
| Single accent move | In a single headline or phrase, use one accent strategy only. If a word is set in italic, keep it in the primary typeface. Do not combine an italic treatment with a typeface swap in the same accented phrase. |
| Section header default | Section headers should stay in DM Sans only. Reserve mixed-type headlines for selected display moments inside campaigns, editorials, or hero compositions where the phrase can still read as one continuous line. |
| Approved serif swap | Use the serif swap only in approved display headlines. Keep the serif phrase at 1.25em with -0.03em tracking so it visually matches the DM Sans line rather than shrinking inside it. |
| Display serif | 1.0–1.1 · Keep large Cormorant display settings tight so the line feels elegant and connected. |
|---|---|
| Section headlines | 1.05–1.1 · Use for DM Sans section headings. The line should feel composed and continuous, not airy or stacked by accident. |
| Body copy | 1.75–1.9 · Use generous leading for reading text, adjusting slightly for measure and contrast. |
| Quotes | 1.15–1.3 · Pull quotes and positioning lines should be tighter than body copy, but not compressed. |
| The test | Crowded → loosen slightly before changing size. Floaty → tighten before adding weight. |
| DM Sans headlines | Slight negative tracking · Use in large DM Sans headlines so the line feels clean and continuous. Never force a line with aggressive tightening. |
|---|---|
| Inline serif phrases | Tighten slightly · When Cormorant appears inside a DM Sans line, reduce spacing enough that the phrase reads as part of the sentence. |
| Serif display | Near neutral spacing · Large standalone Cormorant should stay elegant. Tighten only enough to avoid visible gaps. |
| Labels & UI | Positive tracking · Use for small uppercase labels, eyebrows, and utility text. This is for clarity, not decoration. |
| The test | Fragmented line → correct spacing before changing typefaces. One phrase jumps forward → reduce tracking contrast first. |
Controlled hierarchy
Stone eyebrow → light sans heading → grey body copy at 16px → hairline divider. Every level is distinct. Spacing is generous and consistent.
Flat or overcrowded
Avoid pages where all text feels the same size, spacing looks accidental, or Cormorant is used as a decorative heading font throughout.
Taste, imagery, and art direction
The clothing is always the subject
Approved photography modes
Operational context
Real locations that explain the role without turning the image into a busy scene.
Controlled editorial
Minimal or neutral backgrounds that clarify design, styling, and silhouette.
Compositing-ready
Images shot with consistent light direction so they work together in decks and portals.
Detail support
Close crops that explain materials, finishing, and silhouette without becoming abstract.
Intentional and readable
The uniform reads clearly, the scene supports the clothing, the lighting is consistent, and the subject looks natural in the role.
Generic or off-taste
Avoid stock-looking images, cluttered scenes, dramatic mixed lighting, or shots that look like lifestyle advertising rather than uniform communication.
Structured, intentional, never empty
| 4px | Base unit — internal component gaps, badge padding. |
|---|---|
| 8px | Tight spacing — eyebrow to headline, card number to card title. |
| 16px | Standard gap — headline to body copy, list items, button groups. |
| 24px | Component gap — body to CTA, between card elements. |
| 40px | Section gutter — horizontal padding throughout (6vw on main content). |
| 72px | Section rhythm — standard vertical padding per section top and bottom. |
| 2–3px | Grid gap between tiles, cards, and photo panels. Creates the 'tight grid' effect without borders. |
Core layout patterns
Section intro
Opens a chapter with kicker, heading, and description. Always has a border-bottom before content begins.
Photo + text duo
58/42 or 50/50 split. Photo on left or right. Ghost overlay text on photo. Client bar at bottom of photo.
Dark section
Background #181818. Left column: eyebrow + heading + body + CTA. Right: 2×2 card grid with hairline borders.
Tile grid
4-column photo card grid with gradient overlay, department label in stone, italic name in cream.
Minimal does not mean empty
Repeatable, intentional structure
Approved patterns make pages easier to build, easier to scan, and easier to keep on-brand. Structure is not a constraint — it is the brand.
Improvised or hollow
Avoid creating a new visual system for every deck, over-indexing on minimalist emptiness, or placing elements randomly without a structural logic.
Assets, templates, and escalation
Asset library
Logo files
Primary mark files for digital, print, and presentation use. Black and white variants included.
Download logo packDeck templates
Approved presentation structures pre-aligned to these brand standards. Use these as starting points — do not build from scratch.
Download templatesPhotography selects
Approved image sets that define current ICO taste. Use for onboarding presentations and external partner briefs.
Access image library| Always escalate | New layout patterns, unusual typography behaviour, non-standard colour use, logo modifications, co-branded applications, or imagery that feels borderline off-taste. |
|---|---|
| Never escalate | Straightforward use of approved blocks, approved language, standard logo variants, and reference imagery from the approved library. |
| The test | If you are not sure whether something is on-brand, it probably isn't. Ask rather than guess. A question takes 5 minutes. A rebrand takes longer. |