Scope Of Work

Load Context First

Before executing this skill, read the following files from the project folder if they exist:

1. USER.md — who the user is, how they think, how they work
2. BUSINESS.md — their business, products, positioning, brand voice, content strategy
3. ICP.md — their ideal customer, their language, their fears, what makes them buy
4. Voice or brand voice skill — look for any installed skill related to voice, tone, or brand voice and apply it automatically
5. Any additional context provided by the user in this session

Use all context silently. Do not reference or summarize files unless asked.

Scope of Work Generator

Purpose: Write a clear, detailed SOW document that protects both parties by defining exactly what will be delivered, when, and under what terms. Clean, professional, and boundary-setting.

Structure

# Scope of Work

**Project:** [Project Name]
**Client:** [Client Name / Business]
**Provider:** [User Name / Business from context]
**Date:** [Date]
**Version:** 1.0

---

## 1. Project Overview

[2-3 paragraphs describing the project, its goals, and expected outcomes. Clear enough that someone uninvolved could understand what this project is about.]

---

## 2. Deliverables

| # | Deliverable | Description | Format | Due Date |
|---|------------|-------------|--------|----------|
| 1 | [Name] | [Detailed description of what this includes] | [File type / format] | [Date] |
| 2 | [Name] | [Description] | [Format] | [Date] |
| 3 | [Name] | [Description] | [Format] | [Date] |

---

## 3. Timeline & Milestones

| Phase | Milestone | Date | Deliverable |
|-------|-----------|------|-------------|
| Kickoff | Project start / onboarding | [Date] | — |
| Phase 1 | [Milestone name] | [Date] | [Deliverable #] |
| Phase 2 | [Milestone name] | [Date] | [Deliverable #] |
| Completion | Final delivery | [Date] | All deliverables |

**Total project duration:** [X weeks/months]

---

## 4. What's Included

- [Specific inclusion #1]
- [Specific inclusion #2]
- [Specific inclusion #3]
- [Communication: X check-ins per week/month via Y]
- [Revisions: X rounds of revisions per deliverable]

---

## 5. What's NOT Included

- [Specific exclusion #1]
- [Specific exclusion #2]
- [Specific exclusion #3]
- Additional work beyond this scope will be quoted separately

---

## 6. Revision Policy

- **Included revisions:** [X] rounds per deliverable
- **Revision turnaround:** [X] business days per round
- **Feedback window:** Client has [X] business days to provide feedback on each deliverable
- **Additional revisions:** Billed at $[X]/hour or $[X] per revision round
- **Definition of a revision:** Changes to existing work. New work or scope changes are separate.

---

## 7. Payment Terms

| Milestone | Amount | Due Date |
|-----------|--------|----------|
| Deposit (on signing) | $[X] ([X]%) | [Date] |
| [Milestone payment] | $[X] ([X]%) | [Date] |
| Final payment | $[X] ([X]%) | On completion |
| **Total** | **$[X]** | |

**Payment method:** [Bank transfer / Stripe / PayPal / etc.]
**Late payment:** Invoices due within [X] days. Work pauses after [X] days overdue.
**Cancellation:** [Terms for early termination — deposit non-refundable, etc.]

---

## 8. Client Responsibilities

The client agrees to:
- Provide all necessary materials, access, and information by [date/timeline]
- Provide feedback within [X] business days of each deliverable
- Designate one primary point of contact for project communication
- [Any other client obligations]

---

## 9. Acceptance

By signing below, both parties agree to the terms outlined in this Scope of Work.

**Provider:**
Name: _______________
Signature: _______________
Date: _______________

**Client:**
Name: _______________
Signature: _______________
Date: _______________

Quality Checklist

• Project overview is clear and complete
• Every deliverable has description, format, and due date
• "What's NOT Included" section sets clear boundaries
• Revision policy is specific (rounds, turnaround, definition)
• Payment terms include deposit, milestones, and late policy
• Client responsibilities are defined
• Signature block included
• Language is clean and professionally neutral
• No ambiguous terms ("ASAP", "reasonable time", etc.)
• Based entirely on user-provided project details

Note: This is a professional document template, not legal advice. Recommend the user have their attorney review before use.