Engineering employment capacity planner

Count paid time first, then remove the time already committed to leave, learning, meetings and support. The result is a planning allowance for feature work, never a delivery promise. This local tool sends and stores nothing.

1. Planning window and employment inputs

Employees in this plan Nominal working days per employee Planned start date for new starters New starters in this team Nominal days missed per new starter

Nominal days are your window assumption, not a country's legal working-time figure. Count a missed day only once. If new starters have an unknown start date or missed days, clear the field; the start-adjusted result will be withheld. With no new starters, set missed days to zero; a start date is not needed. Confirm contract readiness, local holidays, leave and working pattern with the employer.

2. Exclusive non-feature allocations, team totals

Planned leave days Training and learning days Meetings and coordination days Support and on-call days Days counted in two buckets

All entries are person-days across the team. Enter overlap only when the same paid time appears in exactly two allocation buckets, such as a support day also entered as a meeting day. Leave before someone's actual start is not paid time in this window: remove it from leave instead. Support allocation includes on-call work only where it consumes planned working time; assess out-of-hours arrangements separately.

3. Release choice and sensitivity

Feature days the proposed scope needs Meetings/support uncertainty, ± % Non-feature days for one extra ready employee

The extra employee is a hypothetical person ready for this whole window. Their non-feature allocation is editable; hiring, access and ramp time still need separate validation. The sensitivity range changes meetings and support only, holding leave, training and entered overlap fixed. If that overlap becomes impossible at either end, the range is withheld. It is a scenario, not a statistical confidence interval.

Planning result

Before a release date becomes a promise

Your engineering estimate: validate the feature-day scope with the team; check dependencies, parallel work and ramp time. Days do not convert to story points.
Employer/provider confirmation: verify the applicable leave, public-holiday calendar, working pattern, contract and feasible start date in each country.
Your operating choice: assign actual support coverage and paid learning time before calling remaining days feature capacity. Never use assumed unpaid overtime to close a gap.