A website project can sound straightforward until the first request adds a new page, a payment flow, or a second language. If you and your client have different ideas about what the original price includes, a small change can become a difficult conversation.
A written scope gives both sides a shared description of the work. It does not need to be a long contract: a clear project brief attached to an appropriate agreement can make deliverables, assumptions, reviews, and next steps easier to discuss. This guide is a project-planning checklist, not legal advice. Contract, tax, intellectual-property, and consumer rules vary by location; get qualified advice when the terms or risks warrant it.
Start with the outcome, then list the deliverables
Describe the client's goal in one or two sentences, then turn it into things you can deliver and review. “Build a modern website” is too broad to estimate. “Set up a five-page WordPress site using the approved design, with a contact form that sends submissions to the client's nominated email address” gives both sides a more concrete starting point.
For each deliverable, record details that can change the work:
- Pages and flows: name the pages, forms, account steps, or other user journeys included.
- Content and assets: say who supplies copy, images, translations, product data, and licenses.
- Integrations: identify the specific services and level of integration, such as embedding a booking link versus building a custom booking flow.
- Technical boundaries: note the agreed platform, supported browsers or devices, hosting responsibility, and any known constraints.
- Handoff: say whether the work includes source files, administrator access, documentation, training, or launch support.
Also list what is not included when a client could reasonably assume otherwise. Examples might be writing the copy, migrating an existing store, buying third-party licenses, adding unlisted pages, or providing ongoing maintenance. Exclusions should be specific and neutral; they are not a substitute for discussing what the client actually needs.
An overview from ContractCounsel on freelance contracts highlights items such as deliverables, payment terms, and deadlines. It is a U.S.-focused legal resource, so use it as a prompt for discussion rather than a universal contract template.
Write down assumptions and client dependencies
Estimates depend on information and access being available. Make those assumptions visible before they turn into delays or unplanned work. For a small website, dependencies might include:
- the client supplies final copy and images in an agreed format;
- the client names one person to consolidate feedback;
- access to the domain, hosting, and current site is provided before implementation;
- a third-party service supports the required integration; and
- the client reviews each milestone within an agreed period.
If a dependency is uncertain, make it a discovery task or a decision the client must resolve before you commit to later work. Avoid promising a launch date that assumes an untested integration or missing content will arrive on time. State how a delayed dependency affects the schedule and when you will revisit the plan.
Agree on reviews, revisions, and acceptance
“Two rounds of revisions” is easy to write but can still mean different things. Define a round as one consolidated set of feedback on a named deliverable, and say which types of changes it covers. For example, adjusting the spacing and wording on an approved page may fit the agreed review; adding a new page or changing the approved checkout flow is a different request.
Describe how the client will review each milestone and what evidence shows it is ready for that review. A staging link, a list of completed pages, and a short set of agreed checks are more useful than “let me know if you like it.” Include who can approve the work and how feedback should be sent.
Keep three situations distinct:
- Included revision: feedback that refines a deliverable while staying within the agreed requirements and review allowance.
- Defect or missed requirement: the delivered work does not match an agreed requirement. Compare it with the scope and follow the correction process in your agreement.
- Change request: the client wants work that adds to or changes the agreed deliverables, assumptions, or acceptance criteria.
The distinction helps you discuss the request without treating every comment as extra work or every new idea as a defect.
Connect milestones, schedule, and payment
Break the project into reviewable milestones, such as approved structure, design, implementation, and launch handoff. For each one, note what you will provide, what the client needs to provide or approve, and what work follows. Then connect the payment schedule to the arrangement you and the client have agreed on; there is no single percentage schedule that fits every project.
Be explicit about what happens when client feedback, content, or access is late. A schedule should show dependencies rather than silently treating every date as guaranteed. Freelancers Union's client-management guidance includes advice for securing payment before, during, and after a gig; use its suggestions alongside terms suited to your project and location.
Use a simple change-request workflow
When a new request arrives, pause long enough to understand its impact. A lightweight process works even if you manage the project by email:
- Record the request. Capture what the client wants and which original deliverable it affects.
- Clarify the result. Ask what outcome they need, what content or access is involved, and how they will review it.
- Estimate the impact. Explain any added work, dependencies, cost, and schedule change. If the impact is not yet knowable, propose a small discovery step before estimating the full change.
- Get written approval before starting. Confirm the updated scope and terms through the approval method in your agreement.
- Update the project record. Add the approved change to the scope, milestone plan, and invoice or estimate as appropriate.
For example, the original project may include five English-language pages and a contact form. If the client later asks for a Spanish version, first clarify whether they will provide approved translations, which pages and form messages need translation, and whether the site setup supports the extra language. Then give the client a written estimate and revised schedule. Do not start the additional implementation until both sides have approved the change.
If the client does not approve the estimate, keep working to the original scope or pause the affected work as your agreement allows. Stay factual: the request may be valuable, but it changes the agreed plan.
Keep a compact project record
Store the approved scope, estimates, feedback, change decisions, invoices, and payment confirmations in one project folder or system. After a call, send a short written recap of any decisions that affect deliverables, price, or schedule and ask the client to confirm it. This avoids relying on memory when the project spans several weeks.
For U.S. businesses, the IRS recordkeeping overview says a recordkeeping system should clearly show income and expenses and notes that the business affects which records are needed. Keep the records required for your own location and situation; the IRS guidance is not a universal retention rule.
Pre-kickoff scope checklist
Before work starts, confirm that you can answer these questions in writing:
- What outcome is the client paying for?
- Which pages, features, integrations, and handoff items are included?
- What is explicitly excluded or dependent on a later decision?
- Who supplies content, assets, access, and approvals, and when?
- What does each milestone deliver, and how will the client review it?
- How many feedback rounds are included, and what counts as a new request?
- How do schedule and payment respond to delays or approved changes?
- How will either side record approval and keep the latest scope available?
If several answers are still vague, resolve them before treating the estimate or launch date as final. Once the scope is agreed, turn its milestones into a working plan; this web design project-management guide can help with that next step.
