What to Include in a Freelance Contract

A freelance contract does not need to be long, and it does not need to sound like a law firm wrote it. What it needs to do is answer, in plain language, the handful of questions that cause almost every freelance dispute: what is being made, what it costs, when you get paid, and what happens when something changes. Get those on paper before the work starts, and most of the arguments you have heard other freelancers describe simply never get the chance to happen.

Here is the clause-by-clause checklist we would run through, in the order it usually appears in the document.

1. Who the agreement is between

Start with the boring part, because it matters more than it looks. Name both sides in full: your business name (or your legal name if you work under it) and the client's — the actual entity paying you, not just the friendly contact you have been emailing. If you are dealing with someone at a larger company, make sure the party on the contract is the company, not the individual, so you know who is on the hook if payment stalls. Add the date the agreement takes effect and each side's contact details, and you have the foundation.

2. The scope of work — including what is not included

This is the clause that does the most work, so give it the most care. Vague deliverables can never be finished, because there is always one more reasonable-sounding addition.

• Name the deliverables concretely. "A five-page marketing website" beats "a website." "Three social graphics, sized for one platform" beats "some graphics."
• Say what is out of scope. This is the part most people skip, and it prevents more disputes than anything else. A single line like "This project does not include copywriting or ongoing maintenance" is a kindness to everyone.
• Define what "done" looks like. How will you both know the work is finished and accepted? Deciding that in advance turns "I guess we're done?" into a clear moment.

3. Revisions — the number, and what happens after

Endless revisions are where a profitable project quietly becomes an unprofitable one. Put the limit in writing, and say plainly what happens once it is reached. A clause you can adapt:

Two rounds of revisions are included in this project. Additional rounds, or changes outside the agreed scope, are quoted separately as a change order and approved before the work begins.

Stated on day one, this reads as a normal term. Reached for on day forty, it feels like a fight. The document lets you set the boundary while everyone is still in the friendly part of the relationship.

4. Price, payment schedule, and terms

Settle the money in the same breath as the scope, because the two are really one decision. Spell out:

• The total price, and what it covers — this should map exactly to your deliverables from clause 2.
• The schedule — ideally a deposit up front, one or more milestone payments, and a final balance on completion.
• The terms — when each payment is due, written as a real timeframe ("due within 14 days of the invoice date," not "net 14" a client may not know), how they can pay, and any late fee, stated calmly up front.

The goal is that nothing on your final invoice is a surprise. Every number should trace back to a line the client already agreed to.

5. How changes get handled

Every project gets extra requests. The freelancers who stay profitable are not the ones who say no — they are the ones who decided in advance how to say yes. A short clause sets the pattern:

Any work requested beyond the agreed scope will be documented as a written change order describing the added work and its cost, to be approved by both parties before that work starts.

That one sentence turns "can you also just..." from an awkward negotiation into a routine step. The document does the asking for you.

6. Ownership of the work

Clients often assume they own everything the moment they hire you; you may assume you keep the rights until you are paid. Do not leave that to assumption. A common, fair approach is to tie the transfer of ownership to final payment:

Ownership of the final deliverables transfers to the client upon receipt of full payment. Until then, all work remains the property of the freelancer.

If you want to reuse the work in a portfolio, or you are licensing rather than transferring rights, say so here too. Small clause, large source of relief later.

7. Ending the agreement early

Projects sometimes stop before the finish line. A brief cancellation clause protects both sides: what notice is required, and what happens to work already done and deposits already paid. A simple version says the client pays for work completed up to the cancellation date, and the deposit covers your committed time. You do not need anything elaborate — you need it written down, so an early ending is a clean exit rather than a standoff.

8. Signatures — and the record around them

An agreement is only worth what you can prove was agreed. Put the scope, revision limit, payment terms, and the rest into one document and get both sides to sign it.

A kickoff call where you "basically agreed" is not an agreement; it is two different memories waiting to disagree.

An electronic signature is generally recognized the same as an ink one for ordinary freelance agreements — under the U.S. E-SIGN Act and state UETA, and Canada's PIPEDA Part 2 — as long as both sides intended to sign, consented to signing electronically, and there is a kept record of who signed which version and when. That last part, the timestamped record around the signature, is what turns a signature into protection rather than a memory. For a deeper look at what makes an e-signature hold up, see are electronic signatures legally binding.

Where Drift Catch fits

Once you know which clauses belong in the agreement, the next question is how to get it signed and keep it honest as the project moves. That is the part Drift Catch is built for. You set the deliverables and revision limits, the client e-signs the actual scope and terms, and from that moment the scope locks to exactly what they signed — with a timestamped record of who agreed and when. Anything beyond the signed scope is then visibly extra rather than a matter of opinion. You can see that flow in our freelance software that locks scope after signing.

The change-order clause from step 5 becomes a button: when a client asks for something outside the signed scope, it turns into a short add-on they e-sign before the work happens, which is the heart of how we stop scope creep with e-signed change orders. For the highest-risk work, a change order can be set to require payment before it moves forward — that pay-before-work gate is a Pro-plan feature that runs on your connected Stripe, while collecting payment yourself stays entirely manual on the lower tier.

The short version

A good freelance contract is not a wall of legal language — it is a plain-English answer to a few questions: who this is between, exactly what you are making (and what you are not), how many revisions are included, the price and payment schedule, how changes get handled, who ends up owning the work, and how either side can walk away. Write those down, get them signed, and keep the record. The work is hard enough; the agreement around it should be the calm part.

If you are still putting the foundations of your freelance business in place, our guide on how to start freelancing and the rest of our Learn guides are a good next step.

This is general information, not legal advice. Contract terms and what they require vary by region and situation — for an agreement that fits yours, have a professional review it.