Before the discussion
- Choose the public task and intended office.
- List current tools and approved public examples.
- Identify meeting or operating dates.
Prepare a public website change the office can maintain.
Use this list for a defined service page, archive or request-routing project.
Before development
- Confirm publication, records, privacy and accessibility review.
- Agree on fields, roles and maintenance owners.
- Define the useful result and a recovery option.
Before publication
- Check mobile pages, keyboard use and document routes.
- Try fictional unclear, duplicate and failed requests.
- Keep tests separate from real requests and public alerts.
- Verify receipt wording and staff follow-up.
At handover
- Confirm account, code and documentation ownership.
- Assign routine content reviews and unresolved work.
- Document connection care and any ongoing support.