The Freelance Welcome Packet: A Section-by-Section Checklist

Most freelance welcome packets are built backwards. They open with a page about the studio’s values, a photo, a paragraph of mission statement — and then, on page six, in smaller type, the part the client actually needed: when you are reachable, how many revision rounds they get, and who owns the files when it is over.

The packet is not a brochure. The client already hired you; the selling is done. What the document is really doing is answering, in advance, the questions that would otherwise arrive as email at inconvenient hours. That reframing decides everything about what goes in it — and about how short it can be.

This is the artifact, not the process. If you are still deciding what your onboarding sequence should look like — what happens before the yes, what happens in the first 48 hours after the signature — start with our guide to the client onboarding process for freelancers, then come back here to write the document that sequence hands over.

Sort the sections by weight before you write a word

Not every section of a welcome packet does the same kind of work. Three of them carry consequences if they are wrong: a court, an invoice, or a refund can turn on their wording. Four of them save you time but cost you nothing if they are imperfect. The rest are decoration.

Writing them in that order matters, because the heavy sections take a morning of real thought and the light ones take twenty minutes of copy-and-paste from your last three projects.

Section	Weight	What it protects	First version takes
Scope, deliverables, acceptance criteria	Heavy	Against unpaid extra rounds	60–90 min
Ownership and licensing of the work	Heavy	Against a dispute over the files	45 min, plus a lawyer’s eyes
Payment terms, invoice triggers, tax form	Heavy	Cash flow	30 min
Communication windows and response times	Operational	Your evenings	15 min
Revision rounds, counted and defined	Operational	Your margin	20 min
Access, credentials, and how to send them	Operational	Week-one momentum	15 min
Week-one calendar	Operational	Client anxiety	10 min

The time estimates are our own, based on writing these documents from scratch rather than from a template. They assume you already have three finished projects to mine for language.

The three sections that carry real consequences

Scope, deliverables, and how “done” gets decided

Procurement departments solved this problem decades ago, and the vocabulary is worth stealing. A statement of work — the document a vendor signs with a corporate client — separates the scope of work from the deliverables schedule from the acceptance criteria, that last one being, in the Wikipedia summary of statement-of-work practice (consulted 16 September 2026), the part that “specifies how the buyer or receiver of goods will determine if the product or service is acceptable, usually with objective criteria.”

Objective criteria is the phrase to sit with. “Client is happy with the design” is not a criterion; it is a mood. “Three homepage concepts delivered as Figma files, one selected within five business days, two rounds of refinement on the selected concept” is a criterion, because both of you can look at it and agree whether it happened.

Write this section as a list of nouns with dates attached, and a separate short list titled not included. The second list is the one that prevents the awkward conversation in week five.

Ownership: the clause most packets get wrong

Here is where a lot of freelance welcome packets confidently say something that may not be true. The phrase “all work is delivered as work made for hire” appears in thousands of freelance templates, and for most freelance deliverables it does not do what people think it does.

Under US law, a commissioned work only qualifies as a work made for hire if it clears four conditions at once, set out in the Copyright Office’s Circular 30, Works Made for Hire (revised 08/2024; consulted 16 September 2026): there is a written agreement, both parties sign it, they expressly agree the work is a work made for hire, and the work falls into one of nine listed categories. Those nine categories are a contribution to a collective work, part of a motion picture or other audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, or an atlas. As the circular puts it, if a work fails any of these requirements, it is not a work made for hire.

Read that list again with freelance work in mind. A logo is not on it. A website is not on it. A photograph commissioned for a brand campaign is not on it. Application code is not on it. For those, the “work made for hire” line transfers nothing on its own — the mechanism that actually moves the copyright is an assignment: an explicit transfer of rights, typically written to take effect on receipt of final payment.

Typical freelance deliverable	On the nine-category list?	What actually transfers it
Logo or brand identity	No	Written assignment of copyright
Website design or front-end code	No	Written assignment, or a licence
Commissioned photography	No	Written assignment, or a licence
A chapter written for someone’s edited anthology	Yes — contribution to a collective work	Signed work-made-for-hire agreement
Subtitles or a translated manual	Yes — translation	Signed work-made-for-hire agreement

This is general information about how the doctrine is structured, not legal advice, and it describes US law only — jurisdictions differ, and moral rights complicate the picture in several of them. The practical takeaway for the packet is narrower and safe: state plainly when rights transfer, what transfers, and what you retain (portfolio use, process work, your own tooling), then have a lawyer check the operative sentence once. One review covers every client you will ever onboard.

Money: the trigger, the clock, and the form they need from you

Three things belong here, and they are more specific than “50% upfront.”

The trigger: what event causes an invoice to be issued. Signature, milestone acceptance, calendar date, delivery. Ambiguity here is what turns a 30-day payment term into a 50-day wait — we ran the arithmetic on that in net 15 vs net 30 payment terms, where the invoice date and the client’s accounts-payable cut-off do more damage than the stated term.

The clock: the term itself, written in days from invoice date, with the late-payment consequence spelled out in the same sentence.

The paperwork: if your client is a US business, their finance team cannot pay you cleanly until they have your tax identification on file. Form W-9 (IRS, page last reviewed 27 June 2026; consulted 16 September 2026) is used to provide your correct Taxpayer Identification Number to the party that has to file an information return about what they paid you. Volunteering it inside the welcome packet — rather than waiting for a procurement email three weeks later — removes a delay that has nothing to do with your work. Non-US freelancers working with US clients will usually be asked for a W-8 series form instead; name the one that applies to you.

The operational half: four sections that delete email

These sections have no legal weight. Their entire value is that each one prevents a category of message from ever being sent.

Communication windows

State the hours, the time zone, the channel, and the response-time promise, and then keep the promise modest enough that you always beat it. “Email, answered within one business day” is a better commitment than “Slack, always on,” because the second one is a description of your future resentment.

Revision rounds, counted and defined

A round is not a comment; a round is a consolidated set of feedback delivered at once. Say that explicitly, say how many rounds are included, say what happens on round three — hourly rate, or a change order — and say how long the client has to send feedback before the project pauses. That last clause is the one most packets omit, and it is the one that saves a project from drifting for six weeks.

Access and credentials

List what you need before day one: repository access, brand assets, a named decision-maker, logins. Then say how to send the sensitive parts — a password manager share, not a Slack message. Asking for this as a checklist rather than a paragraph roughly halves the number of follow-ups, in our experience of running both formats.

The week-one calendar

Four lines: kickoff call, first checkpoint, first deliverable, first invoice. New clients are quietly anxious about whether anything is happening. Four dated lines answers that permanently.

What to cut

Cut the mission statement, the founder photo, the “our values” spread, the stock imagery, and the paragraph about your process philosophy. They were persuasion assets, and persuasion is finished — the client signed. Every page of decoration lowers the odds that the sections carrying consequences get read.

Cut anything that duplicates the contract without matching it word for word, too. A welcome packet that paraphrases a contract clause loosely creates two documents that disagree, which is worse than having one. Where the packet touches contractual ground, quote the contract or point to it.

Where the packet should live

Format follows revision frequency. A PDF is fine if the content is stable and you want it to feel like a document; a living page — Notion, a Google Doc, a client portal — is better if project-specific sections change per engagement, because the client always has the current version and you never email a v3.

If you already run a client platform, the packet usually belongs inside it as a template that clones per project, which is the whole argument for the portal-plus-forms tools we compared in Dubsado vs HoneyBook and 17hats vs Dubsado. If you do not, a document and a folder is genuinely enough — the proposals, contracts and CRM section of this site exists mostly to argue that the paperwork should be right before the software gets involved, and our CRM comparison for freelancers makes the same point at greater length.

One overlap worth exploiting: if your proposal tool already stores reusable content blocks — the kind of library the tools in our proposal software roundup are built around — the scope and terms sections of the packet can be the same blocks your proposals use, maintained once. Same for the invoice trigger language and whatever you set up in your invoicing software.

Assembling it in one afternoon

Write it in this order. The sequence is deliberate: each step feeds the next, and the first three are the ones that would hurt to get wrong.

Order	Section	Where the text comes from
1	Scope and acceptance criteria	Your last three signed proposals, with the vague verbs removed
2	Ownership and licensing	Your contract, quoted — reviewed once by a lawyer
3	Payment terms and tax form	Your invoicing setup, plus the correct tax form
4	Revisions and communication	The three arguments you have already had with clients
5	Access checklist	The onboarding emails you sent last quarter, deduplicated
6	Week-one calendar	A template with five blanks

If you only write two pages, write these

The minimum viable packet is one page of scope and acceptance criteria, and one page split between payment terms, revision rounds, and the access checklist. That version can be written this afternoon, and it removes most of the email traffic a full packet would.

The ownership section is the one to add second, once a lawyer has looked at the sentence — not because it saves time, but because it is the only part of the document where being wrong is expensive rather than annoying. Everything else on the list is a convenience. Those two pages are the business.

Sources consulted 16 September 2026: US Copyright Office, Circular 30, Works Made for Hire (revised 08/2024); IRS, About Form W-9; Statement of work, Wikipedia. Time estimates and the deliverable table are our own analysis. We have no affiliate relationship with any tool named in this article. Nothing here is legal or tax advice.