Louis House Style — English
When this applies
Apply this style guide to any English-language output:
- Legal documents (contracts, opinions, corporate filings, court submissions)
- Professional communications (client emails, memos, legal updates)
- In-product UI text (onboarding, tooltips, notifications)
- Consumer-facing content (legal explainers, help text, empathic responses)
- Marketing copy (blog posts, social media, whitepapers)
Voice and register
Two registers, not one
Louis writes for two distinct audiences and the style must shift accordingly:
| Audience |
Register |
Reading level |
Example |
| Lawyers, GCs, paralegals |
Technical legal English |
Professional / expert |
"The indemnification obligation survives termination for a period of three years." |
| Consumers, self-represented users |
Plain English |
8th grade / accessible |
"You're protected for three years after the contract ends." |
When the user's persona is known, apply the appropriate register automatically. When in doubt, default to plain English — a lawyer will not be offended by clarity; a consumer will be confused by legalese.
Grammar and punctuation
Active voice
Prefer active over passive voice in all registers. Passive voice creates ambiguity about who is doing what — which is the opposite of what a legal document needs.
- Active: "The Buyer shall pay the deposit within five business days."
- Passive: "The deposit shall be paid within five business days." (by whom?)
Exception: passive voice is acceptable when the actor is genuinely unknown or irrelevant to the obligation.
Oxford comma
Always use the Oxford (serial) comma in lists: "the Buyer, the Seller, and the Guarantor" — not "the Buyer, the Seller and the Guarantor." Omitting it creates ambiguity that has been litigated.
Sentence length
- Legal documents: long sentences are acceptable where precision requires it, but the main clause should be identifiable within the first 20 words.
- Professional communications: 15–25 words per sentence is optimal.
- Consumer content: 10–15 words per sentence. Break complex ideas into two sentences.
Exclamation marks
Never in legal documents or formal professional communications. Acceptable sparingly in consumer-facing onboarding copy only.
Headings and structure
- Sentence case for all headings in prose documents and UI: "When to use this" not "When To Use This."
- Exception: legal document section titles follow the convention of the jurisdiction's formal document standard — typically all-caps or Title Case for major clause headings.
- No heading ending with a period.
Numbers and quantities
| Quantity |
Format |
| One through nine |
Spell out: "seven business days" |
| 10 and above |
Numerals: "10 business days" |
| Percentages |
Numerals: "25%" not "twenty-five percent" |
| Contract amounts (casual) |
"$1,000" with dollar sign |
| Contract amounts (legal docs) |
"USD 1,000" — spell out currency code |
| Large round numbers |
"USD 1 million" or "USD 1,000,000" — use consistent form throughout |
Never write "1,000$" (sign after amount) in any context.
Currency
- Casual context (consumer chat, informal email): "$1,000" (symbol before amount) is acceptable for USD.
- Legal documents (contracts, opinions, formal correspondence): write "USD 1,000" — spell out the ISO currency code. Do not use symbols.
- For MENA currencies in English legal docs: AED 150,000; SAR 500,000; LBP 10,000,000.
Dates
Two acceptable formats; choose based on audience:
| Format |
Use case |
| May 12, 2026 (US-style) |
US audience, US legal documents |
| 12 May 2026 (UK/Commonwealth style) |
UK, DIFC, ADGM, international documents, GCC |
Never use: 12/05/2026 or 05/12/2026 — these are ambiguous between US and European conventions and must not appear in legal documents.
Conjunctions
- "and" when listing items that are all included.
- "or" when listing alternatives.
- Do not use "/" as a substitute for "and/or" in legal drafting — "and/or" itself is acceptable only when both meanings are genuinely intended; prefer "A, B, or both."
What to avoid
- Nominalizations (turning verbs into nouns): "make a payment" → "pay"; "provide notification" → "notify."
- Double negatives.
- Unnecessary Latin (res judicata, force majeure excepted where they are the term of art).
- "Hereinafter", "therein", "hereto" and similar archaic legalese — use plain alternatives ("in this agreement", "in that document", "attached to this agreement") in drafts that prioritize plain language. Retain in documents where the jurisdiction's court or registry conventions require them.
Related skills
- [[voice-brand-louis-house-style-ar]]
- [[voice-brand-louis-house-style-fr]]
- [[voice-brand-email-cold-outreach-mena]]
- [[voice-brand-email-investor-update]]
1---2name: voice-brand-louis-house-style-en3description: Louis House Style — English4---56# Louis House Style — English78## When this applies910Apply this style guide to any English-language output:11- Legal documents (contracts, opinions, corporate filings, court submissions)12- Professional communications (client emails, memos, legal updates)13- In-product UI text (onboarding, tooltips, notifications)14- Consumer-facing content (legal explainers, help text, empathic responses)15- Marketing copy (blog posts, social media, whitepapers)1617## Voice and register1819### Two registers, not one2021Louis writes for two distinct audiences and the style must shift accordingly:2223| Audience | Register | Reading level | Example |24|----------|----------|---------------|---------|25| Lawyers, GCs, paralegals | Technical legal English | Professional / expert | "The indemnification obligation survives termination for a period of three years." |26| Consumers, self-represented users | Plain English | 8th grade / accessible | "You're protected for three years after the contract ends." |2728When the user's persona is known, apply the appropriate register automatically. When in doubt, default to plain English — a lawyer will not be offended by clarity; a consumer will be confused by legalese.2930## Grammar and punctuation3132### Active voice33Prefer active over passive voice in all registers. Passive voice creates ambiguity about who is doing what — which is the opposite of what a legal document needs.34- Active: "The Buyer shall pay the deposit within five business days."35- Passive: "The deposit shall be paid within five business days." (by whom?)3637Exception: passive voice is acceptable when the actor is genuinely unknown or irrelevant to the obligation.3839### Oxford comma40Always use the Oxford (serial) comma in lists: "the Buyer, the Seller, and the Guarantor" — not "the Buyer, the Seller and the Guarantor." Omitting it creates ambiguity that has been litigated.4142### Sentence length43- Legal documents: long sentences are acceptable where precision requires it, but the main clause should be identifiable within the first 20 words.44- Professional communications: 15–25 words per sentence is optimal.45- Consumer content: 10–15 words per sentence. Break complex ideas into two sentences.4647### Exclamation marks48Never in legal documents or formal professional communications. Acceptable sparingly in consumer-facing onboarding copy only.4950## Headings and structure5152- **Sentence case** for all headings in prose documents and UI: "When to use this" not "When To Use This."53- Exception: legal document section titles follow the convention of the jurisdiction's formal document standard — typically all-caps or Title Case for major clause headings.54- No heading ending with a period.5556## Numbers and quantities5758| Quantity | Format |59|----------|--------|60| One through nine | Spell out: "seven business days" |61| 10 and above | Numerals: "10 business days" |62| Percentages | Numerals: "25%" not "twenty-five percent" |63| Contract amounts (casual) | "$1,000" with dollar sign |64| Contract amounts (legal docs) | "USD 1,000" — spell out currency code |65| Large round numbers | "USD 1 million" or "USD 1,000,000" — use consistent form throughout |6667Never write "1,000$" (sign after amount) in any context.6869## Currency7071- **Casual context** (consumer chat, informal email): "$1,000" (symbol before amount) is acceptable for USD.72- **Legal documents** (contracts, opinions, formal correspondence): write "USD 1,000" — spell out the ISO currency code. Do not use symbols.73- For MENA currencies in English legal docs: AED 150,000; SAR 500,000; LBP 10,000,000.7475## Dates7677Two acceptable formats; choose based on audience:7879| Format | Use case |80|--------|----------|81| May 12, 2026 (US-style) | US audience, US legal documents |82| 12 May 2026 (UK/Commonwealth style) | UK, DIFC, ADGM, international documents, GCC |8384Never use: 12/05/2026 or 05/12/2026 — these are ambiguous between US and European conventions and must not appear in legal documents.8586## Conjunctions8788- "and" when listing items that are all included.89- "or" when listing alternatives.90- Do not use "/" as a substitute for "and/or" in legal drafting — "and/or" itself is acceptable only when both meanings are genuinely intended; prefer "A, B, or both."9192## What to avoid9394- Nominalizations (turning verbs into nouns): "make a payment" → "pay"; "provide notification" → "notify."95- Double negatives.96- Unnecessary Latin (res judicata, force majeure excepted where they are the term of art).97- "Hereinafter", "therein", "hereto" and similar archaic legalese — use plain alternatives ("in this agreement", "in that document", "attached to this agreement") in drafts that prioritize plain language. Retain in documents where the jurisdiction's court or registry conventions require them.9899## Related skills100101- [[voice-brand-louis-house-style-ar]]102- [[voice-brand-louis-house-style-fr]]103- [[voice-brand-email-cold-outreach-mena]]104- [[voice-brand-email-investor-update]]