How We Engage: MSA, SOW & Workflows
A clear, structured engagement model from first agreement to accepted delivery.
Last updated: May 25, 2026
PMOstart engagements run on a simple, transparent structure: a Master Services Agreement sets the overall terms once, and each piece of work runs under its own Statement of Work. The workflows below show how an engagement moves from agreement to accepted delivery.
Master Services Agreement (MSA) overview
The MSA is the umbrella agreement signed once at the start of a relationship. It covers the standing terms that rarely change: confidentiality, intellectual property, payment terms, liability, and how disputes are handled. With the MSA in place, new work can start quickly without renegotiating core terms each time.
This page provides an overview only. The full MSA is provided as a separate document for review and signature.
Statement of Work (SOW) template
Each project runs under a Statement of Work that references the MSA. The SOW is where the specifics live: scope, deliverables, timeline, milestones, fees, assumptions, client responsibilities, acceptance criteria, and change control. A SOW template placeholder is available on request and is finalized per engagement.
- Scope and out-of-scope items
- Deliverables and milestones
- Timeline and dependencies
- Fees and payment schedule
- Assumptions and client responsibilities
- Acceptance criteria and change control
MSA to SOW Engagement Workflow
- 1 Discovery callConfirm goals, scope, constraints, and fit. Booked via Calendly, phone, or the intake form.
- 2 MSA executedSign the Master Services Agreement once to establish standing terms. Decision point: Are core terms acceptable to both parties?
- 3 SOW draftedPMOstart drafts a Statement of Work with scope, deliverables, timeline, and fees.
- 4 SOW reviewed and signedClient reviews, requests adjustments, and approves. Decision point: Is scope, timeline, and fee approved?
- 5 Kickoff scheduledEngagement begins with a structured kickoff and delivery norms.
Change Request Workflow
- 1 Change loggedThe requested change is captured with its driver and expected impact.
- 2 Impact assessedPMOstart assesses impact on scope, schedule, cost, and risk. Decision point: Does the change materially affect scope, timeline, or fee?
- 3 Change order issuedA written change order documents the agreed adjustment to the SOW.
- 4 Approval and updateBoth parties approve; the plan and SOW are updated. Decision point: Is the change order approved by the client?
Service Acceptance Workflow
- 1 Deliverable submittedPMOstart submits the deliverable against the SOW acceptance criteria.
- 2 Client reviewClient reviews within the agreed review window. Decision point: Does the deliverable meet the acceptance criteria?
- 3 Feedback or acceptanceIf changes are needed, feedback is logged and addressed; otherwise the deliverable is accepted.
- 4 Formal acceptanceClient confirms acceptance in writing and the milestone closes.