Philippines staffing guide · Published
Write a capacity warning note before an outsourced queue overloads
A warning that arrives after the deadline is an apology. Define the threshold, separate volume pressure from process pressure, and end the note with a decision request.

The short answer
Set a visible threshold, state whether the pressure is volume or process, and end with a named decision and a time. Escalate before the customer promise is at risk.
Define the warning threshold in advance
A capacity warning is useful only if the team knows what number triggers it. Set the threshold from the queue's normal range, not from the worst day anyone remembers. Use two signals: the number of items waiting and the age of the oldest item.
Either signal can justify a warning, and together they show whether the queue is busy or stuck. Write the thresholds where the team can see them.
Review the thresholds after a quiet month and after a busy one. A threshold that never triggers is too high, and one that triggers every week is too low, so both need a note in the change log. Adjust with the evidence rather than the mood of the meeting.
Keep the change log beside the number so the team knows why it moved. A threshold without a history is just a guess, and a guess cannot be defended when the queue is under pressure.
Separate volume pressure from process pressure
A queue can grow because more work arrived or because the work became slower. The response is different in each case. Volume pressure needs capacity, triage, or a delay message.
Process pressure needs a fix to the step that is blocking items. A warning note should state which one it sees, what evidence supports the view, and which remedy the reader should consider first.
Look at the age distribution before calling it volume. If new items are moving normally and old items are stuck, the problem is a blockage rather than a flood. If every item is aging at the same rate, the team is genuinely short of capacity.
Record the pattern in the note with two or three examples. The pattern is more persuasive than a single average, especially when the reader has to choose between adding capacity and fixing a step.
Write a short note with a decision request
The note should fit on one screen and end with a decision. State the queue, the threshold that was crossed, the evidence, and the options. Give each option a cost and a consequence so the reader can choose without another meeting.
Name the person who must decide and the time by which the decision is needed. A warning without a decision request is only a complaint.
Keep the tone factual and avoid blaming the team. The note is about the queue, not about who worked hard. Use the numbers, the examples, and the customer promise that is at risk.
Then state what the team will do while waiting for the decision, including which items it will protect first. That shows ownership and prevents the note from becoming a reason to stop, even when the answer takes another day or two.
Escalate before the queue misses a promise
The first warning should arrive while there is still time to protect the promise. If the note appears after the deadline has passed, the only remaining decision is how to apologize. Work backward from the customer commitment to find the latest useful warning point.
Build that point into the threshold so the team does not have to judge it in the moment. Early warnings are cheaper than recovery, and a warning that names the decision is cheaper still.
Send the note to the person who can change capacity, not only to the person who shares the queue. Copy the account owner so the customer conversation can start early. If the decision is not made by the stated time, escalate to the next level with the same note.
Do not rewrite the facts for the new reader. A consistent record makes the escalation credible.
Review warnings to improve forecasts
Collect the warnings for a quarter and compare them with what actually happened. Some warnings will have predicted a real problem, and some will have been false alarms. Both are useful because they show where the threshold or the forecast is wrong.
Adjust the model with the evidence and note the change. The goal is fewer surprises, not fewer warnings.
Share the review with the team that does the work. They see the arrival pattern before the dashboard does and can explain a spike that the data alone cannot. Ask what signal they noticed first, and whether it appears before or after the threshold.
Add that signal to the warning note if it is observable. The best early warning is often a person saying the queue feels different, and that signal should be recorded before it is explained away.
Close the loop with the client
A warning that changes capacity should end with a short note to the client. State what was at risk, what was decided, and what the client should expect. Do not wait for the customer to notice a delay before explaining it.
A clear message protects the relationship and gives the client a chance to adjust its own plans. The note can be three sentences if the facts are clear.
Review the client's response at the next operations meeting. If the client consistently adds work without noticing the warning, the intake and priority rules need a conversation. If the client responds quickly, the warning is working and the threshold may be too cautious.
Either way, the review turns a single warning into a shared understanding. That understanding is the real capacity control.
Questions to copy for the sales call
- "What waiting count or oldest-item age triggers a warning today?"
- "Which step is blocking the oldest items in the queue?"
- "Who can approve extra capacity, and how quickly?"
- "What customer promise is at risk if we wait another day?"
Sources
- BLS Handbook of Methods: Methods for measuring workload and interpreting operational data.
- GAO: Assessing Data Reliability: Method for judging whether operational evidence is complete enough to act on.
- SBA: Manage your business: Guidance on planning capacity and managing business operations.
Common questions
How often should the threshold be reviewed?
Monthly at first, then quarterly once the range is stable. Review sooner after a scope change or a new client.
Should the note go to the client?
Send it to the person who can change capacity, and copy the account owner. The client sees it when the decision involves the customer promise or scope.
What if nothing happens after the warning?
Escalate with the same note and a new decision time. Record the delay, because the pattern is useful when the process is reviewed.
Can a warning be verbal?
A verbal warning is faster but easy to lose. Follow it with the short written note so the decision and the time are recorded.