Learning Centre

What to Delegate, and
When You Are Ready

An orientation for the decision that comes before hiring anyone

By The Staffualy Team · Last reviewed 30 July 2026

Most people arrive at the question of remote hiring with a symptom rather than a brief. The evenings are

gone. The reporting slips. Nobody has chased the proposal. The instinct is to find somebody, anybody, and

start handing work over, and that is usually what makes the first attempt fail.

This page is the orientation for the decision that comes first. It covers how to separate work that can

genuinely be handed over from work that only looks portable, how to tell a role apart from a pile of tasks,

when a generalist is the honest answer and when it is not, and what has to be true internally before anyone

external can do useful work. None of it requires you to hire anybody. If you read it and conclude that you

are not ready, that is a legitimate outcome, and cheaper than finding out three months in.

Pill Tags

AUDIT THE WEEK

SCOPE THE ROLE

TEST ON REAL WORK

ONBOARD IN 30 DAYS

KEEP IT FROM DRIFTING

Which work is genuinely delegable, and which only feels like

it

The test is not how much you dislike a task. It is whether the task has a describable input, a describable

output and a rule for what happens in between. Formatting a report, chasing an unpaid invoice, answering

the ten questions customers ask most — these have all three.

Work that only feels delegable fails on the middle part. It looks repetitive from outside, but every instance

depends on judgement nobody has written down: which client gets the exception, what tone you take

when news is bad. That work is not undelegable forever. It becomes delegable the moment those

judgements are captured as rules somebody else can apply — which usually means doing the work

alongside someone for a few cycles and writing down every decision you catch yourself making

without thinking.

A practical starting exercise: for one week, note every task that takes more than fifteen minutes.

Against each, ask whether you could describe what "done" looks like to a stranger in two sentences.

The ones where you can are your first candidates. The ones where you cannot are not ready yet, and

no hire will fix that on your behalf.

A role is not a task list

A task list transfers the doing. A role transfers the noticing. The difference shows at the first exception: a

task list breaks the moment reality departs from the written steps, while a role holds, because the person

owns the outcome rather than the sequence.

The practical test is whether you can complete the sentence "this person makes sure that…" without listing

activities. "Makes sure every client report goes out accurate and on time" is a role. "Pulls the figures, populates

the template, sends the email" is a list, and the moment the figures look wrong or the template changes, the

list stops working and the work comes back to you.

Start with a list if you must — almost everyone does — but treat it as scaffolding. The goal over the first two

months is to replace steps with outcomes, one recurring piece of work at a time. Our article

Delegating a Role Versus Delegating Tasks covers this transition in detail.

Generalist or specialist

The honest rule: hire a generalist when the problem is volume, and a specialist when the problem is skill. If

your week is being eaten by admin, scheduling, chasing and inbox triage, a capable generalist — an

Executive Virtual Assistant or an Operations Virtual Assistant — will absorb most of it, and the variety is

the point.

If the bottleneck is a discipline — the ad accounts, the ledger, the GoHighLevel build, the edit queue — a

generalist will disappoint you slowly. They will do the easy 60% of the work and route the hard 40% back to

you, which is precisely the part you wanted gone. That is what the specialist roles exist for, and it is why we

scope 17 of them rather than one.

Where people go wrong is hiring a specialist to fix a volume problem, or asking a generalist to carry a skill

problem. Both fail politely and expensively. If you are not sure which you have, that is a normal state to be

in, and exactly what a discovery call is for.

The readiness checklist

Before anyone external can do useful work, a few things have to be true internally. None of them are difficult, but every failed first placement we have seen was missing at least one:

A defined first month — not "help with everything", but what the role should have produced by week four,
written down.
One named person who answers questions. Not a rota, not "just ask anyone" — a name.
Access sorted before day one: tools, logins, documents and the permissions to use them.
Recurring work — enough repeated, rhythm-based work for somebody to get materially better at it.
A weekly check-in that survives busy weeks, because the placement drifts in exactly the weeks you skip it.

If you can tick all five, you are ready, and the Hiring Guide is your next step. If you cannot, fix the missing one first — it is cheaper than discovering it three months into a placement.