My first freelance contract arrived as a two-line email: here is the rate, can you start Monday? I said yes before my coffee had cooled. Three weeks later the client wanted a migration finished “by the end of the month”, a scope that had quietly doubled, and an invoice held until “everything is signed off”. None of it was in writing, and every part of it felt like my fault. I have worked remotely for years since, and what changed was not my skill. I learned to read the terms before I said yes, and to write my own when the client had none. Here are the eight clauses I look for first.

1. When and how you get paid

This is the clause that decides whether you eat. Look for the payment window, such as thirty days from invoice, and whether it starts at the invoice date or the date of “approval”, which can drift forever. Check the currency, the method, and who bears transfer fees. Then look for a late payment term. A client who has agreed to a modest interest charge or a pause in work after a missed date tends to pay on time.

2. What exactly you are delivering

Phrases like “support the platform” or “improve the pipeline” sound friendly and mean almost anything. A better agreement lists deliverables or at least a clear description of outcomes, plus what is excluded. If you spot vague wording, rewrite it in your own words and send it back for agreement. That one email has saved me from more arguments than any tool I own.

3. How change requests are handled

Scope creep rarely arrives as a dramatic demand. It comes as “while you are in there, could you also…”. A good clause says that additional work is quoted separately and begins only after both sides agree. Without it, you are negotiating from guilt every time.

4. Revisions and sign-off

How many rounds of changes are included, and who decides when a piece of work is finished? An open-ended review loop is a quiet way to be underpaid. I like a clause that treats work as accepted if there is no response within a set number of days.

5. Access, credentials and responsibility

Freelance DevOps means holding keys to other people’s systems. Read what the agreement says about who creates accounts, how access is removed at the end, and what happens if something goes wrong during a change. Look especially for any language making you responsible for losses far larger than your fee. A cap on liability tied to the amount you were paid is a reasonable thing to ask for.

6. Ending the arrangement

Every contract should say how it stops. Notice periods, payment for work completed, and a handover duty are the usual parts. The one I watch for is the “kill fee”, a payment if the client cancels a project midway. If there is none, you could lose weeks of planned income overnight with no recourse.

7. Who owns what you build

Clients usually expect to own the scripts and configurations you write for them. That is normal. What deserves attention is the wording about your own reusable tools, templates and know-how. A fair clause leaves those with you and grants the client a licence to use them within the project. Broad language that hands over “all work created during the engagement” may sweep up things you built long before.

8. Confidentiality and what you may say about the work

Almost every client wants discretion. Read how long it lasts, what counts as confidential, and whether you may mention the engagement in a portfolio. Many freelancers forget the last point and later discover they cannot show the best project they ever delivered.

If you want the broader picture of balancing freelance commitments with a regular job, responsible ways to run a freelance side practice next to full-time work covers the clauses employers add on their side as well, and it pairs nicely with this list.

A story that made me a believer

A friend of mine, a cloud engineer working from a small town, took on a monthly maintenance job for a retail client. The agreement renewed itself each month unless cancelled with thirty days’ written notice by post to a head office address. When the client’s priorities changed, she emailed to stop, believing it was done. Two further months of fees were still due, because email did not count. Nobody was being cruel. It was simply written down, and she had not read it.

She now keeps a short note for every client with five lines: payment date, notice period and form, scope in one sentence, revision limit, and who owns what. It takes ten minutes per contract and she tells me she has never lost an argument since.

Bonus: asking for changes without souring the deal

Many new freelancers worry that questioning a clause will make them look difficult. In my experience, the opposite is true. Clients tend to respect someone who asks calmly for a change, and who explains it in practical terms: “I would like payment on fifteen days so I can plan my month.” If a client reacts badly to a reasonable request, it is useful information about the months ahead.

Your community can help with this too. Fellow freelancers will often share sample wording and warn you about clients to approach carefully, as discussed in a post about finding mentors and peers who will answer your questions.

When a lawyer is worth the fee

For small jobs, a clear email exchange may be enough. For longer or larger arrangements, an hour with a lawyer to review a template you can reuse is money well spent. If you are in India and want somewhere to start looking, WakilSahab lets you browse lawyers by area of practice and read news, blog articles and forum discussions on legal topics. It will not tell you what your contract means, but it can help you find someone who will, and the price and scope are for you to agree with them directly.

My pre-signing routine

• Read the whole thing once, slowly, on a screen where I can search.
• Highlight money, dates and anything with the word “all”.
• Send questions in a single email and keep the replies.
• Save the signed copy somewhere I can find in a year.

A yes feels exciting, and the excitement is the exact moment the terms matter most. The headline rate gets you in the door, but the small print decides what the work will really cost you.