A clear path from discovery to everyday use
Each stage produces something that can be reviewed. Scope, responsibilities and acceptance conditions are agreed before development.
- Audit
- Process design
- Custom tool
- Local installation
- Documentation
- Training
- Maintenance
| Stage | What happens | Deliverable to agree |
|---|---|---|
| 01Audit | Understand the workflow, sources, exceptions and effort involved. Check whether a new tool is justified. | Process map, priority issues, feasibility, scope and exclusions |
| 02Process design | Agree rules, inputs, outputs, interface and validation steps. | Specification, prototype where useful, acceptance criteria |
| 03Custom tool | Build incrementally using synthetic data or an authorised, prepared test dataset. | Testable version and verification results |
| 04Local installation | Set up the solution in the agreed environment with explicit requirements and dependencies. | Installation procedure, configuration, functional test |
| 05Documentation | Document usage, rules, errors and operational tasks. | User and operating guide, known limitations |
| 06Training | Walk through routine tasks and exceptions with the people who will use the tool. | Session and materials in the agreed format |
| 07Maintenance | Agree support, updates and scope changes separately. | Support agreement covering responsibilities, costs and conditions |
The client’s role
The client assigns a process owner, validates sources and outputs, and involves IT, security or legal reviewers where required.
Timing and cost
Timing and cost depend on scope. A defined workflow and a discovery stage provide a practical starting point.