Project Management

Please login or join to subscribe to this thread

Method Statement in PMBOK 7: Artifact, Method, or Hybrid Process? — A Project Manager’s Perspective

linkedin twitter facebook   Construction   Quality  
avatar
Aleksandar Loncar Niš, Serbia

Hello,

I have a question regarding the PMBOK Guide and Method Statements in construction projects.

I have extensive experience preparing Method Statements for construction activities. While reviewing the PMBOK Guide, 7th Edition, I noticed that the term “Method Statement” is not explicitly defined or discussed.

From the PMBOK perspective, how should a Method Statement be understood and classified, and how does it fit within the PMBOK framework?

I would particularly appreciate perspective of PMPs and other Construction Project Managers regarding how such a construction-specific document relates to the broader PMBOK approach.

Thank you.

Aleksandar Lončar

Site / Construction Manager

Civil Engineer

Sort By:
< 1 2 3 4 >
avatar
Aleksandar Loncar Niš, Serbia
Oct 28, 2026 11:22 AM
Replying to Luis Branco
...
Thank you, Aleksandar. Your clarification and the Rev. 01 example make the practical contribution of Phase Analysis much clearer.

I agree that classifying a Method Statement as an artifact does not, by itself, explain its operational, control and evidentiary functions over time. Nor should it be expected to. The classification identifies the nature of the documented output, while the other perspectives help us understand how it is developed, used and connected to project execution.

Your example adds an important temporal dimension: establishing which version was applicable at a particular point, when it was approved and how it relates to the corresponding execution and inspection records.

I would add one distinction. Approval, applicability, communication, actual use and demonstrated compliance are related, but they are not necessarily equivalent. Even when a revised Method Statement is approved before an activity begins, we still need to establish whether the applicable requirements reached those performing the work and whether the available evidence supports the conclusion that they were followed.

This also relates to your five elements of the document's dynamic nature. Development, application, revision, alignment with execution and archival value provide a useful basis for examining its evolution. Importantly, alignment with actual execution needs to be assessed throughout the work, rather than assumed to result from revision.

For me, this strengthens the practical value of a temporal perspective. Whether Phase Analysis is best understood as a separate dimension or as an approach operating across Workflow, Function and Relational Analysis remains open. Its usefulness does not depend on resolving that question immediately.

Perhaps the most productive test is whether Phase Analysis helps us identify and explain gaps between the applicable methodology, the decisions and communications surrounding it, and the execution that the available evidence allows us to establish, particularly when these elements evolve at different times.

I look forward to seeing how you develop this perspective further.
Thank you, Luis, for your thoughtful response and additional observations.

My intention with Phase Analysis is primarily to establish a conceptual framework for understanding how the position, role, and functions of a Method Statement evolve throughout the project life cycle.

Within this framework, the Method Statement:
- Is developed as an output of a particular process.
- Becomes an input to other processes.
- Serves as an operational and control document during project execution.
- May be revised and adapted to changing project conditions.
- Retains archival evidentiary value after the completion of the works.
These elements represent the main focus of my Phase Analysis.

I agree that examining whether an approved methodology was actually implemented and verified is a valuable practical application of this perspective.
From your response, I understand that it is important to track five different things:
- When the methodology was approved.
- When it became applicable.
- When those performing the work were informed.
- When it was actually implemented.
- When and how its implementation was documented.
These are relevant questions, but they belong to a more detailed level of analysis — execution control, document management, and compliance of documents.

My subject of analysis is the evolution of the document's role over time, rather than proving that the works were executed in accordance with it. Other project documents, reports, and records should provide evidence of this.
...
2 replies by Aleksandar Loncar and Luis Branco
Oct 30, 2026 9:05 AM
Aleksandar Loncar
...
At this stage, I have not identified a better practical example than the Rev. 01 example presented in my previous comment. However, I intend to continue exploring other examples that may further demonstrate the value of Phase Analysis.
Oct 30, 2026 10:14 AM
Luis Branco
...
Thank you, Aleksandar. Your clarification helps distinguish the conceptual purpose of Phase Analysis from its possible applications in execution control. Following that scope, I would explore how changes in the document’s role relate to changes in its content.

The same approved version may guide execution, serve as a reference for inspection and later remain part of the project archive without requiring revision. Some of these functions may also coexist. Its role can therefore evolve even when its content remains stable.

Meanwhile, execution and inspection records may accumulate separately. They can provide information that prompts a review of the Method Statement, but a review does not necessarily require a revision. For example, a recorded deviation might call for correcting the work to follow the approved method, or reveal a reason to reconsider the method itself.

This suggests a useful distinction between the Method Statement serving as an input to a process and other documents providing inputs to its review and possible revision.

Regarding your additional comment, a complementary example to Rev. 01 could follow an approved Method Statement that remains unchanged while its uses and relationships with execution records evolve. Comparing these situations could illustrate how Phase Analysis addresses both continuity and change.

Would that comparison fit your intended framework? It could help clarify when the document itself changes, when its role changes, and how those developments interact.
avatar
Aleksandar Loncar Niš, Serbia
Oct 30, 2026 8:45 AM
Replying to Aleksandar Loncar
...
Thank you, Luis, for your thoughtful response and additional observations.

My intention with Phase Analysis is primarily to establish a conceptual framework for understanding how the position, role, and functions of a Method Statement evolve throughout the project life cycle.

Within this framework, the Method Statement:
- Is developed as an output of a particular process.
- Becomes an input to other processes.
- Serves as an operational and control document during project execution.
- May be revised and adapted to changing project conditions.
- Retains archival evidentiary value after the completion of the works.
These elements represent the main focus of my Phase Analysis.

I agree that examining whether an approved methodology was actually implemented and verified is a valuable practical application of this perspective.
From your response, I understand that it is important to track five different things:
- When the methodology was approved.
- When it became applicable.
- When those performing the work were informed.
- When it was actually implemented.
- When and how its implementation was documented.
These are relevant questions, but they belong to a more detailed level of analysis — execution control, document management, and compliance of documents.

My subject of analysis is the evolution of the document's role over time, rather than proving that the works were executed in accordance with it. Other project documents, reports, and records should provide evidence of this.
At this stage, I have not identified a better practical example than the Rev. 01 example presented in my previous comment. However, I intend to continue exploring other examples that may further demonstrate the value of Phase Analysis.
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
Oct 30, 2026 8:45 AM
Replying to Aleksandar Loncar
...
Thank you, Luis, for your thoughtful response and additional observations.

My intention with Phase Analysis is primarily to establish a conceptual framework for understanding how the position, role, and functions of a Method Statement evolve throughout the project life cycle.

Within this framework, the Method Statement:
- Is developed as an output of a particular process.
- Becomes an input to other processes.
- Serves as an operational and control document during project execution.
- May be revised and adapted to changing project conditions.
- Retains archival evidentiary value after the completion of the works.
These elements represent the main focus of my Phase Analysis.

I agree that examining whether an approved methodology was actually implemented and verified is a valuable practical application of this perspective.
From your response, I understand that it is important to track five different things:
- When the methodology was approved.
- When it became applicable.
- When those performing the work were informed.
- When it was actually implemented.
- When and how its implementation was documented.
These are relevant questions, but they belong to a more detailed level of analysis — execution control, document management, and compliance of documents.

My subject of analysis is the evolution of the document's role over time, rather than proving that the works were executed in accordance with it. Other project documents, reports, and records should provide evidence of this.
Thank you, Aleksandar. Your clarification helps distinguish the conceptual purpose of Phase Analysis from its possible applications in execution control. Following that scope, I would explore how changes in the document’s role relate to changes in its content.

The same approved version may guide execution, serve as a reference for inspection and later remain part of the project archive without requiring revision. Some of these functions may also coexist. Its role can therefore evolve even when its content remains stable.

Meanwhile, execution and inspection records may accumulate separately. They can provide information that prompts a review of the Method Statement, but a review does not necessarily require a revision. For example, a recorded deviation might call for correcting the work to follow the approved method, or reveal a reason to reconsider the method itself.

This suggests a useful distinction between the Method Statement serving as an input to a process and other documents providing inputs to its review and possible revision.

Regarding your additional comment, a complementary example to Rev. 01 could follow an approved Method Statement that remains unchanged while its uses and relationships with execution records evolve. Comparing these situations could illustrate how Phase Analysis addresses both continuity and change.

Would that comparison fit your intended framework? It could help clarify when the document itself changes, when its role changes, and how those developments interact.
...
1 reply by Aleksandar Loncar
Oct 31, 2026 1:13 PM
Aleksandar Loncar
...
Thank you, Luis, for your thoughtful response and particularly for the excellent example of an unchanged Method Statement (Rev. 00). Your observations help me further refine the conceptual framework of my Phase Analysis, especially by distinguishing changes in the document's role from changes in its content.

1. Refining the original framework

Within this refined framework, the Method Statement:
  • Is developed as an output of a particular process.
  • Becomes an input to other processes.
  • Serves as an operational and control document during project execution, with functions that may coexist.
  • May be reviewed and revised to adapt to changing project conditions, or remain unchanged while its role continues to evolve.
  • Retains archival and potential evidentiary value after the completion of the works.
These elements remain the main focus of my Phase Analysis.

2. Changes in role and changes in content

Your observation introduces an important distinction: the role of a Method Statement can evolve without any change in its content.
During execution, the same approved MS may simultaneously guide the contractor's activities and serve as a reference document for inspection by Supervision and QA/QC personnel. Therefore, a change in role does not necessarily mean that one function ends before another begins. Functions may overlap.
This suggests three possible situations:
A. The content remains unchanged, while the role evolves.
B. The content changes through revision, while the role remains essentially the same.
C. Both the content and the role change.

3. Review versus revision

I also find your distinction between reviewing and revising the Method Statement particularly useful.
Execution and inspection records may trigger a review of the approved methodology, with two possible outcomes:
- If the methodology remains appropriate but its implementation was incorrect, corrective action may be required to bring execution into accordance with the approved MS, without revising the document.
- If the review establishes that the methodology itself needs to change, a revised MS must be prepared and obtain the necessary approvals before the revised method is implemented.
Thus, review does not necessarily lead to revision.

4. Two complementary practical examples: Rev. 00 and Rev. 01

Your proposed Rev. 00 example complements my earlier Rev. 01 example very well.
An approved Method Statement may remain unchanged throughout the works while serving different purposes:
1. Before execution — Rev. 00, approved: Basis for preparing the works.
2. During execution — Rev. 00, unchanged: Operational guidance for construction activities.
3. During inspection — Rev. 00, unchanged: Reference document for Supervision and QA/QC personnel
4. After completion — Rev. 00, unchanged: Archival document with potential evidentiary value.
This demonstrates continuity of content alongside the evolution and possible overlap of functions.
The Rev. 01 example, on the other hand, demonstrates how the document's content may change when a revision of the methodology becomes necessary.

5. Three development scenarios

Based on our discussion, I would now distinguish three scenarios:
Scenario A — Content continuity with evolving roles
Preparation (Rev. 00) ➞ Execution (Rev. 00) ➞ Inspection (Rev. 00) ➞ Archive (Rev. 00).
The document remains unchanged, while its functions evolve and may overlap.
Scenario B — Content change following review
Preparation (Rev. 00) ➞ Execution (Rev. 00) ➞ Review ➞ Revised methodology (Rev. 01).
New conditions or technical requirements make a change in methodology necessary. The revised document is subject to the required approvals before implementation.
Scenario C — Review without revision
Preparation (Rev. 00) ➞ Execution (Rev. 00) ➞ Review ➞ Continued application (Rev. 00).
Content Continuity: The methodology was appropriate, but its implementation was incorrect. Corrective action in the execution of works, with Rev. 00 retained.

6. The refined subject of Phase Analysis

I would now describe the subject of Phase Analysis through three elements:
Position: How the MS participates in project processes, particularly as an input or output.
Role: Which functions it performs.
Content: Whether the approved methodology remains unchanged or is revised.
These elements are examined over time, throughout the project life cycle.
For example, two situations can be identified:
Case A: The process position changes, the role evolves, but the content remains unchanged (Rev. 00).
Case B: The process position remains the same (input to execution), the operational role remains the same, but the content changes (Rev. 00 ➞ Rev. 01).
This leads me to a more precise central question for Phase Analysis:
How do the position, role, and content of a Method Statement change or remain stable throughout the project life cycle, and how do these developments interact?
I believe your observations have helped strengthen my original framework without changing its fundamental purpose. They also show that Phase Analysis should examine not only changes, but continuity, overlapping functions, and the distinction between review and revision.
Thank you again for this valuable contribution. I would be interested in your assessment of this refined framework.
avatar
Aleksandar Loncar Niš, Serbia
Oct 30, 2026 10:14 AM
Replying to Luis Branco
...
Thank you, Aleksandar. Your clarification helps distinguish the conceptual purpose of Phase Analysis from its possible applications in execution control. Following that scope, I would explore how changes in the document’s role relate to changes in its content.

The same approved version may guide execution, serve as a reference for inspection and later remain part of the project archive without requiring revision. Some of these functions may also coexist. Its role can therefore evolve even when its content remains stable.

Meanwhile, execution and inspection records may accumulate separately. They can provide information that prompts a review of the Method Statement, but a review does not necessarily require a revision. For example, a recorded deviation might call for correcting the work to follow the approved method, or reveal a reason to reconsider the method itself.

This suggests a useful distinction between the Method Statement serving as an input to a process and other documents providing inputs to its review and possible revision.

Regarding your additional comment, a complementary example to Rev. 01 could follow an approved Method Statement that remains unchanged while its uses and relationships with execution records evolve. Comparing these situations could illustrate how Phase Analysis addresses both continuity and change.

Would that comparison fit your intended framework? It could help clarify when the document itself changes, when its role changes, and how those developments interact.
Thank you, Luis, for your thoughtful response and particularly for the excellent example of an unchanged Method Statement (Rev. 00). Your observations help me further refine the conceptual framework of my Phase Analysis, especially by distinguishing changes in the document's role from changes in its content.

1. Refining the original framework

Within this refined framework, the Method Statement:
  • Is developed as an output of a particular process.
  • Becomes an input to other processes.
  • Serves as an operational and control document during project execution, with functions that may coexist.
  • May be reviewed and revised to adapt to changing project conditions, or remain unchanged while its role continues to evolve.
  • Retains archival and potential evidentiary value after the completion of the works.
These elements remain the main focus of my Phase Analysis.

2. Changes in role and changes in content

Your observation introduces an important distinction: the role of a Method Statement can evolve without any change in its content.
During execution, the same approved MS may simultaneously guide the contractor's activities and serve as a reference document for inspection by Supervision and QA/QC personnel. Therefore, a change in role does not necessarily mean that one function ends before another begins. Functions may overlap.
This suggests three possible situations:
A. The content remains unchanged, while the role evolves.
B. The content changes through revision, while the role remains essentially the same.
C. Both the content and the role change.

3. Review versus revision

I also find your distinction between reviewing and revising the Method Statement particularly useful.
Execution and inspection records may trigger a review of the approved methodology, with two possible outcomes:
- If the methodology remains appropriate but its implementation was incorrect, corrective action may be required to bring execution into accordance with the approved MS, without revising the document.
- If the review establishes that the methodology itself needs to change, a revised MS must be prepared and obtain the necessary approvals before the revised method is implemented.
Thus, review does not necessarily lead to revision.

4. Two complementary practical examples: Rev. 00 and Rev. 01

Your proposed Rev. 00 example complements my earlier Rev. 01 example very well.
An approved Method Statement may remain unchanged throughout the works while serving different purposes:
1. Before execution — Rev. 00, approved: Basis for preparing the works.
2. During execution — Rev. 00, unchanged: Operational guidance for construction activities.
3. During inspection — Rev. 00, unchanged: Reference document for Supervision and QA/QC personnel
4. After completion — Rev. 00, unchanged: Archival document with potential evidentiary value.
This demonstrates continuity of content alongside the evolution and possible overlap of functions.
The Rev. 01 example, on the other hand, demonstrates how the document's content may change when a revision of the methodology becomes necessary.

5. Three development scenarios

Based on our discussion, I would now distinguish three scenarios:
Scenario A — Content continuity with evolving roles
Preparation (Rev. 00) ➞ Execution (Rev. 00) ➞ Inspection (Rev. 00) ➞ Archive (Rev. 00).
The document remains unchanged, while its functions evolve and may overlap.
Scenario B — Content change following review
Preparation (Rev. 00) ➞ Execution (Rev. 00) ➞ Review ➞ Revised methodology (Rev. 01).
New conditions or technical requirements make a change in methodology necessary. The revised document is subject to the required approvals before implementation.
Scenario C — Review without revision
Preparation (Rev. 00) ➞ Execution (Rev. 00) ➞ Review ➞ Continued application (Rev. 00).
Content Continuity: The methodology was appropriate, but its implementation was incorrect. Corrective action in the execution of works, with Rev. 00 retained.

6. The refined subject of Phase Analysis

I would now describe the subject of Phase Analysis through three elements:
Position: How the MS participates in project processes, particularly as an input or output.
Role: Which functions it performs.
Content: Whether the approved methodology remains unchanged or is revised.
These elements are examined over time, throughout the project life cycle.
For example, two situations can be identified:
Case A: The process position changes, the role evolves, but the content remains unchanged (Rev. 00).
Case B: The process position remains the same (input to execution), the operational role remains the same, but the content changes (Rev. 00 ➞ Rev. 01).
This leads me to a more precise central question for Phase Analysis:
How do the position, role, and content of a Method Statement change or remain stable throughout the project life cycle, and how do these developments interact?
I believe your observations have helped strengthen my original framework without changing its fundamental purpose. They also show that Phase Analysis should examine not only changes, but continuity, overlapping functions, and the distinction between review and revision.
Thank you again for this valuable contribution. I would be interested in your assessment of this refined framework.
...
1 reply by Luis Branco
Nov 03, 2026 7:12 AM
Luis Branco
...
Thank you, Aleksandar. Distinguishing position, role and content makes the refined framework clearer. Your central question now accommodates both change and stability, while recognising that functions may coexist. This gives the Rev. 00 and Rev. 01 examples a useful comparative purpose.

Two further distinctions could strengthen the framework.

First, review without revision need not imply that implementation was incorrect. A review prompted by new information could confirm that the existing methodology remains appropriate and that no corrective action is needed. Your Scenario C illustrates one possible outcome; the broader category also includes confirmation of continued suitability.

Second, a change in the document’s content need not change the execution method it describes. Updating a named responsible person or clarifying a reference could require a document revision while leaving the construction sequence and technique unchanged. Identifying the nature of the change would therefore help distinguish a revised document from a revised execution method.

I would also distinguish the combinations in Section 2 from the development scenarios in Section 5. The former describe what changes or remains stable; the latter describe possible pathways. Making their relationship explicit would help readers avoid assuming that the A, B and C labels correspond across both sections.

For illustrating the framework, your examples could be compared using the three elements you have already defined: position, role and content. This could show how different pathways produce different combinations of continuity and change, including functions that coexist.

These refinements would preserve your conceptual purpose while helping readers distinguish what prompted a review, what changed as a result, and what remained appropriate. Continuity would then be visible as a potentially considered outcome, rather than simply an absence of revision.
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
Oct 31, 2026 1:13 PM
Replying to Aleksandar Loncar
...
Thank you, Luis, for your thoughtful response and particularly for the excellent example of an unchanged Method Statement (Rev. 00). Your observations help me further refine the conceptual framework of my Phase Analysis, especially by distinguishing changes in the document's role from changes in its content.

1. Refining the original framework

Within this refined framework, the Method Statement:
  • Is developed as an output of a particular process.
  • Becomes an input to other processes.
  • Serves as an operational and control document during project execution, with functions that may coexist.
  • May be reviewed and revised to adapt to changing project conditions, or remain unchanged while its role continues to evolve.
  • Retains archival and potential evidentiary value after the completion of the works.
These elements remain the main focus of my Phase Analysis.

2. Changes in role and changes in content

Your observation introduces an important distinction: the role of a Method Statement can evolve without any change in its content.
During execution, the same approved MS may simultaneously guide the contractor's activities and serve as a reference document for inspection by Supervision and QA/QC personnel. Therefore, a change in role does not necessarily mean that one function ends before another begins. Functions may overlap.
This suggests three possible situations:
A. The content remains unchanged, while the role evolves.
B. The content changes through revision, while the role remains essentially the same.
C. Both the content and the role change.

3. Review versus revision

I also find your distinction between reviewing and revising the Method Statement particularly useful.
Execution and inspection records may trigger a review of the approved methodology, with two possible outcomes:
- If the methodology remains appropriate but its implementation was incorrect, corrective action may be required to bring execution into accordance with the approved MS, without revising the document.
- If the review establishes that the methodology itself needs to change, a revised MS must be prepared and obtain the necessary approvals before the revised method is implemented.
Thus, review does not necessarily lead to revision.

4. Two complementary practical examples: Rev. 00 and Rev. 01

Your proposed Rev. 00 example complements my earlier Rev. 01 example very well.
An approved Method Statement may remain unchanged throughout the works while serving different purposes:
1. Before execution — Rev. 00, approved: Basis for preparing the works.
2. During execution — Rev. 00, unchanged: Operational guidance for construction activities.
3. During inspection — Rev. 00, unchanged: Reference document for Supervision and QA/QC personnel
4. After completion — Rev. 00, unchanged: Archival document with potential evidentiary value.
This demonstrates continuity of content alongside the evolution and possible overlap of functions.
The Rev. 01 example, on the other hand, demonstrates how the document's content may change when a revision of the methodology becomes necessary.

5. Three development scenarios

Based on our discussion, I would now distinguish three scenarios:
Scenario A — Content continuity with evolving roles
Preparation (Rev. 00) ➞ Execution (Rev. 00) ➞ Inspection (Rev. 00) ➞ Archive (Rev. 00).
The document remains unchanged, while its functions evolve and may overlap.
Scenario B — Content change following review
Preparation (Rev. 00) ➞ Execution (Rev. 00) ➞ Review ➞ Revised methodology (Rev. 01).
New conditions or technical requirements make a change in methodology necessary. The revised document is subject to the required approvals before implementation.
Scenario C — Review without revision
Preparation (Rev. 00) ➞ Execution (Rev. 00) ➞ Review ➞ Continued application (Rev. 00).
Content Continuity: The methodology was appropriate, but its implementation was incorrect. Corrective action in the execution of works, with Rev. 00 retained.

6. The refined subject of Phase Analysis

I would now describe the subject of Phase Analysis through three elements:
Position: How the MS participates in project processes, particularly as an input or output.
Role: Which functions it performs.
Content: Whether the approved methodology remains unchanged or is revised.
These elements are examined over time, throughout the project life cycle.
For example, two situations can be identified:
Case A: The process position changes, the role evolves, but the content remains unchanged (Rev. 00).
Case B: The process position remains the same (input to execution), the operational role remains the same, but the content changes (Rev. 00 ➞ Rev. 01).
This leads me to a more precise central question for Phase Analysis:
How do the position, role, and content of a Method Statement change or remain stable throughout the project life cycle, and how do these developments interact?
I believe your observations have helped strengthen my original framework without changing its fundamental purpose. They also show that Phase Analysis should examine not only changes, but continuity, overlapping functions, and the distinction between review and revision.
Thank you again for this valuable contribution. I would be interested in your assessment of this refined framework.
Thank you, Aleksandar. Distinguishing position, role and content makes the refined framework clearer. Your central question now accommodates both change and stability, while recognising that functions may coexist. This gives the Rev. 00 and Rev. 01 examples a useful comparative purpose.

Two further distinctions could strengthen the framework.

First, review without revision need not imply that implementation was incorrect. A review prompted by new information could confirm that the existing methodology remains appropriate and that no corrective action is needed. Your Scenario C illustrates one possible outcome; the broader category also includes confirmation of continued suitability.

Second, a change in the document’s content need not change the execution method it describes. Updating a named responsible person or clarifying a reference could require a document revision while leaving the construction sequence and technique unchanged. Identifying the nature of the change would therefore help distinguish a revised document from a revised execution method.

I would also distinguish the combinations in Section 2 from the development scenarios in Section 5. The former describe what changes or remains stable; the latter describe possible pathways. Making their relationship explicit would help readers avoid assuming that the A, B and C labels correspond across both sections.

For illustrating the framework, your examples could be compared using the three elements you have already defined: position, role and content. This could show how different pathways produce different combinations of continuity and change, including functions that coexist.

These refinements would preserve your conceptual purpose while helping readers distinguish what prompted a review, what changed as a result, and what remained appropriate. Continuity would then be visible as a potentially considered outcome, rather than simply an absence of revision.
avatar
Aleksandar Loncar Niš, Serbia
Thank you, Luis, for your helpful response and valuable suggestions. Based on your detailed comments, I have further developed the Phase Analysis.

THE NEW FRAMEWORK FOR PHASE ANALYSIS
Where and when does the Method Statement appear?

Although the theoretical framework of this paper primarily relies on PMBOK 7, a reference to the PMBOK Guide – Eighth Edition is necessary for the purposes of phase analysis. While the seventh edition eliminated the traditional process-based structure, PMBOK 8 reintegrates the process approach through its domains.

If we examine the PMBOK Guide – Eighth Edition and the processes within the Governance Performance Domain, the dynamic nature of this document becomes most apparent. We can observe that the Method Statement changes its position depending on the project phase. This is most clearly illustrated through the ITTO models (Inputs, Tools &amp; Techniques, Outputs).

ITTO Models and the Position of the Method Statement
1. In the Integrate and Align Project Plans process — the Method Statement would be an output.
Planning phase. In this phase, the Method Statement is the intended outcome. It is developed during this process.

2. In the Manage Project Execution process — the Method Statement would be an input.
It could be included as an item under Project Documents.
Execution phase. Once construction works begin, the Method Statement becomes an operational document. It serves as an instruction and a guide defining how the work must be carried out, that is, how the construction activities are to be executed.

3. In the Manage Quality Assurance process — the Method Statement would also be an input.
Control phase. It becomes the benchmark and the officially approved reference standard against which supervision and quality control managers verify whether the works on site are being carried out exactly as agreed and approved.

The Operational and Control Functions of the Method Statement

During the execution phase, the Method Statement serves both as an operational document and as a control reference. As an operational document, it guides the contractor's activities in carrying out construction works in accordance with the approved methodology. At the same time, it serves as a reference for Supervision and QA/QC personnel when verifying whether the works are being executed in accordance with the approved procedures and requirements. These functions are not mutually exclusive and may coexist throughout execution.
The Second part is in the next comment
...
1 reply by Aleksandar Loncar
Nov 05, 2026 10:07 AM
Aleksandar Loncar
...
Phase Analysis – Position, Role and Content Throughout the Project Life Cycle

1. Refining the Original Framework

Within this refined framework, the Method Statement:

- Is developed as an output of a particular process.
- Becomes an input to other processes.
- Serves as an operational and control document during project execution, with functions that may coexist.
- May be reviewed and revised to adapt to changing project conditions, or remain unchanged while its role continues to evolve.
- Retains archival and potential evidentiary value after the completion of the works.
These elements remain the main focus of my Phase Analysis.

2. Changes in Role and Changes in Content

Your observation introduces an important distinction: the role of a Method Statement can evolve without any change in its content.

During execution, the same approved MS may simultaneously guide the contractor's activities and serve as a reference document for inspection by Supervision and QA/QC personnel. Therefore, a change in role does not necessarily mean that one function ends before another begins. Functions may overlap.

This suggests three possible situations:

Combination 1. The content remains unchanged, while the role evolves.

Combination 2. The content changes through revision, while the role remains essentially the same.

Combination 3. Both the content and the role change.

3. Review versus Revision

I also find your distinction between reviewing and revising the Method Statement particularly useful.
Execution and inspection records may trigger a review of the approved methodology, with three possible outcomes:

- If the review confirms that both the methodology and its implementation remain appropriate, no corrective action or revision of the Method Statement is required.
- If the methodology remains appropriate but its implementation was incorrect, corrective action may be required to bring execution into accordance with the approved MS, without revising the document.
- If the review establishes that the methodology itself needs to change, a revised MS must be prepared and obtain the necessary approvals before the revised method is implemented.
Thus, review does not necessarily lead to revision.

4. Two Complementary Practical Examples: Rev.00 and Rev.01

Your proposed Rev.00 example complements my earlier Rev.01 example very well.

An approved Method Statement may remain unchanged throughout the works while serving different purposes:

1. Before execution — Rev.00, approved: Basis for preparing the works.
2. During execution — Rev.00, unchanged: Operational guidance for construction activities.
3. During inspection — Rev.00, unchanged: Reference document for Supervision and QA/QC personnel.
4. After completion — Rev.00, unchanged: Archival document with potential evidentiary value.
This demonstrates continuity of content alongside the evolution and possible overlap of functions.

The continuity of Rev.00 does not simply represent a situation in which nothing has changed; it may also be the result of a deliberate professional assessment that no revision is necessary.

The Rev.01 example, on the other hand, demonstrates how the document's content may change following a review.

5. Three Development Scenarios

Based on our discussion, I would now distinguish three scenarios:

Scenario 1 — Content Continuity with Evolving Roles

Preparation (Rev.00) ➞ Execution (Rev.00) ➞ Inspection (Rev.00) ➞ Archive (Rev.00).
The document remains unchanged, while its functions evolve and may overlap.

Scenario 2 — Content Change Following Review
Document Revision and/or Methodology Revision
Preparation (Rev.00) ➞ Execution (Rev.00) ➞ Review ➞ Revised document (Rev.01).

New conditions or technical requirements may make a change in the document or in the construction methodology necessary. The revised document is subject to the required approvals before implementation, where applicable.

Scenario 2.1. Document revision without methodology revision
Rev.00 → Rev.01, while the approved construction methodology remains unchanged.
Examples:
- Change of responsible personnel.
- Update of document references.
- Clarification of existing procedures.

Scenario 2.2. Document revision involving methodology revision
Rev.00 → Rev.01, with a change to the approved construction methodology.

Scenario 3 — Review without Revision
Preparation (Rev.00) ➞ Execution (Rev.00) ➞ Review ➞ Continued application (Rev.00).

Scenario 3.1. Review confirms continued suitability
The methodology and its implementation are appropriate. No corrective action or revision of the MS is required.

Scenario 3.2. Review identifies implementation deficiencies
The methodology remains appropriate, but its implementation is not. Corrective action is taken to bring execution into accordance with the approved MS, without revising the document.

6. Comparative Analysis of Position, Role and Content
The three development scenarios can be further examined through the same three analytical elements: Position, Role and Content.

Scenario 1 – Content Continuity with Evolving Roles
Position: Changes throughout the project processes, from an output during planning to an input during execution and quality assurance.
Role: Evolves during the project life cycle. The MS serves as an operational document and a control reference. These functions may coexist.
Content: Remains unchanged (Rev.00).

Scenario 2 – Content Change Following Review
Position: Follows the same general process path, from an output during planning to an input during execution and quality assurance.
Role: Remains essentially the same, although the document is revised. Its operational and control functions continue.
Content: Changes from Rev.00 to Rev.01. The revision may involve a change in the construction methodology or may be limited to other document content.

Scenario 3 – Review without Revision

Position: Follows the same general process path, from an output during planning to an input during execution and quality assurance.
Role: Continues throughout execution. The review confirms the suitability of the existing methodology or identifies implementation deficiencies requiring corrective action.
Content: Remains unchanged (Rev.00).

7. The Method Statement as Evidence

At the end of the project, it can also be regarded as and serve as evidence that the works were executed in accordance with it.

If changes to the execution of works are planned, it is good practice to revise the Method Statement — so that the execution of works is once again in accordance with it. This is consistent with the Assess and Implement Changes process. The revision ensures that the document is once again fully aligned with the actual conditions on site. The Method Statement evolves along with the project.

This means that the document is not static but adapts to changing circumstances.

In this way, at the completion of the works, the Method Statement can still serve as evidence (Archive) — because it has been revised and aligned with the actual execution of works. It constitutes documentary evidence that the works were carried out safely, in accordance with established procedures and contractual requirements, thereby protecting the contractor against subsequent claims or legal disputes. In the event of litigation, arbitration, or investigations into site incidents, the approved Method Statement is among the first documents requested. It establishes the exact procedures and safety measures that the contractor was required to follow when executing the works.

I am aware that the primary documentary evidence on a project consists of site records confirming the actual execution and quality of the works — such as RFIs (Requests for Inspection), MARs (Material Approval Forms), Construction Diaries, Laboratory Reports, Monthly Reports, Checklists, and ITP Forms. Nevertheless, I believe that the Method Statement can also serve as evidence.

When compared with RFI forms and checklists, the approved Method Statement demonstrates that the project was not carried out based on guesswork, but according to a verified, safe, and documented method. This is important because what is not documented "did not happen".
avatar
Aleksandar Loncar Niš, Serbia
Nov 05, 2026 9:52 AM
Replying to Aleksandar Loncar
...
Thank you, Luis, for your helpful response and valuable suggestions. Based on your detailed comments, I have further developed the Phase Analysis.

THE NEW FRAMEWORK FOR PHASE ANALYSIS
Where and when does the Method Statement appear?

Although the theoretical framework of this paper primarily relies on PMBOK 7, a reference to the PMBOK Guide – Eighth Edition is necessary for the purposes of phase analysis. While the seventh edition eliminated the traditional process-based structure, PMBOK 8 reintegrates the process approach through its domains.

If we examine the PMBOK Guide – Eighth Edition and the processes within the Governance Performance Domain, the dynamic nature of this document becomes most apparent. We can observe that the Method Statement changes its position depending on the project phase. This is most clearly illustrated through the ITTO models (Inputs, Tools &amp; Techniques, Outputs).

ITTO Models and the Position of the Method Statement
1. In the Integrate and Align Project Plans process — the Method Statement would be an output.
Planning phase. In this phase, the Method Statement is the intended outcome. It is developed during this process.

2. In the Manage Project Execution process — the Method Statement would be an input.
It could be included as an item under Project Documents.
Execution phase. Once construction works begin, the Method Statement becomes an operational document. It serves as an instruction and a guide defining how the work must be carried out, that is, how the construction activities are to be executed.

3. In the Manage Quality Assurance process — the Method Statement would also be an input.
Control phase. It becomes the benchmark and the officially approved reference standard against which supervision and quality control managers verify whether the works on site are being carried out exactly as agreed and approved.

The Operational and Control Functions of the Method Statement

During the execution phase, the Method Statement serves both as an operational document and as a control reference. As an operational document, it guides the contractor's activities in carrying out construction works in accordance with the approved methodology. At the same time, it serves as a reference for Supervision and QA/QC personnel when verifying whether the works are being executed in accordance with the approved procedures and requirements. These functions are not mutually exclusive and may coexist throughout execution.
The Second part is in the next comment
Phase Analysis – Position, Role and Content Throughout the Project Life Cycle

1. Refining the Original Framework

Within this refined framework, the Method Statement:

- Is developed as an output of a particular process.
- Becomes an input to other processes.
- Serves as an operational and control document during project execution, with functions that may coexist.
- May be reviewed and revised to adapt to changing project conditions, or remain unchanged while its role continues to evolve.
- Retains archival and potential evidentiary value after the completion of the works.
These elements remain the main focus of my Phase Analysis.

2. Changes in Role and Changes in Content

Your observation introduces an important distinction: the role of a Method Statement can evolve without any change in its content.

During execution, the same approved MS may simultaneously guide the contractor's activities and serve as a reference document for inspection by Supervision and QA/QC personnel. Therefore, a change in role does not necessarily mean that one function ends before another begins. Functions may overlap.

This suggests three possible situations:

Combination 1. The content remains unchanged, while the role evolves.

Combination 2. The content changes through revision, while the role remains essentially the same.

Combination 3. Both the content and the role change.

3. Review versus Revision

I also find your distinction between reviewing and revising the Method Statement particularly useful.
Execution and inspection records may trigger a review of the approved methodology, with three possible outcomes:

- If the review confirms that both the methodology and its implementation remain appropriate, no corrective action or revision of the Method Statement is required.
- If the methodology remains appropriate but its implementation was incorrect, corrective action may be required to bring execution into accordance with the approved MS, without revising the document.
- If the review establishes that the methodology itself needs to change, a revised MS must be prepared and obtain the necessary approvals before the revised method is implemented.
Thus, review does not necessarily lead to revision.

4. Two Complementary Practical Examples: Rev.00 and Rev.01

Your proposed Rev.00 example complements my earlier Rev.01 example very well.

An approved Method Statement may remain unchanged throughout the works while serving different purposes:

1. Before execution — Rev.00, approved: Basis for preparing the works.
2. During execution — Rev.00, unchanged: Operational guidance for construction activities.
3. During inspection — Rev.00, unchanged: Reference document for Supervision and QA/QC personnel.
4. After completion — Rev.00, unchanged: Archival document with potential evidentiary value.
This demonstrates continuity of content alongside the evolution and possible overlap of functions.

The continuity of Rev.00 does not simply represent a situation in which nothing has changed; it may also be the result of a deliberate professional assessment that no revision is necessary.

The Rev.01 example, on the other hand, demonstrates how the document's content may change following a review.

5. Three Development Scenarios

Based on our discussion, I would now distinguish three scenarios:

Scenario 1 — Content Continuity with Evolving Roles

Preparation (Rev.00) ➞ Execution (Rev.00) ➞ Inspection (Rev.00) ➞ Archive (Rev.00).
The document remains unchanged, while its functions evolve and may overlap.

Scenario 2 — Content Change Following Review
Document Revision and/or Methodology Revision
Preparation (Rev.00) ➞ Execution (Rev.00) ➞ Review ➞ Revised document (Rev.01).

New conditions or technical requirements may make a change in the document or in the construction methodology necessary. The revised document is subject to the required approvals before implementation, where applicable.

Scenario 2.1. Document revision without methodology revision
Rev.00 → Rev.01, while the approved construction methodology remains unchanged.
Examples:
- Change of responsible personnel.
- Update of document references.
- Clarification of existing procedures.

Scenario 2.2. Document revision involving methodology revision
Rev.00 → Rev.01, with a change to the approved construction methodology.

Scenario 3 — Review without Revision
Preparation (Rev.00) ➞ Execution (Rev.00) ➞ Review ➞ Continued application (Rev.00).

Scenario 3.1. Review confirms continued suitability
The methodology and its implementation are appropriate. No corrective action or revision of the MS is required.

Scenario 3.2. Review identifies implementation deficiencies
The methodology remains appropriate, but its implementation is not. Corrective action is taken to bring execution into accordance with the approved MS, without revising the document.

6. Comparative Analysis of Position, Role and Content
The three development scenarios can be further examined through the same three analytical elements: Position, Role and Content.

Scenario 1 – Content Continuity with Evolving Roles
Position: Changes throughout the project processes, from an output during planning to an input during execution and quality assurance.
Role: Evolves during the project life cycle. The MS serves as an operational document and a control reference. These functions may coexist.
Content: Remains unchanged (Rev.00).

Scenario 2 – Content Change Following Review
Position: Follows the same general process path, from an output during planning to an input during execution and quality assurance.
Role: Remains essentially the same, although the document is revised. Its operational and control functions continue.
Content: Changes from Rev.00 to Rev.01. The revision may involve a change in the construction methodology or may be limited to other document content.

Scenario 3 – Review without Revision

Position: Follows the same general process path, from an output during planning to an input during execution and quality assurance.
Role: Continues throughout execution. The review confirms the suitability of the existing methodology or identifies implementation deficiencies requiring corrective action.
Content: Remains unchanged (Rev.00).

7. The Method Statement as Evidence

At the end of the project, it can also be regarded as and serve as evidence that the works were executed in accordance with it.

If changes to the execution of works are planned, it is good practice to revise the Method Statement — so that the execution of works is once again in accordance with it. This is consistent with the Assess and Implement Changes process. The revision ensures that the document is once again fully aligned with the actual conditions on site. The Method Statement evolves along with the project.

This means that the document is not static but adapts to changing circumstances.

In this way, at the completion of the works, the Method Statement can still serve as evidence (Archive) — because it has been revised and aligned with the actual execution of works. It constitutes documentary evidence that the works were carried out safely, in accordance with established procedures and contractual requirements, thereby protecting the contractor against subsequent claims or legal disputes. In the event of litigation, arbitration, or investigations into site incidents, the approved Method Statement is among the first documents requested. It establishes the exact procedures and safety measures that the contractor was required to follow when executing the works.

I am aware that the primary documentary evidence on a project consists of site records confirming the actual execution and quality of the works — such as RFIs (Requests for Inspection), MARs (Material Approval Forms), Construction Diaries, Laboratory Reports, Monthly Reports, Checklists, and ITP Forms. Nevertheless, I believe that the Method Statement can also serve as evidence.

When compared with RFI forms and checklists, the approved Method Statement demonstrates that the project was not carried out based on guesswork, but according to a verified, safe, and documented method. This is important because what is not documented "did not happen".
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
Thank you, Aleksandar. In my reading, you have developed a conceptual framework for tracing how a Method Statement’s process position, functions and content change or remain stable over time. Its contribution lies in examining these elements together, including situations where they evolve differently.

Sections 1–6 give that framework greater clarity. They distinguish document revision from methodology revision, recognise that review can confirm continued suitability, and accommodate functions that coexist.

Regarding the framework’s internal consistency, a key refinement concerns Section 7, where some statements need to be aligned with those distinctions and with your earlier clarification about evidence.

A Method Statement can have evidentiary value. The question is what it provides evidence of. An approved version can help establish the documented methodology and requirements, provided its applicability to the work and period concerned is established. Whether the work was actually performed accordingly requires examination of the relevant execution and inspection evidence.

Section 7 goes further when it describes the document as evidence that the works were carried out safely and in accordance with contractual requirements. Similarly, revision can support alignment with site conditions, but does not itself ensure that alignment or demonstrate implementation.

Your Rev.00 example helps resolve this within the framework. An unchanged version can retain evidentiary relevance, while a superseded version may remain relevant to earlier work or decisions. Connecting each version to the requirements, events and records it helps explain would strengthen the temporal analysis without making revision a condition of evidentiary value.

I would also reconsider the statement that what is not documented did not happen. Missing documentation may limit what can be established; it does not establish that an event never occurred.

One further clarification concerns Scenario 2 in Section 6. A revised document may retain the same role, but this is one possibility rather than a necessary feature of revision. Allowing the role to remain stable or change would preserve your Combination 3.

These refinements would strengthen the framework’s central contribution: helping readers identify what changes, what remains stable and how those developments interact, while keeping conclusions proportionate to the evidence available.
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
Aleksandar, in a separate observation, I would like to address how your framework is mapped to the PMBOK Guide, Eighth Edition.

The reintroduced process guidance provides a useful reference for examining how a Method Statement participates in project work. I would distinguish, however, between project phases, Project Management Focus Areas and individual processes. A document becoming an input to another process does not necessarily indicate that the project has entered a different phase.

One specific adjustment concerns Manage Quality Assurance. In the Eighth Edition, this process sits within the Governance Performance Domain and the Executing Focus Area. Describing it as a “Control phase” could therefore blur the distinction between the document’s control function and the process’s placement in the guide.

I would also make the status of your Method Statement mapping explicit. Identifying it as an output of Integrate and Align Project Plans, or as an input to other processes, should be presented as your contextual application of the framework unless supported by an explicit reference in the guide. In particular, integrating project plans does not, by itself, establish where a construction execution document is produced.

Finally, the Eighth Edition can help illustrate your analysis without being a necessary condition for it. Your central question about position, role and content remains meaningful independently of the edition used to map particular processes.

These distinctions would strengthen the connection with PMBOK 8 while preserving the contribution of your framework: examining the document’s evolution over time without assuming a fixed sequence of phases or a universal process pathway.
...
1 reply by Aleksandar Loncar
Nov 06, 2026 2:26 PM
Aleksandar Loncar
...
Thank you, Luis, for your valuable observations and suggestions. I will incorporate them into my work.
I intend to explore the evidentiary role of the Method Statement further, but this will require additional time and a more detailed analysis.
Regarding the PMBOK® Guide – Eighth Edition, I was not sufficiently careful with some of the terminology and made several mistakes. Your comments have helped me clarify these distinctions.
I will continue developing the framework, including the proposed Relational Analysis perspective.
avatar
Aleksandar Loncar Niš, Serbia
Nov 05, 2026 11:51 AM
Replying to Luis Branco
...
Aleksandar, in a separate observation, I would like to address how your framework is mapped to the PMBOK Guide, Eighth Edition.

The reintroduced process guidance provides a useful reference for examining how a Method Statement participates in project work. I would distinguish, however, between project phases, Project Management Focus Areas and individual processes. A document becoming an input to another process does not necessarily indicate that the project has entered a different phase.

One specific adjustment concerns Manage Quality Assurance. In the Eighth Edition, this process sits within the Governance Performance Domain and the Executing Focus Area. Describing it as a “Control phase” could therefore blur the distinction between the document’s control function and the process’s placement in the guide.

I would also make the status of your Method Statement mapping explicit. Identifying it as an output of Integrate and Align Project Plans, or as an input to other processes, should be presented as your contextual application of the framework unless supported by an explicit reference in the guide. In particular, integrating project plans does not, by itself, establish where a construction execution document is produced.

Finally, the Eighth Edition can help illustrate your analysis without being a necessary condition for it. Your central question about position, role and content remains meaningful independently of the edition used to map particular processes.

These distinctions would strengthen the connection with PMBOK 8 while preserving the contribution of your framework: examining the document’s evolution over time without assuming a fixed sequence of phases or a universal process pathway.
Thank you, Luis, for your valuable observations and suggestions. I will incorporate them into my work.
I intend to explore the evidentiary role of the Method Statement further, but this will require additional time and a more detailed analysis.
Regarding the PMBOK® Guide – Eighth Edition, I was not sufficiently careful with some of the terminology and made several mistakes. Your comments have helped me clarify these distinctions.
I will continue developing the framework, including the proposed Relational Analysis perspective.
...
1 reply by Aleksandar Loncar
Nov 07, 2026 7:53 AM
Aleksandar Loncar
...
Luis,

I would now like to explore another perspective: Relational Analysis of the Method Statement.
Project documents may be individually correct, yet inconsistencies may only become apparent when their relationships are examined. This is one of the key contributions of Relational Analysis.
MS, RA, and ITP are interdependent documents that must remain fully aligned. A change in construction methodology requires a review and, where necessary, an update of the Risk Assessment and ITP to maintain consistency across all three documents. This alignment must work in both directions, as Risk Assessment may also precede the Method Statement and influence the selection of the methodology itself.
I would illustrate this perspective with three practical examples:

1. Method Statement ⬌ Project Schedule — Consistency
Hypothetical Example
The Project Schedule allocated 16 hours for the continuous concreting of a massive river pier foundation (approximately 2,000 m³ of concrete), assuming a concrete placing rate of 125 m³/h. However, the Method Statement indicated that 24 hours were required, and the actual concreting was completed in approximately 29 hours, at a placing rate of around 70 m³/h.
Relational Analysis reveals the inconsistency between the planned duration, assumed production capacity, the Method Statement, and actual execution.

2. Method Statement ⬌ Risk Assessment — Safety Alignment and Risk Control Integration
The Method Statement describes the installation of main concrete truss girders, while the Risk Assessment identifies the risk of electric shock from a nearby overhead power line. Relational Analysis examines whether the identified hazard and the required safety measures are adequately reflected in the construction methodology.

3. Method Statement ⬌ Project Drawings — Information Flow and Traceability
The Project Drawings define the geometry and dimensions of river piers. The Method Statement uses and processes data from these drawings to calculate the concrete quantities required for each of the three concreting stages. Relational Analysis examines how information from the drawings is transferred, processed, and incorporated into the construction methodology.

To distinguish Relational Analysis from other perspectives, consider a Method Statement revised to change river pier concreting from two stages to three:

  • Workflow Analysis examines how the change from two to three concreting stages is incorporated into the Method Statement through revision, review, approval and implementation.
  • Functional Analysis examines how the MS defines and guides the concreting sequence.
  • Relational Analysis examines how this change affects the RA, ITP, and Project Schedule, and whether these documents remain consistent.
The distinction I am proposing is that Workflow Analysis focuses on the document's development and use, Functional Analysis on its functions, and Relational Analysis on the relationships, dependencies, and consistency between documents.
In this sense, the primary unit of analysis is not the Method Statement in isolation, but its relationships with other project documents.
Treating Relational Analysis as a separate perspective becomes particularly valuable when individual project documents appear correct, but inconsistencies, dependencies, or gaps emerge only through their interaction. This is especially important when changes to one document affect others, potentially influencing project planning, safety, quality, or execution.
I would be interested in your opinion on whether this provides a sufficient basis for treating Relational Analysis as a distinct analytical perspective.
< 1 2 3 4 >

Please login or join to reply

Content ID:

People on dates shouldn't even be allowed out in public.

- Jerry Seinfeld

Sponsors