Placeholder Allocation

You know how restaurants let you hold a table for 15 minutes? A placeholder allocation is the scheduling equivalent — it reserves capacity without fully committing to it.

Say a new client project is 80% likely to start in two weeks. You don't want to formally allocate your senior developer yet (the SOW isn't signed), but you also can't risk them getting booked solid on something else. So you drop a placeholder: "Senior Dev — Project Chimera, tentative, March 18-29, 6h/day." It shows up on the timeline in a muted or dashed style — visible, but clearly not confirmed.

Two Flavors

Placeholders typically come in two forms:

Unnamed role placeholder. You know you'll need "a designer" for three weeks, but you haven't decided who. The block sits on a generic row or is tagged by skill. When the project is confirmed, you swap it for a real person — ideally someone whose availability and skills fit.

Named but tentative. You've picked the person, but the project isn't greenlit. The placeholder holds their time in the schedule so other PMs can see the potential conflict.

When to Use Them

Placeholders shine during forecasting and pipeline planning. An agency with a healthy sales pipeline might have 30-40% of next month's schedule in placeholder state — and that's fine. It means you're planning ahead rather than scrambling when contracts land.

The key discipline: convert or kill placeholders regularly. A weekly schedule review should ask "Is this still likely? Promote to confirmed or remove it." Stale placeholders are clutter that undermines trust in the schedule — if half the blocks are ghosts, people stop believing any of it.

When converted, placeholders feed into capacity planning and profitability forecasts, giving you a best-case/worst-case view of upcoming utilization.