Overview
A concrete client delivery workflow example showing how an agency can manage internal production, client review, approvals, and reporting in Kanvly. The example walks through the team situation, board setup, live cards, notes, cadence, common mistakes, and measurement signals so the workflow feels concrete instead of generic.
The real workflow scenario
An account lead, strategist, designer, copywriter, and operations owner are managing a monthly retainer with weekly deliverables. The agency needs clean client updates, but the real production state includes messy internal notes, draft feedback, and blockers that should not be exposed directly.
The point of this example is not to prescribe one universal process. It shows how small agencies and service teams managing retainers or recurring client deliverables can turn a messy operating moment into a board, notes, and cadence that the team can actually use during a normal week.
- Landing page copy pass.
- Ad creative round two.
- Monthly performance summary.
- Client approval on campaign brief.
- Follow-up tasks from last call.
The board setup
Start with the board flow Queued -> Active -> Internal review -> Client review -> Approved -> Reported. The lane names are intentionally plain because the first job of the board is shared readability, not process decoration.
Each card should answer owner, next action, status, and why the work matters. If a card needs more explanation than a title can hold, that context belongs in an attached note rather than a side conversation.
The notes and context to keep
The board shows motion, but the notes explain judgment. In this example, the durable context is: Private account context and stakeholder preferences. Draft feedback before it becomes client-facing. Reported summary that can be reused next month.
This is the difference between a task tracker and a workspace. A task tracker can say that something moved to review. A workspace should also make it clear what changed, who decided it, and what the next person needs to know before acting.
The weekly cadence
The cadence is deliberately lightweight: Monday account prep separates committed work from possible work. Wednesday internal review catches creative and strategic blockers. Friday status packaging turns internal state into a clean client update.
This rhythm keeps the system trustworthy without turning it into a ceremony-heavy process. The team should leave each review knowing which cards moved, which cards are blocked, and which notes were updated because a decision changed.
Mistakes to avoid
Most teams do not fail because the board has the wrong color or the wrong icon. They fail because the workflow slowly stops reflecting reality.
Use the first two weeks to remove friction rather than add fields. If people keep updating private lists, asking where context lives, or skipping the board during real work, the system is too far away from the actual operating habit.
- Putting client-facing status and internal production detail in the same sentence.
- Starting every retainer from scratch instead of reusing a proven service rhythm.
- Letting approvals sit without a named next action.
How to know it is working
Good measurement should describe whether the workflow is becoming easier to trust. For this example, watch: Approval cycle time. Deliverables waiting on client review. Status-prep effort before weekly updates.
The strongest sign is behavioral. When the team opens the workspace first, trusts the board during review, and uses notes to preserve decisions, the workflow is doing its job.
- Pick one active workflow with real owners before changing the whole system.
- Create the first board with only the statuses the team can explain.
- Move live cards first and leave historical work behind until the new flow is trusted.
- Attach notes for decisions, briefs, support answers, or stakeholder context.
- Review blocked, stale, and ownerless cards on a predictable cadence.
- Turn repeated work into a template only after the team has used it once.