Methodology
Utilisation to Headcount Planner methodology
Educational only: Business decision support, not accounting, tax or legal advice.
Privacy: Calculations run locally; Margin101 does not receive your commercial inputs.
Update policy: Reviewed when formulas or official dependencies change.
Scope: Market-neutral small-business planning using your own assumptions.
1. Formulas and units
requiredHeadcount = ceil(required billable hours รท billable capacity per person)Where
- requiredBillableHours
- Required billable hours (hours/period)Source: User assumption
- requiredHeadcount
- Required Headcount (count)Source: Calculated output
- billableCapacityPerPerson
- Billable Capacity Per Person (hours/period)Source: Calculated output
billableCapacityPerPerson = available hours per person ร target utilisationWhere
- availableHoursPerPerson
- Available hours per person (hours/person/period)Source: User assumption
- targetUtilisation
- Target utilisation (proportion of paid capacity billable)Source: User decision
- billableCapacityPerPerson
- Billable Capacity Per Person (hours/period)Source: Calculated output
headcountGap = required headcount โ current headcountWhere
- currentHeadcount
- Current headcount (people)Source: Business record
- requiredHeadcount
- Required Headcount (count)Source: Calculated output
- headcountGap
- Headcount Gap (count)Source: Calculated output
currentBillableCapacity = current headcount ร billable capacity per personWhere
- currentHeadcount
- Current headcount (people)Source: Business record
- billableCapacityPerPerson
- Billable Capacity Per Person (hours/period)Source: Calculated output
- currentBillableCapacity
- Current Billable Capacity (hours/period)Source: Calculated output
capacityGapHours = required billable hours โ current billable capacityWhere
- requiredBillableHours
- Required billable hours (hours/period)Source: User assumption
- currentBillableCapacity
- Current Billable Capacity (hours/period)Source: Calculated output
- capacityGapHours
- Capacity Gap Hours (hours/period)Source: Calculated output
Money inputs and outputs use the currency selected in the scenario without changing the canonical methodology. Rates, margins, utilisation and buffers are entered as percentages and converted to decimal values for calculation.
2. Worked example
Input assumptions
The worked rows are rendered from the registered engine and visible default fixture.
- Required billable hours
- 1,000 hours/period
- Available hours per person
- 160 hours/person/period
- Target utilisation
- 0.75 proportion of paid capacity billable
- Current headcount
- 7 people
Calculation and outputs
requiredHeadcount
requiredHeadcount = ceil(required billable hours รท billable capacity per person)- Required billable hours
- 1,000 hours/period
- Available hours per person
- 160 hours/person/period
- billableCapacityPerPerson
- 120 declared output unit
- currentBillableCapacity
- 840 declared output unit
- capacityGapHours
- 160 declared output unit
Engine result: 9
billableCapacityPerPerson
billableCapacityPerPerson = available hours per person ร target utilisation- Required billable hours
- 1,000 hours/period
- Available hours per person
- 160 hours/person/period
- Target utilisation
- 0.75 proportion of paid capacity billable
- capacityGapHours
- 160 declared output unit
Engine result: 120
headcountGap
headcountGap = required headcount โ current headcount- Required billable hours
- 1,000 hours/period
- Current headcount
- 7 people
- requiredHeadcount
- 9 declared output unit
- currentBillableCapacity
- 840 declared output unit
Engine result: 2
currentBillableCapacity
currentBillableCapacity = current headcount ร billable capacity per person- Required billable hours
- 1,000 hours/period
- Available hours per person
- 160 hours/person/period
- Current headcount
- 7 people
- requiredHeadcount
- 9 declared output unit
- billableCapacityPerPerson
- 120 declared output unit
- headcountGap
- 2 declared output unit
- capacityGapHours
- 160 declared output unit
Engine result: 840
capacityGapHours
capacityGapHours = required billable hours โ current billable capacity- Required billable hours
- 1,000 hours/period
- Available hours per person
- 160 hours/person/period
- Current headcount
- 7 people
- requiredHeadcount
- 9 declared output unit
- billableCapacityPerPerson
- 120 declared output unit
- currentBillableCapacity
- 840 declared output unit
Engine result: 160
Example
The worked rows are rendered from the registered engine and visible default fixture.
- Billable Capacity Per Person
- 120 hours/period
- Required Headcount
- 9
- Headcount Gap
- 2
- Current Billable Capacity
- 840 hours/period
- Capacity Gap Hours
- 160 hours/period
The exact engine-derived outputs are shown in the labelled rows below.
Interpretation
The utilisation to headcount result uses only the entered commercial assumptions.
3. Validation and boundary checks
- Inputs must be finite and remain within the visible boundaries.
- Rates are decimal values and all monetary inputs use one consistent currency and period.
- Whole operational capacity is rounded only where the engine explicitly applies floor or ceiling.
- Required billable hours minimum
requiredBillableHours โฅ 0 hours/periodโ A lower value is rejected before calculation.- Required billable hours maximum
requiredBillableHours โค 10,000,000 hours/periodโ A higher value is rejected before calculation.- Available hours per person minimum
availableHoursPerPerson โฅ 0 hours/person/periodโ A lower value is rejected before calculation.- Available hours per person maximum
availableHoursPerPerson โค 10,000,000 hours/person/periodโ A higher value is rejected before calculation.- Target utilisation minimum
targetUtilisation โฅ 0 proportion of paid capacity billableโ A lower value is rejected before calculation.- Target utilisation maximum
targetUtilisation โค 0.99 proportion of paid capacity billableโ A higher value is rejected before calculation.- Current headcount minimum
currentHeadcount โฅ 0 peopleโ A lower value is rejected before calculation.- Current headcount maximum
currentHeadcount โค 10,000,000 peopleโ A higher value is rejected before calculation.
4. Assumptions and source classification
- All costs, prices, hours, probabilities and volumes are user-supplied; no market benchmark is inferred.
- Tax is outside these neutral commercial comparisons.
- The engine retains full precision; formatting never feeds back into calculation.
This planner has no current policy-data dependency. Its commercial assumptions are user supplied. Registered family-level regression suites exercise the shared business-logic engine and worked-result reconciliation.
5. Limitations
- The model does not predict demand, delivery performance, contract enforceability or customer behaviour.
- It does not replace accounting, tax, legal or financial advice.
This is educational decision support, not tax, accounting, legal or financial advice. Check the treatment of your actual transactions under the rules that apply to your business and seek qualified advice where appropriate.
6. Update and evidence policy
Registered family-level suites test formula invariants and example reconciliation; the release ledger records that coverage without claiming a separate oracle for every line of public copy. There is no official threshold or benchmark to refresh for this planner. Commercial inputs remain user-supplied because they vary by business and contract.
Change history
- : Initial public release of the planner and methodology after pre-launch calculation, content, source and interaction review.
Related reading
Guides to interpret the decision and its assumptions.
- Agency Economics: Utilisation, Rate, Scope and Pipeline
Connect utilisation, recovery rate, scope delivery and committed pipeline without treating one ratio as an agency forecast.
Read guide