Bench Time

The term comes from sports — players on the bench are part of the team, in uniform, ready to play, but not currently on the field. In agencies, it's the same idea: someone's on payroll but has no billable work assigned.

Bench time isn't inherently bad. Zero bench time across an entire team actually signals a problem — it means there's no buffer for unexpected work, sick days, or new opportunities. You *want* some slack in the system. The question is how much, and whether you're using it well.

Visible vs. Invisible Bench Time

Here's the thing most agencies get wrong: they don't actually know who's on the bench. Without a shared timeline view of everyone's allocations, idle capacity hides behind busywork. Someone might reorganize their Figma files for three days because no one realized they were free.

When bench time is visible — clear gaps on a calendar that everyone (or at least every PM) can see — it becomes actionable. A PM with a project kickoff next week spots that a developer is free *this* week and pulls the start date forward. That's a win you'd never get if availability lived only in people's heads.

Making Bench Time Productive

The agencies that handle this best have a playbook for idle time:

1. Internal product work or R&D 2. Skill development and cross-training 3. Prospecting support — building case studies, pitch decks 4. Process improvement and tooling

A healthy target for most studios is 10-15% bench time — enough buffer to absorb surprises without bleeding money. If you're consistently above 20%, that's an underallocation pattern that needs attention. If you're at 0%, revisit your headcount planning because your team is running too hot and overtime is probably filling the gaps.