The Proof Before
You Let Go
Your Delegate earns trust by leaving a record of what happened, what it recovered, and what it knew to bring back to you.
Go back a month from The Check You Skip. You’re still teaching pottery at six on Thursdays, and you’re right to open the roster. Your Delegate has sent the door instructions for the first time. You open the booking record to see what actually happened.
Twelve messages went out. Eleven students have acknowledged the instructions. The twelfth message bounced. If the Delegate says all twelve were notified, the problem isn’t that an address failed. That happens on ordinary Thursdays. The problem is that the Delegate counted an attempt as a result. You would still have to be the person who knew the difference.
Decide where the work ends
In The Eval Is in Your Stomach, I asked how far a Delegate has to follow dinner before it can call the job done. The pottery version is simple: everyone who has a seat knows where to go, in time to get there. Define that before you ask for proof. Otherwise the Delegate can amass evidence for a finish line you didn’t mean.
In this studio, an acknowledgment from the student is evidence that the instructions reached her. A copy in the sent folder proves only that the message left. Two green check marks won’t help if both come from the same send event. Ask where each mark came from and what you’d still be able to get wrong if it were true.
From the studio record
Four entries in the record
Examples from the studio’s trial, including a rehearsal with missing replies.
- 01 Attempt
- All 12 door messages sent. The send log shows that the Delegate took an action. One of those messages still bounced.
- 02 Outcome
- All 12 students acknowledged the correct entrance. The replies match the current roster and room. A reply confirming last week’s address wouldn’t count.
- 03 Recovery
- One bounce caught and resolved. The Delegate used the student’s alternate contact on file, which it had permission to use. It verified the reply without waiting for you to notice.
- 04 Return
- Two acknowledgments couldn’t be verified. The Delegate told you before the cutoff, named the two missing confirmations, and kept the roster open. It didn’t call the work done.
Watch what it does when it can’t know
Clean Thursdays tell you what happens when the sources work and the students reply. Before you stop checking, rehearse one of the failures that would otherwise leave you guessing. In a test roster, take away the replies and let the clock run. Can the Delegate still reach you through the agreed channel before you have to act? Does it say what it couldn’t verify, or does it turn missing information into a confident report? If the Delegate itself can go offline, make sure a missed verification triggers a separate reminder. An alert can’t depend on the system whose silence it’s meant to catch.
A rehearsal gives you evidence about the case you tried. It doesn’t add twelve imaginary students to the record of real work. Run real classes with the old check in place long enough to see representative conditions, including the usual churn of cancellations. Compare a sample of the Delegate’s claims with the underlying replies. Make a note of anything you had to notice, prompt, or repair. A class that went well because you chased the last reply doesn’t prove the Delegate can carry the roster alone.
In The Trust Gradient, I described how evidence buys a smaller role for supervision. Here, that means taking away a check while keeping the means of checking. Keep the replies and the return channel. Skip the ordinary Thursday recheck for one cycle, with enough time to recover if a problem surfaces. Then look at what happened at the review you arranged beforehand. The record should still be there without you having to keep it current. Keep whatever safeguards the stakes require.
Before you withdraw attention
Name the next check you can remove
You’re ready when you can name the work you’re releasing, point to evidence that it finishes without your intervention, and say how an unresolved case will reach you while there’s still time to do something about it. If the room, the systems, or the permission to act changes, ask whether the old record still fits.
“I can skip the 5:12 roster check. The Delegate has verified the full roster on ordinary Thursdays, handled a bounce within its authority, and shown it can reach me when confirmation is missing. I can still inspect the replies if something changes.”
In The Attender, I explain why you can’t talk yourself into a quieter expectation. What changes it is what keeps happening. You may still want to look on the first Thursday you’ve agreed to skip. The record gives you a reason to leave the roster closed while the habit catches up.
At six, the students come in through the right door. The last one puts her bag down and asks where she should sit. You hear the question, because by then you’ve stopped counting.
1 thought on “The Proof Before You Let Go”