Plain-language service pages
Rewrite program names, eligibility, documents, and next steps around the task a person needs to complete.
Plain-language service page setPlain-language public-service writing / Wellington · Remote
Write the next public step in words people can use.
A plain-language SEO writing practice creating service pages, task guidance, and accessible public resources for people who may be short on time, confidence, or context.
- QuestionProgram names made sense internally but not to first-time visitors.
- Plain answerPlain-language service pages connected everyday questions with eligibility and the right form of help.
- Next stepAccessible public guide series
Plain-language reviews available
SEO content writing
Plain-language public-service writing, from research to publish.
Task guidance
Write step-by-step instructions, form guidance, and handoff copy that reduce avoidable uncertainty.
Public task and microcopy setAccessible resource writing
Create scannable guides that explain unfamiliar terms and remain useful under stress.
Accessible public guide seriesIllustrative content programs
Lantern Route turns expertise into useful pages.
Community support
Open Door Network
Plain-language service pages connected everyday questions with eligibility and the right form of help.Program names made sense internally but not to first-time visitors.Local government
River County
Rewritten guidance resolved overlapping instructions and named the next department at each handoff.Several departments published overlapping guidance.Education nonprofit
Bright Path Fund
Task-led resource pages explained each learning need and the available support in direct language.Resources were arranged by initiative rather than learner need.Editorial operating model
Lantern Route keeps every draft accountable.
- Baseline
- Accessible
- Plain language, landmarks, and readable pathways shape every page.
- Writing
- Need-led
- Public questions organize the copy before departmental structures.
- Impact
- Illustrative
- Fictional cases avoid unsupported claims about service uptake.
Writing standards
The editorial rules behind Lantern Route.
- 01
Use public language
Internal program vocabulary should never become a discovery barrier.
- 02
Design for stress
Information must remain readable when time, attention, or confidence is limited.
- 03
Respect the handoff
The next service step is part of the content experience.
Next step / content brief