The client-delivery workflow, end to end
Turn intake into assigned work, production, client review, approval, and a finished record.
This is the spine every other workflow branches from: a request arrives, becomes owned work, gets produced, gets decided on, and ends as a record.
Capture the request with structured context
Work enters through an intake form or a request rather than a message, so it arrives with an outcome, a reason, and a deadline attached. A request that arrives complete removes the clarification round that usually costs the first two days.
Triage ownership, project, priority, and due date
Before production starts, someone confirms the request is understood, sets an owner and a date, and checks it belongs in this project at all. Triage is where you catch work that should have been a conversation.
Produce work in visible workflow stages
The task moves across stages that describe real states. Because stages are visible, nobody has to ask for status, and a stage that keeps filling shows you the constraint without anyone running a report.
Move the deliverable into Client Review
Client decisions get their own stage rather than being a status on a task. This makes time spent waiting on a client countable, which is what lets you show where delay actually comes from.
Request a named decision and record the outcome
Ask one named approver rather than posting for comment. Approved or Changes requested is recorded with the person, the time, and a note, on the task and in the audit log.
What success looks like
- A piece of work can be traced from the original request through to a recorded decision, with an owner at every point and no step that exists only in someone's memory.
Common mistakes to avoid
- Letting work start from a chat message, so nobody agreed what was being asked for.
- Treating client review as a status rather than a stage, which hides decision delay.
- Accepting verbal approval, leaving nothing to point at when scope is questioned.
Common questions
At intake. If work reaches production without passing triage, the rest of the workflow inherits the ambiguity.
The approval carries the actor, the time, and the note, so a scope discussion starts from evidence rather than recollection.
Related pages
Need help applying this workflow?
Tell us how your team works and we will help you set this up on a real project.