Measure the baseline before peak

A capacity trigger needs a baseline, and the baseline should come from ordinary weeks rather than the busiest week on record. Measure the volume, arrival pattern, handling time, and rework rate for each queue over at least four normal weeks. Separate the work that scales with volume from the work that scales with exceptions. Without that split, a peak plan will add people to the wrong queue.

Record the baseline in a short table that the operations lead can read beside the live dashboard. Include the day of week and the hour of day when the queue usually peaks. Note the assumptions behind the handling time, such as whether it includes review or only first touch. The baseline is a reference point, not a promise that next season will look the same.

Choose leading indicators

Backlog size is a lagging indicator, because the queue is already late by the time it grows. Choose two or three leading indicators such as arrival rate, oldest-item age, and the share of items waiting for a supervisor. A rise in any one of them may be noise, but a rise across two or three is a reason to act. Keep the set small enough that the team checks it every day.

Include one indicator that measures the human cost of the peak, such as overtime hours or the number of skipped breaks. A plan that protects the queue by exhausting the team will fail in the following month. The leading indicators should show whether the team is absorbing the peak or merely postponing the damage. Review the indicators with the same owner who will approve the response.

Set trigger thresholds in writing

Write the threshold as a number and a duration, such as an oldest-item age above two days for three consecutive mornings. A threshold without a duration will fire on a single bad hour and lose credibility. Name the person who confirms the trigger and the person who can approve the response. Keep the rule where the team can see it, not in a planning document that nobody opens during the peak.

Define a green, amber, and red state so the response is proportionate. Green means the normal routine continues, amber means a named backup takes one queue, and red means the team opens the pre-approved capacity action. Each state should have an owner and a check time. A threshold that does not change anyone's behavior is only a report.

Separate queue types

A single capacity number hides the difference between a queue that can wait and a queue that cannot. Separate customer-facing work, payroll or billing inputs, and internal cleanup into distinct lanes with their own triggers. A backlog in the cleanup lane may be tolerable for a week, while a backlog in the payroll lane may be a same-day problem. The trigger should reflect the consequence of waiting.

Give each lane its own owner and its own service expectation. When the team is under pressure, protect the lane with a hard deadline first and let the flexible lane absorb the delay. Record that priority decision in advance so the specialist does not have to choose between two managers in the moment. The priority order should be reviewed when the client's business cycle changes.

Pre-approve the hiring steps

The worst time to discover that a requisition needs three approvals is the week the queue breaks. Map the steps to add a temporary specialist, an extra shift, or a cross-trained backup, and get the approvals before the peak. State the budget range, the start date, and the training time for each option. The trigger should release a pre-approved action, not start a new negotiation.

Keep the approval record with the capacity plan and note the date it expires. If the peak passes without using the option, close it rather than leaving an open authorization. A pre-approval that nobody remembers can become an uncontrolled spend. The operations lead should confirm the current status at the start of every month.

Cross-train before the peak

Cross-training is the cheapest capacity option and the easiest to postpone until it is too late. Choose one backup for each critical lane and give that person real practice on ordinary days, not only a written procedure. Record the tasks the backup can complete without help and the tasks that still need a supervisor. A backup who has never handled a live item is a name on a list, not coverage.

Schedule the practice during a normal week so a mistake does not land in the peak. Rotate the backup through the full queue, including the exception path and the handoff note. Ask the backup to complete one item while the primary observes and one item alone. Update the cross-training record after each practice session.

Tell the client what the trigger changes

The client should know in advance which service levels may change when the trigger fires. Explain the amber and red states in plain language and name the contact who will confirm the change. Avoid promising that the team will absorb unlimited volume, because that promise removes the reason for the trigger. A clear threshold protects the client from a surprise more than a vague assurance does.

When the trigger fires, send a short notice with the current state, the action taken, and the expected effect on turnaround. Do not wait until the queue is already late. If the action requires a temporary cost or a changed deadline, ask the client owner to approve it in writing. Keep the notice with the capacity record for the next review.

Review the trigger after the peak

After the peak, compare the trigger dates with the actual queue performance and the cost of each response. Ask whether the threshold fired too early, too late, or at the right time. Check whether the backup was actually available and whether the pre-approved action started when expected. Record the answers beside the original plan.

Change one threshold or one step at a time, then keep the earlier version for comparison. If the peak produced no trigger at all, the baseline may be too low or the indicator may be measuring the wrong thing. Close the review with one owner and one date for the next test. The capacity plan should improve with each season rather than restart from scratch.

If the records and decision rights are already defined but need a steady operator, workforce operations support can turn approved examples, decision lines, and review rules into a draft your manager can check. The manager still owns exceptions and final approval.

For the next step, compare this workflow with Write a work sample that predicts outsourced performance and Map Philippine holidays into a client service calendar. For access and oversight, use the authoritative planning reference alongside your own policy.