← Previous lessonFree lesson 2 of 3 · lesson 2 of 49Next lesson →

Unlock all 49 lessons of Project Progress Measurement and ReportingFull course ₹40,000 · paid

Price & syllabus
Free lesson · 18 min · no payment

Plan Phase: Statement of Work, WBS and RACI Matrix

A free lesson from Skill-Lync's Project Progress Measurement and Reporting course, on Grow by Skill-Lync · Last updated 16 Nov 2026 · Session: “Week 1 Session 2”

What will you learn in this free Project Progress Measurement and Reporting lesson?

The instructor explains what the plan phase includes and why it sets the baseline for progress reporting. The lesson covers the statement of work, three ways to build a work breakdown structure (a two-tower residential example is used for top-down), and the RACI responsibility assignment matrix.

  • Purpose of the statement of work
  • Top-down, bottom-up and template WBS
  • Two-tower residential WBS example
  • Reading a RACI chart

What comes after lesson 2?

The next free lesson is lesson 3, “Network Diagrams, Gantt Charts, Resource Plans and Budget Control” (31 min). Later in Skill-Lync's Project Progress Measurement and Reporting course (paid): lesson 4, Week 1 Session 4; lesson 5, Week 2 Session 1; lesson 6, Week 2 Session 2. The full course has 49 lessons (19 h 34 min of video); see the course overview or its price and syllabus.

Lesson transcript

Machine transcript of the lesson audio (lightly cleaned). Technical terms may contain errors; the video is the reference.

Now we will learn about what is plan phase. So plan phase, it includes statement of work, work breakdown structure, responsibility assignment matrices, project schedule, resource plans and histograms. So we will learn one by one. Plan phase also includes pre-start estimates, budgets, COC, COC means cost of construction, risk management plan, communications plan, QHSE, Q stands for quality, H as in health, S as in safety, N as in environment plan. So QHSE plan. Then verification and validation plan. So what is the significance of this plan phase? A plan phase provides an effective communication tool to understand the project goals and the means to achieve them. It also defines the outcomes, results and whatever commitments have been made by a team. It establishes guidelines and standards which needs to be followed while executing every activity while monitoring and controlling them. So these guidelines and standards must be followed.

It sets the baseline for evaluating and reporting progress. So baseline will be set to measure the project health in terms of cost and time. It will be done with the help of plan phase. It forms the basis for scope control and change management. So with the help of plan phase. So we will ensure that scope is not beyond or the activities are done as per the specifications and whatever change is happening or whatever change is incurring at project, it needs to be recorded as per the standard procedure which is mentioned in the plan phase.

Now we will learn about statement of work. So what is the purpose of statement of work. So the purpose is it is to define the scope of the project to set and establish customer expectations, act as a contract or agreement if required to set the purpose or goal of the project to identify the various stakeholders like client, customer and end user of the project. So what is the purpose of statement of work also helps to answer the following. So what is the purpose or goal of the project? What are the objectives behind the project? Why is the project being done? What is its motto? Who is the initial customer or client or end user? Who is the end user or final customer? What are the customer deliverables or outcomes or services? What technical support is required for all those product services and deliverables? What is the budget?

SOW also helps in answering what is the budget? What is the budget? What is the final date for the deliverables? What are the measurable success indicators metrics? What kind of support is required from the customer? What contingency plans are in place if there is any risk or any you know any critical condition is there situation is there? So how do we mitigate that? So it also includes in the SOW. So SOW includes statement of work includes customer, project, project, title of the project, purpose of the project, and background. It also includes all the deliverables, products, or services, measurable success indicators by which we will evaluate the project success. It includes customer support and risk mitigation plans. Now we will learn about work breakdown structure. So what is work breakdown structure? As I told you earlier, a work breakdown structure is a project management tool that takes a step-by-step approach to complete large projects by breaking down the project scope by breaking down the project scope into very smaller components. So it is a hierarchical decomposition of the total scope performed by the project team to achieve the project objectives and create the required deliverables. So it is known as work breakdown structure. It is a hierarchical decomposition. In the right you can see a chart. So at the top it is a project. Then it is divided into phase 1.1, then 1.2 deliverable, then subproject 1.3, then subproject 1.4. Then further it is divided into into various work packages if you can see. Deliverable 1.1.1. So this is our work scope of a total scope of a project is decomposed into various work packages. So that the resource timeline can be assigned to it and we can execute that project. So its function is to break and divide the scope of the work into smallest possible manageable parts that relate to key deliverables, milestones, and phases. It defines and facilitates the communication of cost, budget, schedule, timelines, quality, quality, and resource performance data to all stakeholders. A proper breakdown structure links the components of cost estimates and activities of the schedule, which will help in making the feasible schedule and a budget.

It also assists the project team and transitioning the plan into the schedule. Work breakdown structure provides the basis for all project reporting. It includes the collection and monitoring of data and forecasting of cost and schedule trends. It provides a framework to define each specific element for which schedules will be developed. The work defined at the lowest level of the work breakdown structure for which cost and durations are estimated and managed are known as work packages. So project manager always gives a very high importance to work breakdown structure. So what is it and why is it needed? In simple terms, as I told you earlier also, it is a hierarchical depiction of all the tasks.

The tasks that must be done to complete a project. The tasks at the lowest hierarchical level define units of work that can be defined and whose time, cost, and resource requirements can be accurately calculated and this will give you a resource plan, this will give you activity schedule, this will give you an activity cost, and finally the budget. So there are essentially three ways to create a work breakdown structure. Those are the basic techniques. So first one is top-down, bottom-up, and template based. So guys, what is top-down approach?

So top-down approach is it generates a complete and more accurate WBS. So in this top-down approach, the WBS is derived by decomposing the overall project into sub-projects or lower-level tasks. This decomposition is based on general project characteristics and not on detailed design elements. The decomposition continues until the tasks or work units reach a level where they can be accurately defined and estimated. This approach is by far more popular than the other approach which is bottom-up approach. Why? What is the reason behind this? Because it is more logical.

It is only rational to first define a solution to a problem and then dissect the solution into steps required to implement them. So it is a logical process. So the natural working is to first start with a broad approach to a problem and then repetitively and iteratively narrow it down to very specifics. So if you see a chart on this slide, you will get an idea of what this WBS is. So suppose there is an A type of project, project A. So it will be divided into two parts.

So it is a residential project which consists of two towers, tower 1 and tower 2. So your project A will be divided into two components, tower 1 and tower 2. Now we will break tower 1 and tower 2 into their respective activities. So tower 1 is divided into civil, finishing, electrical and plumbing. Similarly, tower 2 is also divided into these four activities, civil, finishing, electrical and plumbing. So this is the basic model. You can further divide the civil, finishing, electrical, plumbing into various other activities. Like in civil, we can divide it into substructure, superstructure.

Finishing, we can divide it into block work, flooring works, doors, windows, electrical, shaft, conduiting, wiring, then plumbing, piping, shaft works, flat works. So this is how our WBS is prepared. So we have explained the top down approach. Now we will see what the bottom down approach is. So the bottom down approach is more of a brainstorming exercise. You know, where all the team members and stakeholders are involved and asked to make a list of lowest level tasks which are required to complete a project. In many instances, this can turn quite messy or chaotic if the tasks identified by the team are not all at the same level.

There may be confusion. It is also time consuming to ensure that all the tasks at a given level have been completely identified. So this bottom down approach is resource intensive since it assumes that all members of the team have sufficient expertise or domain knowledge and a complete understanding of the project requirements. And they are able to be able to identify and integrate tasks at different levels. So this is just an assumption based. So the biggest disadvantage in bottom up estimating is that almost always more than a few low level tasks are unintentionally skipped or deleted.

So many times we team members skip the some lowest level tasks because team members are either not knowledgeable to all parts of the project. Suppose an expert who is an expert in a finishing or in a MEP or electrical, he won't be able to identify the lowest task which is involved in the structure or RCC. I will not recommend at least the bottom sub approach unless the WBS is created by a group of experts who have a very detailed knowledge of the project and its decomposed elements.

Like it should be done by an expert who is very well aware of the complete project. Either it is electrical or it is plumbing or it is finishing or it is RCC. Third one is templates based. So the template based it is a technique which is based on some standard template templates of WBS which are used in an organization. Now we will learn about responsibility assignment matrix which is also known as RAM. So this matrix is a grid that shows the project resources assigned to each work packages which are defined by the WBS.

chapter 4 25 26 26 Our RACI chart is a common way of showing stakeholders who are responsible, accountable, consulted or informed and are associated with project activities, decisions and deliverables. So why we use this responsibility assignment matrix? So it is very important part of project management. So it is required because it ensures that all the tasks which are involved are assigned to the right people and the right time. It also shows the level of involvement of people working to achieve the desired results. So suppose there are many activities, there are n number of activities.

So to perform those activities, it is very important for a project manager to assign the right person on the job and at that too at the right time. So he will be solely responsible for certain roles and responsibilities to execute that activity. And he can perform better because he is having expertise and domain knowledge for that particular activity. If you deploy some other resource and that too at an improper time, then it will lead to delays, over budgeting, that's all. If you can see this right side chart, it is a RASI chart.

So what do you mean by RASI chart? So it is R stands for responsible, who works on actually. A stands for accountable. C stands for consulted. I stands for informed. And Q stands for quality reviewer. So these are the team members. If you can see on the top, Jeff, Michael, Reto. So you yourself consider Alex, Anna, Bill. These are the different stakeholders. And the activities are in the column. Planning and schedule, risk management, quality management, procurement. Under procurement, first is specifications listing. Second is site requirements.

Third one is calls for tenders. Budget approval. Then contract negotiations. So if you see first activity, planning and schedule. So who is the responsible who will prepare this planning and schedule? It will be Jeff. Michael will be accountable for that. Like he also will be responsible. But more responsible will be Jeff. Then it will be for information. It will be given to Reto. Okay. And you yourself and Felix will be consulted. Like you will act as a consultant. You will advise them. But the responsibility lies with the Jeff.

And accountability with Michael. Similarly, in risk management, the responsibility lies with the Sue. And accountability is with Fred. And who all will be informed? Michael and Reto. And quality reviewer will be you yourself. Similarly, quality management, procurement. You can see the list goes on. So this is how a RASI chart is prepared. So a responsibility assignment matrix. It actually describes the participation of various organizations, people and their roles in completing tasks or deliverable for a project. So it's used by the program manager or project manager in clarifying roles and responsibilities in a cross-functional team, projects and processes.

So it is very widely used in project management as a communication tool to ensure that all the work tasks are designated to a responsible team member. It can define that what a project team is responsible for within each component of the work breakdown structure. It could also be used within a working group to designate or depute roles, responsibilities and levels of authority for specific activities. The matrix format shows all activities associated with one person and all people associated with one activity. This ensures that there is only one person accountable for any one task to avoid the confusion.

Now we will see what the project schedule is. So basically a schedule is a model for executing the project activities including duration, dependencies and other planning information. It results from the project plan. So schedules are developed at various points and various stages in the planning process. They are prepared and maintained to track, monitor and report progress, forecast, work progress and completion. They are used to monitor and control the successful execution of the project. So why it is required? Because it determines if the requested completion date is feasible.

Or it also states that the required intermediate milestone dates are feasible or not. It identifies the start and completion dates of all the activities and also the intermediate milestones. It determines the logical sequence of the activities. So in schedule the activities are sequenced by a logical way. It also facilitates resource loading and its allocation. So with the help of schedule, all the resource can be assigned and allocated to a particular activity. It tracks the progress by setting up a baseline first and then tracking with actual dates.

So if you have prepared a schedule, so what we do? We prepare a schedule. Then what we do? We start tracking it against the baseline which has been set in the initial stage. So it helps us to track the progress against the baseline dates. So you will come to know that whatever you have planned in the baseline schedule, where you are at present. So what are the steps which are involved in schedule preparation? So the first step is we define the schedule activities which are required to complete the project.

Like we list out all the activities which are required to complete the project. Then we sequence all the activities in a proper order. Then next step is to link all the sequenced activities with logical relationships. We link them with the proper relationships. Like there are four relationships. SS which is start to start. FF finish to finish. SF is start to finish. And then FS finish to start. So what is SS? So when in predecessor, there are two activities. Predecessor and next upcoming is called successor activity.

If your predecessor activity start is directly linked with the start of successor activity, then this relationship will be start to start. Finish to finish relationship means that by the finish of your predecessor activity, your successor activity should also be finished. Like activity 1, completion date is 31st January. Then the completion of activity 2 which is successor is also is 31st January if you have provided the finish to finish relationship. Next is start to finish. The start to finish is start of your predecessor activity will depend on finish of your successor activity.

The last one is finish to start. It means that your successor activity will start only after the finish of your predecessor activity. Like example of activity 1 and activity 2. Activity 1 is predecessor and activity 2 is successor. So suppose activity 1 is getting completed on 15th of January 22. Then it is mandatory that the activity 2 will start after the 15th of January because we have linked with finish to start. Then we estimate the resources required for the execution of all activities and assign and allocate those resources to all the activities.

So I will tell you there are some types of schedule which are used in our projects. One is pre-construction schedule. So it involves all the pre-construction activities and their completion timelines. So another one is milestone schedule. So it presents major milestones with plan dates and their completion dates. Then comes your major project schedule. So it presents linked activities with plan dates, duration, milestones and resources. Next one is your baseline schedule which is done at the pre-planning stage. So it is derived from to meet the project execution plan and all other schedules are measured against this baseline schedule.

Then comes your catch-up schedules, 4-week look ahead, weekly. So these are some frequently used schedules which are used to monitor and report the progress. And these are measured against your baseline schedule.

Want the rest of Project Progress Measurement and Reporting?

Get the full course syllabus and fees.

The full course is paid (₹40,000). We'll send the syllabus and call you back within one working day.

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.

Full course · paid

Unlock the full Project Progress Measurement and Reporting course

The remaining 46 lessons, mentor-reviewed projects and a certificate come with the paid course (₹40,000). Leave your details: we'll send the syllabus and fees and call you back.

Get the syllabus and fees

A counsellor calls you back within one working day.

By submitting you agree to our Terms and Privacy Policy.

Grow by Skill-Lync · free lesson

Start watching

Free, no payment. Leave your details once and every free lesson on Grow plays straight away. A Skill-Lync counsellor may call you about the full Project Progress Measurement and Reporting course.

By submitting you agree to our Terms and Privacy Policy.

Talk to a career counsellor

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.