Statement of Work Accomplished Sample Philippines

Standard Operating Procedure: Generation of Statement of Work Accomplished (SOWA)

Document Control Block

• Document ID: TR-OPS-SOWA-PH-001
• Effective Date: 2023-10-27
• Version: 1.0
• Review Cadence: Annually (last review: 2023-10-27)

---

Executive Summary & Scope

This Standard Operating Procedure (SOP) outlines the standardized process for generating a Statement of Work Accomplished (SOWA) document at Template Registry, specifically tailored to accommodate common business practices and regulatory considerations within the Philippines. The SOWA serves as a formal record detailing completed project deliverables, tasks, and effort expended over a defined period or upon milestone completion, aligning with the original Statement of Work (SOW). This document is critical for client billing, project progress reporting, and final project closure.

Scope: This SOP applies to all project managers, team leads, and project teams responsible for delivering client projects or internal initiatives with defined SOWs within Template Registry's Philippine operations. It covers the end-to-end process from data gathering to client submission and archiving.

Out of Scope: This SOP does not cover the creation of the initial Statement of Work (SOW), contract negotiation, or specific financial accounting procedures beyond verifying accomplished work for billing purposes.

---

Prerequisites & Required Tools

Prerequisites:

• Approved and signed Statement of Work (SOW) or equivalent project contract.
• Clearly defined project plan, milestones, and deliverables.
• Access to project management software records (tasks, statuses, assigned resources).
• Access to time tracking system logs (accurate and complete).
• Client communication records and deliverable acceptance acknowledgments.
• Template Registry's standard SOWA template (current version).

Required Tools & Systems:

• Project Management System (PMS): Jira, Asana, Trello, or equivalent (for task tracking, progress updates).
• Time Tracking System (TTS): Harvest, Clockify, Zoho Projects, or equivalent (for detailed effort logging).
• Document Management System (DMS): SharePoint, Google Drive, Confluence, or equivalent (for SOW, project plans, and SOWA storage).
• Office Productivity Suite: Microsoft Word/Google Docs (for SOWA generation and editing).
• Communication Platform: Email, Microsoft Teams, Slack (for internal coordination and client communication).

Compliance Standards:

• Republic Act No. 10173 (Data Privacy Act of 2012): Ensure all client and project data handled and included in the SOWA complies with privacy regulations, particularly concerning personal or sensitive information.
• General Accepted Accounting Principles (GAAP) in the Philippines: While not directly an accounting procedure, the SOWA provides factual basis for invoicing and revenue recognition, requiring accuracy and verifiable data.
• Template Registry's Internal Information Security Policies: Adherence to data handling, storage, and access protocols.

---

Roles & Responsibilities (RACI Matrix)

• R - Responsible: Performs the task.
• A - Accountable: Ultimately answerable for the correct and thorough completion of the deliverable or task. Ensures prerequisites are met.
• C - Consulted: Provides input and expertise.
• I - Informed: Kept up-to-date on progress.

---

Step-by-Step Procedure

Phase 1: Preparation & Data Gathering

• • 1.1 Retrieve Official SOW/Contract: Access the approved SOW/contract from the DMS to understand the agreed scope, deliverables, milestones, and reporting requirements for the period/milestone under review.
• • 1.2 Identify Reporting Period/Milestone: Confirm the specific dates or project phase for which the SOWA is being generated.
• • 1.3 Gather Project Management Records:
  • • 1.3.1 Extract all completed tasks and sub-tasks from the PMS, noting their status, completion dates, and associated resources.
  • • 1.3.2 Consolidate documentation of achieved milestones, deliverable acceptance forms, and relevant project communications.
• • 1.4 Collect Time Tracking Logs:
  • • 1.4.1 Extract detailed time logs from the TTS for all team members for the specified reporting period/milestone.
  • • 1.4.2 Verify time entries against PMS tasks for consistency and accuracy. Resolve discrepancies with team members.
• • 1.5 Compile Deliverable Evidence: Gather links, screenshots, or copies of completed deliverables and artifacts for easy reference during review.
• • 1.6 Document Deviations/Change Requests: Identify any approved change requests, scope deviations, or issues encountered during the period, along with their resolutions.

Phase 2: Draft Generation

• • 2.1 Obtain SOWA Template: Download the latest approved SOWA template from the DMS.
• • 2.2 Populate Header Information:
  • • 2.2.1 Enter Project Name, Project ID, Client Name, Client Contact, Reporting Period/Milestone, and SOWA Date.
  • • 2.2.2 Include reference to the original SOW/contract ID.
• • 2.3 Detail Work Accomplished (Aligned with SOW):
  • • 2.3.1 Systematically list each deliverable and task as defined in the original SOW.
  • • 2.3.2 For each item, provide a concise description of work performed, completion date, and responsible team members.
  • • 2.3.3 Where applicable, include metrics or quantifiable results achieved (e.g., number of features developed, tests conducted).
  • • 2.3.4 Include direct links or references to corresponding completed deliverables in the DMS.
• • 2.4 Summarize Effort & Resources:
  • • 2.4.1 Provide a summary of total hours expended, broken down by major task categories or resources (if required by SOW).
  • • 2.4.2 Compare actual effort against planned effort (if budget/effort tracking is part of the SOW).
• • 2.5 Report on Milestones Achieved: List all milestones completed within the reporting period, along with their completion dates.
• • 2.6 Document Deviations & Resolutions: Create a dedicated section for any approved scope changes, issues encountered, their impact, and resolutions, referencing formal change requests where applicable.
• • 2.7 Include Next Steps (Optional): Briefly outline planned activities for the subsequent reporting period or next project phase, if relevant.
• • 2.8 Prepare for Client Acknowledgment: Ensure the SOWA includes a clear section for client review, acceptance, and signature/acknowledgment.

Phase 3: Internal Review & Approval

• • 3.1 Project Manager Review:
  • • 3.1.1 Review the draft SOWA for accuracy, completeness, and alignment with the SOW and project records.
  • • 3.1.2 Verify all reported tasks are actual and verified accomplishments.
  • • 3.1.3 Ensure deviations are properly documented and justified.
• • 3.2 Team Lead/Technical Review (if applicable):
  • • 3.2.1 Review technical descriptions and ensure they accurately represent the work performed.
  • • 3.2.2 Confirm that reported effort aligns with actual work completed by the team.
• • 3.3 Quality Assurance (QA) Review:
  • • 3.3.1 Conduct a final check for grammatical errors, formatting consistency, and adherence to Template Registry's branding guidelines.
  • • 3.3.2 Verify compliance with this SOP and internal quality standards.
• • 3.4 Finance Department Review (if applicable):
  • • 3.4.1 Review SOWA content, particularly effort and deliverable completion, to validate accuracy for invoicing purposes.
  • • 3.4.2 Flag any inconsistencies that might affect billing.
• • 3.5 Obtain Internal Approval: Secure final internal approval from the Project Manager and any other designated stakeholders.

Phase 4: Client Submission & Acknowledgment

• • 4.1 Formal Submission: Transmit the approved SOWA to the client's designated contact via email or the agreed communication channel.
  • • 4.1.1 Attach all relevant supporting documentation or links (e.g., deliverable acceptance forms).
• • 4.2 Track Acknowledgment: Follow up with the client to confirm receipt and initiate their review process.
• • 4.3 Address Client Feedback:
  • • 4.3.1 Promptly address any questions, concerns, or requested revisions from the client.
  • • 4.3.2 If significant revisions are required, repeat relevant steps from Phase 2 and 3.
• • 4.4 Obtain Client Acknowledgment: Secure formal client acknowledgment or signature on the SOWA, as required by the SOW/contract. This may involve a digital signature or a formal email acceptance.

Phase 5: Archiving & Documentation

• • 5.1 Save Final SOWA: Save the client-acknowledged/signed SOWA as a PDF in the designated project folder within the DMS.
• • 5.2 Update Project Status: Update the PMS with the completion of the SOWA submission and acknowledgment.
• • 5.3 Inform Finance: Notify the Finance Department that the SOWA has been accepted, enabling invoice generation if applicable.
• • 5.4 Close SOWA Cycle: Formally close the SOWA generation process for the specified period/milestone.

---

Quality Assurance & Verification

Key Metric Thresholds:

• SOWA Data Accuracy: >98% (verified against PMS/TTS records).
• Timely Submission: SOWA submitted to client within 3 business days of reporting period end or milestone completion.
• Internal Review Cycle Time: <2 business days from draft completion to internal approval.
• Client Acceptance Rate: 100% (all submitted SOWAs receive formal client acknowledgment).
• Critical Errors: 0 critical errors (e.g., misrepresentation of deliverables, incorrect dates, erroneous effort data).

Common Pitfalls & Mitigation:

• Incomplete/Inaccurate Data:
  • Pitfall: Missing time logs, unrecorded tasks, or inconsistent data between systems.
  • Mitigation: Enforce strict daily time logging policies. Implement mandatory weekly data reconciliation checkpoints by Team Leads.
• Misrepresentation of Work:
  • Pitfall: SOWA claims work not fully completed or overstates achievements.
  • Mitigation: Strict adherence to SOW terms. Require objective evidence (links, artifacts) for each reported item. Mandatory QA review.
• Lack of Client Sign-off/Acknowledgment:
  • Pitfall: SOWA submitted but no formal client approval is received, leading to billing disputes.
  • Mitigation: Establish clear client communication protocols for SOWA acknowledgment. Implement automated reminders and escalation paths for unresponsive clients.
• Non-compliance with SOW Terms:
  • Pitfall: SOWA format or content does not match contractual reporting requirements.
  • Mitigation: Initial PM review against SOW. QA checklist explicitly includes SOW compliance verification.

Audit Checklist:

• • SOWA aligns with the original SOW terms and reporting frequency?
• • All reported accomplishments are traceable to PMS records and documented deliverables?
• • Total reported effort aligns with TTS records (within acceptable variance)?
• • All significant deviations from the SOW (e.g., scope changes) are clearly documented and formally approved?
• • Client acknowledgment/signature (or formal acceptance) for the SOWA is on file?
• • The final SOWA is archived correctly in the DMS?
• • Personal or sensitive data (if present) is handled in compliance with RA 10173?

---

Troubleshooting FAQ

1. Scenario: The client disputes a significant portion of the work reported in the SOWA, claiming it was not delivered or is incomplete.

• Solution:
  1. Gather Evidence: Immediately cross-reference all disputed items with detailed project records: specific task completion in PMS, associated time logs from TTS, relevant communication logs (emails, chat transcripts) with the client regarding acceptance or feedback, and deliverable review comments.
  2. Schedule Review: Propose a joint meeting with the client to walk through the evidence item by item. Present screenshots, links to completed work, and communication records proving delivery and/or acceptance.
  3. Adjust if Necessary: If discrepancies are found (e.g., internal error, miscommunication), acknowledge them and propose a revised SOWA with accurate details. Focus on transparent resolution.

2. Scenario: Data for a specific activity or task is missing or incomplete in the project management or time tracking systems, preventing accurate SOWA generation.

• Solution:
  1. Immediate Inquiry: Contact the assigned Project Team Member(s) and Team Lead directly to obtain verbal or written confirmation of the work performed and estimated effort.
  2. Cross-Reference: Check other sources such as daily stand-up notes, code repositories, design files, or internal communication channels for indirect evidence of completion.
  3. Documentation & Escalation: If data cannot be fully retrieved, document the missing information and the steps taken to recover it. Inform the Project Manager and client (if necessary) about the inability to provide exact data, proposing a mutually agreed-upon estimate based on available information or historical averages, and reinforce data entry discipline for future periods.

3. Scenario: The internal review and approval process for the SOWA consistently causes delays, impacting timely client submission.

• Solution:
  1. Review SLA Compliance: Verify if designated reviewers are adhering to the internal review Service Level Agreement (SLA) (e.g., 1-day turnaround).
  2. Identify Bottlenecks: Analyze the review workflow to pinpoint the exact stage or individual causing the delay. This might be due to reviewer unavailability, excessive workload, or unclear review instructions.
  3. Implement Streamlining:
     • Parallel Review: If feasible, initiate technical and compliance reviews in parallel rather than sequentially.
     • Automated Reminders: Utilize system-generated reminders for pending reviews.
     • Standardized Checklist: Provide reviewers with a concise checklist to expedite their process.
     • Escalate: If delays persist due to resource constraints, escalate the issue to department heads to reallocate review resources or adjust reviewer workloads.