How to Write a Statement of Work (Peter S. Cole et al.)
Problem
An undefined requirement prevents contractors from knowing what work the government expects.
Action
State the required work, results, deliverables, and limits in one controlled document.
Outcome
Both parties gain a common description of the contractual work.
Chapter: Overview - What Is a Statement of Work?
Problem
A weak SOW creates uncertainty during competition and performance.
Action
Give the SOW the same care as the other binding parts of the contract.
Outcome
The acquisition rests on a clear and enforceable description of the work.
Chapter: Overview - Importance of the SOW
Problem
Unclear requirements cause bidders to make different assumptions.
Action
Remove ambiguity and define expected results before requesting final proposals.
Outcome
Offerors submit proposals that are easier to compare fairly.
Chapter: Overview - Need for a Clear and Concise SOW - Before Award
Problem
Unclear post-award duties lead to disputes and uneven performance.
Action
Write each duty so both parties can apply it during contract performance.
Outcome
The government and contractor can resolve performance questions against shared requirements.
Chapter: Overview - Need for a Clear and Concise SOW - After Award
Problem
The government cannot enforce expectations that lack an objective baseline.
Action
Define measurable standards and connect them to each required result.
Outcome
Performance can be assessed against agreed contractual criteria.
Chapter: Overview - Need for a Clear and Concise SOW - To Establish Performance Standards and a Contractual Baseline
Problem
Missing workload and condition data forces contractors to guess about cost and effort.
Action
Provide the quantities, conditions, assumptions, and schedules needed for a sound estimate.
Outcome
Prospective contractors can prepare more realistic prices and staffing plans.
Chapter: Overview - Need for a Clear and Concise SOW - To Provide Prospective Contractors with a Basis of Estimate
Problem
Different interpretations create errors, questions, and disputes.
Action
Use direct terms and define every important expectation consistently.
Outcome
All parties understand the requirement in the same way.
Chapter: Overview - Need for a Clear and Concise SOW - To Communicate Effectively
Problem
A correct SOW can still fail when other solicitation or contract sections contradict it.
Action
Cross-check the SOW against all related instructions, evaluation factors, clauses, and schedules.
Outcome
The solicitation and the resulting contract present a single consistent requirement.
Chapter: Overview - Relationship of the SOW to the Solicitation and Contract
Problem
The government cannot evaluate an important requirement when the proposal instructions omit it.
Action
Make Sections L and M request and evaluate evidence for every major SOW requirement.
Outcome
Proposal content and source selection criteria support the work being purchased.
Chapter: Overview - Format and Content of the Solicitation and Contract - Relationship of the SOW to RFP Sections L and M
Problem
Offerors may overlook requirements that proposal instructions do not address.
Action
Direct offerors to explain how their proposals satisfy each significant SOW requirement.
Outcome
Evaluators receive enough information to judge complete technical coverage.
Chapter: Overview - Use of the Proposal Preparation Instructions - To Ensure Appropriate Coverage
Problem
Different proposal structures make equivalent information difficult to find and compare.
Action
Require all offerors to follow the same section order and response format.
Outcome
Evaluators can compare proposals more quickly and consistently.
Chapter: Overview - Use of the Proposal Preparation Instructions - To Standardize Proposal Format
Problem
Broad requests produce claims that evaluators cannot verify.
Action
Identify the exact plans, methods, schedules, staffing data, and supporting evidence that offerors must provide.
Outcome
The government receives information that supports a defensible evaluation.
Chapter: Overview - Use of the Proposal Preparation Instructions - To Require Specific Information
Problem
Poorly organized instructions cause omissions and inconsistent responses.
Action
Arrange proposal instructions by topic with clear numbering, limits, and cross-references.
Outcome
Offerors can prepare complete proposals in a predictable form.
Chapter: Overview - Formatting the Proposal Preparation Instructions
Problem
Small errors can change meaning or create conflicts across acquisition documents.
Action
Review the final package for accuracy, completeness, consistency, and correct references.
Outcome
The solicitation reaches offerors with fewer defects and ambiguities.
Chapter: Overview - Need to Check Your Work Carefully
Problem
A premature solution can hide the actual mission need or an unrealistic delivery date.
Action
Define the required result and validate when the organization truly needs it.
Outcome
The acquisition targets the right requirement on a workable schedule.
Chapter: Planning and Preparation - Acquisition Planning - What Is the Real Requirement, and When Is It Needed?
Problem
A requirement lacks direction when success has no clear test.
Action
Choose observable measures and acceptance criteria before drafting detailed work requirements.
Outcome
The contract can focus effort and oversight on successful results.
Chapter: Planning and Preparation - Acquisition Planning - How Will Success Be Measured or Determined?
Problem
An unaffordable requirement wastes planning effort and delays the award.
Action
Develop a realistic cost estimate and compare it with confirmed funding.
Outcome
The planned acquisition fits the available budget.
Chapter: Planning and Preparation - Acquisition Planning - What Is It Likely to Cost, and What Funds Are Available?
Problem
Internal assumptions can lead to requirements that overlook available commercial capabilities.
Action
Study suppliers, customary practices, prices, risks, and existing solutions before finalizing the SOW.
Outcome
The requirement reflects realistic market conditions and encourages competition.
Chapter: Planning and Preparation - Market Research
Problem
Unexamined dependencies often become gaps in scope, schedule, or responsibility.
Action
Trace the work, decisions, inputs, outputs, risks, and handoffs through the full project.
Outcome
The SOW covers the work needed to reach the final result.
Chapter: Planning and Preparation - Thinking the Project Through
Problem
Large requirements hide missing tasks and unclear responsibilities.
Action
Divide the project into logical work elements that cover the full scope without overlap.
Outcome
Planning, estimating, scheduling, and tracking become more reliable.
Chapter: Planning and Preparation - Using a Work Breakdown Structure
Problem
Fixed pricing creates excessive risk when scope and cost conditions remain uncertain.
Action
Choose a fixed-price contract when requirements are stable and costs can be estimated reliably.
Outcome
The contractor carries appropriate cost risk under a predictable price.
Chapter: Planning and Preparation - Choosing the Contract Type - Fixed-Price Contracts
Problem
Forcing uncertain work into a fixed price can produce inflated bids or poor performance.
Action
Choose cost reimbursement when uncertainties prevent reliable cost estimates, and oversight is available.
Outcome
The contract can accommodate necessary effort while the government monitors allowable costs.
Chapter: Planning and Preparation - Choosing the Contract Type - Cost-Reimbursement Contracts
Problem
Payment for hours worked gives the contractor little reason to control total labor use.
Action
Use time-and-materials or labor-hour terms only when other contract types are unsuitable, and set a ceiling.
Outcome
The government gains needed flexibility while limiting financial exposure.
Chapter: Planning and Preparation - Choosing the Contract Type - Time-and-Materials and Labor-Hour Contracts
Problem
The government may know the type of work needed without knowing the exact timing or quantity.
Action
Use an indefinite delivery structure with clear ordering rules, limits, and work descriptions.
Outcome
Authorized needs can be ordered efficiently as they arise.
Chapter: Planning and Preparation - Choosing the Contract Type - Indefinite-Delivery Contracts
Problem
Prescribing a solution can block useful contractor ideas when only the purpose is fixed.
Action
State what the product or service must accomplish without dictating its design.
Outcome
Contractors can propose different ways to meet the operational need.
Chapter: Planning and Preparation - Choosing the SOW Type - Functional Descriptions
Problem
Task instructions can control contractor activity without ensuring useful results.
Action
Define required outcomes, performance levels, and acceptance measures.
Outcome
The contractor gains method flexibility while remaining accountable for results.
Chapter: Planning and Preparation - Choosing the SOW Type - Performance Descriptions
Problem
Confusing functional and performance descriptions can leave the requirement incomplete.
Action
Use a functional description for intended use and a performance description for measurable capability.
Outcome
The SOW expresses the requirement at the right level of detail.
Chapter: Planning and Preparation - Choosing the SOW Type - Differences Between Functional and Performance Descriptions
Problem
Detailed design instructions transfer design responsibility to the government and restrict alternatives.
Action
Specify materials, dimensions, processes, or configurations only when the requirement truly depends on them.
Outcome
Necessary design controls remain without limiting contractor judgment more than needed.
Chapter: Planning and Preparation - Choosing the SOW Type - Design Descriptions
Problem
A broad reference to a proposal can import conflicting statements and unwanted qualifications.
Action
Identify the exact proposal parts that become binding and establish their order of precedence.
Outcome
Only intended contractor commitments become enforceable contract requirements.
Chapter: Planning and Preparation - Incorporating a Contractor's Proposal by Reference
Problem
Some work cannot guarantee a specific result, even when the necessary skills and effort are known.
Action
State the required labor categories, hours, period, and general work objective.
Outcome
The contractor can provide a controlled level of effort without guaranteeing an uncertain result.
Chapter: Planning and Preparation - Distinguishing Between Level-of-Effort (LOE) and Completion SOWs - Level-of-Effort SOWs
Problem
Buying hours does not ensure delivery when the required end product can be specified.
Action
Describe the completed result and make completion the contractor's primary obligation.
Outcome
Payment and accountability center on finishing the required work.
Chapter: Planning and Preparation - Distinguishing Between Level-of-Effort (LOE) and Completion SOWs - Completion SOWs
Problem
The wrong SOW form can make expectations for effort or completion legally unclear.
Action
Use an LOE form for a stated amount of work and a completion form for a defined end result.
Outcome
The contract clearly states whether the contractor owes effort or completion.
Chapter: Planning and Preparation - Distinguishing Between Level-of-Effort (LOE) and Completion SOWs - Distinguishing Between the LOE and Completion Forms
Problem
Contractors cannot estimate either form accurately without workload and complexity information.
Action
Supply relevant quantities, assumptions, historical data, conditions, and expected outputs.
Outcome
Offerors can build realistic estimates for the chosen SOW form.
Chapter: Planning and Preparation - Distinguishing Between Level-of-Effort (LOE) and Completion SOWs - Providing a Basis of Estimate for LOE and Completion Requirements
Problem
Government control over individual contractor employees can create an improper personal services relationship.
Action
Assign results to the contractor and let the contractor's management direct its personnel.
Outcome
The service remains nonpersonal and preserves clear employer responsibility.
Chapter: Planning and Preparation - Personal Versus Nonpersonal Services
Problem
A tailored SOW can unfairly exclude alternatives or hide weak justification.
Action
Describe the actual need and document separately why only one source can meet it.
Outcome
The acquisition remains defensible without disguising source selection as a technical requirement.
Chapter: Planning and Preparation - Sole-Source SOWs
Problem
Follow-on work and options can create hidden commitments or weaken future competition.
Action
Define the option work clearly and state that the exercise depends on the government's need, funding, and contract terms.
Outcome
Future effort can proceed efficiently without becoming an automatic entitlement.
Chapter: Planning and Preparation - Follow-on Efforts and Options
Problem
Detailed task directions can reduce contractor responsibility for service results.
Action
Describe required outcomes, measurable standards, and acceptable quality levels in a performance work statement.
Outcome
The contractor can choose methods while the government evaluates results.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - What Is Performance-Based Service Contracting? - Performance Work Statement
Problem
Oversight becomes inconsistent when the government has no planned method for testing performance.
Action
Define what will be checked, how it will be checked, and what evidence will show compliance.
Outcome
The government can assess service quality with consistent methods.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - What Is Performance-Based Service Contracting? - Quality Assurance Plan
Problem
An incentive can waste money when it rewards activity that does not improve mission results.
Action
Tie each reward to a measurable result that provides real value above the minimum requirement.
Outcome
Contractor effort moves toward performance that matters to the government.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - What Is Performance-Based Service Contracting? - Incentive Plan
Problem
Performance-based methods fail when desired outcomes and quality levels cannot be defined.
Action
Use PBSC when the service result can be stated and measured without directing daily methods.
Outcome
The government can hold the contractor accountable for service outcomes.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - When Is It Appropriate to Use PBSC?
Problem
A service requirement can miss its purpose when it ignores the supported organization's mission and structure.
Action
Identify mission needs, customers, responsibilities, interfaces, and operating constraints.
Outcome
The service requirement supports the organization it is meant to serve.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Developing a Job Analysis - Organizational Analysis
Problem
Assumptions about current work can distort scope and performance standards.
Action
Collect records, observations, interviews, volumes, times, and service data from credible sources.
Outcome
The job analysis rests on verified operating information.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Developing a Job Analysis - Data Gathering
Problem
A contractor may violate required rules when the SOW omits controlling directives.
Action
Review each applicable law, regulation, policy, standard, and local instruction for necessary requirements.
Outcome
The performance work statement includes valid compliance obligations.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Developing a Job Analysis - Directives Analysis
Problem
Government work methods may not reflect efficient commercial service delivery.
Action
Research how capable suppliers define, perform, measure, and price similar work.
Outcome
The planned service uses realistic requirements that the market can support.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Developing a Job Analysis - Market Research
Problem
Listing isolated tasks can hide the results and dependencies that make the service useful.
Action
Identify recurring activities, inputs, outputs, frequencies, volumes, and work relationships.
Outcome
The performance work statement covers the complete service process.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Developing a Job Analysis - Work Analysis
Problem
Standards for every minor activity create costly oversight without protecting important outcomes.
Action
Select critical outputs and define measurable standards and acceptable quality levels for them.
Outcome
Performance management focuses on results with the greatest mission impact.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Developing a Job Analysis - Performance Analysis
Problem
Higher standards can add cost without providing equal value.
Action
Estimate how workload, quality levels, risks, and oversight choices affect total cost.
Outcome
The government can choose service levels that provide reasonable value.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Developing a Job Analysis - Cost Analysis
Problem
Defense acquisitions can fail review when they ignore applicable department rules and approval processes.
Action
Check current DoD policies, templates, responsibilities, and documentation requirements during job analysis.
Outcome
The acquisition supports performance-based goals and department compliance.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Developing a Job Analysis - For Defense Department (DoD) Readers
Problem
A quality plan cannot verify compliance when its checks do not align with contract standards.
Action
Connect each surveillance method, sample, frequency, and remedy to a stated performance requirement.
Outcome
Quality assurance produces relevant evidence of contract performance.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Developing a Quality Assurance Plan
Problem
No single surveillance method can efficiently detect every kind of service failure.
Action
Choose among inspection, sampling, observation, records, customer feedback, and contractor reports based on the risk.
Outcome
The government gathers useful evidence with proportionate oversight.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Types of Surveillance Methods
Problem
Excessive checking wastes resources while weak checking misses important failures.
Action
Select surveillance intensity according to performance risk, service importance, cost, and available data.
Outcome
Oversight effort concentrates on the most important contract results.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Selecting Surveillance Methods
Problem
A quality plan provides little value when it cannot guide actual inspections and decisions.
Action
Document each requirement, standard, surveillance method, schedule, record, and response in a usable format.
Outcome
Quality staff can perform consistent surveillance throughout the contract.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - QAP Example
Problem
Subjective or unclear calculations make financial incentives difficult to administer.
Action
Use a stated formula that links verified performance levels to defined adjustments.
Outcome
Both parties can predict and confirm the financial effect of performance.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Offering Incentives - Formula Incentives
Problem
Some valuable performance cannot be captured fully by a mechanical formula.
Action
Use documented evaluation criteria and a disciplined review process for award incentives.
Outcome
The government can recognize exceptional value through a fair judgment process.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Offering Incentives - Award Incentives
Problem
A contractor may have little reason to invest in long-term improvement when future work is uncertain.
Action
Offer additional contract periods only for sustained performance measured against stated criteria.
Outcome
Excellent performance can earn continued work without guaranteeing it in advance.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Offering Incentives - Award Term Incentives
Problem
An incentive adds cost and complexity when normal contract duties already produce the desired result.
Action
Use an incentive only when the target is measurable, valuable, and responsive to contractor effort.
Outcome
The incentive produces benefits that justify its administration and cost.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Offering Incentives - Should Incentives Be Used in PBSC Contracts?
Problem
Full payment for unacceptable service removes the financial effect of failure.
Action
Define proportional deductions for measured performance below the acceptable quality level.
Outcome
Payment better reflects the value of the service actually received.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Offering Incentives - Deductibles
Problem
Separate performance, surveillance, and incentive documents can work at odds with one another.
Action
Align the performance work statement, quality plan, pricing, remedies, and incentives before award.
Outcome
The contract manages service performance as one coherent system.
Chapter: Writing a Performance Work Statement for Performance-Based Service Contracting - Summary
Problem
A detailed government solution can limit competition and contractor innovation.
Action
Describe mission purpose, required outcomes, constraints, and success measures in the SOO.
Outcome
Offerors can develop different performance work statements that meet the same objectives.
Chapter: Using a Statement of Objectives (SOO) and Related Issues - What Is an SOO?
Problem
An SOO alone does not tell offerors what solution details their proposals must contain.
Action
Use Section L to require a proposed work statement, measures, methods, staffing, schedule, and quality approach.
Outcome
Each proposal contains enough detail to serve as an executable contract.
Chapter: Using a Statement of Objectives (SOO) and Related Issues - SOO Format - Section L
Problem
Evaluation factors can favor a proposal style over mission results.
Action
Use Section M to assess how well each proposed solution meets the SOO objectives and manages risk.
Outcome
Source selection favors the solution with the strongest expected value.
Chapter: Using a Statement of Objectives (SOO) and Related Issues - SOO Format - Section M
Problem
A winning approach is not enforceable when the contract does not identify its binding parts.
Action
Incorporate the accepted work statement and related commitments with exact references and precedence rules.
Outcome
The contractor's proposed solution becomes a clear contractual obligation.
Chapter: Using a Statement of Objectives (SOO) and Related Issues - Incorporation by Reference
Problem
Too much direction defeats the purpose of an SOO, while too little direction hides essential constraints.
Action
State firm objectives and limits while allowing offerors to define the work needed to succeed.
Outcome
Competition produces practical solutions without sacrificing mission control.
Chapter: Using a Statement of Objectives (SOO) and Related Issues - Using an SOO
Problem
Direct comparison is difficult when each offeror proposes a different technical solution.
Action
Use a five-step process to define objectives, request solutions, evaluate them, select one, and incorporate it.
Outcome
The government can compare innovative approaches through a consistent acquisition process.
Chapter: Using a Statement of Objectives (SOO) and Related Issues - Competing the SOO - Five-Step Approach
Problem
Offerors may design unaffordable solutions when they lack realistic budget information.
Action
Release useful funding information when doing so supports fair competition and better tradeoffs.
Outcome
Proposed solutions fit the government's financial limits more closely.
Chapter: Using a Statement of Objectives (SOO) and Related Issues - Competing the SOO - Releasing Funding Information
Problem
An SOO approach fails when proposal instructions, evaluation, and incorporation do not support it.
Action
Connect the objectives to requested proposal content, evaluation factors, and binding contract terms.
Outcome
The selected contractor solution remains tied to the government's mission need.
Chapter: Using a Statement of Objectives (SOO) and Related Issues - Summary
Problem
Readers can misunderstand the document when its purpose and subject are not stated at the start.
Action
Identify the organization, requirement, and basic purpose in a brief introduction.
Outcome
Readers quickly understand what the SOW addresses.
Chapter: The SOW Format - SOW Part I: General Information - Section A: Introduction
Problem
Contractors may misread the requirement when they lack its operating and historical context.
Action
Explain the mission, current situation, prior effort, and relevant environment without adding requirements.
Outcome
Offerors understand why the work is needed and where it fits.
Chapter: The SOW Format - SOW Part I: General Information - Section B: Background
Problem
Unclear boundaries lead to missed work, duplicated effort, and disputes over responsibility.
Action
State the overall work, major objectives, coverage, exclusions, and organizational limits.
Outcome
Both parties can distinguish included work from work outside the contract.
Chapter: The SOW Format - SOW Part I: General Information - Section C: Scope
Problem
Unclear references can impose obsolete, conflicting, or unintended requirements.
Action
List each necessary document by exact title, date, version, and applicable portion.
Outcome
Contractors can identify the external requirements that govern performance.
Chapter: The SOW Format - SOW Part I: General Information - Section D: Applicable Documents
Problem
Missing technical details prevent consistent estimation, performance, and acceptance.
Action
State each required task or result with its conditions, standards, interfaces, and acceptance basis.
Outcome
The contractor knows what technical performance the government requires.
Chapter: The SOW Format - SOW Part II: Work Requirements - Section A: Technical Requirements
Problem
An unnamed or incomplete deliverable cannot be scheduled, priced, or accepted reliably.
Action
Specify each deliverable's content, format, quantity, due date, recipient, and acceptance criteria.
Outcome
The government receives usable products at known times.
Chapter: The SOW Format - SOW Part II: Work Requirements - Section B: Deliverables
Problem
Unclear security duties can expose people, facilities, systems, or information to harm.
Action
Identify required clearances, controls, training, access rules, reporting, and handling procedures.
Outcome
The contractor can plan and perform the work under the required security conditions.
Chapter: The SOW Format - SOW Part III: Supporting Information - Section A: Security
Problem
Location affects access, staffing, travel, equipment, security, and price.
Action
State each place of performance and the work conditions that apply there.
Outcome
Offerors can plan resources and costs for the actual work locations.
Chapter: The SOW Format - SOW Part III: Supporting Information - Section B: Place of Performance
Problem
Unclear start, end, phase, and option dates create uncertainty in scheduling and pricing.
Action
State the base period, milestones, option periods, and any timing dependencies.
Outcome
Both parties can plan and measure performance against one schedule.
Chapter: The SOW Format - SOW Part III: Supporting Information - Section C: Period of Performance
Problem
Contractors may duplicate resources or depend on items the government will not provide.
Action
List each government-furnished item with its condition, availability, delivery, use limits, and return duties.
Outcome
Contractors can price and perform with accurate resource assumptions.
Chapter: The SOW Format - SOW Part III: Supporting Information - Section D: Government-Furnished Property
Problem
Unnecessary qualification rules restrict staffing flexibility and competition.
Action
Identify only essential positions and state the minimum experience, education, skills, and substitution process.
Outcome
Critical work receives qualified leadership without excessive staffing controls.
Chapter: The SOW Format - SOW Part III: Supporting Information - Section E: Qualifications of Key Personnel
Problem
Sealed bidding offers little opportunity to negotiate unclear technical requirements once bids are received.
Action
Write an exact, complete SOW that supports price competition without relying on subsequent discussions.
Outcome
Responsive bids can be evaluated and awarded on the stated requirement.
Chapter: The SOW Format - SOWs for Sealed Bidding - How the Differences Between Sealed Bidding and Negotiation Affect the SOW
Problem
Complex requirements are difficult to understand through narrative text alone.
Action
Use controlled diagrams, tables, exhibits, schedules, data, and reference documents where they improve precision.
Outcome
Offerors can better understand and estimate complex work.
Chapter: The SOW Format - Techniques to Support the SOW
Problem
Scattered information makes requirements hard to find and control.
Action
Organize general information, work requirements, and supporting information in a standard sequence.
Outcome
Readers can locate and apply contract requirements efficiently.
Chapter: The SOW Format - Summary
Problem
Poor writing makes valid requirements difficult to understand and enforce.
Action
Use short active sentences with one clear subject, duty, condition, and measurable result.
Outcome
Readers can interpret requirements consistently and test compliance.
Chapter: Common Problems in Writing SOWs - General Writing Guidelines
Problem
Different requirements for the same work leave contractors unsure which one controls.
Action
Compare every related statement and reconcile differences in scope, quantity, standard, and timing.
Outcome
The SOW presents one coherent set of obligations.
Chapter: Common Problems in Writing SOWs - Common Ambiguities in SOWs - Inconsistency of Requirements
Problem
Different names for the same task, product, or role can imply that separate things are required.
Action
Choose one defined term for each item and use it throughout the acquisition documents.
Outcome
Readers can follow references without guessing whether terms mean the same thing.
Chapter: Common Problems in Writing SOWs - Common Ambiguities in SOWs - Calling a Requirement by Different Names
Problem
Conflicting or impossible dates make compliant performance unattainable.
Action
Check all milestones, lead times, dependencies, review periods, and delivery dates as one schedule.
Outcome
The final contract contains achievable and consistent timing requirements.
Chapter: Common Problems in Writing SOWs - Common Ambiguities in SOWs - Conflicting or Unreasonable Schedules
Problem
Missing conditions or outputs force contractors to fill gaps with different assumptions.
Action
Specify who performs the work, what is required, where it occurs, when it is due, and how it is accepted.
Outcome
Offerors can estimate and perform the same complete requirement.
Chapter: Common Problems in Writing SOWs - Common Ambiguities in SOWs - Incomplete Description of Requirement
Problem
Terms such as timely or adequate do not establish a common performance level.
Action
Replace generalized language with stated quantities, deadlines, conditions, and quality standards.
Outcome
Compliance can be determined from objective evidence.
Chapter: Common Problems in Writing SOWs - Common Ambiguities in SOWs - Vagueness and Generalized Language
Problem
Abstract goals do not tell a contractor what result must be delivered.
Action
Express each broad concept as a concrete output, behavior, condition, or measure.
Outcome
The contractor can act on the requirement and demonstrate completion.
Chapter: Common Problems in Writing SOWs - Common Ambiguities in SOWs - Use of Abstractions
Problem
Comments, opinions, and side explanations can obscure requirements or create unintended meaning.
Action
Keep only information that defines, supports, or clarifies the required work.
Outcome
The SOW becomes shorter and easier to interpret.
Chapter: Common Problems in Writing SOWs - Common Ambiguities in SOWs - Unnecessary Comments
Problem
Poor sentence structure can hide the responsible party or required action.
Action
Write each requirement with a clear subject, active verb, object, and necessary condition.
Outcome
Readers can identify each duty without reconstructing the sentence.
Chapter: Common Problems in Writing SOWs - Common Ambiguities in SOWs - Poor Sentence Construction
Problem
Typographical errors and missing text can change technical or contractual meaning.
Action
Check the final SOW line by line against approved requirements, references, numbers, and attachments.
Outcome
The issued document contains fewer accidental defects.
Chapter: Common Problems in Writing SOWs - Common Ambiguities in SOWs - Typos or Missing Text
Problem
Complicated vocabulary makes simple duties harder to understand.
Action
Replace uncommon or formal terms with plain words that preserve the required meaning.
Outcome
More readers understand the requirement on the first reading.
Chapter: Common Problems in Writing SOWs - Common Ambiguities in SOWs - Overly Complicated Vocabulary
Problem
A long sentence can combine several duties and hide their relationships.
Action
Write separate sentences for separate requirements and keep conditions next to the duties they control.
Outcome
Each obligation becomes easier to interpret and verify.
Chapter: Common Problems in Writing SOWs - Common Ambiguities in SOWs - Excessively Long Sentences
Problem
A SOW requirement may be unenforceable or misleading when it contradicts a contract clause.
Action
Review the SOW and clauses together and revise conflicts before award.
Outcome
The contract gives both parties consistent legal and technical direction.
Chapter: Common Problems in Writing SOWs - Conflicts Between the SOW and Contract Clauses
Problem
The acquisition team may not see technical barriers, cost drivers, or unclear terms known to industry.
Action
Issue a draft solicitation and request focused comments on feasibility, clarity, risk, and competition.
Outcome
The final solicitation reflects useful market feedback before proposals are due.
Chapter: Common Problems in Writing SOWs - Obtaining Contractor Comments - Draft Solicitations
Problem
Shared questions can persist when offerors receive only isolated written exchanges.
Action
Hold a structured conference and publish official answers and amendments to all offerors.
Outcome
Competitors prepare proposals from the same clarified information.
Chapter: Common Problems in Writing SOWs - Obtaining Contractor Comments - Preproposal Conference
Problem
Offerors may detect requirement problems but lack a defined way to raise them.
Action
Tell offerors how to identify assumptions, exceptions, conflicts, and recommended changes in their proposals.
Outcome
The government can evaluate requirement concerns alongside proposed solutions.
Chapter: Common Problems in Writing SOWs - Obtaining Contractor Comments - Proposal Preparation Instructions
Problem
Careless word choice can make a mandatory requirement appear optional or uncertain.
Action
Use consistent words that clearly distinguish obligations, permissions, expectations, and information.
Outcome
Each statement carries the intended contractual force.
Chapter: Common Problems in Writing SOWs - Guidelines Related to the Use of Words
Problem
Undefined phrases and specialized terms invite different interpretations.
Action
Use standard meanings and define any necessary term that readers could understand differently.
Outcome
The SOW communicates specialized requirements with less ambiguity.
Chapter: Common Problems in Writing SOWs - Guidelines Related to the Use of Phrases and Terms
Problem
Informal direction can create disputed work and unauthorized government commitments.
Action
Require changes to pass through the contracting officer under the contract's change procedures.
Outcome
Contract modifications have clear legal authority and documented terms.
Chapter: Managing Changes to the SOW - Legal Precedents Backing Change Management
Problem
A small instruction can alter scope, cost, schedule, or performance without being labeled a change.
Action
Compare each new request or condition with the contractual baseline before authorizing work.
Outcome
Potential changes receive proper review before they create uncontrolled obligations.
Chapter: Managing Changes to the SOW - Identifying Changes
Problem
Poor communication, unclear authority, weak records, and schedule pressure allow changes to bypass control.
Action
Assign change roles and require timely analysis, approval, communication, and documentation.
Outcome
Project changes remain visible and manageable.
Chapter: Managing Changes to the SOW - Managing Project Changes - Factors Affecting Change Mismanagement
Problem
A verbal or incomplete change leaves scope, price, schedule, and approval uncertain.
Action
Record the reason, revised requirement, impact, funding, authority, and effective date on a change order form.
Outcome
Each approved change has a complete and traceable record.
Chapter: Managing Changes to the SOW - Tools for Managing Changes - Change Order Form
Problem
Separate change records make it difficult to control cumulative cost, schedule, and scope effects.
Action
Maintain a separate tracker for each proposed, approved, rejected, implemented, and closed SOW change.
Outcome
The team can monitor status and cumulative contract impact at any time.
Chapter: Managing Changes to the SOW - Tools for Managing Changes - SOW Change Order Tracker