Plain Language Business Writing for Clear Public Documents Training Course

Course overview

Public-facing business documents often fail at the point of use: residents cannot complete a form, customers misunderstand eligibility rules, suppliers miss submission requirements, or staff spend hours explaining letters that should have been clear on first reading. Dense sentences, undefined terms, passive constructions and poorly ordered information create avoidable enquiries, complaints, delays and compliance risk. This course equips professionals to turn policy-led, technical or procedural content into documents people can find, understand and act on.

Participants learn a disciplined plain-language method for letters, forms, notices, web content, guidance notes, reports and consultation documents. They diagnose readability and usability problems; define audience needs and document purpose; organise information around user tasks; write direct sentences; control terminology; use headings, lists and signposting; and test whether a document supports accurate action. The course also addresses the judgement required when legal, regulatory or technical wording must be retained, including how to explain it without changing its meaning.

Delivery combines instructor-led demonstrations, annotated before-and-after examples, individual rewriting practice and team editorial reviews. Participants work on realistic public-document cases and, where suitable, bring a live document from their organisation. They leave with a revised document or document section, a plain-language editing checklist, a reader-testing plan and an implementation brief that identifies priority documents, owners, review stages and measures of improvement.

The course is designed for professionals who write, review, approve or publish documents for customers, citizens, service users, suppliers or internal operational audiences. It is particularly valuable where documents must be clear while remaining accurate, consistent with policy and defensible under scrutiny.

Course objectives

By the end of this course, participants will be able to:

• Apply a plain-language diagnostic to identify audience, purpose, task, risk and readability barriers in a public document
• Rewrite policy-heavy sentences using active voice, concrete verbs, logical sentence order and controlled sentence length
• Structure a letter, notice or guidance document around reader questions and required actions
• Create headings, summaries, lists and signposts that improve document scanning and navigation
• Translate technical, legal and administrative terminology into accurate reader-centred explanations
• Use readability measures and usability checks to assess whether a document can be understood and acted upon
• Conduct a structured peer edit using a plain-language checklist and tracked-change rationale
• Produce a plain-language improvement plan for a priority organisational document set

Benefits of attending

Target competencies

Who should attend

• Communications Officers — who publish public information and need readers to understand messages without follow-up
• Policy Officers — who convert policy decisions into guidance, notices and consultation material
• Customer Service Managers — who need letters and service instructions to reduce avoidable contact
• Regulatory and Compliance Officers — who must communicate requirements accurately without unnecessary legalistic language
• Programme and Project Managers — who prepare stakeholder updates, application materials and operational guidance
• Business Support and Administrative Professionals — who draft forms, procedures and standard correspondence for varied audiences

Requirements and prerequisites

This is a foundation-to-intermediate course and does not require prior plain-language training. Participants should be comfortable drafting and revising business documents in Microsoft Word and should have experience reading or producing workplace communications such as letters, guidance, reports, forms or emails. Familiarity with their organisation’s approval process, style guide or regulatory context is useful but not essential. A laptop with Microsoft Word is recommended for editing exercises and for working on a live document. No legal drafting qualification, formal linguistics knowledge, readability-statistics expertise or specialist design software is required.

Training methodology

The instructor models a practical diagnose–redesign–draft–test method using public letters, eligibility guidance, forms and service notices. Short teaching segments introduce each technique, followed by marked-up rewrite drills in Microsoft Word, paired reader tests and group editorial decisions on realistic cases. Participants compare alternative versions against audience tasks, policy constraints and readability evidence rather than personal preference. Daily feedback builds toward a final document clinic, where each participant completes a revised document section and a workplace implementation plan.

Course outline

Day 1: Diagnosing clarity and reader needs

• The plain-language method: diagnose, redesign, draft and test
• Audience segmentation and reader task mapping
• Purpose statements and action-focused document objectives
• Document risk assessment for high-volume and high-consequence communications
• Reader questions as an information-planning tool
• Plain-language principles in ISO 24495-1:2023
• Baseline document audit using a clarity diagnostic

Workshop: Participants audit a public-facing letter or guidance extract and produce a reader-task map with prioritised clarity issues.

Day 2: Writing direct, accurate sentences

• Active voice and accountable actors
• Concrete verbs and operational instructions
• Sentence length, clause control and logical sequencing
• Front-loading conditions, dates, decisions and required actions
• Replacing nominalisations and abstract administrative language
• Managing modality: must, should, may and will
• Explaining legal and technical terms without altering meaning

Workshop: Participants rewrite a policy-derived notice in tracked changes and annotate each revision with its accuracy and usability rationale.

Day 3: Structuring documents for action

• Inverted-pyramid ordering for public communications
• Question-based headings and descriptive subheadings
• Chunking information into reader-sized sections
• Bullets, numbered steps and decision tables
• Callouts for deadlines, eligibility criteria and exceptions
• Signposting evidence, contacts and next steps
• Form instructions and error-prevention wording

Workshop: Teams redesign a dense service guidance page into a task-based outline, navigation scheme and action checklist.

Day 4: Testing readability and usability

• Readability formulas and their limitations
• Microsoft Word readability statistics and document checks
• Hemingway Editor as a sentence-complexity diagnostic
• Plain-language checklist scoring
• Five-question reader testing protocol
• Peer-edit roles, tracked changes and editorial decision logs
• Accessibility considerations for headings, links and meaningful labels

Workshop: Participants run a peer reader test on a revised document and produce an evidence-based list of final editing actions.

Day 5: Embedding a plain-language practice

• Selecting priority documents by volume, risk and user impact
• Plain-language governance within drafting and approval workflows
• Terminology lists and approved explanations
• Templates, style sheets and reusable document patterns
• Working with legal, policy and subject-matter reviewers
• Measures for enquiries, completion errors and reader success
• Ninety-day plain-language implementation planning

Workshop: Participants complete a document clinic and present a revised document section, editorial checklist and 90-day implementation plan.

Tools & standards covered

Microsoft Word, Adobe Acrobat Pro, Hemingway Editor, ISO 24495-1:2023

A typical training day

Live online deliveries follow the same structure in the East Africa Time zone, with shorter screen blocks and longer breaks.

What the fee includes

How you can take this course

Certification

Participants who complete the full five days receive the Skillset Development Certificate of Completion, stating the course title, course code, dates and delivery format — suitable for professional-development records and employer reimbursement.

Frequently asked questions