COMPEL Certification Body of Knowledge — Module 2.1: Engagement Design and Client Discovery
Article 5 of 10
The Statement of Work (SOW) is the contractual backbone of every COMPEL engagement. It translates the engagement architecture — the scope, phases, deliverables, timeline, and team structure designed through the process described in Module 2.1, Article 4: Engagement Scoping and Architecture — into a binding agreement between the practitioner and the client. A well-crafted SOW protects both parties, creates clarity about expectations, and establishes the foundation for a productive working relationship. A poorly crafted one becomes a source of conflict that consumes energy better spent on transformation work.
This article covers the essential elements of the COMPEL engagement SOW, the commercial structures available to the COMPEL Certified Specialist (EATP), and the professional judgment required to construct agreements that serve the engagement's objectives rather than undermining them.
The SOW as Strategic Document
Many practitioners treat the SOW as an administrative necessity — something to get through so the real work can begin. This is a mistake. The SOW is a strategic document that shapes the engagement's trajectory in ways that persist long after the ink dries.
The commitments made in the SOW determine what will be measured, what will be disputed, and what will be celebrated or blamed when the engagement concludes. Every clause, every deliverable definition, every timeline commitment creates a reference point against which the engagement's success will be judged — by the client, by the EATP, and potentially by client stakeholders who were not part of the negotiation.
The EATP should approach SOW development with the same rigor applied to engagement architecture. This means being precise where precision matters, deliberately flexible where flexibility is needed, and honest about what can and cannot be guaranteed.
Essential Elements of the COMPEL SOW
Engagement Context and Objectives
The SOW should open with a clear statement of why the engagement exists and what it aims to achieve. This section connects the SOW to the discovery process and establishes shared understanding of the engagement's purpose.
The objectives statement should be specific enough to be testable but not so narrow that it prevents the engagement from adapting to what it discovers. For a COMPEL assessment engagement, an appropriate objective might be: "Conduct a comprehensive Artificial Intelligence (AI) maturity assessment across all 18 COMPEL domains, produce a scored maturity profile with supporting evidence, identify critical gaps and interdependencies, and deliver a prioritized roadmap of recommendations."
Avoid objectives that promise outcomes the EATP cannot control. "Increase organizational AI maturity from Level 2 to Level 4" is a transformation outcome that depends on the client's execution over years — it is not an engagement deliverable. "Design a transformation roadmap targeting Level 4 maturity with sequenced initiatives, resource estimates, and success metrics" is a deliverable the engagement can produce and the EATP can be accountable for.
Scope of Work
The scope section defines what the engagement includes and excludes. It should address:
Organizational scope — which business units, functions, or geographic regions are covered. If the engagement covers a subset of the organization, the boundaries must be explicit. "Corporate headquarters and the North American business unit" is clear. "The organization" is not.
Methodological scope — which COMPEL stages the engagement will execute, which of the 18 domains will be assessed (and to what depth), and what level of rigor applies. A full assessment covers all 18 domains with deep evidence gathering. A focused assessment might cover all 18 at a screening level with deep assessment in eight priority domains. The SOW should specify which approach applies.
Exclusions — what the engagement will not cover. Explicit exclusions prevent scope disputes later. Common exclusions include technology implementation, vendor selection, hands-on model development, and regulatory compliance audits. If the client expects something that is not included, the exclusion forces that conversation during SOW development rather than during delivery.
Deliverables
Each deliverable must be defined with enough specificity that both parties can determine whether it has been completed and meets quality standards. The deliverable definition should include:
Name and description — what the deliverable is and what it contains. "Maturity Assessment Report" is a name. "A comprehensive document presenting scored maturity ratings across all 18 COMPEL domains with supporting evidence, gap analysis by pillar, cross-domain dependency mapping, and a prioritized list of recommendations" is a description.
Format and medium — how the deliverable will be presented. A written report, a presentation deck, a workshop session, and an interactive dashboard are all valid formats for assessment findings. The SOW should specify which format applies to each deliverable.
Acceptance criteria — the standards by which the deliverable will be judged as complete. This may include review periods, revision cycles, and the process for resolving disagreements about deliverable quality.
Timeline and Milestones
The timeline section translates the phase structure from the engagement architecture into calendar dates. It should specify:
Phase start and end dates for each phase of the engagement. These provide the macro-level schedule that the client uses for planning.
Key milestones within each phase — interim checkpoints where specific activities complete or deliverables are due. Milestones create accountability and visibility. They also provide early warning signals if the engagement is falling behind.
Dependencies and assumptions — conditions that must be met for the timeline to hold. Common dependencies include client data availability, stakeholder access for interviews, and timely review of draft deliverables. If a dependency is not met, the timeline impact should be clearly understood by both parties.
Team and Governance
The SOW should define the engagement team — at least at the role level — and the governance structure that will manage the engagement. Key elements include:
Practitioner team roles — the EATP as engagement lead, specialist assessors, analysts, and any other roles required. The SOW should specify the seniority and capability expectations for each role, even if specific individuals are not named.
Client team roles — the expected contribution from the client side. This includes the executive sponsor, the day-to-day client project manager, subject matter experts for interviews, and any client team members who will participate directly in engagement activities. Client team commitments are as important as practitioner commitments — and more frequently the source of engagement delays.
Governance structure — the steering committee composition, meeting cadence, decision-making authority, and escalation paths. Governance is addressed in detail in Module 2.1, Article 6: Stakeholder Alignment and Engagement Governance, but the SOW should establish its basic parameters.
Commercial Terms
The commercial structure of the SOW requires careful design. The EATP must select the pricing model that best balances risk, incentive alignment, and administrative simplicity for the specific engagement.
Commercial Structures
Fixed-Fee Engagements
In a fixed-fee model, the EATP quotes a defined price for a defined scope of work. The client knows exactly what they will pay. The EATP accepts the risk that the work may take longer or cost more than estimated.
Fixed-fee works well for assessment-only engagements where the scope is well-understood and the variables are manageable. It creates clarity for the client's budgeting process and incentivizes the EATP to work efficiently.
The primary risk is scope creep. If the engagement encounters unexpected complexity — a larger organizational footprint than anticipated, data access delays that extend the timeline, or stakeholder availability problems — the EATP absorbs the cost. The SOW must include a clear change management process that addresses how scope changes are identified, approved, and priced.
Time-and-Materials Engagements
In a time-and-materials model, the client pays for actual effort at agreed daily or hourly rates. This model transfers more risk to the client but provides maximum flexibility to adapt the engagement as circumstances evolve.
Time-and-materials works well for engagements with uncertain scope — advisory relationships, complex transformation programs where the path forward will be shaped by what the assessment reveals, or environments where the EATP expects significant client-side delays that will affect the engagement timeline.
The primary risk is client confidence. Without a fixed price, the client may become anxious about cost escalation. The SOW should include a budget estimate (not a cap, but a planning number), a mechanism for tracking and reporting actual effort against the estimate, and explicit triggers for re-estimation conversations.
Hybrid Models
Many COMPEL engagements benefit from a hybrid approach that applies fixed-fee pricing to well-defined phases and time-and-materials pricing to phases with greater uncertainty.
A common pattern is fixed-fee for the assessment phase (where the scope is predictable) and time-and-materials for the roadmap design and execution support phases (where the scope depends on assessment findings). This gives the client budget certainty for the initial commitment while preserving flexibility for subsequent phases.
Value-Based Pricing
In some engagements, the EATP may structure pricing around the value the engagement creates rather than the effort it consumes. Value-based pricing requires a clear articulation of the expected value — cost savings, revenue impact, risk reduction — and a pricing mechanism tied to achieving that value.
Value-based pricing is commercially attractive when it works but requires sophisticated measurement capabilities and high trust between the parties. It is typically viable only in engagements where the value metrics are quantifiable and attributable to the engagement's work. The measurement frameworks from Module 2.5: Measurement, Evaluation, and Value Realization are directly relevant here.
Risk Allocation in the SOW
Every SOW allocates risk between the parties, whether explicitly or implicitly. The EATP should approach risk allocation deliberately, ensuring that each risk sits with the party best positioned to manage it.
Scope risk — the risk that the work required exceeds what was anticipated — is managed through change control provisions. The SOW should define a change request process: how scope changes are identified, documented, assessed for impact, and approved by both parties before additional work proceeds.
Timeline risk — the risk that the engagement takes longer than planned — should be addressed through dependency clauses that adjust timelines when client-side dependencies are not met. If the client delays interview scheduling by two weeks, the engagement timeline should adjust by at least two weeks without penalty to the EATP.
Quality risk — the risk that deliverables do not meet expectations — is managed through acceptance criteria and review processes. The SOW should define a review period (typically five to ten business days), a revision cycle (typically one round of revisions included in the base fee), and a process for resolving disagreements.
Termination risk — the risk that one party needs to exit the engagement prematurely — should be addressed through termination provisions that define notice periods, payment for work completed, and obligations regarding work product and confidentiality.
Legal Considerations
While the EATP is not a lawyer, several legal dimensions of the SOW require attention.
Intellectual property — the SOW should specify ownership of engagement work products. The standard COMPEL engagement model provides that client-specific deliverables (assessment reports, roadmaps, recommendations) become client property upon delivery and payment. The COMPEL methodology itself, including assessment tools and frameworks, remains the property of the practitioner or the licensing entity.
Confidentiality — engagement work inevitably involves access to sensitive client information. The SOW should include confidentiality provisions or reference a separate Non-Disclosure Agreement (NDA).
Limitation of liability — most professional services agreements include a cap on the practitioner's liability, typically limited to the fees paid for the engagement. This protects the EATP from claims that vastly exceed the engagement's commercial value.
Data protection — if the engagement involves access to personal data, the SOW should address data protection obligations consistent with applicable regulations such as the General Data Protection Regulation (GDPR) or equivalent national frameworks.
The EATP should seek legal counsel for significant engagements and should never agree to contractual terms they do not understand. This is a professional responsibility, not a commercial preference.
From Proposal to Signature
The journey from scoping document to signed SOW typically involves several iterations. The EATP presents an initial proposal based on the engagement architecture, the client provides feedback, and the terms are refined through negotiation.
Negotiation is not adversarial — it is collaborative design. Both parties are working to create an agreement that supports successful delivery. The EATP should approach negotiation with transparency about what they can deliver, honesty about the risks involved, and flexibility about commercial structures. Rigidity on scope when flexibility on pricing would solve the problem — or vice versa — is a negotiation failure.
The proposal document that precedes the formal SOW serves a different purpose: it sells the engagement. The SOW codifies the agreement. The proposal should articulate the client's situation, the proposed approach, the expected value, and the EATP's qualifications. It should be compelling without being promotional, specific without being rigid, and confident without making promises the engagement cannot keep.
Looking Ahead
A signed SOW authorizes the work but does not ensure that the right people are aligned behind it. The next article, Module 2.1, Article 6: Stakeholder Alignment and Engagement Governance, addresses the critical step of establishing the governance structures and stakeholder relationships that will sustain the engagement through its inevitable challenges.
© FlowRidge.io — COMPEL AI Transformation Methodology. All rights reserved.