A customer asks whether a job can be ready by Friday. The work looks straightforward, so the answer is yes. Only later does the team remember two other deadlines, a colleague's planned absence and the time needed for review.
The problem may not be poor effort. It may be that the promise was made before anyone looked at the work already in progress.
A small team does not need complicated capacity software to make a more reliable commitment. It needs a short, shared picture of what can reasonably be done.
Start with work already promised
Before accepting a new deadline, write down the important commitments due in the same period. Include work that is nearly finished but still needs checking, sending or approval.
A calendar shows meetings and absences. A task list shows work. Looking at both together is often more useful than either on its own.
Count usable time, not just working hours
Five people working a full week do not have 200 hours available for a new project. Customer questions, routine support, administration and unexpected issues take part of that time.
Use a rough estimate based on a normal week. The aim is not to measure every minute. It is to avoid filling the plan with more work than the team can actually deliver.
Identify the step that could hold everything up
Some jobs need one particular person to approve a draft, access a system or answer a specialist question. The rest of the team may have time, yet the job will still wait at that point.
Ask what depends on one individual and whether a suitable backup or an earlier review is possible. Do not assume that availability on paper means every skill is interchangeable.
Leave room for interruptions
Reserve a sensible amount of time for routine requests and ordinary surprises. The right margin depends on the work: a team handling daily customer enquiries may need more flexibility than one working on predictable internal tasks.
Treat this margin as part of the plan, not as unused time that must immediately be filled.
Make the promise precise
Instead of saying only 'Friday', clarify what will be delivered and what remains outside the commitment. A draft for review, a tested final version and a full handover are not the same milestone.
If the date is uncertain, offer a realistic range or a confirmed update point. Clarity early is usually better than an apology after the deadline.
Review capacity without monitoring individuals
A brief team check once or twice a week can cover what is committed, what is blocked and which deadline needs a decision. Avoid turning this into personal activity scoring or collecting unnecessary details about colleagues.
When an urgent task arrives, decide together what will move. A priority is meaningful only when something else is deliberately deprioritised.
Good capacity planning is not about keeping everyone busy every moment. It is about making promises that the team can meet while still having room to do the work well.
