How to Hand Client Work to a Subcontractor

The big project lands Tuesday. Delivery's in three weeks, and you can't do it with the team you have. So you do what every agency and freelancer does: find a subcontractor, book a two-hour Zoom, dump a Drive folder on them, and hope.

Here's how that goes. The Zoom covers the obvious — the brand, the deliverables, the deadline. The Drive folder has forty files, of which six matter, three are current, and one is a rate card from 2024 that looks identical to the new one. The prayer does the rest.

Two weeks later the work comes back and it's… fine. Technically competent, spiritually wrong. You spend your weekend fixing it yourself. The subcontractor did nothing wrong. The handoff failed them — and handoffs fail in specific, fixable ways.

The Support Gap Nobody Talks About

Companies are famously bad at supporting their own people's use of AI — let alone anyone else's. In Gallup's 2026 State of the Global Workplace, less than a third of employees in organisations implementing AI said their manager actively supported their team's use of the technology. Microsoft's 2026 Work Trend Index — 20,000 workers across 10 countries — found only 19% of AI users work in environments where both their capability and their organisation's readiness are high. Only 26% say their leadership is clearly aligned on AI at all.

That's for employees — people with contracts, onboarding programmes and colleagues down the hall. Now ask what a subcontractor gets. A Zoom, a folder, and your faith in their professionalism.

And because they're resourceful professionals, they fill the gaps the only way available: their own AI accounts, their own tools, their own guesses about what your client wants. We wrote about what that invisible usage costs in Shadow AI — for subcontractors, it's the default state, not a hidden one.

Open that Drive folder from their side for a second. Forty files, no map, no idea which version is live. They'll make judgement calls on all of it — quietly, competently, and invisibly to you, right up until the draft comes back. Most subcontracting runs on trust alone, and most of the time trust holds. Until the one client where it doesn't — which is always the client you couldn't afford to lose.

What the Two-Hour Briefing Actually Transfers

A briefing call is good at facts and terrible at judgement. Here's the split.

What transfers fine: deliverables, deadlines, brand colours, the deck template, the client's industry, the contact names.

What doesn't:

The current state. Which version of the positioning survived the last round of feedback. Whether the Q3 strategy doc is the live one or the one they killed.
The rules. The words the client bans. The claims they can't legally make. "Never say 'solutions.' Never lead with price. UK spelling, always."
The history. Why the deck structure is the way it is — because the CEO skips to page four. Why you never propose video — they burned budget on it in 2023 and it flopped.
The boundaries. What this client considers confidential, which AI tools are allowed at all, and whose approval a deliverable needs before it moves an inch.

Notice the pattern: the call transfers the what, and loses the why and the never. And the why and the never are exactly the things that make output wrong in ways the subcontractor can't see — and you can't spot without reading every line.

The cruellest part of the split: the subcontractor doesn't know what they don't know. They can't ask about the banned word, because they don't know it exists. The gap stays invisible until the deliverable lands — which is why "they never asked" is a handoff failure, not a subcontractor excuse.

A subcontractor's output is a perfect reflection of the context they were given. If it comes back generically wrong, that's not their failure report. It's yours.

The Review Trap

There's a second cost, and it lands on your calendar. When work comes back from an under-briefed subcontractor, somebody has to find every place it's wrong. That somebody is you — because you're the only one holding the context the subcontractor never got.

So you pay twice. Once to the subcontractor for the draft, and once in your own weekend hours checking it line by line against a standard that exists only in your head. The whole economic point of subcontracting was buying back your time. A bad handoff quietly refunds it.

The Handoff Stack

A real handoff has four layers. Score your last one against it.

Most handoffs cover layer one and patchy fragments of layer two. Layers three and four — the reasons and the boundaries — almost never make the trip. Which is why the feedback loop with subcontractors so often sounds like archaeology: "Why did you do it this way?" "You didn't tell me not to."

1. Current documents

Not a folder — the live set. The current rate card, the current brand voice, the current strategy, with anything superseded clearly dead. If the subcontractor has to guess which version is authoritative, you've already lost the version lottery.

2. The rules

Voice, banned terms, spelling, claims discipline, pricing presentation. The checklist the deliverable gets judged against — which should exist whether or not a subcontractor ever sees it. The full version lives in your agency AI policy; clause one exists for exactly this.

3. The decisions and their reasons

The short, honest history: what the client rejected and why, what's politically sensitive, where the bodies are buried. Five bullet points of "why" prevent ninety percent of "spiritually wrong."

4. The boundaries

Which tools are approved for this client's work — account tiers matter here — what data can go where, and who approves output before it ships. If you're thinking "we don't have that written down either," you're in the majority, and the client-data post is the place to start.

What "Solved" Looks Like

The cleanest handoff isn't a bigger briefing. It's no briefing at all — because the context was already assembled before the subcontractor's name came up.

Each client has a workspace holding the four layers — current docs, rules, decisions, boundaries — maintained as a byproduct of the work itself. Handing work over becomes handing access over. The subcontractor's AI reads the same client context yours does, so their first draft starts where your tenth would.

And when the work comes back, you don't re-read every line on gut feel. The output carries a record of what informed it, so review means checking the trail, not redoing the journey. This is the workflow we built Vythos for: client context that travels with the work, to whoever does the work.

The two-hour Zoom becomes twenty minutes — and they're the right twenty minutes. Who the client loves and who needs winning over. What this project is really for. The deadline, and which parts of it are real. The judgement calls only a voice can carry, because everything else was already there before you opened your mouth.

The Honest Trade-Off

Good subcontractors have their own systems, their own tools, their own way — Microsoft's 2026 Work Trend Index found that even among employees, only 19% work in environments that fully support their AI use. For subcontractors, that number is zero. The answer isn't enforcement; it's making your route faster than theirs. When joining your client workspace takes four minutes and the alternative is forty files of archaeology, resistance evaporates.

And if you're the subcontractor reading this: flip the stack into your intake checklist. Before you start, ask for the live docs, the rules, the reasons and the boundaries. Asking doesn't make you difficult — it makes you the one subcontractor whose first draft doesn't need a rescue mission. Agencies remember that.

Scale matters too. For a two-day, one-off job, the Zoom and the folder are honestly fine — the overhead of a real handoff outweighs the risk. The calculus flips when the subcontractor is recurring, the client is long-term, or the work touches anything the client would call sensitive. Which, if you're being honest, is most of it.

The one thing: The briefing isn't the handoff — the context is. If handing work to someone means starting from zero every time, you don't have a subcontractor problem. You have a memory problem with an invoice attached.

How to Hand Client Work to a Subcontractor