All BlueprintsLogistics
Tool and asset checkout
A tool store for a small builder's yard. Every drill, ladder and transformer is an individual thing with a tag, the store can say who is holding it and since when, and what has not come back is on one screen before somebody needs it.
What you’ll build.
A sign-out system for tools and kit. Anybody signs a tool out in their own name, hands back one that was never theirs, or passes it straight to somebody else on site with a photo of the state it was in. A broken tool leaves the pool without losing its history. The storekeeper sees what is not back yet with a name against every line.
What you’ll learn.
Each sprint is built around one skill. You show you have it in a pull request your team reviews, then explain it in a walkthrough.
Authentication
You can register and sign in a user, keep a request authenticated without asking for the password again, and explain where the credential lives in the browser and why there rather than somewhere else.
Assigning jobs to drivers
You can assign a job to a driver, prevent the same job being assigned twice, and show a driver only their own work.
Roles and permissions
You can give users different roles and have the server refuse what a role may not do — not merely hide the button — and show the refusal working against a request the interface never offered.
Proof of delivery
You can capture proof at the point of delivery, store it against the shipment, and produce it later in a dispute.
An order that moves through states
You can move an order through its states, refuse a transition that should not happen, and show the history of how it got where it is.
Notifications people do not mute
You can notify a user when an event concerns them, show an unread count that survives a refresh, and honour a preference that says stop.
Background jobs
You can hand work to a worker, tell the user it is in progress, and show the result when it lands — and say what happens to that work if the process dies halfway.
Going live
Somebody who has never met you can open a URL and use the product — and you can say what is different about the copy running there, where its secrets come from, and what you do when a release turns out to be wrong.
The roadmap. 8 sprints, 39 tasks.
Every sprint has a goal and a set of tasks. Open a sprint to see the tasks you will pick up.
Who is who
The yard's people have accounts, signing out on the counter tablet means something, and the store's own account is not one anybody can issue themselves.
4 tasks
- Somebody who works at the yard can make an account and come back to it
- Signing out at the counter ends that session for good
- A person can end every session they have open from one place
- The storekeeper's account is a different kind, and cannot be self-issued
The yard's kit
Every piece of kit exists one item at a time with its own tag, anybody can look one up and see who has it, and signing one out puts exactly one name against it.
5 tasks
- The storekeeper puts the yard's kit on the register, one item at a time
- Anybody can look a tool up and see who has it
- Signing a tool out puts one name against it
- Two people cannot end up holding the same tool
- A person can see everything they are holding
Back over the counter
A tool comes back and the custody it ends belongs to whoever was holding it, even when the person at the counter is somebody else entirely.
5 tasks
- Handing a tool back puts it in the store again
- A tool can be handed in by somebody who never took it out
- The storekeeper can issue kit to a named person, and the record says who did it
- The limits hold against a request the screens never offered
- A tool cannot be handed in twice
Handed over on site
Custody passes straight from one person to another without the tool coming back to the store, and the moment it changed hands carries a photograph of the state it was in.
5 tasks
- A tool passes from one person to another without coming back to the yard
- Until the other person takes it, the tool is still yours
- A photograph of the tool is taken as it changes hands
- A handover whose photograph never arrived is still a handover
- A tool's history reads as a chain of hands
What does not come back
A tool that is broken, away being repaired or gone for good leaves the pool without leaving the record, and nothing about its past is overwritten.
5 tasks
- A tool handed back broken stops being offered, and says why
- A tool goes away for repair and comes back into the pool
- A tool nobody can find is written off, and the trail ends at a name
- Nothing about a tool's past is written over
- A move that makes no sense is refused
Not back yet
Everything signed out has a day it is due back, what is past that day is on one screen with a name against it, and the person holding it is told while they can still do something about it.
5 tasks
- Everything signed out has a day it is due back
- One screen shows what is not back yet, worst first
- The person holding it is told, and the message is still true when it is opened
- A tool kept longer on purpose is not the same as one that is late
- Somebody's last day is a due date
Nobody in the yard at seven
What is overdue is worked out and chased every morning with nobody pressing anything, exactly once per tool per day, and a sweep that fails is something somebody can see.
5 tasks
- The overdue list is worked out before anybody is in the yard
- Run it three times, and somebody hears about their drill once
- A run that was missed catches up without shouting
- A sweep that stopped running is something somebody notices
- A message that never arrived does not look like one that did
Where the whole yard can reach it
It is on the internet at its own address, sweeping every morning, and a builder can sign kit out from the gate.
5 tasks
- A builder signs kit out from the gate, on their own phone
- Settings and secrets live where it runs
- Seven in the morning happens with the yard locked
- The photographs survive a release
- A bad release goes back without losing who had what
Read before you build. The best engineers do.
Senior engineers read the docs before they touch the code. Every Blueprint comes with short documents on the product and its world, the kind a team hands a new hire. Read them well and you ask sharper questions and walk into every review prepared.
What you are building
The product, who it is for, and what finished means.
What custody means
One thing, one name, at every moment: the claim the whole product is built to keep true.
More logistics Blueprints.
Returns handling
The returns desk behind a small shop. A customer asks to send something back and says why, the warehouse answers, a parcel turns up that may not match either, and somebody has to decide what happens to the goods and to the money before either can end up in the wrong place.
Fleet maintenance log
A servicing log for a small fleet: every van's history in one place, the next service worked out from how fast that van is actually being driven, and what is due soon and what is already overdue on the front page.
Warehouse picking list
Picking for one warehouse: an order becomes a route through the shelves, a picker walks it on a handheld, and everything that goes wrong halfway down the list is recorded rather than quietly shipped.
Build tool and asset checkout.
Start your free week. Adaeze runs your kickoff, and Lars reviews every pull request.