Delivery standards
The gates every project passes
Standards are only useful if they can be checked. These are written so you can ask for evidence at any time.
Quality gates
Written problem statement, named users, success measures and first journeys agreed by you.
Prototype tested with representative users; major issues fixed; build plan costed.
Each increment reviewed, tested, demonstrated in a preview and accepted by you.
Accessibility, security, performance and content checklist complete; rollback plan written.
Support plan agreed, monitoring in place, run-book handed over.
Standards across every level
- Accessibility target: WCAG 2.2 AA, tested automatically and manually.
- Second-engineer review on every code change.
- Personal data minimised and recorded in a data map.
- Secrets never stored in source code.
- Releases only during working hours.
- Weekly written progress reports.
Handover
Source code lives in your repository from day one. At handover, accounts are confirmed in your name, our access is removed, and you receive a run-book covering deployment, backups, restore and updates.