# Story — Aleris Brand OS concept bundle

Sources in order; each file follows as it stands in the corpus, frontmatter first.

<!-- source: foundation/index.md · status: accepted -->

---
title: Brand in brief
lang: en
status: accepted
type: foundation/index
depends_on: []
propagates_to:
  - foundation/*
  - baseline/*
  - communication/*
  - physical/*
last_verified: 2026-08-11
translation_status: verified
translation_source: foundation/index.md
---

# The Aleris brand

## The Present Expert

Aleris is a specialist who has time for you. We combine medical expertise with human closeness — clear, responsible, and with genuine interest in the person we meet. This holds in care, in communication, and in every decision we make about how we express ourselves.

---

## How the system works

There are things that are always true about Aleris — the voice, the palette, the typeface, the principles. These are constant. Then there are things that *should* be adapted: the register, the colour composition, the order of information, the level of detail. These are contextual.

This distinction is fundamental to understanding the brand and rendering it correctly. See *Constant and Contextual* for the framework.

---

## Start here

**Building a digital product?**
Start with Baseline — tokens, components, interaction patterns. The voice lives in *Voice*.

**Writing patient communication?**
Start with *Voice* and continue to Communication — document types, genre guides, phrasing examples.

**Making a brand decision?**
Start with *Constant and Contextual*. It gives you the logic to reason with, even in situations the manual doesn't explicitly cover.

**Want to understand what Aleris stands for?**
Read this page. Then read *Voice* and *Emotional Mode as a Design Entry Point*. That gets you a long way.

---

## What always applies

**The test:** Does this feel written for me in my situation?

**The palette:** Petrol, sand, orange. Three families, three roles. Never arbitrary colours. See *Colour*.

**The typeface:** Museo Sans, Arial as fallback. Sentence case throughout. Never all caps. See *Typography*.

**Emotional mode governs the expression:** Same character, different information architecture — depending on where the recipient is. See *Emotional Mode as a Design Entry Point*.


<!-- source: principles/constant-and-contextual.md · status: accepted -->

---
title: Constant / contextual
lang: en
status: accepted
type: principles/reasoning-tool
layer: principle
depends_on: []
propagates_to:
  - foundation/emotional-modes
  - baseline/*
  - communication/*
last_verified: 2026-08-27
---

# Constant and contextual

## How do you know what you're allowed to change?

The Aleris brand has parts that are always the same — and parts that *should* be adapted to the situation. The difference between the two is the most important thing to understand before you make a brand decision.

Easiest to show with examples.

---

## Example 1: Two welcome messages

One patient is about to undergo a cardiac assessment. Another is booking a health check-up out of curiosity.

Both receive a welcome message from Aleris. Both should sound like the Present Expert — calm, clear, attentive.

But the one who is anxious needs to know *what happens next* already in the first sentence. The process made visible, the steps named, a contact person identified. Predictability eases worry.

The one who books out of curiosity needs something else. They've made an active decision and want to feel affirmed in it — not treated as if something is wrong. Here we lead with what the examination gives, not with the procedure.

| | Patient before a cardiac assessment | Patient booking a health check-up |
|---|---|---|
| **Reader state** | Uncertainty, need for control | Curiosity, desire to make a considered decision |
| **We lead with** | Reassurance: what happens, step by step | Outcome: what the examination gives |
| **We dial down** | Clinical details that may increase worry | Risk messaging that undermines a sense of agency |
| **We close with** | A way to make contact — a human is available | The next step — a low threshold to proceed |

**The character is identical. The information architecture is entirely different.**

What is *constant*: the Aleris voice — presence, calm, precision, warmth.
What is *contextual*: what we lead with, what we dial down, how we structure the content.

---

## Example 2: Changed opening hours, three channels

A clinic has changed its opening hours. Three channels need updating.

**The website** explains: new hours, from when they apply, how to rebook. The tone is friendly and clear — the visitor could be anyone.

**The internal email to staff** is shorter and more direct. Staff don't need an explanation of why opening hours exist. They need to know what has changed, from which date, and what it means for their schedule.

**The SMS to patients with booked appointments** is shorter still. One sentence about what has changed, one link to rebook. No preamble, no filler. Respect for the format *is* respect for the recipient.

| | Web | Internal email | SMS |
|---|---|---|---|
| **The recipient** | Anyone | Colleague | Patient with a booking |
| **We explain** | Everything — new hours, why, how to rebook | Only the change and the consequence | Only the change and the next step |
| **Register** | Friendly, instructive | Collegial, concise | Minimal, respectful |

**Three channels, three registers. The character — calm, clear, attentive — is constant.** Using the same phrasing in all three would have signalled that we don't see a difference between the situations. And that is the opposite of presence.

---

## Example 3: Colour

The Aleris colour palette — petrol, sand, orange — is constant. It is the same whether you make a patient brochure or an internal presentation.

How the colours are distributed is contextual. A landing page uses sand generously, with petrol as the text colour and orange as an accent. A clinical interface compresses the palette and gives petrol more dominance. The palette doesn't change. The composition does.

---

## The principle

**Constant** = what is always true about Aleris, regardless of channel, format, or situation. The character, the palette, the choice of typeface, the hard rules. If you change these, Aleris is no longer recognisable as Aleris.

**Contextual** = how we adapt the expression to the conditions of the situation. The register, the order of information, the colour distribution, the level of detail. These *should* change — keeping them constant makes the communication worse, not better.

### Quick test

When you make a brand decision, ask yourself:

1. **Should this be the same regardless of who, where, when, and why?** → Constant. Follow the guideline.
2. **Does the right choice depend on the situation — who the recipient is, which channel, which reader state?** → Contextual. Read the situation. Use your judgement.
3. **Can't find any guidance at all?** → You've found a gap in the system. Flag it.

---

*This framework runs through the whole of Brand OS. Every chapter shows what is constant and what is adapted within its area.*
