Approved, somewhere in chat
The auditor asks who approved the write-off. It was a thumbs-up in a chat thread, and nobody can find it.
InsteadEvery approval leaves a receipt: who approved, under which rule, and when.
The video
Video planned55 secondsHow every video is made
The script
- The one point
- Every approval leaves a receipt an outside auditor can check: who approved, under which rule, when, and any later edit.
- Why a video
- Time passing and cause and effect: a thumbs-up scrolls away in a busy thread, months pass, and an auditor’s question has no answer; then one click leaves a receipt that answers it.
- Picture
- Brand mark and sound, then the heading ‘Approved, somewhere in chat’ on the site’s background, fading straight into the guide with no black.
- On screen
- Approved, somewhere in chat
- Picture
- Guide in the usual place and framing, to camera. Lower third: guide’s first name, ‘Soundly Run guide’.
- Voice
- The auditor asks who approved the write-off. It was a thumbs-up in a chat thread, and nobody can find it. As a company grows, asks land in busy chats, and a thumbs-up is the quickest yes.
- On screen
- Guide’s first name, Soundly Run guide
- Picture
- A chat thread scrolls; a small thumbs-up under an ask drifts up and out of sight as hundreds of messages pass. A calendar flips months ahead. An auditor’s question card arrives; search results come back empty. No numbers.
- Voice
- Months later, nobody can show who approved it, or whether they were allowed to.
- On screen
- Approved, but nobody can show it
- Picture
- Drawn Record screen, Example tag top left, context ‘Grace’s crew’. Step band on prepare. Heading ‘Write off invoice 3318, unpaid since May?’. Callout 1 on Asked in: ‘Finance chat, by Owen, team lead’. Callout 2 on Rule: ‘Write-offs up to $10,000: finance operations lead’.
- Voice
- Owen asks in the finance chat. The ask becomes one card, with the rule that says who may approve it.
- On screen
- Example: the ask, with the rule that decides it
- Picture
- Step band on review. Cursor moves to Approver: ‘You, Grace, finance operations lead’, then Receipt keeps: ‘Who, which rule, when, and this card as you see it’, then Later edits: ‘Shown beside the original, with who and when’.
- Voice
- Grace is the approver under that rule. The receipt keeps who, which rule, when, and what she saw. Any later edit shows beside the original, so who authorised it has an answer on the record.
- On screen
- Example: the receipt keeps who, which rule, when
- Picture
- Step band on decide. ‘Approve the write-off’, ‘Change’ and ‘Pass’ all visible. Cursor clicks ‘Approve the write-off’, held two seconds. Heading turns ‘Approved, with a receipt’; Approver row reads ‘Grace approved, 20 Oct 14:02, under the write-off rule’. Guide in picture-in-picture.
- Voice
- Grace decides: approve the write-off, change it, or pass. Her click is the approval, and it leaves the receipt.
- On screen
- Approved. The receipt is in the decision record, ready for the auditor.
- Picture
- Guide in the same place and framing as The moment. Small inset: the auditor’s question card again, now answered by one receipt.
- Voice
- Nobody searches old chat threads for a thumbs-up any more. The helper keeps the receipts; a person approves. It does not watch, score or replace anyone.
- On screen
- Every approval leaves a receipt.
- Picture
- Standard end card, the same in every video: the page title, the brand mark and one small line, ‘Example screens’.
- On screen
- Approved, somewhere in chat
On screen as proof
- Drawn Record screen ‘Write off invoice 3318, unpaid since May?’, tagged Example
- Rule row and Receipt keeps row walked in order: who, which rule, when
- ‘Approve the write-off’ click held two seconds, Change and Pass visible
- Result: ‘Grace approved, 20 Oct 14:02, under the write-off rule’
Before and after
- Before
- A thumbs-up is quick; a form feels like red tape
- After
- One click approves, and the click leaves the receipt
- Before
- Nobody checks the approver could approve that much (delegation of authority)
- After
- Each receipt names the rule that let them approve
- Before
- An edit made later looks just like the original (audit trail)
- After
- A read-only record, with any later edit shown beside the original, answers who allowed it
How it works
Each approval leaves a receipt in the decision record that an outside auditor can check.
- An ask for approval in chat becomes one card naming the rule for who may approve it; a thumbs-up alone is not the approval.
- The named approver decides on the card; the receipt keeps who, which rule, when and what they saw. AI helpers act only once it exists.
- An auditor reads the receipts in the decision record; a later edit shows beside the original, with who and when.
RecordExample
Grace's crew · Example
Write off invoice 3318, unpaid since May?Approved, with a receipt
- Asked in
- Finance chat, by Owen, team lead, Tue 20 Oct
- Write-off
- Invoice 3318, $8,400, unpaid since May
- Rule
- Write-offs up to $10,000: finance operations lead
- Approver
- You, Grace, finance operations leadGrace approved, 20 Oct 14:02, under the write-off rule
- Receipt keeps
- Who, which rule, when, and this card as you see it
- Later edits
- Shown beside the original, with who and when
Source: finance chat, 20 Oct
Approve the write-offChangePassApproved. The receipt is in the decision record, ready for the auditor.
Built to work in the email, calendar, chat, finance and sales tools you already use.
What it never does
- Acts alone only inside limits a person sets; asks first for anything else.
- Reaches only what its job needs.
- Never watches, scores or replaces anyone.