How to scope an outsourced role (so it actually works)
When an outsourcing engagement underperforms, the cause is usually upstream: a fuzzy scope. Get the brief right and most other problems disappear. Here's a simple way to do it.
- Most outsourcing disappointments trace back to a vague brief, not the wrong person.
- Scope around tasks and outcomes, not a job title.
- A one-page scope covers five things: tasks and frequency, outcomes and how they’re measured, tools and access required, communication rhythm, and what stays with you.
Start with tasks, not a title
"We need an admin assistant" is a title, not a scope. Instead, list the actual tasks weighing your team down this week — the recurring, documentable ones. That list is the real job.
Define the outcomes
For each task, write what "done well" looks like and how you'll know. Invoices issued within 24 hours of job completion. Pipeline updated daily. Reports out every Monday by 9am. Clear outcomes make performance obvious to everyone.
Document the tools and access
List the systems involved and the access each task needs. This both speeds onboarding and keeps access least-privilege from day one — good for security and clarity alike.
Set the communication rhythm
Decide how you'll stay in sync: a short daily check-in, a weekly review, the channel for urgent items. Rhythm prevents both micro-management and radio silence.
If you're working with a managed provider, share this scope early — a good partner will sharpen it with you and match the right person to it. Not sure if the timing's right? See our 7 signs your business is ready to outsource.
Frequently asked questions
How detailed should the scope be?
Detailed enough that a capable stranger could understand the recurring tasks, what 'good' looks like, and which tools to use. A single page is usually enough to start.
What if I don't know exactly what I need yet?
That's normal. Start by listing the tasks that drain your week. A good provider helps turn that raw list into a structured role during scoping.
Should I outsource the most complex work first?
No — start with repetitive, well-understood tasks that don't need your judgement. Prove the model there, then expand into more specialised work.