Method & standards
Criteria first. Claims never.
Instead of achievements, here are the tests we expect our own work to pass, and the evidence you should receive for each.
The five criteria
| Criterion | The question | Evidence you receive |
|---|---|---|
| Usable for the job | Can the people it is for complete their main task without help? | Task walkthrough on the target devices, with notes on hesitations. |
| Accessible | Can people using keyboards, screen readers or larger text get through it? | Keyboard and screen-reader notes per key screen; known gaps listed. |
| Stable | Does it behave the same next week, on the devices that matter? | Device and browser list actually tested; defect log. |
| Honest in its messages | Does it tell users truthfully what happened, especially on errors? | Screens or copies of each error and confirmation message. |
| Owned by you | Could you carry on without us tomorrow? | Account, domain, code and file locations recorded in your name. |
Evidence matcher
Pick the type of work and the criteria you care about. The list below tells you what to ask any supplier for, including us. It is a local planning aid: nothing is sent or stored, it is not AI, and it is not a quote.
How a piece of work moves
Conversation
We agree what the work is for, who uses it and what "done" means, in writing.
Criteria
We pick which of the five criteria apply and what evidence will be produced.
Make and check
Work proceeds in short stages, each shown to you with its evidence attached.
Hand over
Files, accounts and notes move into your name, with the evidence pack.