The typical subcontractor onboarding goes like this: you send an access invite to your project management tool, shoot them a brief “here’s a task” message, and wait to see what comes back. What comes back is mediocre work that doesn’t match your standard. You redo it, conclude the sub isn’t good enough, and either let them go or continue tolerating the rework cycle.
The sub wasn’t the problem. The onboarding was the problem. They produced work based on their previous experience because you gave them a task before giving them context. They didn’t know your standard because you never showed it to them. They guessed what “good” looked like, and they guessed wrong.
A 7-day onboarding workflow fixes this. It’s front-loaded, the first week feels like low productivity because you’re investing in context-building instead of task output. The payoff is Week 2: a subcontractor who’s producing work that matches your standards rather than work you need to redo from scratch.
Day 1: The Context Dump
Day 1 has one job: get everything out of your head and into theirs. Not everything forever, everything they need to be oriented before they touch a single task.
Four things to cover:
1. What your business does and who it serves. Not your mission statement, a real description. “I work with B2B SaaS companies at Series A-B helping them build their first content function. My clients are typically CMOs or founders with a 2-5 person marketing team. Typical engagement is 12 weeks.” This context tells them who they’re ultimately serving when they do work for you.
2. What your quality standard looks like. Show your best work. Pull 3-5 examples of deliverables you’re proud of, reports, strategies, documents, whatever you produce. Share them and say: “This is the standard I hold work to. When you’re producing anything for me, this is the bar.” No sub can meet a standard they haven’t seen.
3. Your client communication norms. How do you communicate with clients? Formal or casual? How quickly? What tone? If the sub will ever communicate with clients directly, they need a clear picture of your voice. If they won’t, they still need to know because it affects how they write client-facing deliverables.
4. Non-negotiables. Every practice has things that are non-negotiable, quality thresholds, client confidentiality, communication response times, formatting standards. Name them explicitly on Day 1. “I never send a client a deliverable that hasn’t been reviewed by me. I always respond to client messages within 24 hours on business days. These are my baseline standards and I expect everyone working with me to operate the same way.”
The context dump can be a Loom video (faster to produce), a written document (easier to reference later), or a 60-minute live call. The best version is both: a written document they keep, plus a Loom that adds color and personality to what the document says.
Days 2-3: Tools Access and Process Walkthroughs
Days 2-3 are operational. Set up their access to every tool they’ll use, and walk them through your key processes before they’re asked to run them.
Tools access checklist:
- Project management tool (where tasks live)
- Communication channel (Slack, email, whatever you use)
- Shared document storage (Google Drive, Notion, etc.)
- Any client-facing tools they’ll touch
- Time tracking if applicable
- Any templates or asset libraries
Don’t assume they know how to use your tools the way you use them. Record a Loom walkthrough of your project management tool: how tasks are structured, how briefs are written, how status is updated, where completed work goes. A 10-minute Loom saves 3 weeks of confusion.
Process walkthroughs to record:
- How a typical client engagement runs from kickoff to delivery
- How a specific deliverable type is produced (the most common one they’ll touch)
- How you handle client feedback and revision cycles
- How you structure your communication with clients
These Looms take 10-15 minutes each to record and can be rewatched when they’re uncertain. Build them once, use them for every future hire. The investment in recording them pays forward permanently.
Every Loom you record for onboarding a subcontractor is also documentation of your process. By the end of your first onboarding, you’ll have a process library that makes every future onboarding faster and exposes the gaps in your own operational clarity. Onboarding the first sub is as much a self-audit as it is a training exercise.
Day 4: First Small Task With a Detailed Brief
Day 4 is their first real task. The task should be small enough to complete in 2-4 hours, clear enough that there’s a binary standard for success, and real enough that the output is genuinely useful.
The brief needs to be more detailed than you think. First-task briefs should include:
- Background: Why does this task exist? What client or project is it for? What context does it feed into?
- Deliverable: Exactly what should be produced? What format? How long?
- Standard: What does done-right look like? Link to a comparable example if you have one.
- Non-obvious requirements: Anything about tone, structure, or approach that isn’t obvious from the brief itself.
- Deadline: Specific date and time, not “end of week.”
- Questions to ask before starting: “If anything in this brief is unclear, ask before you start rather than after you’re done.” This permission structure prevents them from spending 4 hours going in the wrong direction.
A brief this detailed feels like over-documenting on a simple task. It’s not, it’s calibrating. The first task brief teaches them your briefing standard. Every brief you write afterward sets the expectation for how they’ll write briefs to their own hires someday. And it tells you whether your own briefing process is clear enough to produce the output you want.
Days 5-6: Feedback and Revision
When they deliver Day 4’s task, review it against the brief and your quality standard. Write specific, actionable feedback.
The feedback formula:
- What was done well (name it specifically, “the structure of this section follows the template correctly and the depth is right”)
- What needs adjustment (name it specifically, “the recommendation section is too high-level; each recommendation should be actionable in the next 30 days, like [example]”)
- Why it matters (connect the note to your standard or the client’s need, “clients use this section as a working plan, not background reading”)
- What the revision should look like (give a concrete direction, not just a critique)
Have them revise by end of Day 6. The revision tells you as much as the original delivery:
- Did they incorporate the feedback accurately?
- Did the quality improve as much as it should have?
- Did they ask clarifying questions about the feedback where appropriate?
- How did their energy seem, engaged and learning, or deflated and resistant?
The revision cycle is the most important feedback loop in the first two weeks. Run it cleanly and specifically.
Day 7: First Independent Task
Day 7 is their first task that they’ll complete with a standard brief, not the extra-detailed onboarding brief, but a normal working brief of the type you’d write going forward.
This is a calibration moment. Can they operate with normal-level direction? Do they know when to ask questions and when to proceed? Is their output consistent with what the first task suggested?
Choose a task type that’s similar to Day 4’s task but slightly more complex. Assign it with a standard brief. Watch what happens.
Two outcomes are both instructive:
- Strong output: They’ve internalized the context and standards from Days 1-6. Proceed to full task delegation with standard briefs.
- Output with notable gaps: Identify whether the gap is a context gap (they needed more information) or a judgment gap (they had the information and made a poor decision). Context gaps are fixable with better briefing. Judgment gaps require more guided practice.
What Productivity Looks Like in Week 2 vs. Week 4
Week 2 baseline (after structured Day 1-7 onboarding):
- Can execute admin tasks independently
- Can produce research tasks with a clear brief
- First-draft documents require your review and moderate editing (30-50% edit rate)
- Communication is proactive on blockers
- Quality shows understanding of your standard even if not yet consistently meeting it
Week 2 baseline (without structured onboarding):
- Still figuring out tools
- First tasks have missed the brief in significant ways
- Revision cycle is producing frustration on both sides
- Quality is inconsistent because the standard hasn’t been established
Week 4 after structured onboarding:
- Admin tasks are fully independent, no review needed
- Research tasks are reliable, review catches small errors rather than structural problems
- First-draft documents require light editing (10-20% edit rate)
- They’ve begun to internalize your standard and apply it without prompting
The difference between a structured and unstructured onboarding shows up clearly in week 4. With structure, week 4 is full independent execution on multiple task types. Without structure, week 4 is still a heavy review burden, you’re still catching the same types of errors you caught in week 1 because the standard was never clearly communicated.
Building the Onboarding Asset Library
Everything you create for the first subcontractor’s onboarding becomes a permanent asset for future hires. Don’t start from scratch each time.
After the first onboarding, organize what you created:
- The written context document → goes in your onboarding folder, updated when your practice changes
- The Loom walkthroughs → go in a “New Hire Library” folder in your video tool, organized by topic
- The first-task brief template → goes in your task brief library as the “new hire task” template
- The feedback from Days 5-6 → if it involved fixing a standard that wasn’t clearly documented, add that standard to your quality guide
The second subcontractor onboarding takes 60% of the time of the first because you already have the assets. The third takes 40%. By the fourth, you have a functional onboarding system that produces productive contributors in 7 days instead of 3-4 weeks.
That’s the compounding benefit of getting the onboarding right the first time.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
