Setting expectations at the start

Prevent the problems instead of managing them.

Almost every client relationship that goes badly went badly at the start, in what was not agreed.

Agree how you will communicate. Which channel, how often, and what response time is reasonable. A client who expects a reply within an hour and a freelancer who replies within a day will both feel wronged, and neither of them said anything.

Agree what is included and what is not, specifically. Not "a website" but the number of pages, how many rounds of revision, what content they supply, and what happens if they want a fourth round. The scope conversation is uncomfortable for ten minutes at the start and saves an argument that lasts for months.

Agree the payment terms, including when each payment is due and what happens if it is late. For a new client, take a deposit. This is normal professional practice everywhere and it is the single most effective protection a freelancer has.

Agree what you need from them, and by when. Most projects run late because the client did not send the content or did not give feedback, and then the delay is remembered as yours. Name their deliverables and their dates in writing alongside your own.

Put all of it in one document and have them confirm it. It does not need to be a contract drafted by a lawyer for small work, but it does need to be written and acknowledged.

Then say what you will not do. Being clear about the boundary at the start is far easier than defending it later.

Lab — try it yourself

Write your standard scope and terms document once, properly. Then use it for every client rather than rewriting it each time.

Check what you learned

Create your free BvLogic ID to take the quiz and record your score.

Create your BvLogic ID

Continue to lesson 2 Up next 2. Updates that keep a client calm