PROJECT OVERVIEW

This project involves the design and development of [PROJECT] for use by [Client Name]. A brief outline of the project here might outline the problems to be solved and overcome, as well as explain how the new project will improve or solve the current issue in hand.

The scope and tasks required to complete this project will follow the timelines outlined within in order to deliver the components at the associated costs listed. 

PROJECT OBJECTIVES 

This project has been proposed to achieve the following objectives:

OBJECTIVE 1: What standards must the new project fulfil?

OBJECTIVE 2: What functions must the new project have?

OBJECTIVE 3: How can the success of the project be measured?

PROJECT SCOPE

The previous page aimed to set the scene with a wide introduction to the project, and by contrast the project scope aims to narrow this down into exactly what will be delivered, along with a task list breaking down what has to be done into comprehensible steps.  The project scope should be as detailed as possible for stress free project management and to prevent runaway or scope creep.  It is extremely common for clients to ask for more at later stages of a project, so if a task or project element is not listed in the original scope then it gives you grounds to charge for the work.

Below is set out the project scope of [PROJECT NAME] as follows:

1. PRIMARY AIM

Here set out the primary aim of the project or the most pressing matter. When the project is fully complete, what will the client have and how has it been designed to fully meet its requirements?

2. SECONDARY AIM

Break down the primary aim further, so if the overall project is to achieve an aim, or fulfill a need, what features need to be built to complete the project? List everything here and ask your client to check nothing has been missed.

3. TERTIARY AIM

This final aim may list checks for the finished project, and/or list ongoing support options available for the client after the project is finished if applicable.

PROJECT TASKS

A project task list allows you to methodologically lay out and describe to your client exactly what work you will have to do, in a step by step fashion, in order to pull off the project successfully.  A complete task list will give clients insight into the work that goes on behind the scenes and also is instrumental for you in justifying your fees for the project.

The tasks required to achieve the scope as described above are as follows:

TASK 1: DESCRIBE THE FIRST MAJOR TASK

What is the first logical step you must take in order to produce work that will move the project along to the middle stage?  After this task, you might need to seek client sign-off and/or invoice settlement from your client before you move on to the next stage.

TASK 2: LEAD ON TO THE SECOND MAJOR TASK

This second major task should represent up to around 70% of the work that you plan to undertake.

TASK 3: THE FINAL MAJOR TASK

What is the final 30% of work that you must do to get the project finished and your client left smiling?

ADDITIONAL OPTIONS

The scope of this project are limited to the above listed items and tasks. Any additional items will be counted as out of scope, and may only be added with separate authorisation and approval from [CLIENT]. 

Extra items may only be added through the use of separate SOWs.

DELIVERABLES

Deliverables will refer to items that the client will receive from you at key stages of this project. They may consist of plans, draft versions of the final project or specifications. 

After sending a deliverable, you will probably to seek sign-off and/or invoice settlement from your client before you move on to the next stage. 

During a project, if the client knows what deliverable is to be expected next, they will be able to follow the project and likely bring forth fewer objections or amendments.

DELIVERABLE 1: DESIGN PLAN

The first stage of any project is generally a plan of what will be built, coded or constructed. Great attention to detail at this stage ensures fewer questions or problems further down the line.  

DELIVERABLE 2: DRAFT VERSION OF THE PROJECT

With an exceptional plan in the bag, development can start on the project. When a draft version is ready, you can present this to the client and proceed to the final and/or test stages of the project.

DELIVERABLE 3: FINAL VERSION OF THE PROJECT

Once the client has signed off the final version, settled any outstanding invoices and is generally happy and satisfied, it's time to deliver the final components.  It is critical to organise beforehand exactly how the project will get wrapped up. This helps manage your client's expectations, and secondly, avoids conflict at this final stage (when impressions are long lasting)!

COMPONENTS

Components are normally essential items that you must deliver to your client to make everything work and hang together.

It may be useful to spread the delivery of components so that a) your client is not overwhelmed and b) so that you can hold something back to guarantee your invoices are settled. Some examples are below:

COMPONENT 1: USER DETAILS

With the best system in the world, without Account/Login details, Passwords, or Access Codes absolutely nothing can be done

COMPONENT 2: SECURITY / AND OR BACKUP

How will your product/ system / design be protected? How often will it need updating or maintenance? Are there any guarantees?

COMPONENT 3: TRAINING DOCUMENTS

If you are able to deliver bespoke training or instructions to your client on how to use the product you have delivered for them, those feelings of excellent customer service will grow exponentially and boost the chances of your company receiving a glowing review.

PROJECT ASSUMPTIONS

Here you should flag up to your client any assumptions you have made in order for the project to go ahead.

This step is a crucial aspect of any carefully planned project and allows foresight for any problematic areas.  This is also a great way to clarify communication, as there may be assumptions that your client (or indeed that you) have not thought about and need adding. 

Needless to say, it's also vital that your client sees and agrees to these. Here are a few assumption examples.

• You will provide digital sign off for each listed stage when required to do so before the project may continue.
• The client will provide necessary material (written or otherwise) that you require for the project's completion.
• Location access, materials or equipment will be available when required
  
• Etc...

KEY MILESTONES

Making a plan like this is just as much in your favour as it is for your client. Putting key milestones in clarifies the stages the project will evolve through and will be critical to refer to.

We have drafted the below schedule for this project and its relevant stages:

FINAL COSTS & INVOICE SCHEDULE

An outline of the costs for the design, development and testing of the site is estimated here followed by the total:

ADDITIONAL NOTES 

This estimate is based on [COMPANY NAME'S] current understanding of the Project Scope and Tasks as well as the Deliverables and Components set out in this Statement of Work.

All invoices are inclusive of 12.5% VAT

All invoices are due and payable within <X> days of receipt by [CLIENT NAME]

ACCEPTANCE

To accept the conditions set out in this Statement of Work,
simply type your name below. 

We look forward to working with you on [PROJECT NAME].