Resources
Insights · 5 min read
How finance requests lose ownership
Requests do not usually get dropped. They get transferred implicitly, from an email thread to a memory, until nobody realises they are the owner.
The failure mode
A vendor sends an invoice to accounts@. Someone forwards it to the founder. The founder replies with context but does not assign it. The bookkeeper sees the thread on Monday and assumes the founder is handling it. Two weeks later, the vendor calls.
Nothing was ignored. The request simply lost its owner in the space between two channels.
The three points of failure
Almost every dropped request fails at one of these three points.
- Channel switch: the request moves from email to chat to spreadsheet, and the owner does not travel with it.
- Implicit delegation: someone replies with context that reads like an instruction, but no one confirmed receipt.
- Absent completion criteria: nobody wrote down what "done" looks like, so the request quietly stays open.
What a request record fixes
A request record forces a named owner, a defined completion state, and a single place to look. It is not a ticketing system; it is the memory that all the other tools rely on.