Army Statement of Work Template

Standard Operating Procedure: Army Statement of Work (SOW) Development & Compliance

---

1. Document Control Block

• Document ID: TR-SOP-SOW-ARMY-V01.03
• Effective Date: 2023-10-27
• Version: 1.03
• Review Cadence: Annually (October) or upon significant regulatory/organizational change.

---

2. Executive Summary & Scope

This Standard Operating Procedure (SOP) establishes the systematic methodology for developing, reviewing, and finalizing Statements of Work (SOWs) specifically tailored for U.S. Army projects, contracts, and solicitations. The objective is to ensure all SOWs meet regulatory compliance (e.g., Federal Acquisition Regulation [FAR], Defense Federal Acquisition Regulation Supplement [DFARS]), institutional quality standards, and clearly articulate project requirements, performance expectations, and deliverables.

Scope: This SOP applies to all personnel involved in the initiation, drafting, technical development, legal review, and approval of SOWs for external contractors, internal teams, or inter-agency agreements pertaining to U.S. Army-funded or supported operations, research, development, acquisition, and sustainment activities within Template Registry. It covers SOWs, Performance Work Statements (PWS), and Statement of Objectives (SOO) development principles.

---

3. Prerequisites & Required Tools

• Personnel Qualification: Demonstrated understanding of acquisition processes, contract types, and U.S. Army operational context.
• Regulatory Knowledge: Proficiency in FAR Parts 1, 2, 4, 7, 10, 11, 15, 37, and corresponding DFARS supplements. Awareness of relevant Army Regulations (e.g., AR 70-1, AR 73-1).
• Access to Reference Documents: Current versions of the FAR, DFARS, Army Acquisition Policy documents, and relevant Army-specific SOW templates or guides.
• Software & Platforms:
  • Microsoft 365 Suite (Word, Excel, SharePoint, Teams) for document creation, collaboration, and secure storage.
  • Template Registry Document Management System (TR-DMS) for version control and archival.
  • Secure communication channels (e.g., MS Teams with CUI/FOUO enabled) for discussions involving sensitive information.
  • Adobe Acrobat Pro for final document locking and digital signatures.
• Compliance Tools: Access to internal legal and contracting offices for review and guidance.
• Security Clearance: Appropriate security clearance as required by project classification (e.g., Secret, Top Secret) for personnel accessing classified SOW details.

---

4. Roles & Responsibilities

---

5. Step-by-Step Procedure

Phase 1: Project Definition & Initial Research

• 1.1 Initiate Project Requirement: PM identifies the need for an SOW based on approved project charters or funding allocations.
• 1.2 Define Objectives: PM, in consultation with TE, clearly articulates project goals, desired outcomes, and key performance indicators (KPIs).
• 1.3 Gather Background Information: Collect all relevant data, including previous contract performance, market research, existing technologies, and applicable Army regulations.
• 1.4 Determine Acquisition Strategy: PM, with CO/COR, outlines the planned acquisition approach (e.g., competitive, sole source, specific contract type). This influences SOW structure (e.g., PWS vs. SOW).
• 1.5 Identify Stakeholders: Document all internal and external parties who will contribute to, review, or be affected by the SOW.

Phase 2: SOW Drafting (Using an Approved Template)

• 2.1 Select Approved Template: Utilize the latest approved Army SOW template from TR-DMS or a project-specific template approved by CO.
• 2.2 Populate Standard Sections:
  • 2.2.1 Introduction/Background: Provide concise context for the requirement, problem statement, and strategic alignment.
  • 2.2.2 Objectives: State high-level, measurable objectives of the project.
  • 2.2.3 Scope of Work: Define the boundaries of the effort, clearly distinguishing what is included and excluded.
  • 2.2.4 Tasks/Requirements: Detail specific, measurable, achievable, relevant, and time-bound (SMART) tasks, sub-tasks, and required methodologies.
  • 2.2.5 Deliverables: List all tangible and intangible products, reports, or services to be provided, with specific due dates or periods.
  • 2.2.6 Performance Standards/Metrics: Establish objective and measurable criteria for acceptable performance for each task or deliverable. Include a Quality Assurance Surveillance Plan (QASP) reference if applicable.
  • 2.2.7 Government Furnished Property (GFP)/Information (GFI): List all government-provided items, data, access, or services with their associated responsibilities and accountability.
  • 2.2.8 Security Requirements: Detail personnel clearances, facility access, data handling, reporting requirements (e.g., OPSEC, AT, Cyber Security, DD Form 254 if applicable).
  • 2.2.9 Period of Performance: Specify the start and end dates or total duration of the SOW.
  • 2.2.10 Place of Performance: Identify physical locations where work will be conducted.
  • 2.2.11 Travel: Stipulate any authorized and reimbursable travel, including approval processes.
  • 2.2.12 Reporting Requirements: Specify format, frequency, and distribution of progress reports, technical reports, and financial reports.
  • 2.2.13 Acceptance Criteria: Clearly define how the government will evaluate and accept deliverables and overall performance.
  • 2.2.14 Contractor Manpower Reporting (CMR): Include appropriate language for reporting contractor personnel if required (e.g., for services contracts).
  • 2.2.15 Special Requirements: Include any unique clauses or conditions specific to the project (e.g., environmental, safety, intellectual property).

Phase 3: Internal Review & Approval

• 3.1 Technical Review: TE reviews the SOW for technical accuracy, completeness, and feasibility.
• 3.2 Programmatic Review: PM reviews for alignment with project objectives, budget, and schedule.
• 3.3 Security Review: Security Officer reviews for compliance with all applicable security regulations and classified information handling protocols (if applicable).
• 3.4 Legal Review: Legal Counsel reviews for legal sufficiency, regulatory compliance (FAR/DFARS), and risk mitigation.
• 3.5 Quality Assurance Review: QA Specialist reviews for clarity, consistency, grammar, formatting, and adherence to TR-SOP-SOW-ARMY standards.
• 3.6 Consolidate Feedback: PM consolidates all review comments and initiates revisions. Resolve conflicting feedback through stakeholder meetings.
• 3.7 PM Approval: PM provides initial approval, signifying the SOW is ready for formal CO/COR review.

Phase 4: Formal Review & Coordination

• 4.1 Contracting Officer (CO) Review: Submit the SOW to the responsible CO for comprehensive review regarding acquisition strategy, contract type applicability, and overall compliance.
• 4.2 Contracting Officer Representative (COR) Input: COR provides input on the clarity of performance requirements, surveillance methods, and project execution feasibility.
• 4.3 Revisions based on CO/COR Feedback: Incorporate all necessary revisions as directed by the CO and COR. Document all significant changes and justifications.
• 4.4 Final Internal Validation: Conduct a final internal review to confirm all CO/COR feedback has been accurately addressed.

Phase 5: Finalization & Distribution

• 5.1 CO Final Approval: CO grants final approval, making the SOW ready for integration into solicitation documents or contract award.
• 5.2 Version Control & Archival: Upload the final approved SOW to TR-DMS, ensuring proper version control and metadata tagging. Archive all previous versions and review comments.
• 5.3 Distribution: Distribute the SOW to relevant parties (e.g., procurement specialists, selected contractor, project execution team) as per project requirements and security protocols.
• 5.4 SOW Management Post-Award: PM/COR ensures the SOW is effectively communicated to the contractor, and that contractor performance is monitored against SOW requirements throughout the contract lifecycle. Manage SOW modifications via formal contract modifications.

---

6. Quality Assurance & Verification

Key Metric Thresholds:

• Compliance Score: 98% adherence to FAR/DFARS and Army-specific SOW requirements.
• Revision Cycles: Max 3 internal review cycles before CO submission.
• Clarity Index: Average readability score (e.g., Flesch-Kincaid) appropriate for technical documents (typically 10th-12th grade equivalent) with minimal ambiguity reported by reviewers.
• Timeliness: SOW completed and approved within 10 business days of initial drafting completion.

Common Pitfalls & Mitigation:

• Ambiguity/Vagueness: Use specific verbs, quantifiable metrics, and clearly defined terms. Require TE/CO sign-off on clarity.
• Non-Compliance (FAR/DFARS): Mandatory legal review and CO sign-off. Regular training on current regulations.
• Scope Creep (during drafting): PM to strictly enforce initial project objectives and scope definition.
• Lack of Measurable Performance Standards: Mandate inclusion of objective KPIs and reference to QASP.
• Insufficient Security Requirements: Mandatory Security Officer review and DD Form 254 (if applicable) integration.
• Inadequate Acceptance Criteria: Require explicit, objective criteria for each deliverable, reviewed by COR.

Audit Checklist:

• Is the SOW built upon an approved, current template?
• Are all sections (Background, Scope, Tasks, Deliverables, Performance, GFP/GFI, Security, etc.) complete and logically structured?
• Is every requirement traceable to a specific deliverable or performance metric?
• Are all regulatory references (FAR, DFARS, Army Regs) accurate and current?
• Has legal counsel provided review and approval?
• Has the Contracting Officer provided final approval?
• Is the SOW version controlled and archived in TR-DMS?
• Are all security requirements clearly articulated and compliant with relevant directives?
• Are the acceptance criteria objective and measurable?
• Is there evidence of multi-stakeholder review (PM, TE, Legal, Security, QA)?

---

7. Troubleshooting FAQ

Q1: The technical requirements are highly complex and difficult to articulate clearly within standard SOW sections, leading to reviewer confusion. A1: Solution: Schedule a dedicated technical clarification workshop involving the PM, TE, and key reviewers (Legal, CO, QA). Utilize diagrams, flowcharts, or appendices to provide detailed technical specifications without cluttering the main SOW text. Consider transitioning to a Performance Work Statement (PWS) model if the complexity favors defining outcomes rather than prescriptive tasks.

Q2: During CO review, significant portions of the SOW are deemed non-compliant with recent FAR/DFARS updates, causing delays. A2: Solution: Immediately convene a joint meeting with the CO, Legal Counsel, and the drafting team. Identify the specific non-compliant clauses. Legal Counsel will provide updated guidance and mandatory language. Implement a mandatory pre-CO review checklist incorporating recent regulatory changes, and schedule bi-annual training for all SOW drafters on current FAR/DFARS amendments.

Q3: A new security threat or classification change impacts an already approved SOW, potentially jeopardizing ongoing work. A3: Solution: The Security Officer must immediately notify the PM, CO, and Legal Counsel. A formal contract modification (SF-30) will be required to update the SOW's security requirements (e.g., DD Form 254, personnel clearances, data handling protocols). Expedite the modification process, ensuring all affected parties (including the contractor) are informed and re-briefed on the updated security posture and requirements.