Service guides / Web & mobile apps
Acceptance checklist · Web & mobile appsService request portals: acceptance checklist
Define how to recognise a usable result. Start with request categories and assignment rules and plan a request submission and progress view.
Available remotely for local and international enquiries. Platform choice and final scope depend on your requirements.
The project in view
- Start with
- request categories and assignment rules.
- Proposed result
- a request submission and progress view.
- A decision to resolve
- updates without clear ownership.
This is a planning example. It does not describe a completed client engagement.
Acceptance checklist for this project
- Check the main journey on agreed screen sizes, with keyboard access, slow connections and failed submissions.
- Write the expected content and format of a request submission and progress view against one agreed sample.
- Include a failing example involving updates without clear ownership, and agree the correct response.
Questions to answer together
- What is the expected result for one agreed example?
- Which edge cases must pass before signoff?
- Who accepts the result, and where is that decision recorded?
What to have at the end
A repeatable acceptance pack with examples, expected outcomes and signoff criteria.
Record the decision on updates without clear ownership alongside the source material. If it is still unresolved, identify who can answer it and what work depends on the answer.
Prepare your enquiry
Use this as a starting point. Add your current process, available examples and constraints before sharing.
Send your completed brief to hello@iansamonte.com or visit the main page to discuss your project.