Skip to main content
Adobe Commerce Expertise Atlas

Manual SOW planning tool

Adobe Commerce Expert-Team SOW Worksheet

Carry the workstream map, named roles, evidence limits, outputs, acceptance rules, delivery controls, continuity, and exit into one reviewable document.

By Nina Kavulia, Principal Analyst Published by B2B TechSelect Last updated

Instructions / 01

Use this after the role and case checks

Complete the expert role map first. Then use the case evidence checklist to separate public proof from proposal proof. Copy confirmed facts and open checks into this worksheet.

Write short sentences. Name an owner for every output, decision, and handoff. Replace broad words such as “support,” “quality,” or “secure” with the exact action, evidence, time, and acceptance owner.

This page is a planning aid, not legal advice or a complete contract. Buyer procurement, security, finance, and legal owners should adapt the final documents to the engagement and governing requirements.

Document record / 02

Name the document, parties, owners, and dates

  • Project: __________________________________________________________
  • Buyer legal entity: _______________________________________________
  • Provider legal entity: ____________________________________________
  • Buyer SOW owner: __________________________________________________
  • Provider SOW owner: _______________________________________________
  • Version and date: __________________________________________________
  • Planned start and end: _____________________________________________
  • Related agreement, policies, and schedules: _________________________
  • Order of precedence if documents conflict: __________________________

Outcome / 03

Define the starting point and accepted result

A public case result is context only. Set this project's baseline, target, method, dependencies, and acceptance owner separately.

Outcome and acceptance record
FieldAgreed wordingEvidence sourceOwner
Business outcome____________________________________
Measured baseline____________________________________
Target condition____________________________________
Measurement method and period____________________________________
Dependencies and exclusions____________________________________
Acceptance owner and deadline____________________________________

Estate / 04

Record what the team will enter and touch

  • Adobe Commerce edition, version, and deployment: ____________________
  • Storefront, themes, apps, extensions, and custom code: _______________
  • Markets, sites, stores, languages, currencies, and tax: ______________
  • ERP, PIM, OMS, CRM, search, payment, identity, and analytics: ________
  • System of record for each shared object: ____________________________
  • Repositories, hosting, environments, and current operators: _________
  • Known defects, debt, incidents, deadlines, and frozen periods: _______

Scope / 05

Give every workstream an output and owner

State what is included, what is excluded, who delivers it, and what proves acceptance. Add or remove workstreams to match the real brief.

Workstream scope and acceptance sheet
WorkstreamIncluded workExcluded workDeliverableAcceptance evidenceProvider roleBuyer owner
Business workflow and analysis________________________________________________________________________
Architecture and platform________________________________________________________________________
Commerce backend or B2B________________________________________________________________________
Storefront and performance________________________________________________________________________
Integration and data________________________________________________________________________
Quality and release________________________________________________________________________
Security and privacy________________________________________________________________________
Operations and continuity________________________________________________________________________

Named team / 06

Record the people who are actually proposed

Company cases, partner records, and staff totals do not fill this table.

Named-team commitment sheet
PersonRole and workstreamDecision or output ownedAllocationWorking overlapStart and endBackup
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________

For each role, also record who may approve a substitution, the notice period, the evidence required for a replacement, overlap time, and knowledge-transfer responsibility.

Decision rights / 07

Separate provider work from buyer duties

Do not hide a required buyer action inside an assumption. Name the person who decides and the time allowed.

Responsibility and decision sheet
Decision or inputProvider ownerBuyer ownerDue timeEvidenceEffect if late
Requirements and scope approval____________________________________________________________
Architecture decision____________________________________________________________
Access and test data____________________________________________________________
Acceptance and release approval____________________________________________________________
Incident and rollback decision____________________________________________________________
Handover and closure approval____________________________________________________________

Delivery controls / 08

Write how the work will be controlled

For each control, name the rule, evidence, owner, and exception path.

Repositories and ownership

Location: ______. Access owner: ______. Branch and review rule: ______. Final code owner: ______.

Environments and access

Environment list: ______. Provisioning owner: ______. Access review: ______. Removal deadline: ______.

Quality evidence

Test levels: ______. Regression scope: ______. Defect severity rule: ______. Approval owner: ______.

Release and rollback

Release authority: ______. Evidence pack: ______. Window: ______. Rollback trigger and owner: ______.

Change control

Request format: ______. Estimate owner: ______. Approval path: ______. Schedule and cost record: ______.

Risk and issue control

Log owner: ______. Review frequency: ______. Severity rule: ______. Escalation time: ______.

Incident response

Contact path: ______. Triage owner: ______. Update interval: ______. Closure evidence: ______.

Monitoring and support

Signals: ______. Alert owner: ______. Coverage window: ______. Runbook location: ______.

Security and privacy

Requirements: ______. Review owner: ______. Findings path: ______. Exception approval: ______.

Continuity / 09

Plan substitution, handover, support, and exit

The end state should be usable by the people who will operate it.

Continuity and exit record
FieldRequired detailOwnerAcceptance evidence
SubstitutionNotice, approval, replacement evidence, overlap, and cost treatment________________________
Knowledge transferTopics, audience, sessions, recordings or notes, and completion test________________________
DocumentationArchitecture, code, interfaces, tests, releases, monitoring, incidents, and known limits________________________
Support handoffCoverage, intake, priority rules, escalation, service records, and open defects________________________
Access removalAccounts, keys, devices, environments, customer data, and confirmation date________________________
Exit packCurrent code, build instructions, credentials handoff, inventories, decisions, risks, and contacts________________________

Evidence trace / 10

Link every important term to its proof and limit

Do not copy a public claim into the SOW without showing why it matters and what still needs confirmation.

Evidence-to-term trace sheet
SOW termSource or proposal recordEvidence classExact supportLimit or open checkOwner
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________

Coverage check / 11

Confirm all twelve field groups

  1. Parties, document references, owners, and dates.
  2. Business outcome, baseline, target, and exclusions.
  3. Adobe Commerce estate and system boundaries.
  4. Included and excluded work by workstream.
  5. Deliverables, acceptance evidence, and acceptance owner.
  6. Named roles, allocation, working overlap, and backup.
  7. Buyer and provider responsibilities and decision rights.
  8. Repositories, environments, QA, release, and rollback controls.
  9. Data, access, security, privacy, and evidence handling.
  10. Change, issue, incident, risk, and escalation paths.
  11. Substitution, knowledge transfer, support, continuity, and exit.
  12. Assumptions, dependencies, evidence trace, approvals, and open points.

Approval / 12

Close gaps before signature

  • □ No required workstream is left under a broad “as needed” phrase.
  • □ Every deliverable has acceptance evidence, an owner, and a review time.
  • □ Every required provider role has a named person or a dated resolution step.
  • □ Buyer inputs and decision deadlines are visible.
  • □ Access, data, security, QA, release, incident, and rollback controls have owners.
  • □ Changes show their effect on scope, time, acceptance, and agreed commercial terms.
  • □ Substitution, continuity, handover, support, and exit are written.
  • □ Public evidence is attributed and no case result is treated as a forecast.
  • □ Assumptions, dependencies, conflicts, and open points have owners and dates.
  • □ Required buyer approvals are recorded in the final document set.

Method reference: LATTICE-11 Expert Team Fit Method. Return to the expert-firm comparison only if a scope change creates a different provider route.

Last updated .