Path: Home · Services · Technical writer in Vancouver, BC

Technical writer in Vancouver, BC

I write and edit the documents organizations depend on and nobody enjoys producing: procedures, policy, help content, course material, and the reference documentation that has to be right the first time.

Available for contract and project work across British Columbia, and open to permanent roles in public sector communications.

Start a conversation

What I do

WorkWhat it looks like
DocumentationUser guides, help systems, reference material, and knowledge bases. Structured authoring where the content is reused; plain Markdown where it is not.
Policy and procedurePolicy documents, operational guidelines, and standard operating procedures — written so the person doing the task can follow them without a second document open.
Plain language editingRewriting institutional prose for the people who have to act on it. Full service page.
Instructional designCourse outlines, learning objectives, eLearning content, and assessment material. A separate discipline from technical writing; I work in both.
Information designWhere the document is not the whole answer — diagrams, decision tables, and visual explainers.

Who I work with

Public sector and non-profit organizations, post-secondary institutions, and small technical teams without a writer of their own.

The common thread is a document with a reader who has no choice about reading it — a staff member following a procedure, a resident checking whether they qualify, a student trying to finish an assignment. That reader cannot be assumed to be motivated, and writing for them is a different job from marketing copy.

Background

  • Technical Writing Certificate, BCIT
  • MFA, University of British Columbia
  • BFA, University of Victoria
  • Educational content writer, BCIT — student-facing guides and learning material
  • Team lead (volunteer), BridgesPro Connect
  • Prior experience teaching ESL, which is where the plain-language habit started

Tools

Microsoft Word and the Microsoft 365 stack · Markdown and Git · MadCap Flare · Adobe FrameMaker · Adobe Acrobat for tagged, accessible PDF output · Adobe Creative Suite for information design

Deliverables come back in the format you sent, plus whatever else the project needs.

Standards

Every document is checked against the standards its audience is held to: the BC Web Style Guide and its Grade 8 reading-level target, WCAG 2.2 Level AA for accessibility, the Microsoft Style Guide for technical terminology, and Canadian spelling throughout.

For what those requirements mean in practice, see Plain language requirements in the BC public sector.

Selected work

Direct samples: BCIT Learning Hub Help Project for task-based documentation; BCIT Student Writing Guide for instructional content; and BCIT Students Guide to Legitimate Use of AI for research-based guidance.

Working together

Engagements run from a single document to a full manual or documentation set. Hourly, per-project, or retainer.

Remote or on-site in Metro Vancouver. Most documentation work is remote; process discovery sometimes is not.

First step is a conversation about what the document is, who has to use it, and what has to be true when they finish reading. That conversation costs nothing and usually shortens the project.

Get in touch