THE PRACTICAL ANSWER
What belongs in a freelance project scope?
Specify the deliverable, quantity, format, required inputs, exclusions, deadline, approval owner, and acceptance criteria. Define the revision allowance and how new requests affect the fee or schedule. Agree on the written scope before production and record changes when they happen.
Explore a client scope template ↗“A few posts” is not a scope
Many project disagreements start with reasonable people imagining different things. A client thinks posting includes graphics, scheduling, and replies. A freelancer thinks it means draft copy. Write down quantities, formats, channels, source materials, and who does each step.
A statement of work should translate the sales conversation into an operational agreement. Use plain language that both sides understand. Templates can help organize a draft, but a contract may need professional review for your jurisdiction and situation.
Define what “done” means
Specify the deliverable and its acceptance criteria. A workflow may be accepted when agreed test cases pass and operating notes are handed over. An article may require factual approval, a defined length range, and an agreed format. Revenue increases or search rankings are usually outside a freelancer's complete control and should not be casually promised.
Name the client reviewer. Ask for one consolidated round of feedback rather than separate messages from several stakeholders. Explain which changes count as revisions to the agreed work and which are a new direction. State what happens when client inputs arrive late.
Make exclusions helpful
Exclusions should clarify ownership. “Includes three approved email drafts. Does not include CRM configuration, list import, campaign scheduling, or deliverability remediation.” The client can now decide whether those additional tasks are needed and who will do them.
Change request language: “This adds [new work] to the agreed scope. I can include it for [revised fee] with delivery on [revised date]. Would you like me to prepare the updated scope for approval, or keep the original plan?”
Include AI and handoff expectations
Agree on approved tools, confidential information, review responsibility, and any restrictions on generated assets. For automations, document account ownership, secrets handling, failure alerts, and support boundaries. For creative work, clarify the rights you can transfer and any third-party license limits.
Close the project deliberately
Deliver the files in the agreed format, summarize what was checked, and identify any outstanding decisions. Ask for acceptance through the agreed channel. Archive necessary records securely according to your agreement and retention obligations, and remove access you no longer need. A clear handoff makes it easier to discuss a future project without leaving the original one open forever.
Put this guide to work with a focused tool or a printable plan.
Open your toolkit ↗Bring your offer, portfolio, or AI workflow to a short fit conversation with Ashley.
Explore focused support ↗