Outsourced Philippines guide
Write a Client-Facing Capacity Note Before Adding Another Queue
Use arrivals, completions, handle time, and a named trade-off to show a client what the team can absorb before another queue lands.
A client often adds a queue with a friendly message and an assumption that the team has spare capacity. The specialist may already be covering a leave, a new report, and an approval backlog that nobody counted. Without a shared note, the request becomes a test of goodwill instead of a scheduling decision. A short capacity note gives the client the numbers, the constraint, and two workable options before the work is accepted.
On this page
Measure arrivals and completions before writing
Export the queue for two normal weeks and count what arrived each day against what the team completed. Use the same definition of done for both numbers so the comparison is honest. A team that receives more than it finishes has a trend, not a bad week, and the note should show that trend. Note any launch, outage, or holiday that makes the period unusual.
Break the counts down by item type, because a total hides the difficult work. Ten password resets and ten reconciliation exceptions consume very different amounts of time. Include the share of items that required rework or a second review, since those hours reduce the capacity available for new arrivals. The client does not need every field, but the note should show the mix behind the headline number.
Describe capacity in the client's units
Translate the team's available hours into the client's own units, such as tickets, invoices, or reports. State the assumption behind the conversion, including the average handle time and the share of time reserved for meetings and checks. If the team can complete forty invoices in a normal week, say so and show the calculation. A client who sees the unit cost can compare a request with the existing load.
Avoid presenting a single utilization percentage as proof of capacity. A team at high utilization may still have room for a small recurring task, or it may be one absence away from missing every deadline. Show the buffer you have kept for leave, breaks, training, and unexpected rework. The buffer is part of the plan, not a sign that the team is underused.
Name the trade-off in plain language
Every new recurring task replaces something unless the client adds capacity. Write the sentence directly: adding this queue within the current hours will delay the weekly report by one day. A trade-off stated in advance is a decision, while the same trade-off discovered later looks like a failure. Keep the sentence specific enough that the client can accept, reject, or change it.
Do not hide the trade-off inside a list of risks with equal weight. Lead with the one existing output that will move, and explain why the two tasks compete for the same hours. If the new queue is genuinely more important, the client can choose to pause the other work. That is a better outcome than a quiet backlog that nobody owns.
Give the client two realistic options
Offer one option that fits within current capacity and one that requires a change. The first might be a smaller scope, a slower turnaround, or a temporary pause on a lower-value report. The second might be additional hours, a new specialist, or a tool change that removes manual work. Both options should be operable, not a real choice plus a warning.
Put a price or a date beside each option, even if the number is an estimate with a stated range. A vague option forces the client to guess, and guessing usually produces the largest request. Give a recommendation with the reason you prefer it. Name the assumption that would change the recommendation, so the client knows what to watch. The note should help the client decide, not simply announce that the team is busy.
Put the note on a fixed cadence
Send the capacity note on the same day each month so the client learns to expect it. Include the current queue, the completed volume, the open exceptions, and the next known constraint. A regular note is easier to trust than a warning that only appears when the team is already behind. It also gives both sides a shared history for the renewal conversation.
Keep the note short enough to read in a few minutes. One page with three numbers and two options is usually enough. Save each version in the account folder so a new manager can see how the workload changed. Add the date and the author at the top so the current version is obvious. The cadence matters more than the format, because a regular habit prevents the surprise request from arriving without context.
Keep the note separate from the sales pitch
A capacity note is an operating document, not a proposal for more services. Write it in plain language, avoid promotional claims, and do not use a client request as an excuse to upsell. The credibility of the note depends on the client believing the numbers are for planning rather than persuasion. If the answer is that capacity is available, say that clearly as well.
When the client does need more capacity, hand the commercial conversation to the account owner after the operating facts are agreed. Separating the two conversations keeps the specialist out of a negotiation they did not choose. It also makes the eventual change easier to implement, because the scope and the trade-off were settled before the price was discussed. The client sees one honest operating picture and one clear commercial next step.
Sources and next steps
Continue with operations support, then confirm scope, authority, and review ownership before expanding the role.