Why expectations cause trouble
Many client disagreements are not about quality. They are about gaps between what one person assumed and what the other person delivered. The client thought three rounds of changes were included; you thought one. They expected a reply within an hour; you check messages twice a day. Neither side did anything unreasonable, yet both end up frustrated.
Spending a little time at the start to spell out the basics is one of the most reliable ways to prevent this. It does not remove all problems, but it gives both sides a shared reference when something shifts.
Define the scope
Scope is the list of what the project includes, and just as importantly, what it does not. Be specific about:
- Deliverables. What exactly will the client receive, and in what format?
- Quantity. How many pages, items, versions or sessions?
- Exclusions. Tasks that might reasonably be assumed but are not part of this agreement, such as sourcing images, ongoing maintenance or extra rounds of edits.
- Inputs. What you need from the client, such as text, files, access or decisions.
A hypothetical example: “Three rounds of edits on a single article of up to a stated length, delivered as a document” is much clearer than “editing.” If the client later asks for something outside that description, you have a basis for discussing an adjustment instead of arguing.
Agree on timelines, including the client’s part
A schedule has two sides. You commit to delivery dates, and the client commits to providing materials and feedback on time. If a project depends on their input, say so plainly: “I can deliver the first draft five working days after I receive the materials.”
Consider including:
- Start date or the condition that starts the clock, such as receipt of materials or a deposit.
- Key milestones and approximate dates.
- How long the client has to respond with feedback.
- What happens if feedback arrives late. For example, the delivery date may move accordingly.
Give estimates as realistic ranges where appropriate, and avoid committing to dates you are unsure about. If your workload overlaps with multiple projects, factor that in before you quote a date, not afterward.
Handle revisions and feedback
Revisions are a common source of friction because they have no natural end. Decide early:
- how many rounds are included
- what counts as a revision versus a new request
- who gives feedback on the client’s side, so you do not receive conflicting comments from several people
- how feedback should be sent, such as in one consolidated message
When a client changes direction after approving something, it is reasonable to explain that this goes beyond the agreed revisions and offer a quote or a plan for the extra work. Do this politely and without blame. People often do not realize how a change affects the effort involved.
Clarify communication
Set out how and when you will communicate. Useful points include:
- Preferred channels, such as email for decisions and a quick message for small questions.
- Typical response times, expressed as a range, like “within one to two business days.”
- Your working hours and any days you are unavailable.
- How you will give updates, whether at milestones or on a regular schedule.
Being clear about response times protects you as well as the client. Without this, some clients assume constant availability. Tell them what they can expect, and then meet it consistently. Good email etiquette, including clear subject lines and a short summary of next steps, makes written communication easier to follow.
Talk about payment
Money should not be a surprise. Agree before starting on the price or how it is calculated, when invoices are sent, the payment terms and any deposit. State what happens with late payments in a measured way, within whatever rules apply where you work. Different countries have different rules on this, so check the local requirements if you are unsure.
Be honest about what you cannot promise
It is tempting to say what a client wants to hear, particularly when you want the work. Resist promises about outcomes that depend on factors you do not control, such as how many people will respond to your design, or how quickly a search engine will rank a page. Describe what you will do, and be open about the uncertainty. Avoiding overstated claims at this stage prevents disappointment later and builds credibility.
Put it in writing
Spoken agreements are easily misremembered. After a call, send a brief summary: “To confirm what we discussed, the project includes X and Y, the first draft is due on this date, and I will need Z from you by then.” Ask the client to reply with confirmation.
For larger or riskier projects, a more formal document is wise. The reasons for documenting terms are covered in the discussion of written agreements, and for anything with significant money or legal consequences, it is sensible to get advice from a qualified professional familiar with your location. A short project proposal can also serve as a starting point for the agreed scope.
Revisit when things change
Projects evolve. If scope grows, a deadline moves or a new stakeholder joins, bring it up promptly and update what you agreed. A brief message such as “This adds work beyond what we outlined; here are two options” keeps the conversation practical.
If a conversation becomes tense, return to the shared reference. Focus on what was agreed and what is needed now, not on who was at fault. Active listening, meaning that you repeat back what you understood and ask what they need, often defuses misunderstandings quickly.