# Fully booked is why it's late

> A fully booked team is a late team, because waiting grows fast as people near full capacity. It eases when repeatable work comes off the busiest person.

A fully booked team tends to run late, because waiting time climbs steeply as people near full capacity. Small requests wait behind the busiest person. It improves when repeatable work comes off the busiest person and some slack is left.

The team is fully booked. Everyone is busy all day, the schedule looks efficient, and still everything is late. Small requests wait for days.

## What owners try

Owners keep everyone at full capacity, because idle time feels like waste. They add another project to fill any gap and ask the team to work faster.

## Why a full week makes work wait

When a person is nearly always busy, any new request has to wait for them to finish what they started. Each request waits longer as they near fully booked, and the wait grows faster and faster. A fully booked person is a queue by design.

The busiest person is usually the one everything passes through, so their queue becomes the team's lateness.

## Signs of waiting on the busiest person

- Quick asks sit for days until the busiest person is free.
- The busiest person is on every thread and every approval.
- Quick questions pile up in their inbox.
- Urgent work jumps the line and delays everything behind it.
- The team looks full, yet deadlines still slip.

## Find who work is waiting on

1. **List what is late this week** Work is waiting on someone in each case.
2. **Next to each item, write the name it waited on** The longest waits matter most.
3. **See which name repeats** That person is the line.
4. **List what they did more than once** The same reply, check or update.
5. **Pick the one repeated job to move first** Start with the job that takes the least judgment.

## What to take off the busiest person

Look at what that person does again and again: the same checks, the same replies, the same updates. Repeatable work can follow a written rule or a drafted step that a person approves, so it stops waiting in their line.

*Work that waits on the busiest person, and where each kind can move.*

| Work that waits on them | Where it moves |
| --- | --- |
| The same replies, again and again | Drafted from a template for a person to approve |
| Status updates | Sent automatically when the work moves to its next stage |
| First drafts of routine documents | Prepared ahead for a person to review |
| Judgment calls | Stay with the busiest person |

Leave some slack on purpose. A person who is not booked solid can take the urgent thing without everything else slipping.

## Decisions you keep

- Decisions about how much slack to leave.
- Which work stays with the busiest person.
- What a draft says before it goes out. A person approves it.

[What the system can see and change](https://signalnine.io/access-and-data)

The system behind this: repeatable work taken off the most-booked person, with drafts a person approves and some slack left in the week.

## Questions

**Why is my team fully booked and everything still late?**

A person near full capacity has no room for anything new, so each request waits for them to finish, and the wait stretches as they fill up.

**Is this a people problem or a planning problem?**

Mostly neither. It is how queues behave: waiting grows fast as anyone nears full. Planning decides how much slack the busiest person has.

**Do I have to hire another person?**

Not first. Look at what repeats on the busiest person's plate. Hiring into the same shape gives the same queue, though a hire can be right once repeatable work is off that person.

**What is a good utilization rate for a team?**

There is no single right number. The point is to leave enough slack that the busiest person can take what arrives without everything behind it slipping.

[EMAIL ME ONE EXAMPLE](https://signalnine.io/contact#write) Send one example of where this happens, and I'll say what I'd change first.

## Related

- [The owner-approval bottleneck: when every yes waits for you](https://signalnine.io/md/bottlenecks/owner-approval): Replies, proposals and discounts all wait for the owner's yes. Written rules send the routine to a named person and bring the owner only the exceptions.
- [How fast can your proposals go out with the time you have?](https://signalnine.io/md/tools/proposal-throughput): Enter your proposals a month, the hours each takes and the spare hours you have. See whether they fit, the queue they build and your fastest turnaround.
- [Why clients keep asking "where are we on this?"](https://signalnine.io/md/bottlenecks/where-are-we-on-this): Many client check-ins exist because an update was missing. Answering faster does not stop them. Status sent before they ask, from the work itself, does.
- [A drafted reply to each lead, approved from your phone before it sends](https://signalnine.io/md/systems/inquiry-desk): AI drafts replies to lead emails that pass a junk screen, from your business facts. Risky asks get flagged. Nothing sends until a person approves it by phone.

---
Mashrur Rahman, Founder, SignalNine. Published 2026-10-17, updated 2026-10-17.
Id: P36
Canonical: https://signalnine.io/bottlenecks/fully-booked-and-still-late