Onboarding a freelancer or subcontractor properly, before the first task

This page may contain affiliate links from which Blur Studio earns commissions.

Agencies run on a mix of full-time staff and freelance or subcontracted talent far more than most other business types, and the onboarding paperwork for that freelance layer gets skipped more often than it should, usually because the engagement starts fast, a project lands, a freelancer is brought in within days, and formal paperwork feels like it can catch up later. It often doesn't, and the specific gap it leaves, who actually owns the work this person creates, and what happens to confidential client information they were exposed to, is exactly the kind of thing that's expensive to discover missing after the fact.

Documents, and the order that actually matters

1. The NDA, first, before any client information is shared. A freelancer working on agency projects is almost always exposed to confidential client information, unreleased campaigns, internal strategy, sometimes financial details, well before any formal engagement contract gets discussed. Getting the NDA signed before that exposure happens, not after, is the only version of this that actually protects anything, since an NDA signed after confidential information has already been shared is protecting against future disclosure, not the disclosure that's already happened. A template and checklist are in NDA for contractors and freelancers.

2. The IP assignment. This confirms explicitly that work created by the freelancer under the engagement belongs to the agency (and through the agency, ultimately the client), not the freelancer personally. Without this in writing, default copyright rules in most jurisdictions actually favor the creator, meaning a freelancer could, in a worst-case dispute, claim some ownership or rights over work they were paid to create for someone else's project. This is a genuinely important clause to get right and signed before any actual creative or technical work begins, not after a deliverable has already been handed to a client.

3. The tax form. A W-9 for a US-based independent contractor (which you'll need to issue a 1099 at year end if payments cross the IRS threshold), or the relevant local equivalent for a contractor based elsewhere, since this varies by country and you should confirm the specific requirement for where your contractor is based rather than assuming a US form covers an international freelancer.

One packet

Combine all three into a single onboarding document a new freelancer or subcontractor signs once, rather than three separate requests sent at different points, which both delays the point at which you're actually protected and creates more chances for one piece to get missed entirely. QuickSigner, an electronic signature platform for uploading a document, adding signer fields, and collecting a legally binding signature from any device, supports this kind of combined packet as a reusable template, with the standard NDA and IP assignment language staying consistent across every freelancer you bring on, and only the individual's name, rate, and specific engagement details changing each time.

Set a clear, firm policy that no client-facing or client-information-adjacent task starts before this packet is fully signed, and actually hold to it even when a project timeline feels tight, since the tight-timeline moments are exactly when the "we'll sort the paperwork out after" shortcut feels most tempting and is also when it does the most damage if something later goes wrong on that specific engagement. The employee version of this packet is in the new hire paperwork checklist and e-sign packet.

Non-solicitation, and keeping the engagement genuinely independent

A fourth consideration worth building into the packet, even if it's not always a standalone separate document: a non-solicitation clause preventing a freelancer from going directly to your client, bypassing the agency, for future work. This is a real risk specifically because of how agency-freelancer relationships work, the freelancer meets and works directly with your client, sometimes closely, and without this clause in place, nothing formally stops that client from simply hiring the freelancer directly on the next project and cutting the agency out entirely.

Separately, and this matters more than it might seem, the actual working relationship needs to stay genuinely independent-contractor in practice, not just on paper, if you want the classification itself to hold up. In the US, factors like how much control you exercise over when and how the freelancer works, whether they work for other clients too, and whether they use their own equipment and process all matter to whether a contractor relationship is correctly classified rather than functioning as de facto employment without the associated taxes and benefits. This is a genuinely complex area that varies by state and by the specifics of each relationship, so if you're treating freelancers in a way that increasingly resembles employment, regular set hours, exclusive availability, close day-to-day direction, it's worth getting that specific question reviewed by an accountant or employment lawyer rather than assuming the signed contractor paperwork alone settles the classification. The agreement itself is outlined in the independent contractor agreement template.

Storage

Keep the signed packet, along with the freelancer's rate agreement and any project-specific scope, in one place tied to that individual, retrievable quickly if a dispute over ownership or confidentiality ever comes up, or simply if you want to re-engage the same freelancer on a future project without re-collecting paperwork you already have on file. For contractors you work with repeatedly, this record also matters at tax time, having a current, correctly completed W-9 or equivalent on file for everyone you've paid during the year makes year-end filing meaningfully less stressful than tracking down missing forms from six different freelancers in January, often while they're also slow to respond because the engagement that originally required the form ended months earlier and the request now feels like it's coming out of nowhere.

A worked example

A growing agency brings on a freelance developer for a two-week sprint on a client's product launch, moving fast because the client's own timeline is tight. Work starts the same day the freelancer is confirmed, with the actual onboarding paperwork, promised to follow "once things calm down," never quite catching up before the engagement wraps. Six months later, the agency wants to reuse part of that code on a different client's project and the freelancer, reasonably, points out there's no signed agreement establishing that the agency actually owns the work outright. Separately, the client, impressed with the freelancer's work during that sprint, reaches out directly about a follow-on project, something a signed non-solicitation clause would have at least required a conversation about, rather than something that happened silently with no obligation on either side to even mention it to the agency. What should have been a non-issue becomes a real negotiation, and a real cost, to resolve after the fact, for something that would have taken the freelancer two minutes to sign on day one if the process had required it before any work started.

How I'd approach this

The agencies that get this right aren't necessarily more careful people, they've just made the onboarding packet a genuine blocker, not a formality that can be skipped under deadline pressure, no client-facing work starts without it, full stop, regardless of how tight the timeline feels in the moment. That one firm rule, held consistently, prevents almost every version of the IP, confidentiality, and client-poaching problems that otherwise surface months or years later, when it's far more expensive and far more awkward to fix than it would have been to simply ask for a signature on day one. If you're bringing on freelancers regularly and this onboarding currently happens inconsistently, sometimes before work starts, sometimes after, building one connected, consistent flow is exactly the kind of work I do. Get in touch if that's genuinely where you're stuck.