Do I need a written contract for every freelance client?

Legally, it depends on where the client is and how much they are paying: $250 in California, $500 in Illinois including aggregate work across 120 days, $800 in New York State. Practically, yes for everything. The threshold tells you when the client is breaking the law by not having one; it does not tell you when a written scope becomes useful, which is always. This is general information, not legal advice - check your own jurisdiction, and get a lawyer involved on anything high-value.

What should a freelance client onboarding checklist include?

Legal entity name and mailing address for both parties, your day-to-day contact and the separate accounts payable contact, a signed agreement with an itemised service list and payment date, a scope of work with explicit exclusions and revision limits, an NDA if the work touches confidential material, and an agreed written route for change requests. Collect the identity details first; they are required content in every state statute above and the hardest to extract later.

Who is responsible for producing the contract, me or the client?

Under all three state laws the obligation sits with the hiring party. In practice most small and mid-sized clients have no process for it, so if you wait for them the work starts undocumented. Sending your own agreement at proposal stage is both faster and strategically better, because the party who drafts is the party whose terms are the starting point.

Does a client onboarding process actually reduce late payment?

It removes the most common causes. A stated due date, a named accounts payable contact, and an itemised service list mean the invoice arrives at the right desk, matchable against an agreement, with a date already attached. That does not stop a client who cannot pay, but it does stop the far more frequent case of an invoice that is simply sitting in the wrong inbox with nothing forcing a decision.

Client Management

The Freelance Client Onboarding Checklist (And the $250 Rule That Makes Half of It Legally Required)

Most freelance onboarding advice is a vibe: send a welcome packet, set expectations, be professional. Since 2024 it is also, in three large US states, a compliance question with a dollar threshold attached. If a client pays you more than a certain amount, they are legally required to put the deal in writing - and the freelancer who sends that document first is the one who controls what it says.

The written-contract thresholds you are onboarding against

Three states now require a written contract between a hiring party and a freelance worker above a set value, and the thresholds are lower than most freelancers assume. Illinois moved first: the Freelance Worker Protection Act was signed on 4 August 2023 and took effect 1 July 2024, covering work of at least $500 - counted either in a single contract or in aggregate across all contracts in a 120-day period, which quietly catches a run of small retainer jobs. New York's Freelance Isn't Free Act, in force in New York City since 15 May 2017, expanded statewide on 28 August 2024 at a threshold of $800. California's SB 988, the Freelance Worker Protection Act, took effect 1 January 2025 at $250 - the lowest of the three, and low enough that a single day of design work clears it. These laws bind the hiring party, not you. But in practice the client rarely produces the document, so onboarding is where you hand them one.

Jurisdiction	Threshold	In force from
Illinois - Freelance Worker Protection Act	$500 (single contract or aggregate over 120 days)	1 July 2024
New York State - Freelance Isn't Free Act	$800	28 August 2024
New York City - Freelance Isn't Free Act	$800	15 May 2017
California - SB 988	$250	1 January 2025

Step 1: collect the identity details before you write anything

Every one of these statutes requires the contract to carry the name and mailing address of both parties, so collect them at the point of first agreement rather than chasing them later when the client has gone quiet. What you actually need: the legal entity name (not the brand name - 'Acme Studio' may be 'Acme Holdings LLC' on paper), the mailing address, the name and email of your day-to-day contact, and separately the accounts payable contact if the company has one. That last field is the highest-value thing on the list and the one most freelancers skip. An invoice sent to your project contact and forwarded internally is the single most common cause of a late payment that nobody is actually disputing. Store all of it against a client record, not in the email thread where you first got it.

Step 2: send the agreement before the proposal is accepted, not after

The usual order is proposal, verbal yes, then a contract sent as a formality a week into the work. Reverse it. Send the agreement alongside the proposal so acceptance covers both, because the gap between 'they said yes' and 'they signed' is exactly when scope starts moving and you have no document to point at. The agreement needs an itemised list of services and their value, the compensation method, and the date payment is due - or, if no date is stated, the statutes generally default to payment on completion, which is worse for you than any term you would have negotiated. Include a late-fee clause even if you never intend to enforce it; its practical function is being quotable in a reminder email.

Step 3: separate the sales document from the scope document

A proposal sells the work. A scope of work defines it. Collapsing them into one document is convenient at signature and expensive three weeks later, because every scope question then reopens a document the client experienced as a pitch they already approved. Keep them as two artefacts: the proposal carries pricing, positioning and terms; the scope of work carries the deliverables list, the explicit exclusions, the number of revision rounds, and what constitutes acceptance. The exclusions list is the part that earns its keep. 'Two rounds of revision' means nothing without 'additional rounds billed at X per round', and 'website design' means nothing without 'does not include copywriting, photography, or ongoing maintenance'.

Step 4: agree the change-request route at onboarding, not at the first change

Scope creep is not a discipline problem, it is a routing problem. If there is no named channel for a change request, changes arrive as casual asks in whatever medium is closest - a chat message, a line at the end of a call - and get absorbed into the original fee because refusing them mid-conversation costs more social capital than doing them. Fix it during onboarding by naming the route in the agreement itself: additions to scope go through a written change request that states the work, the added cost, and the effect on the deadline, and are not started until it is approved. Saying this at onboarding, when nobody is asking for anything, is a five-second conversation. Saying it for the first time when a client asks for one extra page is a negotiation.

Step 5: decide where the record lives before the first invoice

Onboarding produces four or five documents in a week - agreement, proposal, scope of work, sometimes an NDA, then the first invoice - and by default they end up in four different places: a PDF in Downloads, a signed copy in email, a proposal in a design tool, an invoice in a spreadsheet. That sprawl is survivable with one client and unmanageable with ten, and it is what makes a simple question like 'what did we agree about revisions on this project' take twenty minutes. The fix is boring: pick one place where a document is filed under the client it belongs to, and file everything there as it is created rather than at the end. Client onboarding software, a client workspace, or a rigorously maintained folder structure all work. Nothing works if the decision is deferred.

Frequently asked questions

Do I need a written contract for every freelance client?: Legally, it depends on where the client is and how much they are paying: $250 in California, $500 in Illinois including aggregate work across 120 days, $800 in New York State. Practically, yes for everything. The threshold tells you when the client is breaking the law by not having one; it does not tell you when a written scope becomes useful, which is always. This is general information, not legal advice - check your own jurisdiction, and get a lawyer involved on anything high-value.
What should a freelance client onboarding checklist include?: Legal entity name and mailing address for both parties, your day-to-day contact and the separate accounts payable contact, a signed agreement with an itemised service list and payment date, a scope of work with explicit exclusions and revision limits, an NDA if the work touches confidential material, and an agreed written route for change requests. Collect the identity details first; they are required content in every state statute above and the hardest to extract later.
Who is responsible for producing the contract, me or the client?: Under all three state laws the obligation sits with the hiring party. In practice most small and mid-sized clients have no process for it, so if you wait for them the work starts undocumented. Sending your own agreement at proposal stage is both faster and strategically better, because the party who drafts is the party whose terms are the starting point.
Does a client onboarding process actually reduce late payment?: It removes the most common causes. A stated due date, a named accounts payable contact, and an itemised service list mean the invoice arrives at the right desk, matchable against an agreement, with a date already attached. That does not stop a client who cannot pay, but it does stop the far more frequent case of an invoice that is simply sitting in the wrong inbox with nothing forcing a decision.