Free template

Shopify Theme Project Scope Template

A scope document for theme projects: deliverables, templates in scope, revision limits, the sign-off process and change orders.

Where ThemeSync fits

Free. No email required. Use your browser’s print dialog and choose “Save as PDF”.

Template mappings on a development theme
Template

Shopify Theme Project Scope

A complete scope document template for theme development projects. Defines deliverables, revision limits, sign-off process, and change order procedures.

Template mappings on a development theme

By ThemeSync · themesync.dev · 2026

Project Overview

Fill in the project basics. This section provides context for the rest of the document and is referenced when evaluating scope change requests.

Project Details

Project Name
Client
Store URL
PlatformShopify / WooCommerce
Project TypeFull theme build / Redesign / Landing pages / Page refresh
Start Date
Target Launch Date
Project Lead
Client Contact

Project Description

Brief description of the project goals and context. What is being built and why.

Deliverables — Template List

Define deliverables as specific templates — not vague "pages." Each template is a countable, reviewable, approvable unit of work.

# Template Name Type Description Status
1page.homePageHomepage with hero, featured collections, value props—
2product.defaultProductStandard product page (images, variants, add-to-cart)—
3product.bundleProductBundle product with component breakdown—
4collection.defaultCollectionStandard collection grid with filtering—
5collection.featuredCollectionFeatured collection with hero banner—
6page.aboutPageAbout/story page with team section—
7page.contactPageContact page with form—
8page.faqPageFAQ with accordion sections—
9page.landingPageMarketing landing page template—
10blog.defaultBlogBlog listing page—
11article.defaultArticleBlog post template—
12cartCartCart page / drawer—

Add or remove rows to match your project. The key is specificity — each row is one approvable deliverable.

Explicitly excluded

Any templates NOT listed above are out of scope. Additional templates require a change order (see Section 5). Common exclusions to state explicitly:

  • Additional custom product templates beyond those listed
  • Custom landing pages not specified above
  • Third-party app customization or integration beyond default placement
  • Custom checkout modifications (Shopify Plus only)
  • Email notification template customization
  • Multi-language/localization setup

Revision Policy

Define clear boundaries for what constitutes a "revision" vs. a "change request." This section prevents the most common scope disputes.

Definitions

Revision (Included in Scope)

A modification to an existing deliverable that brings it closer to the approved design. The output should match what was approved in Figma/design phase. Revisions correct implementation issues — they don't introduce new requirements.

Examples: Fixing spacing that doesn't match the design, correcting a color value, adjusting font size to match the mockup, fixing responsive behavior that was spec'd differently.

Change Request (Additional Scope)

A modification that introduces new requirements not present in the approved design. Changes add features, alter approved layouts, or request entirely new pages/sections.

Examples: "Can we add a mega-menu?" (wasn't in design), "Can we change from 3 columns to 4?" (approved design showed 3), "Can we add a custom calculator?" (new feature).

Revision Rounds

PhaseIncluded RoundsTimeline Per Round
Design revisions (in Figma)2 rounds3 business days
Development revisions (on preview)2 rounds5 business days

After the included revision rounds, additional rounds are billed at the project's hourly rate ($___/hr).

Feedback Requirements

  • All feedback for a given round must be submitted together — not piecemeal over multiple days
  • Feedback must be submitted within 5 business days of receiving the preview
  • If no feedback is received within the deadline, the current state is considered approved
  • Contradictory feedback (requesting a change, then requesting the original back) counts against revision rounds
Why this matters

Without explicit revision limits, projects spiral. A "quick tweak" becomes 5 rounds of back-and-forth. Defining rounds upfront sets expectations and makes scope conversations easier — you're referencing an agreement, not having a confrontation.

Sign-Off Process

Define what "approved" means and how it's captured. This protects both parties.

Approval Chain

StageApproverWhat's ApprovedMethod
DesignClientVisual design direction (Figma)Written confirmation (email or Figma comment)
Internal QAPM / QA LeadCross-browser compatibility, code qualityInternal sign-off in project tool
Client ReviewClientImplementation matches expectationsPer-template approval (email or feedback tool)
LaunchClient + PMReady to go liveWritten confirmation

What "Approved" Means

  • Approval is per template — each deliverable in Section 2 is approved individually
  • Approval means "this template is complete and ready for launch as-is"
  • After approval, changes to that template are change requests (even if they seem small)
  • Approval is documented with date and person (email timestamp or tool record)

Approval Timeout

If a template has been in "awaiting approval" status for more than 10 business days without client response, it is considered approved. Client will be reminded at day 5 and day 8.

Important

Post-approval changes are billed as change orders regardless of size. This isn't about being rigid — it's about maintaining clear boundaries so both parties know where they stand. Small requests can be accommodated generously at the developer's discretion.

Change Order Process

When a request falls outside the agreed scope, this process applies.

How a Change Order Works

  1. Client makes a request that falls outside the scope defined in Section 2 or contradicts an approved design
  2. Developer identifies it as out-of-scope and notifies the client (referencing this document)
  3. Developer provides an estimate — hours, cost, and impact on timeline
  4. Client approves or declines the change order in writing
  5. If approved: work begins after written confirmation; invoice added to project total
  6. If declined: the original scope continues unchanged

Change Order Rates

Hourly rate for changes$___/hr
Minimum charge per change order___ hours
Turnaround for change order estimate___ business days

What Triggers a Change Order

  • Requesting a new template not listed in Section 2
  • Requesting new functionality not in the approved design
  • Significant design direction changes after design approval
  • Additional revision rounds beyond those included
  • Third-party app integration beyond default placement
  • Content migration or data entry work
  • Requesting work outside the agreed platform (e.g., email templates, external landing pages)
Keeping the relationship healthy

Change orders aren't punishment — they're clarity. Most clients appreciate knowing exactly what's included vs. extra. The scope document should feel protective for both sides, not adversarial.

Timeline

High-level milestones. Adjust dates per project. Note which milestones require client action — delays on their side shift subsequent dates.

MilestoneTarget DateOwnerDependencies
Project kickoffBoth—
Design delivery (Figma)Agency—
Design approvalClientClient reviews within 5 days
Development completeAgencyDesign approved
Preview ready (internal QA passed)Agency—
Client review periodClientClient reviews within 5 days
Revisions completeAgencyFeedback received
Final approvalClientClient signs off within 5 days
LaunchAgencyAll approvals received
Timeline protection clause

Dates above assume client responses within the stated timeframes. Each business day of client delay shifts all subsequent milestones by one business day. If cumulative client delays exceed 10 business days, the project timeline will be renegotiated.

Responsibilities

Agency Provides

  • Design (Figma), development, and deployment of all listed templates
  • Cross-browser QA (Chromium, Firefox, WebKit) at desktop, tablet, and mobile viewports
  • Preview environment with correct template mapping
  • Client feedback mechanism (pin-based tool or structured template)
  • Revisions within the included rounds
  • Launch deployment and 24-hour post-launch monitoring

Client Provides

  • Timely feedback within stated deadlines
  • Brand assets (logo, fonts, color codes, photography) by project kickoff
  • Content (product descriptions, page copy, images) or confirmation to use existing
  • Access to Shopify admin (collaborator access or staff account)
  • Shopify Admin API token (for template sync and store data access)
  • Decision authority — the reviewer must have sign-off power

Agreement

Both parties agree to the scope, deliverables, timeline, and processes described in this document. Work proceeds based on this agreement.

Agency

Signature: Date:

Name: Title:

Client

Signature: Date:

Name: Title:

Note

This template is a starting point — not legal advice. Have your attorney review before using in client engagements. Customize to your jurisdiction, business terms, and project specifics.

In ThemeSync

Where ThemeSync fits

You write the scope document. Three of its sections have a direct counterpart in ThemeSync, so the agreement and the review use the same list. Screens are from a demo store.

Template mappings including a conditional rule for the Bundles collection
Deliverables · Template listEach template in scope is mapped to a real store URL on the development theme. The client reviews exactly the templates in the contract.
Feedback session view with comments grouped by page
Revision policyEach review round is one feedback session with its own date and its own comment list, so “two rounds of revisions” is something both sides can count.
ThemeSync team page with Designer, QA and PM roles
Sign-off processRoles map to the sign-off steps in the scope: Designer signs off on visual design, QA on functionality, PM on scope. Approvals are recorded per page and viewport (Agency plan).