Safe and fast
is not a trade-off you have to make.
You choose which controls apply and who signs each one. A control you switch on cannot be skipped — the app stops there until your approver answers — and every yes and every no is recorded for an auditor: name, time, what it applied to.
Is this worth building?
Someone answers that first.
Every other tool starts you on a blank page. This one starts with a short form your company wrote, sent to the people your company says decide. It takes a minute to fill in, and it is the only step that can save you the entire build — because the question is not “can we do this?” but “should we, and who says so?”
- What is it
- Van safety checks
- Who is it for
- Our drivers · 40 people
- Why now
- Two vans went out unchecked last month
- How big
- Small
- What it uses
- Staff names and van records. No customer details.
every one of these
yes to her own
- 01Your questions, not oursYour company writes this form. We do not supply the questions, because a delivery depot and a hospital do not ask the same things before they spend money.
- 02It goes to the right people, in orderOne person, or several, in the order you choose. The second person is not asked until the first has answered. And the list of who decides is locked in the moment you send it, so nobody can change it halfway through.
- 03You cannot approve your ownThe person who asks is never the person who says yes. This is not a warning you can click past — if the two are the same person, the software simply refuses.
- 04It will not sit forgottenIf nobody answers, it moves on to the next person instead of dying in an inbox until you give up and go back to a spreadsheet.
- 05Or switch it offIf your company would rather people just start building, turn this off and they can. That is a real choice, and it gets written down like every other one.
The people, the company and the reference number here are made up. The form, the refusal to let you approve your own request, and the order people get asked in are real.
It does not move
until somebody says yes.
Here is one app going from a request on a phone to something the drivers are using. Each barrier is a real person or a real check, and it stays down until that person has looked at what they are approving. Seven hours, start to finish.
She has never written code.
Everyone who said yes
is named.
The people, the company and the app here are made up. Your company chooses which of these approvals it wants. The ones you switch on cannot be skipped — the software will not let anyone past them.
You choose who has to approve.
Then nobody can go around them.
Here is every point where your app can be stopped, and who stops it. Switch on the ones your company cares about and leave the rest off. Anything you switch on is enforced — it is not a rule in a document somebody can ignore, it is something the software will not let anyone past. Every yes and every no goes into one list.
Switch one on in watch mode
and see what it would
have stopped.
- The requestShould we build this at all?
- The planIs this the right plan?
- A person reads the workSomeone checks each change by hand.
- A computer reads it firstProblems get caught before a person looks.
- Is it what you asked for?Someone compares it to the plan.
- The testsEverything that worked still works.
- Someone tries to break inA report, tied to this exact version.
- The rules you work underA certificate for this version, this rulebook.
- Legal reads itSomeone checks what people are agreeing to.
- What it says to customersSomeone reads the wording people will see.
- Your team tries itIt goes somewhere real people can use it.
- Security problems block itA release waits while serious problems are open — and an app nobody has scanned is not cleared either.
- It goes liveEveryone gets it.
| When | What was checked | Result | Who | Details |
|---|---|---|---|---|
| 17 Apr · 09:12 | The request | Cleared | D. Okafor | Van safety checks — yes, worth building |
| 17 Apr · 14:31 | The plan | Cleared | R. Mehta | 12 checks, with photos |
| 18 Apr · 10:02 | The work | Cleared | Automatic | Nothing blocking, 3 things to tidy |
| 18 Apr · 11:47 | Security | Blocked | Automatic | 2 serious problems — release held |
| 19 Apr · 09:26 | Security | Cleared | Automatic | Both fixed. Nothing serious left |
| 19 Apr · 16:31 | Going live | Cleared | S. Grant | Approved this exact version |
These are the real checks, described in plain words. One detail worth knowing: the check that holds a release back is the security scan. The break-in test is a separate thing and does not, on its own, stop a release from going out. The people, the app and the times above are made up.
All of it fits in your hand.
Including saying no.
The same questions, the same stages, the same approvals. Start an app from the loading bay. Watch it get built on the train. Say yes to it going live from the back of a taxi — after reading exactly what is about to change.
The people, the app and the times here are made up. The screens, and the buttons they refuse to show you, are real.
Turn on the ones you need.
Leave the rest off.
A depot and a teaching hospital do not need the same approvals. Start with none of them and switch on what your company actually cares about — or run one in watch mode first and see what it would have stopped.