Skip to content
Okouro Glossary
Table of contents DefinitionFormulaWhy it mattersHow to make capacity planning usefulHow Okouro shows itQuestionsRelated terms
Back to the glossary
People

Capacity planning

Capacity planning matches future consultant supply (headcount, skills, availability) against future demand from committed missions and weighted pipeline, so hiring and training decisions come before the gap bites.

Definition

Capacity planning compares the supply you will have next quarter, headcount, skills and availability dates, with the demand you expect: missions already committed plus the part of the pipeline you choose to weight. It answers hiring and training decisions. Allocation answers a different question, who is on which mission today. The two are read together, never confused.

The unit is days or person-days per period, compared skill pool by skill pool, never headcount globally. Forty consultants is the wrong unit when the demand is for senior Java developers. A global average hides a bench in one pool next to a shortage in another, and that average is the number that triggers both failure modes at once.

Formula

Capacity for a period = sum over people of (available working days x billable share); demand = sum over committed and targeted missions of required days.

Example: 10 consultants x 20 days x 80% = 160 billable days available against 175 days of committed demand, a 15-day gap before the pipeline even counts.

Why it matters

Two failure modes book most of the damage. Over-hire against an optimistic pipeline and the bench eats the margin you counted on. Under-hire against real demand and you miss placements, then subcontract at worse rates to keep clients whole. Both come from the same shortcut, one global headcount number instead of a pool-by-pool view of days. Planning per pool turns a vague worry into a dated gap you can decide on.

How to make capacity planning useful

  1. 1

    Plan per skill pool, never per global headcount. A single average hides a bench in one pool and a shortage in another, and both cost money.

  2. 2

    Refresh the supply side with real leave plans, not theoretical calendars. Availability dates move, and a plan built on assumed presence overstates capacity every quarter.

  3. 3

    Decide each gap explicitly: hire, subcontract, or decline. Write the decision down with a date, so the next review starts from a choice and not a hope.

How Okouro shows it

The Okouro allocation board shows current placements and upcoming end dates per person, which is exactly the supply side a capacity plan starts from. Keep headcount, skills and availability in one view, and start from the free plan.

Questions

Capacity planning or staffing?
Staffing places people on missions you already know about, matching available consultants to open slots. Capacity planning decides the roster and the skills you need for demand that has not arrived yet. Staffing works inside the team you have; capacity planning decides whether that team is the right size.
How far ahead should we plan?
As far as your commitments and your credible pipeline reach, commonly one to four quarters. Beyond that horizon the supply side becomes guesses, people you have not hired and skills you have not verified, and the plan stops informing hiring decisions.

Stop patching your operation together.

One account, one workspace, every role. Set it up today and let the month close itself.