Most problems are expectation problems
When a freelance project goes badly, the cause is often not poor skill but a gap between what the client expected and what they got, or between when they expected it and when it came. Quality matters, but predictable communication matters nearly as much. A client who knows what is happening and when usually stays relaxed. A client left guessing tends to start imagining the worst.
The good news is that expectations can be set deliberately, early and in plain words.
Set the rules at the start
A short kickoff message, or a call followed by a written summary, is a good place to cover the working basics. Consider including:
- Your working hours and response time. For example, “I reply to messages within one business day.” Avoid promising instant replies you cannot keep.
- Preferred channels. Say which channel you use for what. Quick questions might go in chat, while decisions and files go by email. Thinking through communication channels at the outset avoids messages scattered across five places.
- Who decides. Name the person who gives final approval, particularly when several people at the client’s company have opinions.
- How feedback is given. Ask for consolidated feedback in one message rather than piecemeal comments from many people.
- How and when you will update them.
Putting these in writing, even briefly, gives both of you something to refer back to.
Response times in practice
Clients rarely mind a reply that takes a day, as long as they know that is normal. What they dislike is silence they did not expect. If you will be away, say so ahead of time and name when you will be back. If you are working across time zones, explain what that means in practice, for example that a message sent in their afternoon might get answered the next morning.
The same applies in reverse. It is reasonable to say what you need from the client and by when: “To finish by the 20th, I will need your feedback by the 12th. If it comes later, the delivery date may move.” This turns a vague hope into a shared schedule.
Habits from asynchronous communication help here. Write messages that can be understood without a live conversation: state the context, the question, any deadline and what happens next. Fewer back-and-forth exchanges means less friction for everyone.
Revision limits
Unlimited revisions can quietly turn a modest project into an endless one. Agree on a specific number of revision rounds, and define what counts as a round, for example one set of consolidated feedback. Specify what happens beyond that, such as extra rounds billed at your hourly rate. This belongs in your scope agreement and should be echoed in your proposal.
Explain the reason in friendly terms. A limit is not a threat; it keeps the project moving and the price predictable. Also help the client use rounds well: ask them to review against the goals you agreed, not shifting preferences.
Update rhythms
Choose a rhythm that fits the project:
- Short projects: an update at the start, a draft or midpoint check, and delivery.
- Longer projects: a brief weekly note.
- Ongoing arrangements: a regular summary at a set time each week or month.
Good status updates are short and follow a pattern: what is done, what is next, what you need from the client, and any risk to the timeline. A hypothetical example: “Done: outline and first two sections. Next: remaining sections and a first full draft by Thursday. Need: confirmation of the audience description. Risk: none at the moment.” Five lines can be enough.
Resist the urge to hide bad news. A delay mentioned early, with a revised plan, is far easier for a client to accept than one revealed on the deadline. Sentences such as “I found an issue that may add a day; here is how I will handle it” show control, not weakness.
Meetings: use them sparingly
A call is often the quickest way to resolve something complicated, but a series of unplanned calls can eat your working time. Agree how meetings will be scheduled, how long they last, and who needs to attend. Send an agenda beforehand and a summary of decisions afterward. If you do host video meetings, keep them focused. A few good habits for running better video meetings make a noticeable difference.
Handle changes gracefully
Changes are normal. The aim is not to prevent them but to make them visible. When a request lands that affects scope, time or cost, say so right away and propose an option: add it for a fee, move the deadline, or swap it for something else. Confirm the decision in writing. If a conversation drifts toward conflict, the approaches in handling difficult clients professionally can help.
Tone and courtesy
Clients usually judge you on how the work felt as well as how it looked. Be polite, clear and consistent. Acknowledge messages even if you cannot answer fully yet (“Received, I will come back to you by Wednesday”). Follow sensible online etiquette: read the whole message before replying, answer every question asked, and avoid sending messages late at night in a way that signals you are always available.
Close the loop
When the project ends, send a short wrap-up: what was delivered, where the files are, what support remains, if any, and how to reach you later. Then ask for brief feedback. Notes on what worked in communication feed directly into your next kickoff message, improving your process each time.
No technique guarantees a trouble-free project, and some clients will test even the clearest boundaries. But a clear start, a steady rhythm and honest updates remove most of the avoidable trouble.