Capacity check before commitment

This is the single most important workflow in CapacityIQ — and the highest-leverage rule we recommend adopting.

The rule

Not after. Not "I'll check later." Not "we'll figure it out in sprint planning."

At the moment of commitment.

Why this matters

Most missed deadlines aren't because the team got slow. They're because the PM committed to work without checking whether the team had capacity to do it.

Eight months ago I (the founder, Sabelo, talking from real experience) committed Netstar to a hardware certification deadline. The certification engineer was already at 110% utilization on existing work. Promising the new initiative meant slipping two existing ones. We slipped them. The CEO was unhappy. The engineer burned out.

Adopting "capacity check before commitment" took our on-time delivery rate from 60% to 89% in one quarter — without changing team size or speed.

How Roadmap OS makes this easy

When you add a new initiative on the Roadmap module:

1. Click + Add initiative (or press N)
2. As you set the date range, the capacity sidebar slides in from the right
3. The sidebar shows team availability for that date range
4. Each team member's row shows their current utilization for those weeks
5. Add hours allocation per person at the moment of commitment

If a row goes red as you add hours, you've over-committed. Either:

• Pick a different date range (capacity might be different a month later)
• Reduce hours / scope
• Reassign to a different person
• Or — push back on the commitment

The mental shift

The hard part isn't using the tool. It's building the habit of looking before you say yes.

When the CEO asks "can we ship this in Q3?" — the new answer is:

"Let me check capacity. Give me 60 seconds."

Open Roadmap OS. Look at CapacityIQ for Q3. Then answer based on what you actually see, not based on optimism or deadline pressure.

When to push back

If your check shows over-commitment:

1. Quantify it ("the team is at 115% for that window")
2. Propose alternatives ("we can ship in Q4 instead, OR we can drop these other two initiatives, OR we can hire one more engineer")
3. Let the leader choose

Pushing back with capacity data is much more credible than pushing back with vibes.

Make it a hard rule

Add this to your team's Definition of Commitment:

Before any initiative is added to the active roadmap, the proposing PM must include a capacity check screenshot showing the affected team's utilization for the proposed date range.

Yes, this slows down the "let's just commit" moment. That's the point.

Next steps

• The 80% utilization rule — why never plan to 100%
• Cross-functional capacity — handling design + eng + QA in the same plan