Statement of Work Project Charter

Template Overview

Vague project boundaries lead to toxic scope creep, missed deadlines, and contractual disputes. The Statement of Work Project Charter establishes complete mutual clarity between stakeholders and delivery teams, documenting exact technical deliverables, milestones, acceptance criteria, payment triggers, and out-of-scope boundaries in plain Markdown.

Markdown Template Structure

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

---
title: "SOW Charter: [Project Title] — [Client / Stakeholder]"
date: [YYYY-MM-DD]
project_lead: "[[Project Lead / Solutions Architect]]"
client_sponsor: "[[Client Executive Sponsor]]"
contract_reference: "SOW-2026-XXXX"
project_budget: "$75,000 / Fixed Bid"
estimated_completion: "2026-12-15"
status: "Draft / Approved / In Progress"
tags: [project-management, sow, contract, deliverables, charter]
---

# Statement of Work Project Charter — [Project Title]

## 1. Project Background & Business Purpose
- **Executive Summary:** [Client Name] requires an on-device transcription and note-generation integration within their internal macOS desktop workflow.
- **Strategic Business Objective:** Enable secure local meeting documentation compliant with strict legal confidentiality policies, eliminating third-party cloud data exposure.

## 2. In-Scope Deliverables & Acceptance Criteria
| Deliverable ID | Technical Deliverable Description | Acceptance Criteria | Target Date |
|---|---|---|---|
| **DEL-01** | Native CoreAudio capture daemon | Captures 16kHz audio buffer with < 1.5% CPU overhead | 2026-10-31 |
| **DEL-02** | Local Whisper inference engine | Transcribes 30-min audio in < 90s on Apple M-series chips | 2026-11-15 |
| **DEL-03** | CommonMark template formatting pipeline | Ingests JSON transcript; outputs valid Markdown frontmatter | 2026-11-30 |
| **DEL-04** | Security audit & sandbox profile | Verifies zero outbound network sockets via macOS trace | 2026-12-10 |

## 3. Explicitly Out-of-Scope (Boundaries)
*Any features or activities below require a mutually signed Change Order:*
- Web browser extension or Electron client port (Desktop Swift only).
- Cloud storage integration or multi-tenant user accounts.
- Legacy Intel (x86_64) Mac optimization (Apple Silicon targets only).

## 4. Milestone Schedule & Payment Triggers
| Milestone # | Milestone Description | Completion Trigger | Payment Allocation |
|---|---|---|---|
| **M1** | Project Kickoff & Architectural Spec | Signed Charter & Architecture Doc | 25% ($18,750) |
| **M2** | Core Engine Beta Release | Delivery of working command-line binary | 35% ($26,250) |
| **M3** | GUI Client & Sandbox Validation | Successful security audit pass | 25% ($18,750) |
| **M4** | Final Acceptance & Knowledge Transfer | Code repository transfer & documentation | 15% ($11,250) |

## 5. Risk Management & Assumptions
- **Hardware Assumption:** Client engineering team has access to M2/M3 development hardware.
- **Regulatory Assumption:** Local macOS sandboxing satisfies internal compliance without custom enterprise certificates.

## 6. Formal Sign-Off & Approvals
> [!IMPORTANT] Sign-Off Approval
> By signing below, both parties acknowledge the scope, deliverables, payment triggers, and terms detailed in this Statement of Work.

- **For Delivery Team:** `[[Project Lead Name]]` — Date: [YYYY-MM-DD]
- **For Client Sponsor:** `[[Client Sponsor Name]]` — Date: [YYYY-MM-DD]

Filled Real-World Example

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

---
title: "SOW: Medical Audio Pipeline — Apex Health"
date: 2026-10-06
project_lead: "[[Devin Zhao]]"
client_sponsor: "[[Dr. Robert Sterling, CIO]]"
contract_reference: "SOW-2026-8911"
project_budget: "$95,000"
status: "Approved"
tags: [sow, medical, engineering]
---

# Statement of Work Project Charter — Medical Audio Pipeline

## 1. Overview
Devin Zhao finalized the SOW with Apex Health for an on-device clinical dictation pipeline.

## 2. Key Term
Strict boundary established: all audio processing must execute locally on clinic iMac hardware with zero internet egress, satisfying HIPAA compliance mandates.

When to Use and When to Avoid

When to Use

• Use when kicking off client consulting projects, technical contracting, or vendor engagements.
• Use internally between departments to establish clear SLA commitments for platform initiatives.
• Use to prevent scope creep by anchoring deliverables to signed acceptance criteria.

When to Avoid

• Avoid using for internal exploratory hackathons or lightweight bug-bash sprints.
• Avoid using when requirements are completely unknown (run a Discovery Sprint first).

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the contract negotiations and project scope notes:
1. Extract all in-scope deliverables and match each with measurable acceptance criteria.
2. Identify out-of-scope boundaries to prevent project creep.
3. Formulate a structured Markdown Statement of Work with milestone payment triggers.

Your data remains securely on your Mac with zero cloud exposure.