AlerisBrand OS

Accepted

Using Aleris in AI tools

What this answers: you are making something with an AI tool — an invitation, a greeting, a routine sheet, slides, an image — and you want it to look and sound like Aleris rather than almost like Aleris.

Ask any AI tool for "a healthcare brand" and you get a white page, a headline in capitals, a pill-shaped button and a photograph of someone in a white coat smiling at a clipboard. Nothing in it is wrong enough to point at, and none of it is ours. Below is the short set of values that fixes it, in a form you can paste.

You do not need to read the rest of this site to use this page.

Paste this before you ask for anything

Copy the whole block into your AI tool — at the start of the conversation, or into its project instructions if it has them — and then ask for what you actually want.

Follow the Aleris visual identity in everything you produce in this conversation.

Colour — use these exact values and no others:
- Page background: #f2ece4 (sand). Never white.
- Cards and panels sitting on that background: white.
- Text and headings: #004851 (petrol).
- The one thing you most want the reader to do: #d14811 (orange). Only one per page.
- Decorative orange, never behind white text: #f58c61.
- Green #4f866e means "done". A dot, a badge or a label.
- Red #c14444 means an error.
- Lines, borders and rules: #d7d2cb.

Type:
- Arial. Only use Museo Sans if you know it is installed.
- Sentence case everywhere: headings, labels, tabs. Never all caps.
- Do not use the characters → ← ✓ ≤ ≥ in text.

Never draw these — place them afterwards in PowerPoint, Canva or Word:
- The Aleris logo, the wordmark, a unit's name, dates, phone numbers, web addresses.
- Leave the top of the page clear so they can be put there.

Images:
- A generated image may set mood, pattern and colour.
- It must never claim to show a real Aleris place, a real patient or a real result.

Language:
- Write to the reader as "you", not about them in the third person.
- Calm and direct. No exclamation marks, no "Absolutely!", no marketing adjectives.
- Say what something is before saying why it matters.

If you remember only four things

  1. The page is sand, not white. #f2ece4.
  2. One orange thing per page, and it is the thing you want the reader to do.
  3. Sentence case. Never capitals — not in a heading, a label or a tab.
  4. Never let the tool draw the logo. Place it afterwards.

The colours

Value Name What it is for What it must never do
#f2ece4 sand-100 Page background for anything a patient or a colleague reads Be replaced by white
#faf8f6 sand-50 Page background for tools, admin and dashboards Appear on patient-facing material
#ffffff white Cards and panels on top of sand Be the page background
#004851 petrol-500 Text, headings, structure —
#d14811 orange-600 The single most important action Appear twice on one page, or on a petrol background
#f58c61 orange-500 Accent, decoration, print Sit behind white text
#4f866e confirm-500 "Done" — a dot, a badge, a chip Be a button fill
#c14444 error-500 Errors and warnings Be used decoratively
#d7d2cb gray-100 Borders and dividers —

Everything here is quoted from the token file the products themselves are built from, aleris-tokens.css. The reasoning behind the palette is on Colour.

When you need more colours than these — a chart, a set of icons, a numbered list — there are twelve more in the same file, named --color-chart-01-teal through --color-chart-12-dark-sand: teal, mint, two blues, two purples, two terracottas, marine, olive, warm grey and dark sand. Use those rather than inventing any.

Type

Set it in Arial. Museo Sans is the Aleris typeface, but it is installed on very few machines and an AI tool has no way to use it, so what actually reaches the page is Arial. That is the sanctioned substitute and has been since the 2025 guidelines: Arial is the face for PowerPoint and for anything made outside the communication department. Only ask for Museo Sans if you know it is on the machine the file will be opened on.

Sentence case, everywhere. Aleris product names keep their natural casing — Aleris, MittAleris, Aleris Online — including in tabs, labels and buttons.

Five characters break silently. The arrow →, the back arrow ←, the check mark ✓, and ≤ and ≥ are not in Museo Sans. Where the typeface is used, each one falls back to a different face mid-sentence, at a different weight and baseline. AI tools reach for them constantly. Use a word or an icon instead. Safe: the en dash, the em dash, the bullet, ×, … and °.

What gives an AI away

Check for these in anything you have just generated, before you send it.

  • A white page background.
  • Headings or labels in capitals.
  • Arrows and check marks in running text.
  • A Swedish ä that has come back as ā — a sign the tool drew the text rather than typeset it, and a sign the logo will be wrong too.
  • An Aleris logo with the wrong number of rings, or a wordmark in the wrong typeface.
  • A generic mid-blue that is not petrol, usually arriving as "healthcare blue".
  • Two competing oranges.
  • Stock or generated photography of strangers in white coats.
  • Exclamation marks, "Absolutely!", and a closing sentence that says nothing.

The text-level tells — mirror sentences, inflated vocabulary, rhetorical endings — are catalogued with examples on AI-tells and filters, and how Aleris is meant to sound is on The Present Expert.

What this page does not give you

  • The header — the sand band with the logo and your unit's name. It exists as a PowerPoint template and as images for A4 and 16:9. Ask where the current files are rather than building your own version.
  • The logo on its own is served here as aleris-logo.svg and aleris-logo-white.svg. The full identity rules are still in draft.
  • Photography. There is no image library here.
  • Swedish, Norwegian and Danish versions. This site is English for now; the brand voice guides in Swedish are under Design system.

If you are building software

Different job, different rules. Stop pasting values and install the real ones: Setup for AI coding tools is four steps, and BASELINE.md is what a coding assistant should read before writing any interface code.

That is also where the rules this page leaves out live, because they only apply on screen: the 14px type floor, corner radii of 16px on cards and 8px on buttons, 44px touch targets, and Museo Sans in its two weights — 500 for body text and 700 for headings, never 400, which the font does not contain.