Projects, tasks, and delivery in one board

A client asks for one more round of edits. She asks in a chat thread, halfway down a conversation about something else. Someone says sure.

Then the thread moves on. The person who said sure is on a call by the afternoon, and the request that was going to become a task never quite becomes one. The edits themselves may well get made, because somebody remembers on Thursday. It’s everything around them that doesn’t happen. No task was opened, so the timeline still shows the delivery date from before she asked. The approval was a thumbs-up in a chat window. The invoice at the end of the month describes the work that was scoped, and the extra round somebody actually did isn’t on it. Two weeks later nobody can say for certain whether it got done, or whether it was ever billed.

Work rarely goes missing inside a tool. It goes missing in the gap between tools, in the moment someone meant to retype it somewhere else and got pulled into a call instead.

Where the request goes now

Amolfi puts the whole path on one board. That ask from the client becomes tracked work the moment it arrives: a task under the deliverable it belongs to, on the same timeline the delivery date lives on, with the approval as a step someone takes and the board keeps. There is no second system to copy it into before it counts as real, and nothing to drop in the handoff, because there is no handoff.

What changes the shape of the week is where that board sits. Delivery lives in the same workspace as the client record and the invoice, so a piece of work shows up already knowing who it’s for and what it’s worth. Open the client and the extra round of edits is sitting there with everything else in flight for her.

Intake, tasks, deliverables, approvals and timelines all sit on that one board, in the same workspace as the client record and the invoice they belong to. The round of edits is on it.