Path: Home · Services · Plain language editing and policy documentation
Plain language editing and policy documentation
I rewrite policy, procedure, and public-facing documents so the people who have to use them can act on them. Based in Vancouver, working with public sector, non-profit, and post-secondary teams across British Columbia.
What this service covers
Policy and procedure documents. Ministry policy, board policy, internal directives, standard operating procedures. The work is usually structural before it is linguistic: separating the rule from the rationale, giving each obligation an owner, and making conditional logic visible instead of burying it in subordinate clauses.
Operational guidelines. Process documents that staff use while doing the task rather than reading beforehand. Step numbering that survives revision, decision points that read as decision points, and exception handling that does not require a second document.
Public-facing service content. Eligibility criteria, application instructions, notices, and program pages. This is where plain language pays for itself most directly, because every ambiguity becomes a phone call to a service counter.
Learning and reference material. Course outlines, learning objectives, help documentation, and quick-reference guides. Instructional design is a separate discipline from technical writing, and I work in both.
How a project runs
| Stage | What happens | What you supply |
|---|---|---|
| 1. Scope and audience | Define who reads the document, what they must be able to do afterwards, and what constraints are non-negotiable. Written up as a one-page brief you approve before editing starts. | Source documents, any governing style or legal requirements, a subject-matter contact |
| 2. Structural edit | Reorder for the reader rather than the approval chain. Split, merge, or cut sections. Flag content that belongs in a different document. Delivered as a marked-up outline with the reasoning attached. | Decisions on the flagged items |
| 3. Plain-language rewrite | Sentence and word level. Active voice, named actors, one idea per sentence, defined terms. Tracked changes so every edit is reviewable and reversible. | Subject-matter review of substantive changes |
| 4. Accessibility pass | Heading hierarchy, table structure, alt text, link text, colour contrast, and tagging for PDF output. Checked against WCAG 2.2 Level AA. | Access to the source file format, not a flattened PDF |
| 5. Handover | Final files plus a style decision record: every recurring judgment call, written down so your next document does not relitigate it. | — |
Small edits skip stages. A single notice does not need a style decision record. A policy manual does.
Before and after
The example below is constructed rather than taken from client work. It is modelled on the sentence patterns common in provincial program documentation, not drawn from any specific document.
Before
Notwithstanding the foregoing, applicants who have been determined to be ineligible pursuant to Section 4.2 may, at the discretion of the Program Administrator and subject to the submission of such additional documentation as may be required, be reconsidered for enrolment, provided that any such request for reconsideration is received by the Ministry within thirty (30) calendar days of the date of issuance of the notice of ineligibility.
After
Despite the rules above, if you were found ineligible under Section 4.2, the Program Administrator may reconsider your enrolment.
To request reconsideration:
- Make sure the Ministry receives your request within 30 calendar days of the date your notice of ineligibility was issued.
- Submit any additional documents required for reconsideration.
The Program Administrator decides whether to reconsider your application. Meeting these conditions does not guarantee reconsideration or enrolment.
What changed, and why
- The conditions are easier to find. The deadline and documentation requirement appear as separate actions.
- The deadline retains its original meaning. The Ministry must receive the request within 30 calendar days of the notice’s issue date. Sending it by the deadline is not sufficient.
- The scope remains explicit. The rewrite retains the reference to Section 4.2 and the exception to the preceding rules.
- The documentation requirement remains open. Additional documents may be required; the rewrite does not limit them to documents listed in the notice.
- The decision remains discretionary. The Program Administrator may reconsider the application but is not required to do so.
This constructed example demonstrates clearer organization while retaining the stated conditions. In a real document, “the rules above” would need a precise reference, and the policy owner would need to confirm the procedure for submitting a request and any additional documents.
Standards applied
Every document is checked against the standards its audience is actually held to:
- BC Web Style Guide and the province’s 17-item plain-language checklist, including the Grade 8 reading-level target
- WCAG 2.2 Level AA, the conformance level the BC government has committed to for websites and applications
- Microsoft Style Guide for technical and interface terminology
- Canadian spelling and date conventions throughout
- ISO 24495-1:2023 governing principles, where a client wants an international reference point
For what these requirements mean in practice — and what they do not cover — see Plain language requirements in the BC public sector.
Tools and formats
I work in Microsoft Word with tracked changes, Markdown and Git for version-controlled documentation, MadCap Flare and Adobe FrameMaker for structured authoring and single-source publishing, and Adobe Acrobat for tagged, accessible PDF output.
Deliverables come back in the format you sent, plus whatever else the project needs: DOCX, tagged PDF, Markdown, HTML, or a Flare project.
Selected work
Direct samples: BCIT Student Writing Guide for clear instructional sequencing and BCIT Students Guide to Legitimate Use of AI for reader-facing decision support. For task-based help material, see the BCIT Learning Hub Help Project.
- Selected writing projects — instructional guides and reference documentation, including student-facing writing and research guides produced for BCIT
- Policy analysis — eleven briefs on Canadian policy questions covering defence, energy, climate adaptation, housing, and inequality
- Selected infographics — information design work, for projects where the document is not the whole answer
For a procedural example built from scratch, see How to write an SOP that people actually follow, which includes a reusable template.
Enquiries
Available for contract and project work, and open to permanent roles in public sector communications. Engagements range from a single document to a full manual or documentation set.
Tell me what the document is, who has to use it, and when you need it back.