Plain Language Business Writing for Clear Public Documents Training Course

Course overview

Public-facing business documents often fail not because the underlying decision is wrong, but because readers cannot find the point, understand the terms, or act with confidence. Policies, service letters, consultation papers, customer notices, forms, web content, and decision summaries can become dense through internal jargon, legalistic phrasing, unexplained process language, and poorly ordered information. This course gives professionals a repeatable plain-language method for turning complex organisational content into clear documents that serve the public while retaining the necessary accuracy, authority, and governance controls.

Participants learn to analyse readers, define the action a document must enable, and structure information around real reader questions. They practise using the plain-language techniques that matter in business settings: purpose-first openings, informative headings, logical sequencing, active verbs, concrete wording, controlled sentence length, defined terms, scannable lists, and usable calls to action. The course also addresses the difficult work of simplifying regulated, technical, or policy-led content without changing meaning, omitting conditions, or making promises the organisation cannot keep.

Delivery combines instructor-led demonstrations, annotated before-and-after examples, peer review, and structured editing workshops using participants' own document types where appropriate. Each participant applies a diagnostic checklist, reader-task map, document architecture template, and editing workflow to a substantial public document. They leave with a revised plain-language document, an evidence-based rationale for key changes, and a practical plan for introducing clearer drafting and review practices in their team.

The course is suited to professionals who write, review, approve, publish, or govern communications for customers, citizens, members, service users, suppliers, or other non-specialist audiences. It is particularly valuable where unclear wording creates avoidable enquiries, complaints, compliance risk, delayed decisions, or uneven service delivery.

Course objectives

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

• Analyse audience needs, reading context, and required actions using a reader-task map
• Diagnose dense public documents with a plain-language diagnostic checklist
• Rewrite purpose statements, headings, and calls to action for immediate reader orientation
• Apply active voice, concrete verbs, and controlled sentence structure without losing accuracy
• Organise complex information with question-led structure, chunking, lists, and informative headings
• Translate policy, legal, and technical source material into clear reader-facing explanations
• Edit forms, letters, notices, and web copy for usability, consistency, and accessibility
• Produce a revised public document and a documented rationale for plain-language changes

Benefits of attending

Target competencies

Who should attend

• Communications Managers — who approve public communications and need consistent clarity across channels
• Policy Officers — who translate policy decisions into guidance, notices, and consultation materials
• Customer Service Managers — who need letters and service information that reduce avoidable contact
• Public Affairs and Engagement Officers — who prepare accessible consultation, campaign, and stakeholder documents
• Compliance and Governance Professionals — who must preserve required controls while making obligations understandable
• Subject-Matter Experts — who contribute technical content that non-specialist readers must use correctly

Requirements and prerequisites

This is a foundation-to-intermediate course and does not require previous plain-language training. Participants should be comfortable reading and revising routine business documents such as letters, policies, guidance, forms, emails, or web pages, and should understand the approval or publication process used in their organisation. Familiarity with Microsoft Word, including Track Changes and comments, is helpful because editing exercises use document-review conventions. A laptop is recommended for live document work. No legal drafting qualification, communications degree, readability-calculation experience, or specialist design software is required. Complete beginners should expect guided practice in editing at sentence, paragraph, and whole-document level.

Training methodology

The instructor models each technique on realistic public documents, including policy extracts, customer letters, forms, web guidance, and decision notices. Participants then work through short individual edits, paired peer reviews, and facilitated group critiques using a common plain-language checklist. Case studies focus on preserving essential conditions while improving reader comprehension and action. Throughout the week, participants progressively revise one substantial document of their own or a supplied equivalent. The final session includes a document clinic and an application-planning workshop that identifies priority documents, reviewers, quality checks, and measures for adoption.

Course outline

Day 1: Plain-language foundations and reader needs

• Plain language as a reader-action discipline
• Reader-task mapping for public documents
• Audience knowledge, motivation, and reading context
• Purpose-first document openings
• Identifying jargon, nominalisations, and institutional language
• Plain Language Action and Information Network guidelines
• Baseline document diagnosis with an editing checklist

Workshop: Participants diagnose a public notice and produce a reader-task map, purpose statement, and prioritised list of clarity problems.

Day 2: Clear sentences and usable wording

• Active voice and accountable sentence construction
• Concrete verbs and direct instructions
• Managing sentence length and clause load
• Replacing nominalisations with verbs
• Defining unavoidable technical and legal terms
• Writing conditions, exceptions, and deadlines clearly
• Using readability measures as diagnostic indicators

Workshop: Participants rewrite a dense eligibility letter, producing a tracked-changes version and a brief explanation of how meaning was preserved.

Day 3: Information design for public documents

• Question-led document architecture
• Informative headings and signposting
• Logical sequencing of actions, evidence, and consequences
• Chunking content into short purposeful sections
• Bullets, numbered procedures, and parallel construction
• Tables for comparisons, fees, and eligibility criteria
• Calls to action and contact routes

Workshop: Participants restructure a policy-based guidance document into a reader-centred outline with headings, action steps, and content priorities.

Day 4: Simplifying complex and controlled content

• Separating source material from reader-facing messages
• Translating legal and policy requirements without overclaiming
• Handling mandatory wording and controlled terminology
• Explaining process decisions and discretionary criteria
• Plain-language forms and evidence requests
• Accessibility considerations for digital documents
• Collaborative review with legal, policy, and subject experts

Workshop: Participants convert a technical policy extract into a public-facing guidance section while documenting mandatory content, assumptions, and unresolved approvals.

Day 5: Editing workflow and workplace application

• Microsoft Word Track Changes and comment-based review
• Adobe Acrobat Pro markup for PDF review
• Hemingway Editor and readability checks
• Plain-language quality assurance before publication
• Peer review protocols and editorial decision logs
• Measuring clarity through enquiries, errors, and completion rates
• Team style guides and implementation planning

Workshop: Participants complete a document clinic, submit a revised public document with an editorial rationale, and create a 30-day plain-language implementation plan.

Tools & standards covered

Microsoft Word, Adobe Acrobat Pro, Hemingway Editor, Plain Language Action and Information Network Federal Plain Language Guidelines

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