Fewer calls. Lower costs. Happier people.
I turn complex content into plain language everyone understands
Who I help
Cities, healthcare providers, universities, non-profits, and public-facing agencies that want to make their information actually usable
Where people get lost
Dense language, missing context, or policy jargon make people give up — and your team pays the price in calls, emails, and confusion
How things improve
Clearer content saves time, cuts costs, and earns trust — fewer questions, faster service, happier people
Why plain-language matters
People give up when information is buried in jargon or long sentencesPlain language makes content faster to read and easier to trustThat saves time, cuts costs, and helps your team serve more people well
How I can help
Fix your busiest FAQ or help page in 7 days, or start with a quick metrics audit
Plain Language Rewrite
from CA$350
Rewrite one page in plain language for clarity and self-service. For more pages, ask for a custom quote
What’s included:
Structure: merge duplicates; add clear question headings and task-based links
Clarity: rewrite for lower reading grade, fewer words, less passive voice
Proof & handoff: before/after metrics (grade, words, passive %) + 2-page mini style guide
Deliverable:
Publish-ready copy (Google Doc/Word)
1-page metrics + 2-page mini style guide (PDF)
Timeline:
7 business days (1 review round)
Add-on (optional):
Bilingual (EN/FR) version available (+ 60 %, add 1 business day; includes one review round)
Metrics & Fix-List Audit
from CA$175
Report on one page. For multiple pages or full-site audits, ask for a custom quote
What’s included:
Metrics: reading grade, word count, passive %
Top fixes: six examples + quick accessibility notes (headings/link text)
Walkthrough (optional): 10-min video, call, or email Q&A
Add-on (optional): Micro-fix ≤250 words (48h turnaround, one pass)
Deliverable:
2–3 page PDF (readability metrics + top fixes)
Timeline:
3 business days
Add-on (optional):
Bilingual (EN/FR) report available (+ 60 %, timeline adjusted as needed)
Ongoing Plain Language Support
from CA$600/month
Ongoing monthly support for public-facing content, with priority service and flexible scope
What’s included:
Continuous rewrites: forms, FAQs, or policy pages updated in plain language
Regular audits: spot checks with readability and accessibility metrics
Advisory: quick reviews, Q&A, and feedback to guide your team
Priority service: Priority turnaround with flexible scope and ongoing access to plain-language expertise
Add-on (optional):
Bilingual (EN/FR) retainer option available at a preferred rate
Reply within 1 business day (PT). Need something different? Ask for a custom quote
Simple 3-step process
From kickoff to delivery in just 7 days
Kickoff & Quote
Share your page and goal. I confirm scope and send a fixed price.Rewrite & Review
Your content is rewritten in plain language with accessibility checks. One round of feedback included.Delivery
You get clear, publish-ready content plus before/after metrics.
Case studies
Two quick before/after fixes with metrics
Toronto Police - When to call 9‑1‑1
Grade 13.7 → 6.9 • Words −18% (125 → 102) • Passive 40% → 0%
BEFORE
AFTER
Source: Toronto Police Service - “Who do I call?” excerpt. Sample from a public page; no endorsement implied. Full case + link below.
Key changes
① Answer first — rule up front; examples moved to a short list
② Channel triage — tells people what to do instead (non‑emergency line / report online)
③ Correct links, plain language — replaced a raw/wrong URL with a labeled link to the right page; shorter, active wording
What I did: front‑loaded the rule • turned examples into bullets • added non‑emergency options • fixed the wrong URL with a task‑based link • cut passive & simplified wording
Metrics
Grade level: 13.7 → 6.9 (↓ 6.8)
Word count: 125 → 102 (↓ 23)
Passive sentences: 40% → 0% (↓ 40 pp)
Link accuracy: 1 → 0
Metrics shown are for the above excerpt only, not the full case study.
Why it matters: fewer unnecessary 9‑1‑1 calls, faster routing to the right channel, and better access for Deaf/HoH users
Method: Flesch–Kincaid grade and passive‑sentence % measured on the highlighted contact‑page excerpt (headings included; navigation excluded; link verified). 2025‑07‑30.
YMCA Canada FAQs - Job‑offer scam emails
Grade 12.6 → 6.6 • Words −52% → (160 → 77) • Passive 30% → 0%
BEFORE
AFTER
Source: YMCA Canada - FAQ excerpt (1 question). Sample from a public page; no endorsement implied. Full case + link below.
Key changes
① Answer first — leads with “It’s likely a scam”
② Do/Don’t steps — concrete actions replace vague warnings
③ Plain, active wording — shorter sentences, easier to scan
What I did: front‑loaded the verdict • made the policy explicit • added Do/Don’t steps • cut passive & simplified wording
Metrics
Grade level: 12.6 → 6.6 (↓ 6.0)
Word count: 160 → 77 (↓ 83)
Passive sentences: 30% → 0% (↓ 30 pp)
Metrics shown are for the above excerpt only, not the full case study.
Why it matters: fewer “Is this real?” calls, faster self‑service, and lower fraud risk for your community
Method: Flesch–Kincaid grade level and passive‑sentence % measured on the highlighted FAQ excerpt (headings included, navigation excluded). 2025‑07‑28.
More before/after examples?
© 2025 IN PLAIN WORDS. All rights reserved.
Questions before you start? Email [email protected]