Skip to content

Master SOW (SKELETON — counsel review required)

NOT legal advice. Per-engagement schedule under the MSA. Mirrors the Y6 proposal structure so an accepted proposal converts cleanly to a SOW.

Sections

  1. Engagement — package (Y2): Quick-Win / Baseline / Advanced; client + scope (# subs/envs, AKS y/n, framework, deadline).
  2. Deliverables — the §4-asset list from the proposal (Y6 §3); roadmap items marked (delivered during engagement — Mx).
  3. Milestones & timeline — from the proposal §5; acceptance per milestone.
  4. Acceptance criteria — the proposal §7 checklist; how acceptance is signified + cure period.
  5. Fees — project fee + retainer; billing schedule (50/50 or milestone); retainer term.
  6. Client responsibilities — Azure sub + GitHub access, licensing (P1/P2), POC availability (proposal §8 assumptions).
  7. Out of scope — proposal §9.
  8. Change control — how scope changes are priced + authorized (ties to the Y2 §5 expansion re-pricing).
  9. Access — reference the cloud-access authorization.
  10. Term — engagement window; retainer auto-renew/notice per MSA.

One SOW per engagement; expansions (Y11 §5) are new SOWs or change orders. Acceptance criteria must be objective (a runbook passes, a loop is demonstrated) — not subjective.