Scope of work for an outsourced task: what to write down

Key takeaways

A scope of work for an outsourced task sets out exactly what the team does: inputs, outputs, expected volumes, turnaround, accuracy target, exceptions and who decides them, systems access, reporting and how changes are agreed. One page per task is usually enough. A clear scope prevents disputes, scope creep and quality drift.

• 1 page per task is usually enough.
• State volumes, turnaround and accuracy as numbers.
• Name who decides each type of exception.
• Agree how changes to the scope are made.

What should a scope of work include?

Cover the points that would otherwise cause a disagreement later. Write them in plain language with numbers wherever possible.

• Task and output: what done looks like.
• Inputs: what arrives, from where, by when.
• Volumes: expected range and peaks.
• Turnaround and cut-off times.
• Accuracy target and sampling plan.
• Exceptions: what is referred, to whom.
• Access, reporting and change process.

• How UK SMEs can use outsourcing to handle repetitive tasks
• Acceptance criteria: define done for outsourced work
• Cut-off times: what same-day processing really means

How is a scope different from the method?

The scope says what is done and to what standard; the method says how. Keep them separate so the method can be improved without renegotiating the scope, while any change to volumes, turnaround or task boundaries goes through the agreed change process.

• Document your processes before you outsource
• BPO SLA examples you can adapt

What does a scope look like in numbers?

In an illustrative scope for supplier invoice processing: 350 to 450 invoices a month, received by 2pm processed same day, 98% accuracy on sampling, invoices over £5,000 or without a PO referred to the finance lead, weekly report on volume, turnaround and errors. These are example figures.

• Purchase order processing: raise, match and close POs
• Quality sampling: how many outsourced items to check

When does a scope need reopening?

Reopen the scope when volumes move outside the agreed range, new task types are added, turnaround needs change or exceptions grow. Small, unrecorded additions are how scope creep starts, so route every change through the agreed process, even when it seems minor.

• Scope creep in outsourcing: how extra work erodes savings
• Quality drift: why outsourced routine work slips over time

What does this look like in practice?

A pattern we see: a dispute about whether a task was 'included' turns out to be a scope that said 'admin support' without detail. One page of specifics would have settled it in advance.

• See client work
• BPO Solutions for UK businesses

Scope of work checklist

Check every scope against these points.

• Output and done standard defined.
• Inputs and cut-offs stated.
• Volumes as a range.
• Turnaround and accuracy as numbers.
• Exceptions and decision owners named.
• Change process agreed.

• Outsourcing repetitive tasks checklist: 20 checks
• BPO contract terms to check before signing

Next step

Send us the task you plan to hand over. We will help you draft a one-page scope and say plainly what needs agreeing before go-live.