One hand-off
One point, and everything it touches.
Pick one hand-off in an operation you already run. The one where something goes wrong most often, or the one where the operation would stop if it did.
We write it down from the answers of the people who work it: what passes, who may act, on whose authority, and what has to be true first. Then we set those answers against each other.
Nothing from your systems. No agreements read, no data extract, no access.
A hand-off is where something passes and the next person must rely on it.
It may be goods, custody, an instruction, an inspection result, a valuation, an approval or a changed number. It may pass between firms, or between roles inside one of them.
At that point somebody acts or states a fact, and somebody else has to decide what it permits. The conditions between those two acts sit with different people, and there is rarely one place that holds them together.
Much of what goes wrong across firms becomes visible at a hand-off. The act itself looks ordinary. What follows from it may not.
It is the smallest part of an operation that can be reconstructed precisely enough to test what it requires and what it changes.
What a single point looks like when it is written down.
Release, in a financed cargo. Eight parties, at one moment, on the left. One hand-off inside it, on the right.
The moment
Release
- SellerActs here
- BuyerPosition affected
- InspectorNot present
- Warehousegives
- Collateral managerActs here
- BankActs here
- InsurerPosition affected
- Carrierreceives
The hand-off
What the carrier is relying on
- A release instruction from the bankstated
- The inspected weight and identity of the goodsstated
- That the allocation is still in forceassumed
- That nobody else has a claim on the same parcelassumed
Whose position moves, and is not here
The buyer may now expect delivery. The insurer may need the change in custody reflected. Both are told when the report runs.
Five of the eight act. Two have their position moved by a decision they take no part in. One is not there at all.
Your review replaces this illustration with one hand-off from your own operation: the giver, the receiver, what is relied on, and the positions changed by the result.
Four documents, including the questions that stay open.
- The hand-off, written out.
- What passes, who may act, on whose authority, who has to accept it, whose sign-off makes it stand, against which evidence, what state has to be agreed before and what state is true after. One page, and it is the thing that did not exist.
- What could not be answered.
- A hand-off has to establish a set of things before it can be relied on, and this separates what your people can confirm, what is assumed, and what stays open. It is not a score and it is not a criticism: nobody has been asked these questions before.
- What it consumes, and what it feeds.
- The facts this point takes in, the facts it produces, and every later act that cannot proceed without one of them. Including acts by parties you do not employ, and acts that happen after the goods have left.
- What it should refuse.
- Six or eight sequences this point should never permit, written so that somebody could check whether it does.
All four are yours, including the questions.
What a hand-off has to establish
For the point you choose, the account has to answer all of them. What comes back separates what your people can confirm, what is assumed, and what stays open.
| What has to be established | For example |
|---|---|
| What is being decided | Release 920 tonnes. Approve a drawdown. Accept a revised certificate. |
| What the decision concerns | The goods, the quantity, the lot, the location, the value, the facility, the claim. |
| Who acts, who must accept, whose sign-off is needed, and who is only told | Four different positions. A party treated as told when it should be accepting is the common one. |
| What must be true first | A current inspection, security in force, notice received, quantity reconciled. And that the parcel itself is still unallocated and available to act on. |
| What proves it | A certificate, an instruction, a warehouse record, an approval, a policy confirmation. |
| Whether the proof is current | Its version, its issuer, its date, its expiry, and whether it has been superseded. |
| Whether it was still true at the moment of acting | Checked at nine, acted at three, changed at eleven. Where nothing is re-checked before acting, the last person to act wins and nothing reconciles. |
| What must never be true | Release above the confirmed quantity. Drawdown against lapsed evidence. Two conflicting instructions standing at once. |
| What happens if it is not satisfied | Refuse, hold, escalate, correct, notify, reassess. |
| What changes next | The permitted quantity, the secured value, the release status, an obligation to notify. |
| Whose position is affected by the result | The bank, the buyer, the insurer, the warehouse, the carrier, the seller. |
| Who must not see it | The warehouse and the financing terms. The carrier and the price. Where nothing states it, the answer defaults to whoever was on the email. |
| What happens when somebody new has to be brought in | A new bank, a new warehouse, a new insurer at the same point. Whether the arrangement absorbs them or has to be rebuilt is worth knowing before the one more arrives. |
Two of them turn a local instruction into a control point: whether the evidence is still current, and whose position changes when the result changes.
They are in the order a reliable workflow would have to answer them before permitting the next act. Nothing runs for this and no system is needed. If the operation is modelled or built later, the account already names the information, the evidence, the conditions and the refusals that any design would have to carry.
Three more that only appear under load
Those are what a hand-off has to establish on an ordinary day. These three are what breaks on a bad one. Nothing tests them while things are calm, so an operation can run for years without knowing whether it has them.
| What also has to hold | What it looks like when it is not there |
|---|---|
| Where the fact came from, all the way back | A certificate proves a weight. What proves the certificate, and the intake before it, and the title before that? Asked in diligence, answered with a folder and somebody’s memory. |
| That it can happen only once | Two releases against the same parcel, or two drawdowns against the same collateral. Each looks correct on its own, and nothing compares them until somebody reconciles. |
| The moment after which it cannot be overtaken | Until that moment is named, a conflicting instruction can still arrive and there is no rule for which one stands. Ask your own people when a release becomes final and see whether the answers agree. |
What the comparison can show.
Whose position changes when this point changes, including parties that do not control the decision, and who relies on the result without being told when it has changed.
And where two of your own people answered the same question differently. Neither of them is wrong about their own side. Neither can discover it alone, because each already knows their own answer.
People describe the part they run. Comparing those accounts is what shows where they do not yet meet.
What changes
| Today | Afterwards |
|---|---|
| We normally do it this way. | The sequence and the conditions are written down. |
| Authority sits in habit, in an email, or in what one person knows. | The act and the evidence that permits it are named. |
| A revised fact looks local. | What else it reaches is visible. |
| A proposed change is assessed from memory. | It can be set against something. |
| What nobody knows stays invisible. | Confirmed facts, assumptions and open questions are separated. |
Four things to do with them on the Tuesday after.
The review does not tell you that a hand-off is safe. It gives you an account against which the next one can be checked.
- Hand it to somebody.
- A new person, a counterparty asking questions, a lender doing diligence. Today that answer is assembled from whoever is available and remembers.
- Set a change against it.
- A new warehouse at that point, a different release condition, a counterparty on other terms. There is now something to test it against instead of memory.
- Close what was found.
- Two people disagreeing about when responsibility moves is a real exposure with a real fix. A party told at month end is a notification somebody can change on Monday.
- Do the next one yourselves.
- You keep the questions. Putting them to the second hand-off costs you nothing, and the answers are comparable with the first because they are the same questions.
A proposed warehouse, release condition, revised certificate or facility term can then be set against something more exact than memory. The result may be to proceed, to proceed with conditions, to obtain a confirmation first, or not to proceed yet.
If everyone agrees, everyone is told and nothing is assumed, you have paid to establish that one point is well described. That is a real outcome and it is the one nobody can tell you in advance.
What each of these is worth on an ordinary Tuesday
Nothing here needs a system. Each row is something an operation either has or does not, and each is answerable by asking.
| What has to hold | What it means in the week |
|---|---|
| The obligated party agreed | The insurer agreed before its exposure moved, and not at month end. |
| Everyone affected was told | The bank knows its borrowing base changed on the day it changed. |
| The condition held first | It did not go ahead and get sorted out later. |
| The fact traces to its origin | A diligence question is answered in an hour instead of a week. |
| It happened once | Two releases against one parcel cannot both look right. |
| It was inside a stated window | Recent is a date somebody can check, and not a feeling. |
| Finality is a named moment | Everybody agrees when it is too late to stop, before it is too late to stop. |
How this would run.
- You pick the hand-off and answer the intake sheet, which is written in the order the answers matter.
- We work through the account with the people who run the point, remote or on site. Where the same question matters to more than one of them, we ask it separately before comparing the answers.
- We write it up and hand back the four documents.
- This is a worked example and not something we sell on its own. Where it is what somebody needs, we agree it as a piece of work; otherwise it is here to show what the questions produce.
Nothing is installed, nothing runs afterwards, and there is nothing to maintain.
It describes one point and names its edges.
- It does not check whether anything is true in the world. We record what your people say and set those answers against each other. Where the answers are wrong, the account is wrong in the same way, and we say where we saw a gap.
- It covers one hand-off. What the points it touches themselves depend on is the whole operation, and that is a different piece of work.
- Nothing runs. Nothing is installed and nothing connects to your systems.
- It promises no saving and no better terms. It makes one point legible, and what that is worth is yours to judge.
It has a purpose where an unclear answer at that point could delay a shipment, expose collateral, invalidate a condition, or make a proposed arrangement harder to assess.
Where the point is routine, carries no real transfer of authority, evidence or consequence, and is not changing, there may be little here worth buying. We will say so.
One point is a specimen. An operation has sixty-five of them, and a change you are about to commit to will touch more than one.