Every good statement of work includes the following information:

• Include the Objective. This section answers the question “Why? It is a highlevel overview of the project and its objectives. General descriptions are acceptable when drafting this “bird’s-eye-view” of the project but avoid language that could be interpreted in more than one way. Be clear; describe measurable and achievable objectives that realistically can be accomplished in the specified time frame.
• Include a discussion of the Scope. This section provides a definitive statement (no options or alternatives) of the “What?” and “How?” What is the work? How will it be accomplished? Or, often, what is NOT the work and what will NOT be accomplished. What are the assumptions? What deliverables (items the contractor presents to a client for review and approval) are being produced? What, aside from the deliverables, must happen administratively (project management) in terms of progress reporting, time tracking, and other communications.
• Add Location. This optional section describes where the work will be performed (if relevant).
• Include a Time frame. This optional section specifies the total time allowed for project completion, the maximum billable hours per time period, and specific times for formal reviews or other project milestones.
• Set down the Schedule. This section states what tasks should be completed by what date/time, and who is responsible for making that happen. Descriptions of tasks and results (primarily deliverables) should be detailed, unambiguous and straightforward so they are easy to understand. Aside from deliverables, the schedule might contain entries for Quality Assurance Testing, Consumer Testing, and Progress Reports. While the schedule should be specific, don’t focus on the “How” as that can put too many hurdles in front of successful project completion. A basic description of the required methodology to be used is sufficient. The Schedule often incorporates details of acceptance criteria (to measure the quality of the outcome) and payment milestones (usually upon acceptance of key deliverables), though these can be described in a different, separate section.
• Include a section on Deliverables. This section describes the mechanism for how the parties will determine whether the product or service is acceptable. The criteria can range from measurable quality standards to a specified number of tests, but in any case must lend itself to objective evaluation.
• Specify the Standards. This section describes any industry standards that must be met to fulfill the contract. Rather than physically reproducing the industry standards in the SOW, specifically referencing a set of standards is sufficient.
• Include any Workforce Requirements. This section specifies any special workforce requirements, e.g., number of employees staffing the project, education requirements (degrees or certifications).
• Note the Price. This section addresses the question of “How Much?” Is the payment a fixed fee? How do expenses/costs factor in? Will the payment be made as a lump sum or in installments? What is the payment schedule? Are there payment milestones?
• Include any Assumptions. Most projects are permeated by various unknowns, for which the parties must make a variety of assumptions. In essence, assumptions are the conditions which the contractor expects will exist in order to complete the project in accordance with the terms of the SOW. For example, the contractor might assume that its employees will be granted access to the
  client’s computer network in order to install the deliverable software. The Assumptions section should identify as many such assumptions as possible and set forth a contingency plan or the consequences in the event that any assumptions fail.
• Include parameters for Project Management. This section describes the process for monitoring the project’s progress. Include items such as: Weekly Meetings, Regular Status Reports, Regular Progress Reports, and Project Management Team Meetings. This section also is a good place to describe any additional obligations which might flow from the project, such as maintenance and repair after the initial design and/or installation.