Agency Project Template

Why most agency templates stop reflecting the engagement

Agency work has a specific failure pattern that a generic project board doesn't catch: the scope on day one is rarely the scope by delivery, and the drift happens in small increments that never individually look worth a fight.

Scope creep is invisible on the board. A client asks for "one more version," and it becomes part of the existing card instead of a new request. Nobody decided to do extra work; it just accumulated into the deliverable already in flight.

Production and review blur together. A deliverable sits in "review" while three more revisions get made without formally going back through it, so the review stage stops meaning anything and sign-off becomes a formality applied to whatever's current at the time.

Utilization is reconstructed from memory. Billable hours get estimated at invoice time rather than logged as the work happened, which is how a profitable-looking engagement turns out to have eaten far more hours than were ever billed.

The engagement and the phase get tracked on the same board. A single list tries to hold both "what did we agree to overall" and "what's due this Tuesday," and it ends up doing neither well. The whole engagement needs room to breathe that a single deadline-driven board doesn't give it.

None of these are unusual mistakes. They're what happens when a template built for internal project work gets reused for client work without accounting for the two things that make client work different: money changes hands, and someone outside the team gets a say in what "done" means.

What a mid-engagement week looks like on the board

By week four of a typical engagement, scope and kickoff are done: the SOW is signed, the deck's been sent, and the board's real activity is in production. Four deliverables sit in progress, at the column cap, with two more waiting because the cap is holding. Nothing new starts until something finishes. One card is in client review, three days in, which the account lead reads as "waiting on them" rather than a delay to chase internally. A revision request comes in over email asking for "one more logo direction." It becomes a new card in the change-request inbox rather than an edit to the concept already in review, so it gets priced and scheduled rather than quietly absorbed. At the end of the week, logged hours against each deliverable roll up into a utilization number the account lead can actually trust, instead of one assembled from memory before the invoice goes out. That's the five-second log next to each task doing its actual job: not a timesheet chore, but a number Friday's invoice can stand on.

How to use it

1. 01Scope the engagement into cards before the kickoff call. Deliverables, not phases. Production needs something concrete to point to, not a paragraph in the SOW that has to be re-interpreted every time.
2. 02Cap production strictly. A small limit, low enough that it's uncomfortable at first, forces the team to finish a deliverable before pulling the next one in.
3. 03Route every "just one more thing" through the change-request inbox. A new card, not an edit to the existing one. This is the single habit that keeps scope visible instead of quietly absorbed.
4. 04Log hours per deliverable as you go. It turns utilization into a report you can pull at any point, instead of a guess assembled at month-end.
5. 05Keep the decision log current as the engagement runs, not as a wrap-up exercise. The point where a scope decision is made is the point it's cheapest to write down.
6. 06Hand off a scoped phase once it's ready to execute against a client deadline. This board stays the container for the whole engagement; a client delivery board tracks the phase that's actually in flight, against its own date.

The structure isn't proprietary; you could rebuild the scope-to-delivery flow in any tool with column limits and a change log. It's written down here because the change-request inbox is the part most agency boards skip, and it's the part that actually protects the margin.