Reference · Level 2 · one of the five
Logistics: every delivery, every exception, and proof that it arrived
Trips and their progress, stock on hand with the reorder lines that matter, and the exceptions - late, damaged, refused - each with the one action that closes it. Proof of delivery is kept with the order, not in a driver's phone.
Part of the OwnYourAI corporate AI training reference. Deliveries, stock and the exceptions that eat the day - with proof of delivery kept where you can find it.
A quick look at what you can build: three screens showing the shape of the system and what it does, on illustrative data. No client's system and no client's data is shown. It is fair to want to see the work before you commit a seat.
Three screens
What the people who use it see
Same system, three moments in a working week.
Why the AI version
Why the AI version of logistics
A stock list is only as good as the last time somebody updated it.
- What it costs you now. Stock gets counted and reordered when someone remembers, and the item that runs out is the urgent one.
- With the AI version. One sentence - what do we need to reorder this week - and the items under the reorder point come back with quantities, the supplier to use and what it will cost.
- The part your current software cannot do. It lists what is in the racks. This reads the delivery notes, the job sheets and the supplier terms, and decides what to order.
Behind the screens
What the course actually builds
The screens are the easy part to look at. This is the part that decides whether the system survives its first month - and the software and the data are the company's own. The machine under it is one we provide or recommend, so there is no hardware to buy; owning the whole thing is Level 3.
- The whole day on one page. Trips, stops and progress - no ringing around to find out where a vehicle is.
- Reorder before you run out. Stock levels against reorder points, with the shortfall listed by item.
- Exceptions with an owner. Every late, damaged or refused delivery lands on a named person's list.
- Proof kept with the order. Time, who received it, and the signature or photo, stored against the delivery.
Session by session
The 8 sessions: building the delivery and stock system
Every session is online learning at the person's own pace, with a scheduled live touchpoint inside it and a trainer present. Each one ends with something your company keeps: 24 hours in total for L2.
| # | The session | What your team does with it | What your company has at the end |
|---|---|---|---|
| 1 | Pick the job | The delivery day, the reorder list and the proof-of-delivery chase are put side by side, with what each costs the team every week in time and in phone calls. | One job chosen, with the cost of it written down. |
| 2 | Map the trips and the stock | Trip sheets, delivery notes, stock levels, reorder points and the customer's own instructions on where to leave things. | A one-page map of where each record lives, plus the do-not-enter list. |
| 3 | Write the brief, and the three limits | What the agent does — hold the day on one page, list the shortfall, chase the proof — and what it never does. | A signed brief: it never closes a delivery without proof, it never promises a customer a time it cannot see, and it never moves stock on its own. |
| 4 | Build the day view | Trips, stops and progress on one page, and the shortfall list built from the company's own reorder points. | A first working version running on the company's own trips and stock. |
| 5 | Test it against a real day | Yesterday's runs are replayed: what it saw, what it missed, and how long each exception sat before someone owned it. | The difference list against one real day. |
| 6 | Guard it | Who may change a delivery status, what a customer sees, what is logged, and what must always be confirmed by a person. | The access list, the log, and the rule for anything that faces a customer. |
| 7 | Put it into the day's routine | The morning dispatch list, the end-of-day exceptions, and the weekly reorder. | The daily and weekly routine on one page, with a named owner for each step. |
| 8 | The build assessment | A real day is run live, with the exception list in front of the trainer. | A running delivery and stock system: the agent, its brief, its limits, its log, and a named owner. |
Where these screens come from
A quick look at what you can build: three screens showing the shape of the system and what it does, on illustrative data. No client's system and no client's data is shown.
Built in the company's own accounts, on the company's own documents, with its own staff logins: the software and the data stay with the company. The machine under it is one we provide or recommend - no hardware to buy. Owning the whole thing is Level 3.
We keep it fair: your documents, your accounts, your numbers.
Next step
Start with the free AI Readiness Report
Tell us the team and the work. We send back a written report on what to build first, what it would take, and what it would change - before you commit to a single seat.
No fee is quoted until you ask for one.