Lesson 9 · SOW, Legal Redlines, and Delivery Handoff
SOW, Legal Redlines, and Delivery Handoff
- Length
- 22 minutes across 7 sections
- You will be able to apply
- The Scope Boundary Test · The Handoff Evidence Pack
- You will produce
- Commit Statement
- You will work
- 4 gated questions
What must be true about the scope, the legal boundary, and the delivery context before the client signs, so that the signature creates momentum rather than ambiguity?
Core question
A signed statement of work is not the end of selling: it is the beginning of delivery. The commercial close succeeds only when the scope is bounded, the legal terms are reviewed, and the delivery team receives enough context to begin work on day one without re-discovering what the seller already learned. You treat the signature as a governed handoff, not a finish line.
The discipline is precision under time pressure. Buyers want speed. Sellers want credit. Delivery wants clarity. Those three forces are compatible only when the scope boundary, the legal review, and the handoff pack are completed before the signature, not promised for afterward.
The pathology: Signature Sprint
The counter is governed completeness. You slow the last five days of the deal by exactly the amount required to confirm scope boundaries, complete legal review, and assemble the handoff evidence pack. At OmniCorp Advisory, Selma Whitfield requires every engagement above the Bronze tier to pass both the Scope Boundary Test and the Handoff Evidence Pack before the document is sent for signature. Beatriz Ferraz, commercial counsel, will not release a document that has not passed legal review. Nkechi Obi, delivery director, will not accept a handoff that lacks confirmed outcomes and named client owners.
Scope questions deferred into delivery; change orders, delayed timelines, and eroded trust.
- Signature Sprint
- Scope questions deferred into delivery; change orders, delayed timelines, and eroded trust.
- Governed completeness
- Boundaries confirmed, legal reviewed, handoff pack accepted; delivery begins with context on day one.
The Scope Boundary Test
Definition
The Scope Boundary Test is the method for confirming what is inside the engagement, what is outside, what is assumed, and what triggers a change order before the statement of work is sent for signature. It forces the seller to answer four questions in writing: what we will deliver, what we will not deliver, what conditions must hold for the scope to remain valid, and what event creates a formal scope change. If any answer is missing, the test fails and the document is not ready.
The test is deliberately simple. Complexity in scope language hides ambiguity. The discipline is to write each boundary in one sentence a delivery lead can read without interpretation. Camille Okafor, senior account executive at OmniCorp Advisory, runs the test on every engagement by writing scope boundaries before selecting the SOW tier, not after.
When to Use It
Use the test after discovery is complete and before selecting the engagement tier. Run it when the buyer has confirmed the outcome, timeline, and success measure but before commercial terms are drafted. Use it again when a buyer requests scope additions during negotiation to determine whether the addition fits the current tier or triggers a change order.
Do not skip the test because the deal is small. Bronze-tier engagements carry scope risk proportional to their margin: a single unbounded deliverable can consume the entire engagement budget in rework. Do not defer the test because the buyer is in a hurry. A buyer who cannot confirm boundaries before signing cannot confirm them after signing.
How to Apply It
- Write what is in scope using deliverable nouns, not activity verbs. Name the output, not the effort.
- Write what is out of scope by naming the adjacent work the buyer might assume is included.
- Write the assumptions: data availability, client resource commitment, environment access, and timeline dependencies.
- Write the change-order triggers: additional integrations, expanded user populations, new regulatory requirements, or timeline extensions beyond the agreed window.
- Confirm each boundary with the buyer contact who owns the outcome before the document enters legal review.
The rule is direct: if you cannot write it in one sentence, you have not decided it. A scope boundary that requires a paragraph to explain is a scope boundary that has not been set.
Named deliverables the engagement will produce, written as output nouns.
- In scope
- Named deliverables the engagement will produce, written as output nouns.
- Out of scope
- Adjacent work the buyer might assume is included, named explicitly.
- Assumptions
- Data availability, client resources, environment access, and timeline dependencies.
- Change-order triggers
- Events that create a formal scope change with new commercial terms.
Worked example 1 of 3
Camille Okafor prepared an engagement for OmniCorp Financial. Adaeze Okonjo, chief risk officer, confirmed the outcome: a governed model-risk review framework for consumer lending AI. Martin Hollis, head of consumer lending, wanted integration with two existing lending platforms. Camille ran the Scope Boundary Test before selecting the tier.
| Boundary | Statement |
|---|---|
| In scope | Deliver a model-risk review framework covering three consumer lending models, with documentation, review cadence, and escalation criteria. |
| Out of scope | Platform integration engineering, data migration, and ongoing model monitoring beyond the agreed review cadence design. |
| Assumptions | OmniCorp Financial provides model documentation for all three models within two weeks of kickoff; Bea Karlsson, model risk lead, is available for four hours per week during the engagement. |
| Change-order triggers | Additional models beyond three, integration engineering requests, or timeline extension beyond twelve weeks. |
Martin initially asked for five models. Camille showed that five models moved the engagement from Silver to Gold tier. Martin confirmed three models were sufficient for the first phase. The boundary decision happened before the document was drafted, not during delivery.
Why This Works
The test works because scope disputes are cheaper to resolve before a signature than after one. Before the signature, a boundary question is a commercial conversation between adults. After the signature, the same question becomes a contractual dispute that consumes legal hours, delays delivery, and erodes the relationship. Camille prevented a scope dispute worth approximately 120 delivery hours by spending 45 minutes on the boundary test.
It also protects the seller. A clean scope boundary gives you the authority to say no to post-signature additions without damaging the client relationship. The boundary was agreed. The addition is new work. The change-order process exists for this reason.
Worked example 2 of 3Optional depth
OmniCorp Health engaged OmniCorp Advisory for clinical AI governance design. Dr. Ilona Reyes, chief medical information officer, confirmed the outcome: a governance framework for three clinical decision-support tools. Colm Byrne, head of clinical operations, assumed that nurse training materials were included. Owen Brackley, principal sales engineer, caught the assumption during the boundary test. Training material development was out of scope. Nadia Haddad, clinical safety officer, confirmed that safety review criteria were in scope. The boundary test prevented a 90-hour training deliverable from entering the engagement without commercial agreement.
Worked example 3 of 3Optional depth
OmniCorp Retail requested an AI ethics review for its recommendation engine. Ingrid Solheim, chief digital officer, wanted the review to cover personalisation, pricing, and inventory allocation. Dev Raghunathan, account executive at OmniCorp Advisory, ran the test and discovered that inventory allocation depended on a logistics integration owned by OmniCorp Logistics. Yusuf Demir, vice president of network operations at OmniCorp Logistics, had not been consulted. Dev placed inventory allocation outside the engagement boundary and added a change-order trigger for cross-entity scope. The deal closed on time with two workstreams instead of three.
Edge Cases and NuancesOptional depth
Some buyers resist written boundaries because they want flexibility. Flexibility without a boundary is not flexibility: it is unlimited scope funded by a fixed fee. You name the flexibility mechanism explicitly. The change-order process is the flexibility mechanism. It allows new work to be added with agreed commercial terms. Refusing to name boundaries is not the same as being easy to work with.
When a buyer says everything is in scope, stop and reframe. Ask which deliverable they would remove if the timeline were cut by four weeks. The answer reveals priority. Priority reveals boundary. A boundary revealed under constraint is more honest than a boundary negotiated under comfort.
Knowledge check
A seller selects a lower tier to protect margin even though the scope clearly exceeds the tier boundary. What will happen during delivery?
The Handoff Evidence Pack
Definition
The Handoff Evidence Pack is the defined set of information that delivery must receive on day one of an engagement: the confirmed outcome, the success measure, named client owners, constraints, risks, and every commitment made during the sale. It exists so that delivery begins with context, not with re-discovery. A complete pack means the delivery lead can run the kickoff meeting without asking the seller to repeat anything that was already agreed.
The pack is not a CRM note. It is a structured transfer of accountability. Nkechi Obi, delivery director at OmniCorp Advisory, rejects any handoff that lacks a named client owner, a success measure, or a list of commitments made during the sales process. If the seller promised a timeline, a resource, or an approach, it belongs in the pack.
When to Use It
Assemble the pack during the final week of the sales cycle, before the signature is obtained. Do not wait until after the close. The pack should be complete by the time the document is signed so that the handoff meeting can occur within 48 hours of signature. Delivery readiness is a pre-close activity, not a post-close scramble.
Use the pack for every engagement regardless of tier. Bronze engagements need less content but the same structure. The discipline is consistent: if you cannot assemble the pack, you have not finished selling. You have finished negotiating and left selling incomplete.
How to Apply It
- Name the confirmed outcome in one sentence using the buyer's language from discovery.
- State the success measure: what number, event, or condition will confirm the outcome was achieved.
- List named client owners with their roles and availability commitments.
- Document constraints: timeline, budget, resource limits, regulatory requirements, and technology dependencies.
- Record every commitment made during the sale: promised deliverables, dates, approaches, or resources that delivery must honour.
The pack transfers accountability. Once delivery accepts it, the seller is released from operational ownership. If the pack is incomplete, the seller remains accountable for the gap. That incentive keeps the pack honest.
Every promise made during the sale that delivery must honour.
- Commitments made
- Every promise made during the sale that delivery must honour.
- Constraints
- Timeline, budget, resource limits, regulatory, and technology dependencies.
- Named client owners
- Roles, availability commitments, and contact details.
- Success measure
- The number, event, or condition that confirms outcome achievement.
- Confirmed outcome
- One sentence in the buyer's language from discovery.
Worked example 1 of 3
Camille Okafor assembled the handoff pack for the OmniCorp Financial engagement. Nkechi Obi reviewed it before accepting delivery responsibility.
| Pack element | Content |
|---|---|
| Confirmed outcome | Governed model-risk review framework for three consumer lending models at OmniCorp Financial. |
| Success measure | Framework accepted by Adaeze Okonjo and Bea Karlsson within twelve weeks, covering review cadence, escalation criteria, and documentation standards. |
| Client owners | Adaeze Okonjo, chief risk officer, owns the outcome. Bea Karlsson, model risk lead, owns technical review. Martin Hollis, head of consumer lending, owns adoption. |
| Constraints | Twelve-week timeline. Bea Karlsson available four hours per week. No access to production model environments until week three. |
| Commitments made | Camille confirmed that the framework would include a regulatory mapping section. Owen Brackley committed to a technical architecture session in week one. |
- Nkechi Obi
- I see three named client owners and availability confirmed. The commitment log shows one regulatory mapping promise and one architecture session. I can run kickoff with this.
- Camille Okafor
- Adaeze confirmed availability yesterday. Bea starts on day three because of a board preparation conflict in week one.
- Nkechi Obi
- Good. I will adjust the schedule and confirm with Adaeze directly. The handoff is accepted.
Why This Works
The pack works because delivery re-discovery is the most expensive form of waste in professional services. Every hour a delivery lead spends asking what was agreed during the sale is an hour that could have been spent on client work. At OmniCorp Advisory, Nkechi Obi measured that incomplete handoffs added an average of 22 hours of rework per engagement in the prior quarter. The pack eliminated that cost by moving context transfer before the signature.
It also protects the client relationship. A delivery team that asks the client to re-explain the outcome signals that the organisation does not communicate internally. The client concludes that the seller made promises the organisation cannot track. Trust erodes before work begins.
Worked example 2 of 3Optional depth
OmniCorp Public engaged OmniCorp Advisory for a digital services AI governance review. Nadia Farouk, director of digital services, owned the outcome. Theo Lindqvist, records and privacy officer, held stop rights on data handling. Grace Mutiso, service owner, owned citizen-facing workflow adoption. Dev Raghunathan assembled the handoff pack. Nkechi Obi flagged a gap: Dev had not recorded a commitment he made about including a privacy impact assessment template. Dev added it. The pack was complete and the handoff meeting occurred within 36 hours of signature.
Worked example 3 of 3Optional depth
OmniCorp Logistics needed an AI safety review for its dispatch optimisation system. Yusuf Demir, vice president of network operations, owned the outcome. Claire Beaumont, head of dispatch systems, owned the technical review. Anders Nilsen, platform engineering lead, managed environment access. Owen Brackley committed during the sale to a platform compatibility assessment in week two. The pack recorded that commitment. When delivery began, Nkechi Obi scheduled the assessment for week two without needing to ask Owen what he had promised. The engagement started on time.
Edge Cases and NuancesOptional depth
Some sellers resist the pack because they believe delivery should discover context independently. That belief confuses delivery independence with delivery ignorance. Independence means the delivery team makes its own tactical decisions. Ignorance means the delivery team lacks the context to make any decision at all. The pack provides context. It does not constrain method.
When a commitment was made verbally but not recorded, add it to the pack honestly. A verbal commitment is still a commitment. If you cannot remember what you promised, that is not a reason to omit it. It is evidence that the pack should have been assembled earlier.
Knowledge check
A seller sends the delivery director a one-paragraph email saying the deal closed and kickoff is next week. No outcome, owners, constraints, or commitments are included. Which failure mode is this?
Decision point
Camille Okafor has a signature date of Friday. Martin Hollis at OmniCorp Financial has asked for two additional models to be added to the engagement. Adding them changes the tier and requires legal review. The quarter closes on Friday. What is the governed move?
Decision point
Dev Raghunathan is assembling the handoff pack for OmniCorp Public. He cannot remember whether he promised Nadia Farouk a privacy impact assessment or only discussed it as a possibility. The signature is tomorrow. What should he do?
Common Failure Modes in SOW and Handoff
Worked scenario: OmniCorp Financial engagement from boundary to handoff
Camille Okafor received confirmation from Adaeze Okonjo that OmniCorp Financial wanted to proceed with a governed model-risk review framework. The buying signal was clear. The quarter-end was twelve days away. Camille began with the Scope Boundary Test rather than the SOW template.
She wrote the four boundaries. In scope: model-risk review framework for three consumer lending models, including documentation, review cadence, and escalation criteria. Out of scope: platform integration, data migration, ongoing monitoring operations. Assumptions: model documentation available within two weeks of kickoff, Bea Karlsson available four hours per week. Change-order triggers: additional models, integration engineering, timeline extension beyond twelve weeks.
Martin Hollis asked for five models. Camille showed that five models moved the engagement from Silver to Gold tier with different commercial terms. Martin confirmed three models were sufficient for phase one and agreed to discuss the remaining two as a follow-on engagement. The boundary decision took 30 minutes and prevented a scope dispute worth approximately 120 delivery hours.
With boundaries confirmed, Camille selected the Silver tier. She engaged Beatriz Ferraz for legal review eight days before the target signature date. Beatriz identified two redline categories in the buyer's proposed changes: liability caps and intellectual property ownership. Both fell within standard negotiation authority. Beatriz resolved them within three business days. The document was ready for signature with two days to spare.
Camille assembled the Handoff Evidence Pack on day nine. Confirmed outcome: governed model-risk review framework for three models. Success measure: acceptance by Adaeze Okonjo and Bea Karlsson within twelve weeks. Client owners: Adaeze for outcome, Bea for technical review, Martin for adoption. Constraints: twelve-week timeline, limited Bea availability, no production access until week three. Commitments: regulatory mapping section confirmed, architecture session in week one committed by Owen Brackley.
Nkechi Obi reviewed the pack on day ten, accepted the handoff, and scheduled the kickoff meeting for the Monday after signature. The client signed on day eleven. Kickoff occurred 72 hours later. No re-discovery was needed. Delivery began with context, not questions. The engagement completed on time, within budget, and the follow-on conversation for two additional models began in week ten.
Mark the level that describes you today. Nothing is submitted.
| Behaviour | Ready | Developing | Not yet |
|---|---|---|---|
| Running the Scope Boundary Test before tier selection | |||
| Completing the Handoff Evidence Pack before signature | |||
| Coordinating legal review within the close timeline |
Commit
Commit Statement
Complete the lines before your next commercial close. Use the deal you are most tempted to rush past the Scope Boundary Test. Sign it and share it with your manager as your operating commitment.
| Window | Field application |
|---|---|
| Days 1 to 7 | Select one active deal approaching close. Run the Scope Boundary Test and write all four boundaries in one sentence each. |
| Days 8 to 14 | Assemble a Handoff Evidence Pack for the same deal. Confirm outcome, success measure, client owners, constraints, and all commitments made during the sale. |
| Days 15 to 21 | Review the legal engagement timeline for your next close. Confirm that counsel is engaged at least two weeks before the target signature date. |
| Days 22 to 30 | Hold a handoff meeting with delivery using the completed pack. Confirm acceptance and schedule the client kickoff within 48 hours of signature. |