# Locale Style Guide

Define audience-specific local writing rules for voice, formality, punctuation, names, numbers, units, interface patterns, accessibility, and governance.

## Usage note

Write this guide for a defined locale, audience, and content system; a language name alone is too broad. Treat the rules as documented editorial decisions rather than claims about how everyone in a region communicates. Include examples and exceptions, involve qualified local editors, and revise the guide when audience evidence, language use, product behavior, or policy changes.

## How to use this template

1. Define the locale, language variety, script, audiences, relationships, channels, risks, and evidence behind the guide.
2. Convert brand voice and local expectations into concrete writing choices with acceptable and avoid examples.
3. Document mechanical, numerical, naming, interface, accessibility, and layout conventions plus explicit exceptions.
4. Link terminology and regulated sources, then assign a process for new questions, conflicts, and approvals.
5. Version the guide, communicate changes, sample published work, and revise rules based on qualified evidence.

## Blank template

### Guide identity and audience

- **Locale, language variety, and script:** [Enter precisely]
- **Guide version and effective date:** [Enter]
- **Products and channels in scope:** [Web, app, email, help, campaign, or other]
- **Primary audience segments:** [Situations and needs]
- **Speaker-reader relationships:** [Support, peer, institution, expert, or other]
- **Evidence used:** [Local editors, research, content sample, or policy]
- **Language owner:** [Name or team]
- **Brand or subject partner:** [Name or team]
- **Out of scope:** [Other regions, regulated copy, or specialized content]

### Voice, register, and structure

- **Default formality and pronouns:** [Rule, reason, and example]
- **Directness and agency:** [Preferred pattern]
- **Sentence and paragraph guidance:** [Length, order, and complexity]
- **Headings and calls to action:** [Pattern]
- **Reassurance, apology, and error tone:** [Pattern]
- **Humor and idioms:** [When suitable or avoided]
- **Inclusive and respectful language:** [Principles and escalation]
- **Preferred example:** [Source intent and target execution]
- **Avoid example:** [Problem and improved version]

### Mechanics and locale formats

- **Capitalization and case:** [Rules]
- **Punctuation and quotation marks:** [Rules and nesting]
- **Spacing, dashes, ranges, and emphasis:** [Rules]
- **Lists, abbreviations, and acronyms:** [Rules]
- **Names, titles, addresses, and telephone numbers:** [Rules]
- **Dates, weekdays, time, and time zones:** [Rules]
- **Numbers, decimals, percentages, currency, and units:** [Rules]
- **Line breaking, wrapping, and forbidden breaks:** [Rules]
- **Sorting and alphabetical behavior:** [If relevant]

### Product content and governance

- **Buttons and links:** [Verb, length, and destination context]
- **Labels and placeholders:** [Pattern and limits]
- **Errors and recovery:** [Cause, next step, and respectful tone]
- **Statuses and notifications:** [Tense and timing]
- **Accessibility:** [Plain language, reading order, alternatives, captions]
- **Terminology source:** [Glossary location and priority]
- **Regulated or approved wording:** [Source and owner]
- **Rule conflict order:** [Accessibility, legal, terminology, local style, brand, or other]
- **Proposal process:** [Question, evidence, reviewer, deadline]
- **Change log:** [Rule, before/after, reason, affected content, date]
- [ ] Examples cover common content types and difficult states.
- [ ] Rules describe a defined audience rather than a national stereotype.
- [ ] Review owners and effective versions are visible.