Practice — Tolerances
Tolerances
Our delivery standards, stated as tolerances: the limits within which we consider work acceptable. They are our own commitments, not third-party certifications.
If work falls outside a tolerance, we report it, explain the cause and propose a correction.
- Definition of done
- Built, peer-reviewed, tested, accessible, demonstrated and documented. Anything short of this is reported as in progress.
- Automated tests
- Run on every change. Critical journeys covered end to end. A failing test blocks release.
- Manual testing
- Against a device and browser matrix agreed in writing beforehand.
- Accessibility
- WCAG 2.2 AA target. Known exceptions listed in the handover with remediation notes.
- Security
- No secrets in source control; least-privilege access; dependency scanning; access revoked on exit.
- Personal data
- Collected only when needed; retention and processors documented.
- Estimates
- Given as ranges with stated assumptions; revised when assumptions change.
- Reporting
- Written update per cycle: completed, in progress, blocked, decisions needed.
- Releases
- Repeatable, scripted, with a written rollback procedure.
- Handover
- Code, designs, credentials and documentation transferred to client control.
Instrument
Check the balance before you commit
Most delivery problems are visible on day one if scope, finish and time are weighed honestly.