Follow the whole journey.
Identify who starts the task, what they need, and what a successful result looks like. Check the complete journey, including confirmation and any downstream update.
Proof
Quality should be something you can check.
A convincing delivery is more than a presentation. Agree what should work, review it in use, and make sure the knowledge needed to run it comes with it.
Download the review checklist
01 / Agree the outcome
Make “done”
concrete.
A feature list describes what to build. Acceptance criteria describe how you will know it works. The checks should reflect your users and your actual workflow.
Check who can do what.
Define the roles, which records each role can see, and which actions require permission. Review access through both the interface and the underlying service.
Plan for the awkward case.
Decide how missing information, duplicate requests, lost connections, and unavailable services should behave. Give users a clear next step when a task cannot finish.
Use the right conditions.
Agree relevant devices, browsers, accessibility needs, data volumes, and integration environments. Those conditions belong in the review plan and project scope.
02 / Review working software
Show the behavior.
Explain the decisions.
A review should leave you able to make an informed decision about the next step.
Walk through agreed scenarios.
Use a working version and the acceptance criteria. Review the main task and relevant exceptions. Record which behaviors are accepted and which need another pass.
Keep the open items visible.
Separate defects, product decisions, and new requests. Describe their effect on priorities, timing, and cost before changing the delivery expectation.
Before a release
- Confirm the agreed workflows and relevant regression checks
- Review permissions, configuration, and any data migration
- Identify outstanding items and who accepts them
- Agree the launch steps, monitoring, and rollback path
03 / Make the delivery usable
The software.
And the knowledge.
Agree the handover contents in the proposal, then review them alongside the product.
- Code & access
Repository access, relevant account responsibilities, ownership terms, and third-party license information.
- Setup & deployment
Build instructions, configuration requirements, environment responsibilities, and the release procedure.
- Operating notes
Relevant monitoring, backup and recovery arrangements, integration dependencies, and how to investigate a failed task.
- Decisions & next steps
Important architectural choices, known limitations, unresolved items, and the agreed support or maintenance arrangement.
A useful conversation tool
Bring a checklist.
Leave with clarity.
Use our project review checklist to discuss scope, reviews, release readiness, and handover.
It is a practical guide for planning a project together. The requirements and commercial commitments for your project are agreed in its proposal.
Let’s talk software
Let’s agree what good looks like.
Bring your workflow and the result you need. We can turn those into clear priorities and a reviewable first scope.