User journeys

Audit a Government Permit Application

Published by whatisADA / Grow Wild Agency · Updated

Purpose and preparation

Review the permit process across instructions, eligibility, uploads, fees and submission status. Use a test environment and synthetic records. Include documents and external payment services within the chosen process.

A practical example

A resident reads the requirements, uploads a plan and corrects an address before reviewing a fee.

How to check it

  1. Map each page and document required to complete the permit. Check whether instructions explain accepted formats, prerequisites and expected information before entry.
  2. Complete the process with the keyboard and assistive technology. Test upload errors, conditional questions and saving or resuming the application.
  3. Review the submission summary and status route. Verify that confirmation identifies what was submitted and how to correct or follow up on a problem.

What can be missed

Auditing only public information pages misses authenticated forms and required documents. Scope the complete service journey and document any inaccessible dependency.

Record your test

Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.

These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.

Primary sources and scope

This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.