The North voice
Introduction
Our voice is how we sound in every sentence: on a slide, in an error message, in a reply to a minister. It is the same calm, clear North, whoever is writing.
Our customers handle confidential work and make decisions that affect many people. They have no time for hype and no tolerance for vagueness. So we write the way a trusted senior adviser talks: plainly, precisely and with quiet confidence.
Voice and tone
One voice, many tones
Voice is our personality. It never changes. Tone is how that personality adapts to the moment: more technical in documentation, warmer in a welcome email, more careful in an incident notice.
Think of a respected colleague. They sound like themselves whether they are presenting to a board or helping a new joiner, but they don't speak to both in exactly the same way.
| Voice | Tone | |
|---|---|---|
| Changes? | Never | With the moment |
| Set by | Who we are | Who we're talking to and how they feel |
| Example | Calm and precise | Reassuring in an outage, crisp in release notes |
Our brand traits
Four traits shape everything we write.
Clear
- Short sentences, active voice, plain words.
- Say what happens, who does it and when.
- One idea per sentence; one message per piece.
NorthStar checks your licence every 15 minutes. If it can't reach Admiral, it keeps working for 48 hours.
NorthStar leverages a robust, periodic entitlement-validation mechanism to ensure seamless continuity.
Calm
- No exclamation marks in product or formal writing.
- No hype: “revolutionary”, “game-changing”, “magic”.
- Name risks plainly, then say what we do about them.
Classified analyses never go to a public model. If no on-premises model is available, Shaheen stops and tells you.
Don't panic! Our amazing AI keeps your secrets 100% safe, guaranteed!!
Precise
- Use exact numbers, names and terms.
- Don't claim what we can't prove.
- Use our product names correctly every time.
Uploaded files are stored as AES-256-GCM encrypted blobs.
Your files are protected by military-grade, bank-level encryption.
Human
- Write to one person: “you” and “we”.
- Use contractions: “you'll”, “we're”, “it's”.
- Put the person in command; the AI assists.
Mai drafts the reply. You decide whether to send it.
The AI autonomously handles your correspondence end to end.
Our writing principles
| Principle | What it means |
|---|---|
| Start with the answer | Lead with the conclusion, the action or the benefit. Context comes second. |
| Reader first | Ask “what does this person need to know or do?” Cut everything else. |
| Plain over clever | If a simpler word works, use it. No puns on serious topics. |
| Show, then tell | A concrete example beats an adjective: “runs on your servers” beats “sovereign”. |
| Humans in command | AI suggests, drafts, analyses. People decide, approve, send. Write it that way. |
| Respect the reader's time | Shorter is kinder. Edit once for sense, once for length. |
Words we use with care
Talking about AI
- Agents draft, analyse, suggest, prepare. People approve, decide, send.
- Don't give AI feelings or intentions: it doesn't “think”, “want” or “understand”.
- Avoid “autonomous” unless we mean it and explain the limits.
- Say which model runs where: “on your on-premises model”, “on an approved cloud model”.
Mai prepared three draft replies for you to review.
Mai thought about your emails and decided to reply.
Shaheen ran six specialist lenses on your sources.
Our AI brain digested your data.
Talking about security and sovereignty
- Explain the mechanism, not just the promise.
- Never say “100% secure”, “unhackable” or “guaranteed”.
- Use “on-premises” (with the s), “residency”, “sovereign” precisely and consistently.
Desks never hold provider keys. Every model call goes through your NorthStar Admiral Server.
NorthStar is completely unhackable.
Tone by channel
| Channel | Tone | Example |
|---|---|---|
| Product UI | Brief, direct, helpful | “Review and send” · “Licence expires in 9 days” |
| Documentation | Precise, structured, neutral | “An operator creates the user in NorthStar Admiral Desktop and issues a licence.” |
| Government proposals | Formal, respectful, evidence-led | “The pilot keeps all data within the Department's infrastructure.” |
| Marketing and web | Confident, warm, concrete | “Your desk. Your data. Your models.” |
| Social | Conversational, one idea | “Mai now asks before it acts.” |
| Support and incidents | Calm, honest, specific | “Sign-in is failing for some users since 09:40. We're working on it; next update at 10:30.” |
| Internal | Friendly, direct | “Thanks, team. Here's what shipped this week.” |
Writing in Arabic
Arabic copy is written natively, not translated, by and for Arabic readers. Tone, forms of address, UI copy, the Arabic glossary and the review workflow are on Writing in Arabic.
UI writing
Microcopy that helps
- Buttons say exactly what happens: “Send 3 emails”, not “Submit”.
- Keep an action's name through the flow: “Publish” → “Published”.
- Errors explain what happened and how to fix it. No blame, no apology, no jargon.
- Empty states invite the next action.
Couldn't reach NorthStar Admiral Server. Check your network, then try again.
Error 0x80042: Request failed.
No analyses yet. Start one from a file or an organisation.
Nothing to see here!
Dos and don'ts
Do
- Lead with the answer.
- Use active voice and contractions.
- Use exact numbers and product names.
- Keep people in command of the AI.
Don't
- Use hype, exclamation marks or emoji in formal writing.
- Overclaim: “100%”, “guaranteed”, “unhackable”.
- Hide behind jargon or acronyms.
- Write as if the AI were a person.
Last updated on 14 October 2026