Start with a task and a decision.
“Public Works” identifies an organization. “Report a damaged street sign” identifies something a resident can do. A service page should own that task even when several departments contribute to delivery. Department pages can explain responsibilities and link to the service; they should not maintain competing versions of the same instructions.
Write the intended outcome before designing the layout: a person can distinguish a routine sign report from an urgent hazard, understand the location information needed, submit through the approved channel and recognize the acknowledgement. This is the page’s testable purpose. A prominent button alone does not establish that the service works.
The GOV.UK start-page pattern (opens in a new tab) provides a useful reference for introducing a transaction. It is UK service-design guidance. The municipal pattern below is an original planning example, with local requirements supplied by the agency.
Give each part of the page a job.
| Page element | Question it answers | Evidence to collect |
|---|---|---|
| Task title and introduction | Is this the service I need? | Resident terminology and defined service boundary. |
| Eligibility and exclusions | Does it cover my situation and location? | Approved jurisdiction, conditions and alternate routes. |
| Before you start | What information or documents will I need? | Only the fields required by the receiving team. |
| Fees and timing | What does it cost and what can I expect? | Current approved fees and carefully defined response expectations. |
| Start and assisted route | How do I act, including without the online form? | Tested destination, opening hours and support arrangements. |
| After submission | Who handles it and how will I hear back? | Acknowledgement, ownership and update process. |
| Owner and review record | Who keeps these instructions accurate? | Service fact owner, source and review trigger. |
On a small screen, scroll the table sideways to see every column.
Put a consequential exclusion before the start action. Place details needed for the next step beside that step. Use descriptive headings and labels that still make sense when someone scans them out of order. Avoid turning every sentence into a collapsible section; readers should see the information that determines whether to proceed.
Worked example: reporting a damaged sign.
Fictional Cedar Bay example, not an operating municipal service. The sample page title is “Report a damaged street sign.” Its opening says: “Use this service for damaged or unreadable street-name signs maintained by Cedar Bay. Describe where the sign is and what is wrong.” The actual agency must supply its own approved boundary and urgent-contact wording before use.
The “Before you start” section asks for a street or intersection, a description of the sign and the observed damage. A photo is optional. Contact information is requested only when the service has an approved reason for it, with an explanation of how staff will use it. An account is not added merely to make the page look like a portal.
The after-submission text explains that acknowledgement confirms receipt. A service team still needs to accept the work and assess the reported condition. The page does not invent a repair deadline or imply that submitting a form guarantees replacement. A status route, if offered, must work for the people who use the service.
The page’s source record points to the responsible team’s approved intake procedure. Its owner checks the destination whenever routing changes. This connects the public instructions to the staff handoff and closure process.
Keep the answer usable on a small screen.
Place the core instructions in HTML so residents can read them without opening a file. Attachments may support the task, but the landing page should explain their purpose, date and format. Compare the alternatives in the HTML versus PDF decision guide.
Check heading order, visible keyboard focus, link wording, text resizing, contrast and error explanations in the actual implementation. Do not put the only version of an address, deadline or instruction inside a decorative image. If an external form opens in another system, explain that transition and test the return path.
The same source facts should support translated versions. A translation button that leads to the homepage loses the task context. Link equivalent service pages and record which source revision each language reflects.

Test understanding before counting clicks.
Ask a likely user to describe which situations the service covers, identify what they need and show where they would start. Let them use their usual device and avoid naming the navigation label you want them to choose. Observe wrong turns and uncertainty as well as completion.
Record whether success was independent, assisted or not completed. If people click the start button but cannot determine eligibility, the page has not answered the preceding question. Use the usability protocol and observation worksheet to turn observations into revisions.
Keep the published URL stable when the page is improved. Track the page in the content audit and assign an owner for every important fact. When planning a redesign, ask a provider to demonstrate this entire service journey, including the form and acknowledgement, rather than showing only a homepage.


