Agency Capacity Planning Without Time Tracking
Why hours are the wrong unit, and what to measure instead
Most marketing agencies doing capacity planning are working with the wrong unit of measurement. They're tracking hours, estimated versus actual, and using that data to decide whether the team is over or under capacity.
The problem is that hours measure when people are working, not what they're producing. In a remote agency, those two things are easy to confuse, and the confusion is expensive.
Why Hours Are the Wrong Measure for a Remote Agency
A team member can spend eight hours on Slack, in internal meetings, and organizing shared drives and produce nothing billable. Another team member can complete everything assigned to them in four focused hours. If your capacity model is built around hours, the first person looks like they're working hard and the second looks like they have capacity left over.
That's backwards. The second person is the one you want to understand and replicate.
There's also a practical issue for agencies working with contractors. Dictating the hours a 1099 contractor must work and tracking their time closely is one of the factors that can trigger reclassification as an employee under IRS guidelines. Measuring their output instead of their time is both the legally safer approach and the one that gives you better capacity data.
How to Measure Agency Output Instead of Hours
The alternative is output-based capacity planning: stop measuring time at the desk and start measuring the actual unit of work that got completed.
In a marketing agency, work happens at multiple levels. There's the client initiative, something like a quarterly content strategy or a campaign launch. There are the deliverables inside it, the five blog posts, the ad creative set, the email sequence. And then there's the atomic unit of work, the specific step that moves one of those deliverables forward: an outline approved, a draft completed, a design passed to review.
That last level is what we mean by a Unit. It's the smallest piece of work that can be verified as complete. It either meets the acceptance criteria for that step or it doesn't. There's no partial credit, no "90% done." The unit passes or it gets kicked back.
When you measure capacity in Units rather than hours, a few things get clearer. You know how many units a given role can produce in a week. You can see at any point whether someone's load is sustainable. And you can spot the difference between someone who is genuinely at capacity and someone who has availability but is slow-moving on a specific type of work.
Time in Station: Measuring the Process Instead of the Person
If you're not tracking hours, you still need to understand how long things take. The metric we use for this is Time in Station.
Time in Station measures how long a unit spends in each step of the workflow, not how long the person was logged in, but how long from when the unit arrived at that step to when it moved forward. That distinction matters because it separates working time from waiting time.
A unit that takes two hours of actual work but sits in a queue for three days has a very different Time in Station than the work time alone would suggest. Most agencies have no visibility into that waiting time, which means capacity problems look like people problems when they're often process problems.
We establish Time in Station baselines using a short effort study, typically about fifteen minutes of structured observation per role, to get an accurate picture of how long each type of unit takes to move through each step. Once you have that baseline, capacity planning becomes straightforward. If a role has a Time in Station of ninety minutes per unit for copy review, and you have twelve units coming through that step this week, you know what that person's week looks like without asking them to log a single hour.
How This Works Inside Asana
When we rebuild an agency's Asana around this model, we remove time-tracking fields entirely. Capacity planning in Asana works like this:
Every team member maintains their task view organized by day of the week. On Monday morning, they pull their assigned units into the specific days they plan to complete them. That forecast is visible to everyone. If someone's forecast is unrealistic based on Time in Station data, it gets flagged before the week starts rather than discovered on Friday.
The dashboard tracks units completed versus units planned, FTA rate for each role, and where units are stalling in the workflow. That combination tells you more about actual capacity than any timesheet.
When a team member consistently produces at a high rate with clean handoffs, that becomes the baseline you use for hiring and for setting expectations with new team members. You don't have to guess what a productive week looks like, because you have the data.
If you want to see how this model gets built into Asana specifically for a marketing agency workflow, our Asana implementation service for marketing agencies includes the unit and Time in Station setup as part of the build.
Frequently Asked Questions
How do you plan agency capacity without time tracking?
Instead of tracking hours, you measure the units of work each role produces and how long each type of unit takes to move through each step in the workflow. Once you have those baselines, you know how many units a role can handle in a given week, and you can assign accordingly. The result is a capacity model built on what actually gets produced rather than on when people are logged in.
What is a unit of work in an agency context?
A unit is the smallest piece of work that can be verified as complete. In a marketing agency, examples include an approved brief, a completed copy draft, a design passed to review, or a report delivered to the client. A unit either meets the defined criteria for that step or it doesn't. Measuring capacity in units instead of hours gives you a concrete, objective view of what the team is producing rather than how long they're spending at their desks.
What is Time in Station and how is it different from time tracking?
Time in Station measures how long a unit spends in each step of the workflow, from arrival to handoff. Time tracking measures when an individual is working. Time in Station tells you about the efficiency of the process; time tracking tells you about the activity of the person. For capacity planning, Time in Station is more useful because it shows you where work is moving efficiently and where it's stalling, which is where most capacity problems actually originate.
How do you track capacity in Asana without time tracking fields?
Each team member maintains a task view organized by day, with their assigned units pulled into specific days as a weekly forecast. A dashboard tracks units completed versus planned, FTA rate, and where units are stalling. That combination gives you a real-time picture of capacity without requiring anyone to log hours. When the forecast and the actual completion data diverge consistently, it's usually a signal about either workload distribution or a process bottleneck at a specific step.
Is it legal to stop tracking hours for agency contractors?
For 1099 contractors, measuring output rather than hours is generally the more legally appropriate approach anyway. Dictating the hours a contractor must work and tracking their time closely is one of the factors that can trigger reclassification as an employee under IRS guidelines. Measuring units of completed work, with clear acceptance criteria, is consistent with how independent contractor relationships are supposed to work. You should verify specifics with a legal advisor for your jurisdiction.