In the process of becoming a property developer, you will need to become familiar with what a Scope of Work is, as it's a crucial part of the development process.
If you think of it like baking a cake, then you start out with a list of ingredients you need. Sounds simple, right? And it is, up to a point. But a good Scope of Work is MUCH more than just the ingredients.
Continuing with the cake analogy, a list of ingredients is certainly the starting point. But where do you find the recipe? A recipe book? A website? And then there's the directions for how to prepare the ingredients in the right way so that you end up with a delicious cake.
Once you start expanding your horizons a little, you soon see there's a lot more to baking a cake than the ingredients. That's when you can start to understand what a Scope of Work means in the development space.
In essence, a Scope of Work outlines the specific tasks, activities, deliverables, and expectations for a particular project. It describes what needs to be accomplished, and the development project's parameters. It can range from very simple to extremely complex.
As a property developer, you need to use a Scope of Work in every situation where you're asking for quotes, be it from a builder or individual trades and consultants. After all, if they don't know what you need them to do, how can they possibly give you an accurate idea of what it's likely to cost to do it?
As I said earlier, a Scope of Work can vary enormously in complexity, depending on who you're preparing it for, but there are some elements which are fairly universal and should be included. Let's take a look at those now.
Project Overview
There's a parable that's been in existence for hundreds of years, known as the story of the three bricklayers. I highly recommend you read it if you want to understand the value of big picture thinking!
At a bare bones level, three bricklayers are asked why they're laying bricks. The first says he's a bricklayer, laying bricks to feed his family. The second says he's a builder, building a wall. The third says he's building a cathedral. One task, three different visions of what that task will achieve.
Include an overview of what the project aims to achieve, and follow that up with identification of the parties involved in the development project, such as the client, contractors already on board and any other stakeholders.
Project Goals and Objectives
While the big picture is key as a starting point, it's also important to outline goals and objectives for your development project. There's plenty of information out there about the best ways to set goals, but as a bottom line you need specific, measurable, and achievable goals and outcomes.
Detailed Description
This is where you get down to the nitty gritty - a comprehensive description of the work to be performed, including the specific tasks, activities, and phases. This should include information about any site specific conditions.
Deliverables and Outcomes
In this section you detail all the tangible results the work should produce. When it comes to a development project, it's likely the outcome is going to be something being built or installed, but could also include things such as a report that's needed as part of the property development process.
More broadly, this can also include a description of quality and performance standards that must be met. Depending on the work, you might also need to reference any industry or regulatory standards that are relevant to the project.
Schedule and Budget
It's also important to include both the schedule and budget for the project. Depending on what the Scope of Works is for, this type of information is necessary when it comes to determining liquidated damages claimed for a project that runs well overtime. It can also be used to offer bonuses for works that are completed early or under budget.
More specifically, you need to indicate when specific tasks or phases are expected to be completed, with all milestones and deadlines clearly defined. Also include details on the budget, cost estimates, and any financial constraints or considerations.
This section may also specify how changes to orders and variations in costs will be managed, including change request procedures and associated costs.
Roles and Responsibilities
This one's possibly not necessary for a small Scope of Works, but in a bigger development project with lots of moving parts, it's important to identify the roles and responsibilities of all project team members, including the client, project manager, contractors, and subcontractors.
As part of that, include an outline of decision-making authority and communication processes. Again, depending on the project, you might also want to include information around:
Acceptance Criteria
Another one that is probably more relevant for larger projects, but list the criteria that will be used to determine if the project is successfully completed and meets your expectations.
So to sum up, a Scope of Work is a crucial document in project management because it provides a clear and comprehensive understanding of the project's requirements, objectives, and expectations. It serves as a reference point for all stakeholders, helping to prevent misunderstandings and disputes. It is often used as a basis for project contracts, and any changes to the scope of work should be documented and managed through a formal change control process.
In other words, it helps you bake an awesome cake!
If you think of it like baking a cake, then you start out with a list of ingredients you need. Sounds simple, right? And it is, up to a point. But a good Scope of Work is MUCH more than just the ingredients.
Continuing with the cake analogy, a list of ingredients is certainly the starting point. But where do you find the recipe? A recipe book? A website? And then there's the directions for how to prepare the ingredients in the right way so that you end up with a delicious cake.
Once you start expanding your horizons a little, you soon see there's a lot more to baking a cake than the ingredients. That's when you can start to understand what a Scope of Work means in the development space.
In essence, a Scope of Work outlines the specific tasks, activities, deliverables, and expectations for a particular project. It describes what needs to be accomplished, and the development project's parameters. It can range from very simple to extremely complex.
As a property developer, you need to use a Scope of Work in every situation where you're asking for quotes, be it from a builder or individual trades and consultants. After all, if they don't know what you need them to do, how can they possibly give you an accurate idea of what it's likely to cost to do it?
As I said earlier, a Scope of Work can vary enormously in complexity, depending on who you're preparing it for, but there are some elements which are fairly universal and should be included. Let's take a look at those now.
Project Overview
There's a parable that's been in existence for hundreds of years, known as the story of the three bricklayers. I highly recommend you read it if you want to understand the value of big picture thinking!
At a bare bones level, three bricklayers are asked why they're laying bricks. The first says he's a bricklayer, laying bricks to feed his family. The second says he's a builder, building a wall. The third says he's building a cathedral. One task, three different visions of what that task will achieve.
Include an overview of what the project aims to achieve, and follow that up with identification of the parties involved in the development project, such as the client, contractors already on board and any other stakeholders.
Project Goals and Objectives
While the big picture is key as a starting point, it's also important to outline goals and objectives for your development project. There's plenty of information out there about the best ways to set goals, but as a bottom line you need specific, measurable, and achievable goals and outcomes.
Detailed Description
This is where you get down to the nitty gritty - a comprehensive description of the work to be performed, including the specific tasks, activities, and phases. This should include information about any site specific conditions.
Deliverables and Outcomes
In this section you detail all the tangible results the work should produce. When it comes to a development project, it's likely the outcome is going to be something being built or installed, but could also include things such as a report that's needed as part of the property development process.
More broadly, this can also include a description of quality and performance standards that must be met. Depending on the work, you might also need to reference any industry or regulatory standards that are relevant to the project.
Schedule and Budget
It's also important to include both the schedule and budget for the project. Depending on what the Scope of Works is for, this type of information is necessary when it comes to determining liquidated damages claimed for a project that runs well overtime. It can also be used to offer bonuses for works that are completed early or under budget.
More specifically, you need to indicate when specific tasks or phases are expected to be completed, with all milestones and deadlines clearly defined. Also include details on the budget, cost estimates, and any financial constraints or considerations.
This section may also specify how changes to orders and variations in costs will be managed, including change request procedures and associated costs.
Roles and Responsibilities
This one's possibly not necessary for a small Scope of Works, but in a bigger development project with lots of moving parts, it's important to identify the roles and responsibilities of all project team members, including the client, project manager, contractors, and subcontractors.
As part of that, include an outline of decision-making authority and communication processes. Again, depending on the project, you might also want to include information around:
- identification of potential risks and how they will be managed or mitigated
- contingency plans and strategies for handling unexpected issues
- safety protocols and requirements that must be followed to ensure a safe working environment
Acceptance Criteria
Another one that is probably more relevant for larger projects, but list the criteria that will be used to determine if the project is successfully completed and meets your expectations.
So to sum up, a Scope of Work is a crucial document in project management because it provides a clear and comprehensive understanding of the project's requirements, objectives, and expectations. It serves as a reference point for all stakeholders, helping to prevent misunderstandings and disputes. It is often used as a basis for project contracts, and any changes to the scope of work should be documented and managed through a formal change control process.
In other words, it helps you bake an awesome cake!
