# Scope of Work Template

Use this outline before kickoff to define the work, exclusions, approval path, and change-control rules for a project.

## 1. Project Summary
- Project name:
- Client or internal stakeholder:
- Project owner:
- Delivery lead:
- Start date:
- Target completion date:
- Primary objective:

## 2. Background and Objective
Write the business context and the outcome the work should create.

Example: Create a client onboarding workspace that gives customers one place to submit files, review project status, and approve launch assets.

## 3. In-Scope Deliverables
| Deliverable | Description | Owner | Acceptance criteria |
| --- | --- | --- | --- |
| Onboarding workspace | Configure the shared project and client-facing view | Delivery lead | Client can access assigned project status |
| Intake form | Collect required launch files and decisions | Operations lead | Required fields and file uploads are tested |
| Shared project brief | Publish goal, milestones, stakeholders, and links | Project manager | Stakeholders approve the brief before kickoff |

## 4. Out-of-Scope Work
- Billing setup
- CRM migration
- Legal copy review
- Custom white-label portal design
- Mobile redesign

## 5. Milestones
| Milestone | Date | Owner | Notes |
| --- | --- | --- | --- |
| Kickoff | 2026-05-26 | Project manager | Confirm scope and stakeholders |
| First workspace review | 2026-06-03 | Delivery lead | Review files, form, and brief |
| Stakeholder approval | 2026-06-10 | Client sponsor | Approve launch checklist |
| Launch handoff | 2026-06-14 | Operations lead | Transfer to ongoing delivery workflow |

## 6. Roles and Responsibilities
- Project owner:
- Delivery lead:
- Client approver:
- Contributors:
- Support contact:

## 7. Dependencies and Assumptions
- Client provides required files before the first workspace review.
- Legal or compliance review is handled outside this scope unless added by change request.
- Launch timing depends on stakeholder approval by the milestone date.

## 8. Acceptance and Sign-Off
The work is complete when:
- Each in-scope deliverable meets its acceptance criteria.
- Required files and links are attached to the project.
- Stakeholders approve the shared brief and launch checklist.
- Open risks or changes are recorded with owners.

## 9. Change Control
New requests should be logged through project intake. The delivery lead reviews each request for schedule, workload, risk, and cost impact before it is accepted into scope.

## 10. Communication Cadence
- Weekly status review:
- Client approval channel:
- Escalation path:
- Final handoff location: