Next platform deadline: Amazon EKS Nov 26, 2026  

All 14 deadlines

Sample contract document · Delivery and governance

Sample statement of work outline

The sections, acceptance criteria and change control in a typical fixed-fee statement of work. Fees are stated in each real SOW, not here.

Sample / template. Fictional systems, names and dates that show the format and depth of what you receive. Not a client deliverable.

Engagement (fictional): PostgreSQL major-version upgrade, 3 waves · Customer: Example Co. · Under: Master Services Agreement dated [date] · A real SOW is typically 6–10 pages

1. Background and objectives

Example Co. runs six Amazon RDS for PostgreSQL databases, four on versions approaching the end of standard support. The objective is to upgrade all six to PostgreSQL 16 with no unplanned downtime and a tested rollback for every change.

2. Scope

In scope

  • Upgrade of the six databases listed in Appendix A, in three waves
  • Rehearsal of each wave in a production-like environment, with measured timings
  • Runbooks, rollback procedures and hand-over documentation

Out of scope

  • Application code changes, schema redesign and databases not listed in Appendix A
  • Support outside the agreed change windows

3. Deliverables and acceptance criteria

#DeliverableAcceptance criteria
D1Upgrade plan and risk registerReviewed and approved in writing by the customer's technical owner
D2Rehearsal report for each waveEach step completed in rehearsal; timings and rollback recorded
D3Production upgrade, waves 1 to 3Agreed data and smoke checks pass; no open severity-1 defects caused by the change
D4Runbooks and hand-over packStored in the customer's repository; hand-over session held and recorded

4. Customer responsibilities

  • Read-only access for discovery; scoped, time-bound change access for agreed windows
  • An application owner to run smoke tests in each window
  • Change approval through the customer's change process

5. Assumptions

  • Change windows are available as listed in the schedule
  • Extensions in use are supported on the target version, or replaced in a prior change

6. Schedule and milestones

MilestoneTarget
Kickoff and access in placeWeek 1
D1 approvedWeek 1
Wave 1 in productionWeek 2
Wave 2 in productionWeek 4
Wave 3 in production and hand-overWeek 6

7. Acceptance

The customer has five business days to accept each deliverable or list the specific criteria not met. We correct and resubmit at no additional charge. A deliverable is accepted when signed off in writing.

8. Fees and invoicing

A fixed fee, stated in the real SOW, invoiced by milestone on acceptance. The paid assessment fee is credited. No time-and-materials charges unless a change request says so.

9. Change control

Either party may request a change. We describe the impact on scope, schedule and fee in a written change request. Nothing outside this SOW is performed or invoiced until the change request is signed.

10. Personnel and governance

  • Named lead engineer; any replacement only with the customer's written approval
  • Weekly status report and call; RAID log reviewed weekly; escalation path as set out in the MSA
  • No subcontracting without the customer's written approval

11. Security, data and ownership

  • Work performed in the customer's environment under the customer's access controls; no production data copied to SRASH systems
  • All deliverables, code and documentation become the customer's property on payment
  • Access revoked and working material returned or deleted at the end, confirmed in writing

Appendix A

Inventory of in-scope databases (as in the assessment report).

Want to see how this would look for your project?

On the free 30-minute review a senior engineer will walk you through how we would plan, report and govern your work.