Work Scope Tracker

Freelance scope records

A website change request form keeps edits from becoming invisible work

Website changes often arrive as quick edits: update this copy, add this section, swap this image, adjust this page. A request form turns those edits into trackable project decisions.

Where Work Scope Tracker fits

Work Scope Tracker helps website freelancers keep each change request tied to a page, deliverable, scope decision, amount, deadline impact, and client approval.

Website request details to record

  • Page URL, section, file, or deliverable affected.
  • Requested content, design, technical, or structural change.
  • Original scope reference or maintenance agreement limit.
  • Estimated hours, additional amount, and delivery impact.
  • Approval state before the edit is performed.

Requests that should not stay informal

  • New pages, new sections, or new landing page variants.
  • Content changes that require layout, SEO, or QA work.
  • Requests after launch approval or after included revision rounds.
  • Changes from a stakeholder who was not part of the original approval.

A practical workflow

  1. 1Record the website request with the affected page or asset.
  2. 2Compare it against the project or maintenance scope.
  3. 3Mark it included, extra, or unclear.
  4. 4Ask for approval if it affects cost, hours, or delivery.
  5. 5Export the completed request history for billing or handoff.

Website change request form fields

Website/page: [URL or page name]
Requested change: [summary]
Type: [content/design/technical/SEO/other]
Original scope reference: [baseline]
Scope decision: [included/extra/unclear]
Estimated hours: [hours]
Additional amount: [amount]
Delivery impact: [date or none]
Approval status: [waiting/approved/declined]

Related problem guides

Try it on a real project

Create a project, write the agreed scope, and record the next request before it becomes another memory test.

Open Work Scope Tracker