Stop pretending your team is 100% available. Plan in three buckets and the quarter finally lands.
Most capacity plans break by week 2. A 3-bucket model — committed, stretch, slack — keeps planning realistic for 8 weeks straight.
This page covers team capacity planning in practice: what to do first, how to turn it into real blocks in your calendar, and how to keep the plan alive when the day changes. Everything below is how we use Hioii ourselves — capture in Brain Dump, choose three outcomes, and box them into 30-minute slots with buffers.
Start from 40h/week, subtract meetings, 1:1s, support rotations, PTO. Most engineers have 22–26h of actual build time. Use that, not 40.
60% committed (the roadmap), 25% stretch (nice-to-have), 15% slack (interrupts, paying down debt). Anything over 85% breaks by week 3 — guaranteed.
A quarterly plan is a guess. Bi-weekly re-planning takes 30 min and survives reality. Lock the next 2 weeks; sketch the following 6.
Start in Brain Dump and empty your head — tasks, ideas, worries — without sorting them. Then mark the three that define a successful day and drag them onto the Time Box grid, where each block is 30 minutes and every block carries a buffer. When something breaks (and it will), Auto-Organize re-plans the rest of the day instead of leaving you with a stale schedule about team capacity planning.
Teams do the same thing in Squad: a shared backlog, delegation with clear owners, and availability that shows busy or blocked slots without exposing the private content of anyone's calendar. Managers see delivery speed and a traffic-light view of what is on track — measurement without surveillance.
Hioii is free to start on the Basic plan, which includes monthly AI credits. Paid plans add more credits, longer history retention, Take Off data export and team features such as seats, shared projects and agent access through MCP.
A spreadsheet with 3 columns per person works. Or use Hioii team view — it sums available hours from time boxes automatically.
They have 8–12h build time. Plan accordingly. Pretending otherwise is how managers burn out.
In real data, teams that book 100% deliver less than teams at 85%. The slack is what absorbs interrupts without breaking commits.