Statement of Work Completed Template

Standard Operating Procedure: Statement of Work Completed (SOWC) Generation

---

1. Document Control Block

• Document ID: TR-OPS-SOW-COMP-001
• Effective Date: 2023-10-27
• Version: 1.0
• Review Cadence: Annually

---

2. Executive Summary & Scope

This Standard Operating Procedure (SOP) outlines the standardized process for generating, internal review, client submission, and final archival of a Statement of Work Completed (SOWC) at Template Registry. The primary objective is to ensure accurate, timely, and compliant documentation of completed project deliverables, facilitating proper project closure, billing initiation, and transparent client communication.

Scope: This SOP applies to all project-based service engagements delivered by Template Registry where a formal Statement of Work (SOW) was executed. It covers the activities from the notification of final work completion by the delivery team to the formal acknowledgment of the SOWC by the client. This SOP explicitly excludes the initial SOW creation process, general project management reporting unrelated to final completion, or change order procedures.

---

3. Prerequisites & Required Tools

Prerequisites:

• An approved and executed initial Statement of Work (SOW) must be on file.
• Confirmation from the Project Manager (PM) and Delivery Lead (DL) that all defined deliverables, milestones, and acceptance criteria outlined in the original SOW have been met and verified.
• All project artifacts (e.g., final designs, code, documentation) must be delivered and internally validated.
• Client communication logs demonstrating active engagement and informal acceptance of final deliverables.
• Access permissions to relevant project and financial systems.

Required Tools & Resources:

• SOW Completed Template: TR-TEM-SOW-COMP-001 (Template Registry Document Management System - DMS)
• Document Management System (DMS): For retrieving templates, storing drafts, and archiving final SOWCs. (e.g., SharePoint, Confluence)
• Project Management Software (PMS): For project status verification and deliverable tracking. (e.g., Jira, Asana)
• Customer Relationship Management (CRM): For client contact information and communication history. (e.g., Salesforce)
• Email Client: For formal communication and submission to clients. (e.g., Outlook, Gmail)
• Digital Signature Software: (Optional, if required by SOW or client agreement) For formal client acknowledgment. (e.g., DocuSign, Adobe Sign)
• Billing System: For triggering invoice generation post-acknowledgment. (e.g., QuickBooks, NetSuite)

---

4. Roles & Responsibilities (RACI Matrix)

---

5. Step-by-Step Procedure

Phase 1: Initiate SOWC Generation

• Step 1.1: Project Completion Confirmation. The Delivery Lead (DL) formally notifies the Project Manager (PM) via PMS (e.g., Jira ticket resolution, task completion) that all SOW deliverables are completed and validated.
• Step 1.2: Initial Review. The PM reviews project logs in PMS to confirm all acceptance criteria are met and any outstanding issues are resolved or formally deferred.
• Step 1.3: SOW Retrieval. The PM retrieves the original, executed SOW from the DMS.

Phase 2: Draft SOWC

• Step 2.1: Template Selection. The PM accesses the latest version of the "TR-TEM-SOW-COMP-001" SOW Completed Template from the DMS.
• Step 2.2: SOWC Population. The PM populates the template with the following details:
  • Project Name, ID, Client Name, and original SOW Reference Number.
  • Start and End Dates of the project.
  • A comprehensive list of all completed deliverables as defined in the original SOW, detailing their fulfillment status.
  • Any agreed-upon variations or change orders that modified the scope, explicitly referencing their approval.
  • Final project cost (if applicable and explicitly required by SOW for completion statement).
  • Instructions for client acknowledgment and designated contact for queries.
• Step 2.3: Initial Draft Saving. The PM saves the draft SOWC in the DMS using the naming convention: SOWC_[ProjectID]_[ClientName]_[YYYYMMDD]_DRAFT.pdf.

Phase 3: Internal Review & Approval

• Step 3.1: Delivery Lead Review. The PM submits the draft SOWC to the DL for technical verification. The DL confirms that all listed deliverables accurately reflect the completed work and meet the technical requirements.
• Step 3.2: Client Relationship Manager Review. The PM submits the draft SOWC to the CRM for review of client-facing language, alignment with client expectations, and any historical communication context.
• Step 3.3: Internal Sign-off. Upon receiving confirmation from the DL and CRM, the PM formally signs off on the SOWC internally (via digital workflow or documented email approval).
• Step 3.4: Final Draft Saving. The PM saves the internally approved SOWC in the DMS using the naming convention: SOWC_[ProjectID]_[ClientName]_[YYYYMMDD]_FINAL.pdf.

Phase 4: Client Submission & Acknowledgment

• Step 4.1: Client Communication. The PM (or CRM, if agreed upon) formally sends the final SOWC to the client via email.
  • The email subject line must clearly state: "Statement of Work Completed: [Project Name] - [Project ID]".
  • The email body should briefly summarize the attached SOWC and request formal acknowledgment within the timeframe specified in the original SOW (typically 5-10 business days).
  • Attach the SOWC_[ProjectID]_[ClientName]_[YYYYMMDD]_FINAL.pdf document.
• Step 4.2: Acknowledgment Tracking. The PM logs the submission date and expected acknowledgment date in the PMS and/or CRM.
• Step 4.3: Follow-up. If no acknowledgment is received within 75% of the specified timeframe, the PM or CRM issues a polite follow-up reminder. A second follow-up is issued if no response is received by the deadline.
• Step 4.4: Client Acknowledgment. Upon client acknowledgment (e.g., signed document, explicit email confirmation), the PM records the date and method of acknowledgment.
  • If formal digital signature is required, the SOWC is routed through the designated digital signature software.
  • If the client disputes the SOWC, refer to Troubleshooting FAQ: Scenario 1.

Phase 5: Final Archiving & Billing Trigger

• Step 5.1: Final Document Archiving. The PM archives the fully acknowledged SOWC (including any digital signature certificates or email threads confirming acknowledgment) in the DMS under the project's designated folder, using the naming convention: SOWC_[ProjectID]_[ClientName]_[YYYYMMDD]_ACKNOWLEDGED.pdf.
• Step 5.2: Billing Trigger. The PM notifies the Finance Department via the designated billing system (or email for manual systems) that the SOWC has been acknowledged, triggering the invoice generation process. Provide the SOWC_[ProjectID]_[ClientName]_[YYYYMMDD]_ACKNOWLEDGED.pdf as a reference.
• Step 5.3: Project Status Update. The PM updates the project status in the PMS and CRM to "Closed" or "Completed - Billing Pending."

---

6. Quality Assurance & Verification

Key Metric Thresholds:

• SOWC Submission Latency: SOWC submitted to client within 2 business days of internal project completion confirmation. (Target: <= 2 days)
• Client Acknowledgment Rate: Percentage of SOWCs formally acknowledged by clients. (Target: >= 95%)
• SOWC Discrepancy Rate: Number of SOWCs requiring amendment post-submission due to errors or omissions. (Target: < 1%)
• Billing Cycle Start Accuracy: Percentage of invoices triggered within 1 business day of SOWC acknowledgment. (Target: >= 98%)

Common Pitfalls:

• Incomplete Deliverable Description: SOWC does not precisely detail each completed deliverable as per the original SOW.
• Mismatch with Original SOW: Discrepancies between the SOWC and the executed SOW regarding scope or agreed terms.
• Delayed Internal Reviews: Bottlenecks in DL or CRM review causing delays in client submission.
• Lack of Clear Client Acknowledgment: Ambiguous or absent formal client acceptance, hindering billing and closure.
• Failure to Track Follow-ups: Inconsistent follow-up on unacknowledged SOWCs.

Audit Checklist:

• Is every SOWC linked to an approved, executed SOW with a unique reference ID?
• Does the SOWC accurately reflect all completed deliverables and milestones, including any approved change orders?
• Is there documented evidence of internal (DL, CRM) review and approval for each SOWC prior to client submission?
• Is there documented formal client acknowledgment (e.g., signed SOWC, explicit email) for each issued SOWC?
• Is the final, acknowledged SOWC archived in the DMS according to the defined naming conventions?
• Was the SOWC submitted to the client within the defined service level agreement (SLA) (e.g., 2 business days)?
• Was the Finance Department notified for billing within 1 business day of client acknowledgment?

---

7. Troubleshooting FAQ

Scenario 1: Client disputes the accuracy or completeness of the SOWC.

• Problem: The client claims certain deliverables are incomplete, incorrectly described, or not aligned with their expectations, despite internal validation.
• Solution: The Project Manager (PM) will immediately schedule a tripartite review meeting involving the Delivery Lead (DL), Client Relationship Manager (CRM), and the client. The PM will cross-reference the original SOW, all project logs (PMS), communication history (CRM, email), and relevant project artifacts. If validated discrepancies are identified, the SOWC will be amended, re-reviewed internally, and re-submitted to the client for acknowledgment, documenting all revisions. If no discrepancy is found, clear evidence will be presented to the client to re-validate completion.

Scenario 2: Client delays SOWC acknowledgment beyond the specified timeframe.

• Problem: The client has not formally acknowledged the SOWC within the agreed-upon review period, despite initial submission and one follow-up.
• Solution: The Client Relationship Manager (CRM) will initiate a proactive phone call or priority email within 2 business days of the final follow-up deadline passing. The CRM will offer a brief call to walk through the SOWC to address any potential questions or concerns. If no response is received after this direct engagement, the CRM, in consultation with the PM, will elevate the matter to the client's executive sponsor (if applicable) or internal management for strategic intervention.

Scenario 3: The SOWC template (TR-TEM-SOW-COMP-001) is found to be missing critical fields or requires updates.

• Problem: During the drafting phase, the PM discovers the current SOWC template lacks necessary fields or contains outdated information for a specific project type or compliance requirement.
• Solution: Immediately report the identified template deficiency to the Chief Operations Architect (Julian Vance) via the designated Template Registry feedback channel (e.g., internal ticketing system). For the immediate SOWC generation, the PM will proceed with the current template, document the missing information in a clearly labeled addendum, and attach it to the SOWC submission, explicitly noting the addendum's purpose in the client communication. This ensures the current project proceeds while template updates are planned.