← Who Booked This?
Who Booked This? · Flow 4 of 4
Task lifecycle
From noticing a coordination gap through someone volunteering to own it — and what happens when nobody does.
Flow 4 — Task lifecycle Flowchart showing how a task is created by any member, sits unclaimed and visible to all, escalates as its deadline approaches, and is voluntarily claimed — never assigned. Flow 4 of 4 Task lifecycle Any member notices a gap Creates a task Description + deadline. Creator ≠ owner. Task sits open, visible to all No one is assigned or obligated Deadline approaches Task rises in visibility App notifies the group "This task is still unclaimed" Someone volunteers Explicit self-claim only No one claims it Gap stays visible Task marked complete Logged in audit trail App never points at a person Noticing a gap never creates obligation — only visibility
Who Booked This? — User Flows May 2026