PagesProject ManagementOfficial

πŸ“Scope of Work

Define project scope, deliverables, timeline, and responsibilities for client or internal engagements.

by Peopsy

Preview: Scope of Work

Scope of Work

πŸ’‘

Project: [Project Name] | Client: [Client Name] | Date: [Date] | Version: [1.0]

Project Overview

[2-3 sentences describing the project, its purpose, and the key outcome. This should be understandable by anyone, including people who are not directly involved.]

Objectives

  • [Objective 1: e.g., Implement CRM integration to sync deal data bi-directionally]

  • [Objective 2: e.g., Migrate historical data from legacy system (24 months)]

  • [Objective 3: e.g., Train 50 end users on the new platform]


In Scope

  • [Scope item 1: e.g., Configuration and setup of core platform]

  • [Scope item 2: e.g., CRM integration (Salesforce, bi-directional sync)]

  • [Scope item 3: e.g., Data migration of contacts, companies, and deals]

  • [Scope item 4: e.g., Two training sessions (admin + end user)]

  • [Scope item 5: e.g., 30 days of post-launch support]

Out of Scope

⚠️

Be explicit about what is NOT included. This prevents misunderstandings and scope creep later.

  • [Out of scope 1: e.g., Custom API development beyond standard integration]

  • [Out of scope 2: e.g., Migration of email/communication history]

  • [Out of scope 3: e.g., Ongoing managed services after 30-day support window]

  • [Out of scope 4: e.g., Hardware provisioning or network configuration]


Deliverables

#

Deliverable

Description

Acceptance Criteria

Due Date

D1

[Deliverable 1]

[Brief description]

[How we know it is done]

[Date]

D2

[Deliverable 2]

[Brief description]

[How we know it is done]

[Date]

D3

[Deliverable 3]

[Brief description]

[How we know it is done]

[Date]

D4

[Deliverable 4]

[Brief description]

[How we know it is done]

[Date]

D5

[Deliverable 5]

[Brief description]

[How we know it is done]

[Date]

Timeline & Milestones

Phase

Activities

Duration

Start Date

End Date

Kickoff

Project kickoff, requirements confirmation

1 week

[Date]

[Date]

Build

Configuration, integration, data migration

[X weeks]

[Date]

[Date]

Test

UAT, bug fixes, performance validation

[X weeks]

[Date]

[Date]

Train

Admin and end-user training sessions

1 week

[Date]

[Date]

Launch

Go-live, monitoring, stabilization

1 week

[Date]

[Date]

Support

Post-launch support and optimization

30 days

[Date]

[Date]


Roles & Responsibilities

Responsibility

Client

Vendor

Project management

βœ…

βœ…

Requirements gathering

βœ… (provide)

βœ… (document)

Platform configuration

βœ…

Integration development

βœ…

Data preparation and cleanup

βœ…

Data migration execution

βœ…

User acceptance testing

βœ…

βœ… (support)

Training delivery

βœ…

Change management

βœ…

βœ… (advise)

Go-live decision

βœ…

Assumptions

  • [Assumption 1: e.g., Client will provide dedicated project manager with decision authority]

  • [Assumption 2: e.g., API access to existing CRM will be granted within first week]

  • [Assumption 3: e.g., Data will be cleaned and deduplicated before migration]

  • [Assumption 4: e.g., End users will be available for scheduled training sessions]

Risks

Risk

Likelihood

Impact

Mitigation

[Risk 1: e.g., Data quality issues]

Medium

High

[Run data audit in Week 1]

[Risk 2: e.g., API rate limits]

Low

Medium

[Implement batching and retry logic]

[Risk 3: e.g., Resource availability]

Medium

Medium

[Lock in resource commitments upfront]


Approvals

Client project sponsor reviewed and approved scope β€” [Name, Date]

Vendor delivery lead reviewed and approved scope β€” [Name, Date]

Both parties agreed on timeline and milestones β€” [Date]

SOW signed by authorized representatives β€” [Date]

About this template

Scope creep kills projects, budgets, and relationships. This scope of work template helps you draw clear lines before any engagement begins. Define what is in scope and β€” just as importantly β€” what is out of scope. List specific deliverables with acceptance criteria so there is no ambiguity about "done." Establish timelines with milestones, clarify roles and responsibilities for both sides, document assumptions, and flag risks. Whether you are scoping a consulting engagement, an implementation project, a services agreement, or an internal initiative, this template protects everyone involved by setting expectations upfront. The 20 minutes you spend filling this out will save you 20 hours of rework later.

Tags

scope-of-workSOWproject-scopedeliverablesconsulting

Install Scope of Work in your workspace

Zealos is a personal operating system for revenue teams. Join early access and we'll deliver this template the moment you're in.

Get early access

More page templates

Weekly Planner

πŸ’œ

Weekly Focus: What is the ONE thing that would make this week a success? Write it here and keep it visible.

Week of: [Date] β€” [Date]


Monday

Most important task for the day

Second priority task

Third priority task

Tuesday

Most important task for the day

Second priority task

Third priority task

Wednesday

Most important task for the day

Second priority task

Third priority task

Thursday

Most important task for the day

Second priority task

Third priority task

Friday

Most important task for the day

Second priority task

Wrap up loose ends and prep for next week


Weekly Review

βœ…

Take 15 minutes on Friday afternoon to reflect on your week. This small habit compounds into massive clarity over time.

  • What did I accomplish this week?

  • What didn’t get done and why?

  • What should I carry forward to next week?

  • What’s one thing I could improve next week?

πŸ“…Weekly Planner

Plan your week with daily task lists, a weekly focus area, and an end-of-week review.

Personal ProductivityOfficial

Change Order Request

πŸ’‘

Complete this form for every proposed change to the original contract scope. Attach supporting documents (sketches, specs, photos) before routing for approval.

CO Details

Field

Value

CO Number

[CO-001]

Project Name

[Project Name]

Contract Number

[Contract #]

Date Initiated

[YYYY-MM-DD]

Requested By

[Name / Company]

Priority

[Standard / Urgent / Critical Path]


Parties

Role

Name

Company

Contact

Owner / Client

[Name]

[Company]

[Email / Phone]

General Contractor

[Name]

[Company]

[Email / Phone]

Architect of Record

[Name]

[Company]

[Email / Phone]

Subcontractor (if applicable)

[Name]

[Company]

[Email / Phone]


Description of Change

Reason for Change:

  • [Owner-directed change]

  • [Design error or omission]

  • [Unforeseen site condition]

  • [Code or regulatory requirement]

  • [Value engineering]

  • [Other: describe]

Detailed Description:

[Provide a detailed narrative of what is changing, why, and what areas of work are affected. Reference drawing numbers, spec sections, and RFI numbers as applicable.]

Reference Documents

  • [RFI #___]

  • [Drawing Sheet ___]

  • [Specification Section ___]

  • [Photo / Sketch attached]


Cost Impact

⚠️

All cost estimates must include labor, material, equipment, subcontractor markup, and overhead & profit per contract terms.

Item

Description

Qty

Unit

Unit Cost

Total

1

[Labor β€” trade description]

[X]

[hrs]

[$XX.XX]

[$X,XXX]

2

[Material β€” description]

[X]

[ea/lf/sf]

[$XX.XX]

[$X,XXX]

3

[Equipment rental]

[X]

[days]

[$XXX]

[$X,XXX]

4

[Subcontractor β€” name/trade]

[1]

[LS]

[$X,XXX]

[$X,XXX]

Subtotal

[$X,XXX]

Overhead & Profit (__ %)

[$XXX]

Total CO Value

[$X,XXX]

Net impact to contract value: [+ / - $X,XXX]


Schedule Impact

Field

Value

Days Added / Removed

[+/- X calendar days]

Affected Activities

[List critical path activities impacted]

Revised Substantial Completion

[YYYY-MM-DD]

Concurrent Work Possible?

[Yes / No β€” explain]


Approval Chain

Step

Role

Name

Date

Status

1

Submitted by (Requestor)

[Name]

[Date]

[Submitted]

2

Reviewed by (PM / Superintendent)

[Name]

[Date]

[Pending]

3

Approved by (GC Principal)

[Name]

[Date]

[Pending]

4

Approved by (Architect)

[Name]

[Date]

[Pending]

5

Approved by (Owner)

[Name]

[Date]

[Pending]


Verification Checklist

Scope clearly defined and not duplicated in other COs

Cost breakdown includes all labor, material, equipment, and markup

Schedule impact reviewed with superintendent

Downstream trade impacts identified (see Cascading Impact page)

Supporting documents attached (drawings, specs, photos)

Insurance and bonding implications reviewed if CO exceeds threshold

πŸ“‹Construction Change Order

Manage change orders from request through approval with cascading impact analysis and a running CO log.

Construction & EngineeringOfficial

Client Onboarding Hub

πŸ’‘

Use this hub as your single source of truth for every new client engagement. Complete the overview below, then work through each sub-page to ensure a smooth, professional onboarding experience.

Client Overview

Field

Details

Client Name

[Company Name]

Main Contact

[Name, Title, Email, Phone]

Account Manager

[Your team member]

Start Date

[YYYY-MM-DD]

Retainer Value

[$X,XXX / month]

Services

[SEO, Content, Paid Media, Social, etc.]

Communication Cadence

[Weekly calls, bi-weekly reports, monthly reviews]

Contract Length

[6 months / 12 months / ongoing]

Billing Cycle

[Monthly / Quarterly]

Primary Goal

[e.g., Increase qualified leads by 40% in 6 months]


Master Onboarding Checklist

Work through each item below. Check them off as you go β€” aim to complete all items within the first two weeks of engagement.

Send welcome email with onboarding packet and team introductions

Schedule kickoff call (all stakeholders from both sides)

Set up shared Slack channel or communication workspace

Collect brand assets (logos, fonts, color codes, style guide)

Configure tools access (analytics, ad platforms, CMS, social accounts)

Create client reporting dashboard with agreed-upon KPIs

Establish content/creative approval workflow and turnaround times

Document escalation paths and emergency contacts

Set up project management board with initial deliverables

Schedule recurring check-in meetings for the first 90 days

Conduct internal team briefing on client goals and sensitivities

Send first check-in summary within 48 hours of kickoff


Key Dates & Milestones

Milestone

Target Date

Owner

Status

Welcome email sent

[Date]

[Name]

Pending

Kickoff call completed

[Date]

[Name]

Pending

All access credentials received

[Date]

[Name]

Pending

Brand guidelines documented

[Date]

[Name]

Pending

Reporting dashboard live

[Date]

[Name]

Pending

First deliverable shipped

[Date]

[Name]

Pending

30-day check-in

[Date]

[Name]

Pending

90-day review

[Date]

[Name]

Pending

πŸ’œ

Pro tip: Share this hub (or a client-facing version) with your new client so they can see progress and know exactly what to expect during onboarding.

πŸš€Agency Client Onboarding Hub

A structured multi-page hub for onboarding new agency clients β€” from kickoff to 90-day success.

AgencyOfficial