A Statement of Work is a document which shows the understanding between a contractor and a client.The SOW spells out the specific services to be delivered, the time in which those tasks and services will be performed, and the amount and due dates for payment.It is intended to serve as a road map to the project and document the expectations of the parties.It should be a description of why, who, what, how, when, and how much.
Step 1: Before starting work, write the SOW.
After the core contract negotiations are done, the SOW is usually created.Negotiations may continue after the work has begun and the SOW is not finalized until the project is well underway.
Step 2: The SOW format needs to be researched.
Different industries and projects have different deliverables, so there is not a single standard SOW.A custom SOW is a good one.
Step 3: Get it right the first time.
A Change Order is a side agreement that can be used to modify the terms of the SOW.A blank Change Order form is a good idea.Change orders can increase the project cost.A well-written SOW can help reduce the need for a change order.No client wants to be in a position where his or her expectations are not known, which can lead to delays, an increase in total cost, or dissatisfaction.
Step 4: The objective should be included.
It is a high-level overview of the project and its objectives.General descriptions are acceptable when drafting the "bird's-eye-view" of the project, but avoid language that could be interpreted in more than one way.Accurately describe objectives that can be accomplished in the specified time frame.
Step 5: Discuss the Scope.
No options or alternatives are provided in this section of the "What?" and "How?"How will it be done?What will not be accomplished is often what is not the work.What are the assumptions?What items the contractor presents to a client are being produced?Administratively, project management must happen in terms of progress reporting, time tracking, and other communications.
Step 6: If possible, add location.
If relevant, this section describes where the work will be performed.
Step 7: A time frame is required.
The total time allowed for project completion, maximum billable hours per time period, and specific times for formal reviews are included in the optional section.
Step 8: The schedule needs to be set down.
What tasks should be completed by what date/time is stated in this section.It is important that the descriptions of tasks and results are easy to understand.There are entries for Quality Assurance Testing, Consumer Testing and Progress Reports on the schedule.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 description of the required methodology is enough.Details of acceptance criteria and payment milestones can be described in a separate section of the schedule.
Step 9: There should be a section on Acceptance.
The mechanism for determining whether the product or service is acceptable is described in this section.The criteria can range from measurable quality standards to a specified number of tests, but in any case must lend itself to objective evaluation.
Step 10: The standards must be specified.
Any industry standards that must be met to fulfill the contract is described in this section.It's not necessary to physically reproduce the industry standards in the SOW.
Step 11: Any workforce requirements should be included.
There are any special workforce requirements listed in this section.
Step 12: You should note the price.
The question of how much is addressed in this section.How do costs factor in?Will the payment be made in installments or as a lump sum?What is the payment schedule?Is there a payment milestone?
Step 13: Any Assumptions should be included.
The parties have to make a variety of assumptions for most projects.The contractor expects certain conditions to exist in order to complete the project in accordance with the terms of the SOW.The contractor might assume that its employees will be granted access to the client's computer network in order to install the software.The consequences of any assumptions that fail should be set forth in the contingency plan section of the Assumptions section.
Step 14: You should include parameters for project management.
The process for monitoring the project's progress is described in this section.Weekly meetings, regular status reports, and project management team meetings are included.Maintenance and repair after the initial design and installation can be described in this section.