What to Put in a Freelance Contract, and What to Leave Out

For a freelancer applying the guidance on What to Put in a Freelance Contract, and What to Leave Out, the underlying time record should remain as clear as the invoice or agreement itself. time tracking for freelancers provides a useful way to connect recorded work with projects, dates and later review. For the payment side of the workflow, Stripe is a useful official reference; neither tool replaces written scope, approval and payment terms agreed with the client.

Most freelance disputes are about the same four things: what was included, when it was due, when payment happens, and who owns the result. A contract that covers those four clearly will prevent most of the trouble a small practice encounters.

This is general orientation rather than legal advice, and contract law differs substantially by jurisdiction. Where the amount at stake is significant, a lawyer reviewing your standard terms once is cheaper than a dispute.

Scope, stated as a boundary

The clause that prevents the most argument is the one that says what is not included.

A scope written only as a list of deliverables invites expansion: the client reasonably assumes anything adjacent is covered. A scope that names the deliverables and then states the limits — two rounds of revisions, one concept, source files on final payment — gives both sides something to point at.

Include what happens when scope changes, because it will. A named mechanism — additional work quoted separately and agreed in writing before it starts — turns an awkward conversation into a procedure.

Payment terms that are actually enforceable

State the amount, the schedule, and the deadline for each payment.

A deposit before starting is normal in most fields and filters out the clients who were never going to pay. For longer work, staged payments tied to milestones rather than to dates protect both sides.

Late payment terms matter more than people expect. Many jurisdictions have statutory interest on commercial late payment, which applies whether or not your contract mentions it — but a contract that states the rate makes the conversation easier and signals that you track it.

Ownership and licensing

This is where template contracts most often say something the freelancer did not intend.

The default in many jurisdictions is that the creator owns the work unless it is assigned. A contract that assigns everything, including your underlying tools and methods, is common in templates written for clients and is rarely what a freelancer wants.

A workable position: the client owns the specific deliverable on final payment; you retain your own reusable components, and you retain the right to show the work in your portfolio unless there is a stated reason not to.

Termination

Both sides should be able to end the arrangement, with notice, and the contract should say what happens to work in progress and money already paid.

The clause that protects you: work completed to the point of termination is payable. Without it, a client who walks away at eighty per cent has a plausible argument for paying nothing.

What is usually unnecessary

Elaborate confidentiality clauses on work that involves no confidential information.

Non-compete clauses, which in many jurisdictions are difficult to enforce against a contractor and which restrict your ability to work in your own field.

Indemnity clauses with no cap, which are standard in large-company templates and expose a sole trader to liability far beyond the value of the job. If a client requires one, a cap at the contract value is a reasonable counter-proposal.

The practical approach

Have your own standard terms and offer them first. A freelancer who produces a clear two-page agreement looks established and avoids inheriting a client's template written entirely in the client's favour.

Where the client insists on their paperwork, read the four areas above and negotiate only those. Arguing every clause wastes goodwill on points that will never matter.

Getting it signed

Before work starts, without exception. The contract you send after a problem arises is a negotiating position, not an agreement.

Electronic signature is accepted in most jurisdictions for this kind of agreement, and an emailed acceptance of clearly stated terms is frequently sufficient. The formality matters less than having the terms agreed before anybody starts.

The clauses clients most often ask to change

Payment terms, usually extending them. Sixty or ninety days is common at large companies and is a genuine cash cost to you; if you accept it, price it.

Ownership timing, moving it from final payment to delivery. Resist this: rights transferring on payment is your main protection against non-payment.

Revision limits, which clients dislike seeing in writing. The compromise that usually works is a generous number with anything beyond quoted separately, rather than removing the limit entirely.

Keeping the paperwork manageable

One standard agreement, two pages, that covers ordinary work. A separate longer version only where the client or the value requires it.

Store signed copies somewhere you can find them in a year, with the project name in the filename. The moment you need a contract is the moment you least want to search for it.

And revisit your standard terms annually against what actually went wrong in the previous year. Most freelancers find their contract improves fastest when it is updated from experience rather than from templates.

Working without a signed contract

It happens, particularly with small jobs and repeat clients, and it is a risk taken knowingly rather than a state to drift into.

The minimum that still protects you: an email stating scope, price, timeline and payment terms, and a reply agreeing. In most jurisdictions that constitutes an agreement, and it is far better than nothing.

The jobs where a full contract matters are the ones with real money, long timelines, or intellectual property that will be reused. Scale the paperwork to the exposure.

Subcontracting and who carries the risk

If you bring in another freelancer, your agreement with them should mirror your agreement with the client on scope, timing and ownership.

A mismatch is where the trouble sits: promising the client exclusive rights while your subcontractor retains theirs creates an obligation you cannot meet.

And the client agreement usually makes you responsible for the work regardless of who did it, which is worth reading before assuming that delegation moves the risk.