Agency Resource Management: A Complete How-To Guide

Think of it as the operational layer beneath project management: projects tell you what needs doing; resource management tells you who will do it and when.

How to Do Agency Resource Management

Agency resource management works best as a repeating cycle, not a one-time plan. Here's how to build that cycle from the ground up.

1. Forecast Demand From Your Pipeline

Start before work is confirmed. The deals in your sales pipeline are a signal, and if you wait for a signed contract to start planning, you're already behind.

Pull your active proposals and weight them by close probability. A deal at 80% confidence deserves a spot on your planning board. A 20% longshot doesn't—but you should know it exists.

Use these inputs to build a rolling demand forecast:

• Proposal stage: Assign a probability (e.g., 50%, 80%, 100%) and estimate the hours needed by discipline.
• Upcoming retainers: Treat renewals as confirmed until a client signals otherwise.
• Backlog: Any sold-but-not-started work counts as near-term demand.
• Historical patterns: If clients in a certain sector tend to ramp fast, build that into your model.

I'd recommend revisiting this forecast weekly. Pipeline changes fast, and a forecast that's two weeks old isn't a forecast—it's a history lesson.

Stay Ahead of What Deserves Your Attention

Get timely perspective on the shifts, decisions, and trade-offs shaping your role, plus practical resources you can put to work.

Get Free Access

Have an account? Log In

2. Map Your Team's True Capacity

Gross capacity (40 hours × headcount) is a fiction. What you need is plannable capacity: the hours left after you subtract everything that doesn't generate billable output.

Use this table to break down capacity realistically:

Capacity Type	What It Includes	Typical Deduction
Gross hours	Full work week per person	Baseline
Non-billable overhead	Internal meetings, admin, training	15–20%
PTO and leave	Booked time off, public holidays	Varies by month
Ramp time	New hires, returning employees	25–50% in first 4 weeks
Buffer	Unplanned work, sick days	10–15%
Plannable hours	What's actually schedulable	~65–70% of gross

Don't skip the buffer. Teams that plan to 100% capacity have no room for a client escalation or a sick day. That's how projects fall apart.

3. Prioritize Projects by Value and Fit

When demand exceeds capacity—and it will—you need a clear prioritization framework. "Who shouted loudest" is not a framework.

Rank your project backlog using these criteria:

• Deadline urgency: Is there a contractual or launch date at risk?
• Margin: Higher-margin projects protect the business; lower-margin work shouldn't crowd out profitable work.
• Client relationship: A long-term anchor client often earns scheduling priority over a one-off project.
• Resource fit: If the right person is available now but won't be next month, timing matters.
• Strategic value: Some work is worth taking at lower margin because it opens a new market or builds a new capability.

Author's Tip

Often, the hardest call is deprioritizing a low-margin project that a junior team member is excited about. Do it anyway—or renegotiate the margin. Good resource management sometimes means uncomfortable conversations.

4. Set Utilization Targets by Role

A single agency-wide utilization rate target doesn't hold up in practice. A senior strategist and a junior copywriter have very different roles, and their billable expectations should reflect that.

Here's how I'd think about target-setting by role type:

Role Type	Suggested Billable Target	Why
Senior delivery leads	60–70%	High non-billable overhead: mentoring, scoping, client strategy
Mid-level practitioners	70–80%	Mostly execution-focused with some collaboration overhead
Junior team members	75–85%	Lower admin load, more execution time
Operations/resource managers	20–30% billable	Their value is in coordination, not direct delivery

Build a 10–15% buffer into every role's plannable hours. That buffer absorbs scope creep, context-switching, and unexpected client requests before they hit the team as overtime.

5. Match the Right People to Projects

Availability is the floor, not the ceiling. The best allocation decisions factor in skills, development goals, working style, and project complexity, and not just who has open hours.

Before assigning someone, ask the right questions:

1. Who has the right skill set?

• Does the team member have what this particular client needs?
• What is their client-facing level of seniority?
  • Do they know the brand? Can they bring something new?
  • Are they consistent, persistent, and dependable?
• How well do they work with their team counterparts?

2. How can we maximize resource utilization?

• Do they have enough capacity to deliver successfully?
• Can they meet their responsibilities on every key date?
  • Any conflicting PTO or client commitments, such as shoot travel or in-person presentations?

Author's Tip

Department heads mostly want to know whether someone has capacity. Time-tracking software lends those need-to-know-now insights, like what everyone is working on, what’s due, when PTO is scheduled, and what other conflicts exist.

3. What do I need to know to see the whole picture?

• Career development: Is this project a stretch opportunity they'd value, or will it stall their growth?
• Client chemistry: Especially on long retainers, personality fit between team and client matters more than people admit.
• Current cognitive load: Someone wrapping a high-pressure project may technically be "available" next week but isn't ready to lead something new.

Build in a check-in before you finalize assignments, not after. Based on how this all unfolds, you can identify who will be needed, what they will need, and how much capacity will be required of them. You'll also be able to properly estimate fees and hard costs, and ultimately decide whether or not this project can be accomplished within existing boundaries, without contributing to burnout. 

6. Track Billable Hours and Utilization Weekly

The plan is only as useful as the feedback you get from tracking actuals. Set up a weekly rhythm for reviewing time against the plan.

What to watch each week:

• Actual vs. planned hours by person: Are people logging more or fewer hours than forecasted?
• Billable vs. non-billable ratio: Is non-billable time creeping up? That's usually a sign of scope drift or internal inefficiency.
• Overtime signals: Anyone consistently logging more than their plannable hours is a resourcing problem in progress.
• Under-utilization: Empty hours often mean poor pipeline visibility or delayed project starts—both worth investigating.

Don't wait for month-end reports to spot problems. By then, the damage is done. In my opinion, a weekly 15-minute scan of utilization data is worth more than a monthly retrospective.

7. Manage Scope Creep and Retainer Boundaries

Scope creep is the hidden tax on agency capacity. It rarely looks dramatic—it's one extra round of revisions, one extra stakeholder added to the call, one extra deliverable that "shouldn't take long."

Here's how to manage it without damaging client relationships:

• Reserve retainer hours by role upfront: When a retainer starts, map which hours belong to which disciplines. That way you spot overservicing early, not at invoice time.
• Log change requests as soon as they appear: Even if you plan to absorb a small request, document it. Patterns of small requests add up to major scope drift.
• Set a threshold for escalation: If a project is tracking more than 10–15% over its estimated hours, that's a conversation with the client—not a silent sacrifice of your margin.
• Use templated language for change orders: The easier it is to raise a change order, the more likely your team will actually do it.

Author's Tip

Most agencies undercharge because they never track the small asks. The fix isn’t aggressive invoicing. It’s actually just honest hour logging from day one.

---

8. Run a Weekly Review and Adjust

Resource management is not a monthly exercise. Plans break within days of being made, and the only way to stay ahead of the chaos is a short, structured weekly review.

Keep it to 30 minutes. Cover these four questions:

1. What changed this week? New projects, lost deals, unexpected absences.
2. Who is over capacity, and what moves? Reprioritize, reschedule, or escalate.
3. What's coming in the next two to four weeks? Are there resourcing gaps you can address now?
4. What decisions need a tie-breaker? Resource conflicts between departments need a named owner—usually an operations manager or director—who has the authority to decide.

The person who runs this meeting matters. It shouldn't be a project manager advocating for their own projects. It should be someone with visibility across all accounts and no personal stake in any single outcome. That neutrality is what makes the meeting useful.

Who Owns Resource Management: Key Roles and Responsibilities

Resource management breaks down when no one has clear ownership. Without a named decision-maker, project managers advocate for their own work, conflicts go unresolved, and leadership ends up making reactive calls that don't reflect the full picture.

This table shows how responsibilities typically split across roles:

Role	Primary Responsibility
Operations/resource manager	Owns the capacity plan, runs resourcing reviews, makes final allocation decisions
Project manager	Communicates project needs, flags timeline shifts, escalates conflicts
Team lead	Surfaces workload concerns, provides input on skill match and team readiness
Department head/director	Breaks ties between competing priorities, approves headcount decisions
Leadership	Sets strategic priorities that determine which projects get first access to resources

The operations or resource manager is the linchpin role. They need visibility across every account (not just the loudest one)mand the authority to make calls that stick. If you don't have a dedicated resource manager, that responsibility falls to whoever has the broadest view of the business, usually an operations lead or a senior project manager not aligned to any single client.

When and How to Bring in Freelancers or Contractors

Freelancers and contractors fill capacity gaps your permanent team can't cover—but bringing them in too late, or for the wrong reasons, creates more problems than it solves.

Signals That It's Time to Contract

Watch for these situations before you need external help, not after:

• Sustained over-capacity: If your team is running above target utilization for two or three consecutive weeks, that's a staffing gap, not a temporary spike.
• Skill mismatch: You've won a project that needs a capability your team doesn't have. Hiring a full-time employee for a short engagement rarely makes financial sense.
• Pipeline confidence: A pipeline that's 60–70% likely to close justifies bringing someone in early—before you're scrambling to staff a project already in motion.
• Predictable seasonal demand: If your agency has known busy periods, build contractor relationships in advance rather than relying on cold outreach when volume spikes.

Author's Tip

I’d recommend keeping a roster of trusted freelancers you’ve worked with before. When a project is already in motion, you don’t have time for a cold search and vetting process. A bench of two or three reliable contractors per discipline is worth building before you need it.

Keep Building Your Resource Management Practice

If you want to go deeper with templates, peer support, and practical tools built for agency project leaders. A DPM membership gives you access to 100+ project resources, live workshops, and a Slack community of project managers working through the same challenges you are.