Seasonal Capacity Contracting with Outsourcing Partners
Seasonal capacity contracting with outsourcing partners is the design of commercial terms under which a business process outsourcing partner carries a share of a buyer's seasonal demand swing as a standing, priced capability, so that capacity moves with the demand curve without the buyer racing to the vendor when it falls behind or releasing trained agents when it catches up. It treats flexibility as something bought and measured rather than requested, and it sits alongside the buyer's own hours, cross-skilling and leave levers described at Supply Elasticity in Workforce Planning.
The page covers the units in which capacity is committed, the notice structure that lets a forecast become a contractual quantity, the pricing models available, the economics that decide between them, and the questions a buyer should put to a partner before proposing any of it.
The problem: fixed blocks against a moving curve
Most outsourced contact-center capacity is bought as blocks of full-time equivalents at a price per productive hour or per FTE per month. Billing under such contracts can move by only one or two percent from month to month while demand moves by ten or twenty; in one estate examined with this method, billed FTE across a four-month season varied by about one percent [illustrative]. The only ways to change the number are to add a block, and keep paying for it, or to cut one, and lose the training investment when the work returns.
The gap is widest where pools are small. A swing that is a tenth of the whole estate is a tenth of each pool only if every pool moves together; where it concentrates in a few language or product pools, as disruption and regional seasonality make it do, it can be a third or more of a sixty-person pool, which no rounding of schedules absorbs. Pools are gated by product, vendor, line of business, language and hours of operation, so flexibility has to be designed at the pool level, which is why cross-skilling appears in a contracting discussion at all.
Release-and-rehire is rarely the answer. Full proficiency for an experienced corporate travel consultant takes three to six months by industry accounts,[1] contact-center attrition in offshore markets runs between 30% and 50% a year,[2] and replacement cost per agent is widely quoted in the five figures.[3]
Commitment units
What a contract commits determines what can flex.
| Unit | What flexes | Typical behavior |
|---|---|---|
| FTE block, price per productive hour | Nothing inside the block; the block itself at the notice period | Shrinkage sits with the supplier; billed FTE is flat |
| FTE per month | Nothing, by construction | The hours inside are the supplier's. The buyer should ask whether flex hours are included at no charge: the people are already employed and paid, so an additional scheduled hour costs the supplier little beyond the shrinkage it carries |
| Productive hours per week inside a band | Hours per head and heads, within the band | The unit that makes a surge-hours model contractual |
| Transaction or contact | Everything; price moves with volume | The supplier prices the peak into the unit; common for back office, email and simple voice[4] |
| Outcome | A performance component on a base fee, typically 10–20%[5] | Attribution and metric definition disputes |
Moving the commitment unit from FTE to productive hours per week inside a band is the single change that lets the other levers work. It needs one definition of a productive hour that both sides read from the same data.
The lock ladder
A flexible contract needs a forecast that becomes progressively firmer as the date approaches. One structure:
| Horizon | What is locked | Tolerance |
|---|---|---|
| 90 days | An outlook by pool | Indicative |
| 45 days | The weekly band | ±10% |
| 21 days | Daily hours | ±3% per day |
| 7 days | Daily schedule | Fixed |
| 1 day | Half-hourly staffing | ±3% per half hour |
A cap on billing above the lock (for example 5%) protects the buyer from paying for capacity it did not ask for; a protected ramp-down protects it from a band that only works upward. The 45-day lock is the flex band; the daily and half-hourly locks are how it is executed. The buyer's side of the bargain is a rolling thirteen-week forecast by pool, refreshed weekly, because a partner will not carry a band it cannot plan against.
Committed and contingent flex
Two layers should be named and metered separately.
- Committed flex is the band the partner staffs to. It is priced into the base rate, with a small premium for hours above base and a small discount for hours the buyer releases, so that the partner is paid for carrying the option.
- Contingent flex is the layer above the band: bench hours, surge hours, overflow. It is an option the buyer pays a standing fee for and exercises with notice.
The standard mechanism in information-technology and business-process outsourcing is the additional and reduced resource charge with a deadband: a baseline volume, a tolerance (commonly ±5–10%) inside which nothing changes, tiered and declining charges above it, and credits below it.[6] A buyer should ask for it by name. The half that partners resist is the reduced resource charge: the contract has to state how fast the buyer can come down and at what cost, or the band is one-directional.
Six pricing models
| Model | Mechanism | Fits | Watch for |
|---|---|---|---|
| A. Flex corridor on FTE | Base ± x% at 30, 60 and 90 days | Any partner; the minimum ask | Corridors that only go up; penalties on the down side |
| B. Annualized hours with a surge band | Hours per head move inside an annual total (for example a 32–46 band on a 38 base) | Pools in countries whose law allows averaging, see Working-Time Averaging and Annualized Hours in Contact Centers | Country law; agent consent; the trough is a pay cut unless pay is annualized |
| C. Bench or burst hours | The partner's cross-client bench serves the buyer's queues at a bench rate | Multi-client sites | Proficiency and certification; data access; correlated surge (below) |
| D. Per transaction | Price moves with volume | Back office, email, simple voice | The partner prices the peak into the unit; unit definition disputes |
| E. Shaped volume commitment | The buyer commits annual hours; the partner shapes them to the curve | Large deferrable blocks | The partner carries hiring risk and charges for it; needs a trusted forecast |
| F. Growth for flex | More volume to the partner that carries the swing | The partner with the deepest bench in the main language | Concentration; comparability before allocation |
In the estate examined with this method, none of A, B, C, E or F was in force and D applied only to the smallest contracts [illustrative]; a buyer should expect to find a similar picture and should check rather than assume. Seats are also often designated on paper and shared in operation; pricing the few genuinely dedicated seats and pooling the rest is a precondition for any of the six.
The median-base, surge-hours model
One combination worth examining with a partner is model B with the lock ladder. The pool is hired and trained at the median week's requirement. In peak weeks scheduled hours per head rise, toward 45 where the law and the person allow and 50 for a burst of a week or two; in trough weeks they fall toward 30–32. Pay follows hours inside an agreed annual total, so there is no overtime trigger and no pay cut. The partner's commitment is productive hours per week inside the band, agreed a quarter ahead from the buyer's forecast.
What it needs from the partner: a band per pool expressed in weekly productive hours; a price for the band and not only for the hour; cross-skilling as a deliverable, since the pool is only elastic if its people can take more than one queue; committed and contingent layers named and metered; and one productive-hour definition. What the buyer brings: the forecast, the definition, a certified record of who is eligible for which queue, growth where it is earned, and a willingness to pay for the option.
Economics
Two comparisons decide between hours-flex, seasonal hiring and release-and-rehire. Both are arithmetic on stated assumptions [estimated].
Peak capacity. Let the base cost per productive hour be 1.00. A seasonal hire paid for T training weeks and then P peak weeks at 85% of tenured productivity costs (T + P) / (0.85 P) per productive hour: 1.76 at six weeks of training and twelve of peak, 1.96 at eight and twelve, 1.65 at eight and twenty. Overtime costs 1.25 to 1.50 in most jurisdictions and 2.00 where the premium is double time. Hours-flex inside an averaging scheme costs 1.00. Setting the two equal gives the crossover peak length P = T / (premium × 0.85 − 1). At a 1.5 premium the seasonal hire only breaks even against overtime for peaks longer than about 22 weeks (six weeks of training) to 29 weeks (eight weeks), so hours-flex at ordinary overtime rates wins for any seasonal peak. At double time the crossover falls to about 9 to 11 weeks, so where the statutory premium is 2× a head-add becomes competitive for peaks longer than about twelve weeks.
Troughs. Replacing a trained agent costs training weeks (eight to sixteen for skilled travel work) plus recruiting and ramp shortfall, roughly fourteen to twenty-two weeks of loaded pay. Retaining the agent through a trough costs at most the idle fraction of paid hours, and less if hours can fall to thirty. Release-and-rehire pays only when the trough is longer than the replacement cost, and most seasonal troughs are shorter; the December trough in business travel is five weeks.
A shared bench is a weaker option than it looks when the buyer's peaks are correlated with other clients' peaks. A weather or airline disruption hits every travel client of a shared partner at once, so a bench option may be unhonorable on exactly the day it is needed. Bench hours suit seasonal peaks, which are forecastable and spread; they do not suit disruption days. Judge a bench offer on a bad day, not an average one, and hold the disruption reserve in instruments the partner cannot have promised elsewhere.
Four questions for a partner
| Question | What a good answer looks like |
|---|---|
| What flexibility does the current contract give: commitment unit, notice up and down, minimum term, corridor? | A number for each, and the clause |
| At multi-client sites, what shared or bench capacity exists, how is it skilled, and how is it priced? | A rate card for bench hours and the ramp time to the buyer's queues |
| Would the partner run a pool on annualized hours with a band, and what does the band cost against today's rate? | A priced corridor and the human-resources rules behind it |
| Which queues would the partner put in a cross-trained group, and what would it take to certify an agent across them? | A skill map against the buyer's lines of business, a training plan in weeks, a proficiency gate the buyer defines |
Limitations
The lock ladder and the band are design patterns, not published standards; their tolerances come from practice rather than research. The economics use round assumptions on training length and productivity and omit recruiting cost, which makes seasonal hiring look better than it is. Published evidence on pooled or bench capacity in travel is vendor marketing without named clients, prices or service levels. The information asymmetry between buyer and supplier in call-center outsourcing is a studied problem,[7] and a band contract does not remove it; it moves the dispute from headcount to the definition of a productive hour.
Maturity Model Position
At lower maturity, flexibility is requested by email and delivered by goodwill, and the estate's billing is flat. At the level where vendor governance is placed and a single productive-hour definition exists, corridors and resource charges can be written and measured. At the highest levels the band is executed through a lock ladder against a rolling forecast, bench and surge layers are metered separately, and the partner that carries the swing earns volume on measured comparability rather than on relationship.
See Also
- Supply Elasticity in Workforce Planning
- Outsourcing as a Risk Lever
- The Vendor as Relief Valve
- Business Process Outsourcing
- Vendor Ecosystem Restructuring Agenda
- Business Travel Demand Seasonality
- Working-Time Averaging and Annualized Hours in Contact Centers
- Scenario Planning and Contingency Staffing
References
- ↑ Travel Market Report, "Three steps to developing a travel agent training program". https://travelmarketreport.com/articles/Three-Steps-To-Developing-A-Travel-Agent-Training-Program
- ↑ Piton Global, "What is the attrition rate in Philippine call centers?" (citing CCAP and Willis Towers Watson). https://www.piton-global.com/blog/what-is-the-attrition-rate-in-philippine-call-centers/
- ↑ Aureon, "The hidden cost of contact center turnover" (citing Gartner). https://aureon.com/blog/the-hidden-cost-of-contact-center-turnover/
- ↑ RethinkCX, "BPO pricing models guide". https://www.rethinkcx.com/blog/bpo-pricing-models-guide
- ↑ Outpace, "BPO pricing models: FTE, transaction, or outcome?". https://theoutpace.com/articles/bpo-pricing-models-fte-transaction-or-outcome
- ↑ Everest Group, "ARC/RRC in outsourcing contracts" and the Exult fee schedule (Schedule C). https://www.everestgrp.com/?p=38820 ; https://contracts.justia.com/companies/exult-inc-70550/contract/1203185
- ↑ Hasija, S., Pinker, E. J., Shumsky, R. A., "Call Center Outsourcing Contracts Under Information Asymmetry", Management Science 54(4), 2008. https://econpapers.repec.org/RePEc:inm:ormnsc:v:54:y:2008:i:4:p:793-807
