leaflets

For a service that has several types/branches (e.g. private vs public vs non-profit company, or any application-type branch), produce a clear, conceptual, plain-language "what each type IS" brief — derived by cross-reading the LAW (Act + Regulations) and the LIVE BPA service form branch, reconciling the two, and tracing every claim to a law section or a form component. Use before writing leaflets, manuals, training, or design docs for a multi-type service, or whenever you need a grounded conceptual model of each branch. Output is a per-type traced content map (the source of truth those artifacts consume). Generalises the OBFC leaflet method.

For a single (non-entity-type) service, produce a clear, conceptual, plain-language "what this service IS and how it works" brief — organised by the citizen journey (purpose → who it's for → what you provide → the steps → what you receive → obligations after) — derived by cross-reading the LAW/regulation and the LIVE BPA service and reconciling them, every claim traced to a law section or a form/flow component. Use before writing a leaflet, manual, or training for a service that has NO legal-form types to compare (a permit, a certificate, a filing, a registration). The journey counterpart to service-concept-brief. Output is a traced journey map (the source of truth those artifacts consume).

Build an applicant-facing leaflet (explainer page) for any online or government service, brand-matched to a target website, with an optional named voice guide that narrates the page (a fixed bubble: auto-scroll, highlight, captions, replay per section). Use whenever the user wants a public leaflet, explainer, one-pager, or guided walkthrough for a service or procedure, or wants to add a voice guide to such a page. Produces a self-contained HTML leaflet styled to match a site the user points to (URL or screenshots), plus an optional guided version, and can deploy both. Generalises an earlier single-registry leaflet builder.