- Plan with usable time.
- Translate customer work into one common unit before comparing demand with the people, skills and equipment truly available.
- Resolve the biggest gap first.
A service business can look busy and still miss a deadline. The diary shows paid hours, while real work also includes setup, travel, questions, reviews and fixes. A weekly capacity plan brings those demands into one view.
The plan is not a promise that every estimate will be right. It is a decision tool. It helps an owner choose what the team can start, what needs a new date and where one scarce skill could block several jobs.
Define one useful unit of capacity
Pick a unit that matches the work. A design studio may use delivery hours. A cleaning firm may use crew shifts. A repair shop may track technician hours and service bays.
Do not mix hours, jobs and revenue in one total. Ten small jobs with familiar steps may need far less effort than one complex project with new dependencies or unusual approvals. Revenue matters for the business, but it does not show whether the right person or tool is free.
The Association for Project Management describes resource optimisation as matching labour and non-labour resources to a schedule. It includes people, materials, equipment and facilities. Your weekly plan should show any resource that can stop delivery.
Start with usable time
List each person, crew, room or machine needed next week. Begin with the hours or shifts that could be worked. Then remove known leave, training, fixed meetings, routine support and other committed duties.
The result is usable capacity. It is not a target for filling every minute. Keep uncertainty visible instead of hiding it inside an aggressive total.
Track rare skills separately. Four available people cannot replace the only engineer who can approve a technical drawing and release the next stage. The APM capacity framework asks planners to consider skills, time, cost, quality and dependencies.
Build the demand list from real promises
Pull work from signed orders, booked appointments, accepted quotes and active projects. Add internal work that cannot wait. Keep possible sales in a separate forecast lane until the customer commits.
For each item, record the customer, outcome, due date, remaining effort, needed skill and current owner. Use ranges when the work is uncertain. A range exposes doubt that one neat number would hide.
If demand starts in the pipeline, connect it to the simple sales forecast. The forecast shows what may arrive. The capacity plan shows what the business can responsibly place into the week.
Compare demand and capacity by constraint
Totals can mislead. The team may have spare hours overall but no free installer on Thursday. Compare the work by day, skill and key equipment.
| Plan line | What to record |
|---|---|
| Usable capacity | Available time after known fixed work |
| Committed demand | Remaining work tied to a real promise |
| Constraint | Skill, person, room, vehicle or equipment |
| Gap | Demand above or below usable capacity |
| Decision | Owner, action and date |
Mark the first point where demand exceeds the matching capacity. That is the decision line. A later shortage may disappear when the earlier issue is resolved.
Choose an action before moving the promise
A gap does not always mean “hire.” First check whether the task is required, correctly scoped and placed in the right order. The GOV.UK Service Manual advises teams to review the backlog before adding people and to change scope or delivery dates when the right skills are not available.
Your choices may include moving a start date, reducing optional scope, splitting the delivery, changing the sequence or using approved outside help. Each choice has a cost and a customer effect. Name both.
Hiring may be the right answer when the gap is stable and the role is clear. Use the first-employee paperwork guide to map the administrative work before treating a new hire as instant capacity.
Run one short weekly review
Use the same view and the same order each week. First check changes to people and equipment. Next confirm committed jobs. Then resolve the largest gap and record customer messages.
End with named decisions, not a colourful board. “Busy on Thursday” is an observation. “Sam will offer the Friday slot to Oak Street by noon” is an action.
GOV.UK guidance recommends combining performance measures with evidence about the user journey. For a small firm, compare the plan with what happened: completion, delay, rework and customer chase points.
Review estimates without blaming people
At week end, compare planned effort with actual effort. Ask what changed. Look for unclear scope, waiting, repeated approvals, missing inputs, travel or avoidable rework.
Do not turn every difference into a performance score. An estimate can fail because the work changed or the system was weak. The aim is a better next plan.
If the same delay repeats, document the stable fix with the one-page SOP method. If the delay begins at handoff, tighten the customer onboarding checklist.
Labelled example: A five-person web studio has 112 usable delivery hours next week after leave, support and fixed meetings. Three committed jobs need an estimated 96 to 118 hours. One launch also needs the only developer who can approve a payment integration.
The owner does not treat 112 as a safe promise. She moves a low-priority internal redesign, confirms the customer's missing access and offers a later start for a fourth job. These figures illustrate the method; they are not a standard utilisation target.
Use a seven-field weekly plan
- Week and review owner
- Usable capacity by person, skill or equipment
- Committed customer outcome
- Due date and remaining effort range
- Dependency or constraint
- Gap and decision
- Next review date
Start with one week and one board. After four reviews, keep the fields that changed decisions. Remove decoration that nobody uses.
Frequently asked questions
What is a weekly capacity plan?
It is a short view of committed work, usable people or equipment time, skill constraints and the decisions needed for the coming week.
Should every staff hour be booked?
No. Start with time that is genuinely available after known leave, meetings, support, administration and other fixed work.
What if demand is higher than capacity?
Choose among moving a date, reducing scope, changing the work sequence, using approved outside help or declining work that cannot be delivered well.
How often should the plan change?
Review it on a fixed weekly rhythm and update it when a material job, deadline, absence or equipment constraint changes.
Sources and scope
Association for Project Management: resource optimisation · APM Competence Framework: resource capacity planning · GOV.UK Service Manual: changing team size · GOV.UK Service Manual: measuring service success. This is general operational guidance, not a staffing, legal or financial rule.