A full diary can hide a fragile business. Operating capacity means the team can accept and complete work predictably without requiring constant rescue. It depends on available people, clear decisions, usable systems and the ability to absorb exceptions.
Separate activity from throughput
Count what enters the workflow, what is completed and what remains waiting. Add the age of unfinished work. A team answering many messages may still have an expanding queue of unresolved customer requests.
For a service business, inspect enquiry handling, appointments, quotations and delivery separately. More bookings are not automatically better if delivery capacity is already constrained.
Find the limiting stage
Choose the stage where work waits longest or repeatedly returns for correction. Ask whether the problem is workload, missing information, authority or quality. Extra staff will not necessarily fix a manager-only approval bottleneck; software will not create appointment capacity.
Run a small change at that stage. For example, standardise the information collected before a survey booking so the office does not repeatedly call the customer back. Measure the resulting queue and rework, not just the number of forms completed.
Protect some capacity for unexpected work. A system planned at maximum load has little room for absence or difficult cases. Review whether the team can meet realistic promises during a normal busy week. The useful question is not “How much did everyone do?” but “Can we complete the work we accept without avoidable delay?”