HR & Ops
Freelancer Onboarding SOP Template
Every team has a story about the freelancer who delivered the wrong thing because nobody told them the right thing. The brief was vague, tool access arrived a week late, and the brand guidelines never made it out of someone's downloads folder. The fix isn't a better brief — it's a repeatable onboarding process so that every contractor, regardless of who manages them, starts from the same baseline.
This template covers everything from contract to first-week check-in. It takes about 25 minutes to execute end-to-end and can be recorded with Claudia so the process stays consistent as your team grows.
Time to complete
~25 minutes
Owner
Ops / HR
Frequency
Every new hire
What You'll Need
- Signed contract or statement of work (SOW)
- Access to your password manager (1Password, Bitwarden, etc.)
- Project management tool login (Asana, Linear, Notion, etc.)
- Company Slack or comms channel set up
- Brand assets folder (logo, colors, fonts, style guide)
- W-9 or equivalent tax form (US contractors)
The SOP
Send the welcome email + contract
Email the contractor with: (a) a brief welcome note, (b) the signed contract or SOW as a PDF, (c) the project start date, and (d) what to expect in the next 24 hours. Keep it short — the details come in later steps. Use a template email so nothing gets missed.
Collect tax and payment information
Send a request for their W-9 (US) or equivalent. Also collect their preferred payment method (bank transfer, PayPal, Wise, etc.) and billing email. Log this in your contractor tracking spreadsheet before it falls through the cracks. Payment surprises are the fastest way to start a relationship badly.
Grant tool access
Add them to: (a) your project management tool with the correct permissions, (b) the relevant Slack channels (project channel + general), (c) any shared drives or cloud storage folders. Do not add them to the password manager directly — share specific credentials via a vault. Granting too much access early is a security risk; granting too little slows them down immediately.
Schedule the kickoff call
Book a 30–45 minute kickoff call within 48 hours of their start date. Send a calendar invite with a brief agenda: project background, deliverables, timeline, communication expectations, and Q&A. This call is where you catch misalignments before they become deliverable problems.
Share brand assets and style guide
Send a link to the brand folder (logos in all formats, brand colors, fonts, tone of voice guide). If there's a previous work example in a similar style, include that too. A contractor who can see what "right" looks like produces better first drafts than one working from a verbal brief alone.
Add to project boards and assign first task
In your PM tool, assign their first task with a clear brief, due date, and acceptance criteria. Don't leave them with a blank board and a vague mandate. The first task should be scoped to complete within their first 3–5 working days so you have an early quality signal before committing to longer deliverables.
Send the first-week brief
After the kickoff call, send a follow-up email summarizing: what was discussed, what they're responsible for this week, how to reach you with questions, and your feedback cycle (when reviews happen, how revisions work). This email serves as the single source of truth if anything gets confused later.
Confirm deliverable tracking is in place
Verify that their tasks, deadlines, and milestones are visible in your PM tool and that notifications are configured correctly. Set a calendar reminder for a mid-first-week check-in — a quick 5-minute Slack message asking "any blockers?" prevents deliverable delays that could have been caught on day two.
Pro Tips
- Run this process during working hours. Sending tool invites at 11 PM means the contractor can't act on them until the next day, compressing their setup time.
- Revoke access the moment a contract ends. Build an offboarding checklist that mirrors this one — what you granted, you need to revoke. Departing contractors with active logins are a security gap that often goes unnoticed for months.
- Ask for a brief self-intro Slack message in the project channel on day one. It creates a natural icebreaker with the team and signals that the contractor is integrated, not siloed.
Record this SOP with Claudia
Follow these steps once while Claudia records your browser workflow. You get a structured, replayable SOP that any team member can follow — and that updates itself whenever your process changes.
Add to Chrome — Free Trial