Saved SOWs0
Draft0
Approved0
Contract valueR0
Open milestones0
Recommended flow: Parties & commercial context → objectives → in/out of scope → deliverables & milestones → responsibilities → pricing → acceptance & change control → preview → save/export.
Document identity
Core commercial and governance metadata.
Parties
Purpose & objectives
Scope
Explicit boundaries reduce scope creep.
Deliverables
Outputs that the client can inspect and accept.
Milestones
Dates, dependencies and payment triggers.
Responsibilities
RACI-style ownership without unnecessary complexity.
Assumptions, dependencies & exclusions
Commercials
Pricing schedule, taxes and expenses.
Governance & control
Sign-off
Document preview
Updates live as you type. Print uses this contract-style layout.
SOW Register
Saved locally in this browser.
| SOW # | Title | Client | Status | Value | Dates | Actions |
|---|
Saved templates
Use templates for recurring service types such as migrations, managed services, training, deployments and consulting engagements.
Template guidance
A good SOW template should define structure, default clauses and recurring deliverables, but should not pre-approve client-specific scope, dates, pricing or acceptance criteria.
- Keep measurable deliverables.
- State exclusions clearly.
- Identify client prerequisites.
- Link milestones to acceptance and invoicing.
- Use formal change control for scope changes.
Backup & restore
Back up the full Easy SOW workspace.
Privacy model
- Core SOW data is stored in your browser using LocalStorage.
- No client contract data is uploaded by this static module.
- Printing / PDF uses the browser print engine.
- JSON and CSV exports are generated locally.