EP037 · Main episode
Work Agent Receipt Check
When an AI agent says the work is finished, what receipt proves the right outcome was delivered at an acceptable total cost, under approved access, evidence, and review conditions?
- Published
- Jul 20, 2026
- Runtime
- 19m 54s
- Record
- Source-backed notes
Complete episode file
Notes, chapters, and evidence
The full editorial record lives here. Open only the section you need, without leaving the Desk.
Episode notes3 sections · 3 release notes
Original release summary
- What changed: When an AI agent says the work is finished, what receipt proves the right outcome was delivered at an acceptable total cost, under approved access, evidence, and review conditions?
- Why it matters: this changes operational decisions, risk posture, and team adoption.
- What to do next week: assign an owner, set clear guardrails, and run a short training pass.
Overview
AI Change Desk is back with a simpler format: one focused weekly episode, built for a commute.
In this episode, Michael briefly explains the hiatus, his move from GTO to the State of Oregon, and the family logistics behind the reset. Then the Desk turns to the operating question that matters now:
When an AI agent says the work is done, what receipt proves it?
OpenAI's latest enterprise scorecard shifts measurement away from seats, token volume, and activity toward useful work, successful-task cost, dependability, and value at scale. ChatGPT Work makes execution context and local-versus-cloud custody part of the evidence path. Microsoft Agent 365 and Copilot Studio show why inventory, licensing, policy state, logs, memory, skills, model choice, and delegated agents also belong on the receipt.
What you will leave with
- The difference between completion and acceptance.
- Why continuity is not custody.
- What full successful-task cost should include.
- Why a log dump is not a usable receipt.
- A seven-part, 45-minute Work Agent Receipt Check for one live workflow.
This week's action
Pick one AI workflow that claims to complete work. Record the accepted outcome, execution path, authority boundary, economics, dependability result, evidence location, and stop owner. If someone outside the room cannot reconstruct the run, the workflow is not ready to scale.
Chapters12 markers
Original release timeline
Sources5 records
Disclosure and questionEditorial record
Disclosure
AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval stayed human-led. This is operational guidance, not legal advice. These are Michael's personal opinions and do not represent the State of Oregon, GTO, or any other organization.
Listener question
What is one AI-related decision your organization keeps postponing right now?
Companion resources1 download
Download the episode resource.
Use the companion Word document when you want the signals, decisions, and assignments from this episode in one place before the meeting starts.
- Key signals and implications in a quick-review format.
- The actions to assign this week, with space to name owners.
- A working sheet for due dates, evidence, and follow-through.
Best Place In The Flow
Put it between listening and action: after the episode lands, before the handoff starts, or during the meeting where assignments get made.
- Use the workbook when someone wants the operational takeaway in under two minutes.
- Use the worksheet when the conversation shifts from analysis to ownership.
- Keep the transcript nearby only when you need fuller context or direct phrasing.