p.06 / Tolerances
How far we let things vary.
Our delivery standards, written as tolerances you can check. If we fall outside one, you are entitled to ask why.
- Scope
- A written scope before work begins: purpose, users, in, out, risks. Every change logged with time and cost effect before it is started.
- Reporting
- A weekly written note: done, next, blocked, decisions needed. Calls are followed by written summaries.
- Builds
- A version you can open on your own device at least every two weeks during active development.
- Code review
- Every change reviewed before merging. Automated tests protect important behaviour.
- Device testing
- Manual checks on real phones and current browsers before each release, including a slow-connection test.
- Accessibility
- WCAG 2.2 AA target, checked with keyboard, screen reader, zoom and contrast tools. Gaps documented.
- Security basics
- Least-privilege access, secrets out of code, dependencies updated, personal data minimised. We are not a certification body.
- Handover
- Repositories, accounts, credentials and documentation transferred, with a walkthrough for the next team.
- Candour
- Delays reported as soon as known. If we are the wrong fit, we say so.