How Agencies Track Team Capacity Before Projects Go Over Budget
The agency capacity problem is not knowing when you are full until you are over-full. Here is how to calculate real available capacity — and how to see it every week without a separate resource management tool.
The Capacity Blindspot That Makes Agencies Over-Commit
The capacity blindspot: when a new project opportunity arrives, the agency owner evaluates it against a mental model of team availability that is typically 2-4 weeks out of date. The mental model was formed the last time the owner looked at what everyone was working on. It does not account for: the vacation approved for the senior designer three weeks ago, the additional scope on an existing project consuming 20% more hours than estimated, the contractor whose engagement ended last week, or the junior developer whose skills are not matched to the incoming project. The result: the owner says yes based on a capacity estimate that is wrong in ways that will only become visible three weeks into the engagement, when the team is working nights and weekends to cover commitments made without full information. Capacity planning is not a complex operation at a 10-person agency. It becomes complex when the data required is spread across multiple tools and people's memories. When centralized and current, the calculation is straightforward.
"When a new project opportunity arrives, the agency owner evaluates it against a mental model of team availability that is typically 2-4 weeks out of date."
The Capacity Formula
Real available capacity is not total contracted hours. It is the difference between total contracted hours and the sum of everything those hours are already committed to. Formula: Available capacity = (Team members × Hours per week) − Approved leave hours − Existing project commitment hours Example: 10-person agency, each contracted for 40 hours per week. Total theoretical capacity: 400 hours per week. Deductions for the coming four weeks: - Senior designer on vacation for 2 weeks: −80 hours (−20/week) - Project manager has approved 4-day leave: −32 hours (−8/week) - Current project commitments require ~280 hours per week based on current tracking Real available capacity: 400 − 20 − 8 − 280 = 92 hours per week of uncommitted capacity. If a new project requires 120 hours per week, the answer is not yes. The honest options: adjust the timeline (client conversation), bring in a contractor, or defer the project. The math is not complicated. The difficulty is having accurate, current inputs for each component.
Why Leave Visibility Is the Most Important Capacity Input
Of the three inputs to the capacity formula, approved leave is the most overlooked and has the longest lead time for impact. Current project commitment hours are visible in recent Work Reports. Team member schedules are known to the manager. But approved leave is typically stored in a leave system that the project planning tool does not read — the PM building the capacity estimate knows that someone is on vacation 'sometime in that period' but cannot tell you which specific days without checking separately. This is why leave management and project planning need to be in the same system. If approved leave automatically appears on the project calendar, capacity estimates for any future period automatically include the leave deductions. If leave is in a separate system, it must be manually checked and incorporated — which means it will sometimes be missed.
"An agency owner evaluating a new project checks current team load, sees 80 hours per week of available capacity, and commits to a project requiring 70 hours per week. Three days later, opening the leave tracker reveals two team members have approved vacation in week two of the new project — reducing capacity to 48 hours for that week. The commitment is already made."
— A scenario that recurs at most agencies
How to Read Work Reports as a Capacity Signal
Work Reports — hours logged per team member per project over a defined period — are the most accurate available signal for current project commitment. They show what actually happened, not what was planned. The capacity signal: the weekly average for each team member. A team member averaging 38 hours per week of project work over the past four weeks is running close to 40-hour capacity. A team member averaging 24 hours has approximately 16 hours of uncommitted capacity. This data is more accurate than project schedule estimates because it reflects the actual rate at which the team is consuming hours — not the estimated rate. Estimates are systematically optimistic. Using Work Reports for future capacity estimation: if a project is in week two of a six-week engagement and has consumed 180 hours, the actual weekly rate is 90 hours. If the original estimate assumed 70 hours per week, the project is running 29% over pace. That 29% overrun reduces available capacity by the same amount. The manager who checks Work Reports weekly sees this in week two. The manager who checks monthly sees it in week six, after two new projects are already committed.
Building a Capacity View from Data Already in Your Platform
A functional capacity view for a 10-person agency does not require Float, Resource Guru, or any dedicated resource management software. It requires four data sources that should already exist in the workspace:
- Work Reports (current project commitment) — weekly hours per team member from the past 2-4 weeks. Estimate of current project commitment based on actual tracking rather than planned allocation.
- Team calendar with leave (future capacity holes) — approved leave for the coming 4-8 weeks, visible alongside project milestones. Shows the future capacity deductions to subtract when evaluating new project commitments.
- Global Kanban (current task assignment state) — who has tasks assigned for the coming week and approximately how many. Rough indicator of workload distribution.
- Live Timers (real-time current state) — who is currently working on what. Not a planning tool — a snapshot of right now.
The Weekly Capacity Review Process
A weekly capacity review for a 10-person agency takes 30 minutes or less:
- Pull Work Reports for the past week — hours per team member per project. Note anyone running significantly above or below historical average.
- Check the team calendar for upcoming leave — any absences in the next four weeks affecting specific project commitments?
- Review the Global Kanban for task distribution — anyone with significantly more or fewer tasks than peers?
- Calculate rough available capacity for the next two weeks: team hours minus leave deductions minus current project pace.
- Compare available capacity against any new project opportunities in the pipeline — any commitments being considered that exceed current capacity?
What Dedicated Capacity Tools Do That a Workspace Doesn't
Float, Resource Guru, and similar dedicated resource management tools provide capabilities beyond what a workspace tool natively supports:
- Scheduled allocation — allocate specific person's hours to a project week-by-week, months in advance, and see the resulting utilization chart.
- Scenario planning — model different project combinations to find the optimal resourcing mix before committing.
- Skills-based matching — filter team capacity by skill set to find not just anyone with available hours but the right person.
- Multi-project Gantt with resource overlay — combined view of all project timelines with team allocation shown simultaneously.
How Melororium Builds a Capacity View
Melororium does not have a dedicated capacity planning module — it has four data sources that combine to produce a capacity view: Work Reports: filterable by team member, project, and date range. A manager pulling the Work Report for the past three weeks gets actual hours-per-person rate — the most accurate input for current project commitment. Team calendar with leave integration: approved leave appears automatically alongside project milestones and task due dates. A manager evaluating a new project's timeline sees which team members are absent during the proposed delivery period. Global Kanban: all tasks across all projects organized by assignee. A vertical scroll shows at a glance which team members have the heaviest current task loads. Live Timers: who currently has a timer running and against which project. A five-second answer for real-time team attention. The combination, checked together in the weekly capacity review, produces a capacity picture accurate enough for planning at 10-person scale — without Float, without Resource Guru, without a separate resource management subscription.
Work Reports, team calendar, and Kanban — your capacity view without Float.
Agency plan: $59/mo for 10 users. Flat fee, no seat tax.
