Statement of Work (SOW) Scope Intake

Template Overview

Poorly written Statements of Work (SOWs) are the root cause of consulting disputes, unpaid invoices, and agency burnout. When scopes are ambiguous, clients assume everything is included, while delivery teams assume everything is out of scope.

A rigorous Statement of Work Scope Intake call bridges this gap. By interrogating assumptions, clarifying technical constraints, establishing concrete acceptance criteria, and documenting out-of-scope boundaries, teams set projects up for profitable delivery.

This template organizes SOW drafting into distinct sections: business objectives, detailed deliverable milestones, explicit assumptions, out-of-scope boundaries, and objective acceptance testing criteria.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "SOW Scope Intake: [Client Project Name]"
date: [YYYY-MM-DD]
client_name: "Pacific Horizon Media"
solutions_architect: "[[Lead Solutions Architect]]"
engagement_manager: "[[Engagement Manager]]"
client_lead: "[[Client VP Digital]]"
estimated_project_value: "$95,000"
project_type: [Fixed Price Milestone | Time & Materials | Retainer]
tags: [sow, scope, consulting, legal, requirements, client]
---

# SOW Scope Intake: [Client Project Name] — [YYYY-MM-DD]

## 1. Project Objective & Business Problem Statement
- **Core Challenge:** Client requires a secure, local-first documentation archive for 200 investigative journalists handling sensitive whistleblower materials.
- **Success Criteria:** Journalists can record high-fidelity audio interviews, generate instant transcripts locally on Apple Silicon, and organize notes in Markdown vaults with zero cloud storage.

## 2. In-Scope Technical Deliverables & Milestones
### Milestone 1: Custom Vault Architecture & Schema Setup ($25,000)
- Deliver bespoke Markdown frontmatter schema supporting journalistic attribution, sources, and verification flags.
- Acceptance Test: 100% schema validation across automated test repository.

### Milestone 2: On-Device Recording & Transcription Integration ($45,000)
- Configure native ScreenCaptureKit and CoreAudio recording profiles for M-series MacBooks.
- Acceptance Test: Zero audio frame loss over 3-hour continuous recording stress tests.

### Milestone 3: Newsroom Training & Documentation Package ($25,000)
- Deliver 10 customized newsroom Markdown templates and conduct 3 live training sessions.
- Acceptance Test: 85% active journalist attendance and successful completion of pilot interview test.

## 3. Explicit Out-of-Scope Scope Boundaries
- **Out of Scope:** Multi-tenant web browser cloud portals (violates core local security mandate).
- **Out of Scope:** Windows and Linux operating system configurations (deployment restricted strictly to macOS).
- **Out of Scope:** Ongoing helpdesk user support past Day 30 following delivery.

## 4. Key Delivery Assumptions & Client Dependencies
- Client IT will provision administrative access to test MacBooks within 5 business days of signing.
- Client will provide written feedback on draft templates within 72 hours of delivery.

## 5. Next Steps for Contract Formalization
- [ ] [[Lead Solutions Architect]] Convert intake notes into formal legal SOW contract language.
- [ ] [[Engagement Manager]] Review pricing model with internal delivery committee.
- [ ] Transmit formal SOW package to [[Client VP Digital]] by [[YYYY-MM-DD]].

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "SOW Intake: Pacific Horizon Media"
date: 2026-10-05
client_name: "Pacific Horizon Media"
estimated_project_value: "$95,000"
tags: [sow, scope, consulting]
---

# SOW Intake: Pacific Horizon Media — October 5, 2026

## 1. Scope Agreed
Project covers deployment of sovereign Markdown vaults for 200 journalists.

## 2. Boundaries Established
Windows builds and cloud syncing are explicitly out of scope. Client accepted Apple Silicon macOS focus.

## 3. Next Action
Draft legal SOW delivered to client legal team on October 8, 2026.

When to Use and When to Avoid

When to Use

• Use during consulting scoping calls, agency project intakes, and professional services SOW drafting.
• Use to establish precise technical deliverables, acceptance criteria, and milestones.
• Use to document explicit out-of-scope boundaries and prevent project scope creep.

When to Avoid

• Avoid using for internal company agile sprint planning (use [[sprint-planning-agenda]]).
• Avoid using for quick exploratory sales discovery chats.

On-Device AI Integration

Capture SOW scope intake meetings with Oyma on macOS:

Analyze the Statement of Work scoping meeting transcript:
1. Synthesize the project business problem, core objectives, and target delivery timeframe.
2. Outline the in-scope technical deliverables grouped into distinct payment milestones with acceptance criteria.
3. Explicitly list out-of-scope boundaries and dependencies required from the client team.
4. Record next steps for formalizing the legal contract and final pricing proposals.
Output in structured, legally disciplined CommonMark.

Your commercial consulting proposals and technical scoping notes stay securely on your Mac.