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
Nov 06, 2026 2:26 PM
Replying to 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.
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 reply by Luis Branco
Nov 10, 2026 9:25 AM
Luis Branco
...
Thank you, Aleksandar.
Yes, I think this provides a sufficient basis for treating Relational Analysis as a distinct analytical perspective. You identify a clear unit of analysis, the relationships between documents, and show what examining those relationships can reveal. The perspective need not be entirely separate from Workflow or Functional Analysis to make a useful contribution.

Your examples illustrate different kinds of relationships: compatibility between planning assumptions, incorporation of risk controls, and traceability of information from drawings into the methodology. Your recognition that Risk Assessment can influence the selection of the method also makes the bidirectional nature of these relationships explicit.

Two further distinctions could help develop the framework.

In your hypothetical concreting example, the difference between the schedule’s 16 hours and the Method Statement’s 24 hours raises a question of documentary consistency, provided both refer to the same work and comparable conditions. Comparing either duration with the approximately 29 hours taken raises a related question about execution variance. Distinguishing these comparisons would help show what can be identified from the documents themselves and what requires investigation through execution records.

A further consideration is that documents can be mutually consistent while sharing an incorrect assumption. A schedule and Method Statement might both rely on the same unrealistic production rate. Their agreement would establish consistency on that point, while the adequacy of the shared assumption would still require evidence about the relevant conditions and capacity.

This suggests examining each relationship through the information, requirement or assumption it carries, the dependencies it creates, and what would need reconsideration if it changed. Alignment could then be assessed at those specific interfaces.

Your proposed change from two to three concreting stages is a useful case for illustrating this. It could show which relationships are affected and whether review confirms continued suitability or identifies a necessary update. Connecting that examination to the applicable document versions would also link Relational Analysis naturally with Phase Analysis.

The strongest contribution, in my view, is making dependencies explicit enough to examine both the coherence of the existing documentation and the implications of changing any part of it.
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
Nov 07, 2026 7:53 AM
Replying to 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.
Thank you, Aleksandar.
Yes, I think this provides a sufficient basis for treating Relational Analysis as a distinct analytical perspective. You identify a clear unit of analysis, the relationships between documents, and show what examining those relationships can reveal. The perspective need not be entirely separate from Workflow or Functional Analysis to make a useful contribution.

Your examples illustrate different kinds of relationships: compatibility between planning assumptions, incorporation of risk controls, and traceability of information from drawings into the methodology. Your recognition that Risk Assessment can influence the selection of the method also makes the bidirectional nature of these relationships explicit.

Two further distinctions could help develop the framework.

In your hypothetical concreting example, the difference between the schedule’s 16 hours and the Method Statement’s 24 hours raises a question of documentary consistency, provided both refer to the same work and comparable conditions. Comparing either duration with the approximately 29 hours taken raises a related question about execution variance. Distinguishing these comparisons would help show what can be identified from the documents themselves and what requires investigation through execution records.

A further consideration is that documents can be mutually consistent while sharing an incorrect assumption. A schedule and Method Statement might both rely on the same unrealistic production rate. Their agreement would establish consistency on that point, while the adequacy of the shared assumption would still require evidence about the relevant conditions and capacity.

This suggests examining each relationship through the information, requirement or assumption it carries, the dependencies it creates, and what would need reconsideration if it changed. Alignment could then be assessed at those specific interfaces.

Your proposed change from two to three concreting stages is a useful case for illustrating this. It could show which relationships are affected and whether review confirms continued suitability or identifies a necessary update. Connecting that examination to the applicable document versions would also link Relational Analysis naturally with Phase Analysis.

The strongest contribution, in my view, is making dependencies explicit enough to examine both the coherence of the existing documentation and the implications of changing any part of it.
...
1 reply by Aleksandar Loncar
Nov 14, 2026 1:37 PM
Aleksandar Loncar
...
Luis,

Based on your detailed e-mail, including your comments, observations and explanations regarding my four analytical perspectives, I have further developed and strengthened the User Analysis.
The descriptions of the respective roles remain unchanged. However, I have added two paragraphs at the beginning to strengthen the analytical basis and revised the concluding paragraph to clarify that differences in how participants approach the Method Statement do not necessarily imply conflicting interests.
I am sharing the revised version, incorporating these improvements based on your valuable feedback.

REVISED AND STRENGTHENED FRAMEWORK FOR USER ANALYSIS

Question: Who uses the Method Statement and why?

The Method Statement is not a document used by only one party — it is read, written, approved and applied by multiple participants. All of them view the Method Statement from their own angle — one for the sake of management, another for the sake of execution, a third for the sake of control, a fourth for the sake of compliance, a fifth for the sake of approval.
While Functional Analysis examines the functions performed by the Method Statement, User Analysis examines who needs those functions, what information different users require, and what decisions or actions that information supports. It therefore considers the relationship between the document's functions, users' information needs, their responsibilities and authority, including the decisions they are entitled or required to make.
For those directly involved in executing the methodology, the analysis may further examine the accessibility, comprehensibility and practical usability of the information provided by the Method Statement.

Role - Why they use it

Project Manager - Management, coordination, alignment with the plan. They use it as a tool for managing risks and resources. Through it, they coordinate the contractor, supervision and investor, because an approved Method Statement is a condition for the commencement of works and for maintaining the planned schedule.

Contractor's Representative - Execution of works according to the approved method. The contractor uses it as an operational instruction for the efficient execution of works and the achievement of the planned works schedule. For them, the Method Statement is a tool for achieving productivity and speed. An approved Method Statement enables works without delays.

Subcontractor's Representative - Execution of their own portion of the works in accordance with the method and coordination with the main contractor

HSE Manager - Verification of identified hazards and assessed risks. Definition of appropriate safety measures for risk control. They use the Method Statement in conjunction with the Risk Assessment and the determination of the responsibilities of participants in implementing the envisaged safety measures.

QA/QC Manager - Verification of the compliance of the execution methodology with quality requirements and the ITP plan. Verification of acceptance criteria and the manner of documenting and demonstrating the quality of the executed works.

Contract Manager - Verification of the compliance of the methodology with contractual requirements. They also use it as a supporting document when considering changes, claims, delays and contractual disputes, where the execution methodology is relevant.

Supervisor - Control of whether the works are being executed according to the approved method, compliance with standards and requirements. Supervision uses it as technical proof that the methodology is safe and accurate, but also as a shield against professional liability.

Engineer - Technical verification of the method — whether the proposed manner of execution is technically correct and feasible. Providing a technical opinion to the supervision/investor prior to final approval.

Investor - Approval of the Method Statement as a condition for the commencement of works. Compliance with the contract, standards, requirements and permits. Protection of the investment's interests — ensuring that the works are performed in a manner that does not jeopardise quality, schedule and value. A basis for subsequent claims or refusal of acceptance if the works are performed differently from what was approved.

This analysis does not follow time — it examines who is involved, what information they need, and what decisions or actions they are responsible for.
Each participant approaches the Method Statement from a different position, shaped by their role, responsibilities, authority and information needs. These differences do not necessarily imply conflicting interests, but they do influence how each participant uses and evaluates the document.
The greatest challenge of the Method Statement as a document is that it must accommodate all these perspectives at the same time.
The decisions and actions of one user may affect all the others. If the Supervisor or the Engineer delays a decision or verification due to caution, for example, the subcontractor may be unable to commence the work. This can disrupt the Project Manager's plan and lead to delays and additional costs.
avatar
Aleksandar Loncar Niš, Serbia
Nov 10, 2026 9:25 AM
Replying to Luis Branco
...
Thank you, Aleksandar.
Yes, I think this provides a sufficient basis for treating Relational Analysis as a distinct analytical perspective. You identify a clear unit of analysis, the relationships between documents, and show what examining those relationships can reveal. The perspective need not be entirely separate from Workflow or Functional Analysis to make a useful contribution.

Your examples illustrate different kinds of relationships: compatibility between planning assumptions, incorporation of risk controls, and traceability of information from drawings into the methodology. Your recognition that Risk Assessment can influence the selection of the method also makes the bidirectional nature of these relationships explicit.

Two further distinctions could help develop the framework.

In your hypothetical concreting example, the difference between the schedule’s 16 hours and the Method Statement’s 24 hours raises a question of documentary consistency, provided both refer to the same work and comparable conditions. Comparing either duration with the approximately 29 hours taken raises a related question about execution variance. Distinguishing these comparisons would help show what can be identified from the documents themselves and what requires investigation through execution records.

A further consideration is that documents can be mutually consistent while sharing an incorrect assumption. A schedule and Method Statement might both rely on the same unrealistic production rate. Their agreement would establish consistency on that point, while the adequacy of the shared assumption would still require evidence about the relevant conditions and capacity.

This suggests examining each relationship through the information, requirement or assumption it carries, the dependencies it creates, and what would need reconsideration if it changed. Alignment could then be assessed at those specific interfaces.

Your proposed change from two to three concreting stages is a useful case for illustrating this. It could show which relationships are affected and whether review confirms continued suitability or identifies a necessary update. Connecting that examination to the applicable document versions would also link Relational Analysis naturally with Phase Analysis.

The strongest contribution, in my view, is making dependencies explicit enough to examine both the coherence of the existing documentation and the implications of changing any part of it.
Luis,

Based on your detailed e-mail, including your comments, observations and explanations regarding my four analytical perspectives, I have further developed and strengthened the User Analysis.
The descriptions of the respective roles remain unchanged. However, I have added two paragraphs at the beginning to strengthen the analytical basis and revised the concluding paragraph to clarify that differences in how participants approach the Method Statement do not necessarily imply conflicting interests.
I am sharing the revised version, incorporating these improvements based on your valuable feedback.

REVISED AND STRENGTHENED FRAMEWORK FOR USER ANALYSIS

Question: Who uses the Method Statement and why?

The Method Statement is not a document used by only one party — it is read, written, approved and applied by multiple participants. All of them view the Method Statement from their own angle — one for the sake of management, another for the sake of execution, a third for the sake of control, a fourth for the sake of compliance, a fifth for the sake of approval.
While Functional Analysis examines the functions performed by the Method Statement, User Analysis examines who needs those functions, what information different users require, and what decisions or actions that information supports. It therefore considers the relationship between the document's functions, users' information needs, their responsibilities and authority, including the decisions they are entitled or required to make.
For those directly involved in executing the methodology, the analysis may further examine the accessibility, comprehensibility and practical usability of the information provided by the Method Statement.

Role - Why they use it

Project Manager - Management, coordination, alignment with the plan. They use it as a tool for managing risks and resources. Through it, they coordinate the contractor, supervision and investor, because an approved Method Statement is a condition for the commencement of works and for maintaining the planned schedule.

Contractor's Representative - Execution of works according to the approved method. The contractor uses it as an operational instruction for the efficient execution of works and the achievement of the planned works schedule. For them, the Method Statement is a tool for achieving productivity and speed. An approved Method Statement enables works without delays.

Subcontractor's Representative - Execution of their own portion of the works in accordance with the method and coordination with the main contractor

HSE Manager - Verification of identified hazards and assessed risks. Definition of appropriate safety measures for risk control. They use the Method Statement in conjunction with the Risk Assessment and the determination of the responsibilities of participants in implementing the envisaged safety measures.

QA/QC Manager - Verification of the compliance of the execution methodology with quality requirements and the ITP plan. Verification of acceptance criteria and the manner of documenting and demonstrating the quality of the executed works.

Contract Manager - Verification of the compliance of the methodology with contractual requirements. They also use it as a supporting document when considering changes, claims, delays and contractual disputes, where the execution methodology is relevant.

Supervisor - Control of whether the works are being executed according to the approved method, compliance with standards and requirements. Supervision uses it as technical proof that the methodology is safe and accurate, but also as a shield against professional liability.

Engineer - Technical verification of the method — whether the proposed manner of execution is technically correct and feasible. Providing a technical opinion to the supervision/investor prior to final approval.

Investor - Approval of the Method Statement as a condition for the commencement of works. Compliance with the contract, standards, requirements and permits. Protection of the investment's interests — ensuring that the works are performed in a manner that does not jeopardise quality, schedule and value. A basis for subsequent claims or refusal of acceptance if the works are performed differently from what was approved.

This analysis does not follow time — it examines who is involved, what information they need, and what decisions or actions they are responsible for.
Each participant approaches the Method Statement from a different position, shaped by their role, responsibilities, authority and information needs. These differences do not necessarily imply conflicting interests, but they do influence how each participant uses and evaluates the document.
The greatest challenge of the Method Statement as a document is that it must accommodate all these perspectives at the same time.
The decisions and actions of one user may affect all the others. If the Supervisor or the Engineer delays a decision or verification due to caution, for example, the subcontractor may be unable to commence the work. This can disrupt the Project Manager's plan and lead to delays and additional costs.
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
Thank you, Aleksandar. The new paragraphs give User Analysis a clearer analytical basis by connecting the document’s functions with users’ information needs, responsibilities and authority. Your clarification that different uses do not necessarily imply conflicting interests also strengthens the conclusion.

In my reading, this supports User Analysis as a distinct perspective. The next refinement would be to bring the retained role descriptions into closer alignment with that definition. For each participant, the analysis could identify the information needed, its intended use, the decision or action it supports, and the relevant responsibility and limits of authority. Not every user needs approval authority: consulting, executing, checking and recommending are also meaningful uses.

Your Engineer description already makes a useful distinction between providing a technical opinion and granting final approval. Applying similar precision to the Supervisor could clarify what information is needed to examine a discrepancy, what action the Supervisor may take, and what requires referral to someone else.

A few statements still move from intended use to an outcome that the description does not establish. An approved Method Statement may remove an approval-related constraint, where applicable, but it does not ensure execution without delays. Likewise, describing it as “technical proof” of safety and correctness or a “shield against professional liability” goes beyond explaining how the Supervisor uses it. Identifying its contribution to review, verification and documentation would keep these descriptions consistent with your analytical purpose.

A short illustrative example involving a foreperson or crew member could also develop your point about accessibility and comprehension: what instructions do they need, where can they obtain them, and whom should they consult when site conditions differ from those anticipated? Some information may come from related documents rather than the Method Statement itself.

Such an example would illustrate the perspective without requiring an empirical assessment of actual project performance. It could show what User Analysis adds beyond identifying participants: examining whether the information associated with the Method Statement is suited to the responsibilities and actions of those expected to use it.
...
1 reply by Aleksandar Loncar
Nov 19, 2026 3:18 AM
Aleksandar Loncar
...
Luis,

Based on your detailed and comprehensive comments, as well as your extensive email, I have further developed and strengthened my Relational Analysis.
I have revised Example 1 and, following Francisco Chagas's comment, added Example 4, which is presented below and is the most complex example in the analysis.
The revised analysis follows.

NEW FRAMEWORK FOR RELATIONAL ANALYSIS
Relational Analysis
Question: Which project documents is the Method Statement connected to, and how do the relationships between them influence their compliance, traceability, interdependencies, and consistency?

The Method Statement is not an isolated document but an integral part of the project documentation system.
My underlying idea is the following:
Project documents may be individually correct, yet inconsistencies, gaps, or conflicting requirements may only become apparent when their relationships are examined. This is one of the key contributions of Relational Analysis.
Relational Analysis examines the relationships between the Method Statement and other project documents, focusing on their consistency, compliance, traceability, dependencies, and the impact of changes across the documentation system.

Scope of Relational Analysis: Documents, Decisions and Actual Execution

Relational Analysis examines the relationships between project documents, decisions made during project execution, and the actual implementation of the works.
It also considers how decisions that change the originally established methodology, construction sequence or technical arrangements affect the relationships between relevant project documents. Such decisions may alter the assumptions and requirements on which existing documents are based, even before the relevant documents have been formally revised.
The analysis therefore examines whether these decisions are adequately reflected in the relevant documentation and whether the documented requirements and arrangements remain consistent with the work actually performed.
The objective is to identify inconsistencies, missing links or gaps between what was documented, what was decided and what was actually implemented. In this way, Relational Analysis provides an additional perspective for examining the coherence of project documentation and its relationship with project execution.
Relational Analysis can help identify inconsistencies, missing links and gaps between project documentation, decisions and actual execution. However, identifying such issues does not, by itself, establish the cause of a defect, determine whether a particular deficiency led to that defect, or assign responsibility. These conclusions require further investigation, supported by appropriate technical inspections, testing, examination of project records and evaluation of the relevant verification processes. Where a defect is identified, it may also be necessary to examine whether the established quality controls were appropriately designed, effectively implemented and capable of detecting the condition in question. Relational Analysis therefore provides an analytical basis for identifying issues that may require further investigation, rather than replacing technical investigation or determining liability.

HORIZONTAL RELATIONSHIP – Coordination and Alignment
The Method Statement is connected with documents that must remain mutually aligned during project execution:
• Risk Assessment (RA)
• Inspection and Test Plan (ITP)
MS, RA, and ITP are interdependent documents that must remain 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.

VERTICAL RELATIONSHIP – Requirements and Compliance
The Method Statement must reflect and comply with applicable project requirements and constraints arising from:
• Contract
• Applicable laws, regulations, and authority requirements
• Technical specifications
• Design documentation
• Applicable standards
• Project Management Plan
The analysis examines how these requirements are transferred into the Method Statement and whether their implementation can be traced and verified.
The analysis also considers:
• Authority requirements – requirements, permits, approvals, and conditions imposed by relevant authorities.
• Authority and hierarchy of project documents – the formal status and precedence of documents in the event of inconsistencies.

DIAGONAL RELATIONSHIP – Functional and Information Dependencies
The Method Statement also interacts with other project documents through functional and information flows, including:
• Project Schedule
• Project Drawings
• Bill of Quantities (BoQ)
• Resource Plan / Resource Allocation
These relationships involve the transfer, processing, and use of information, as well as dependencies between planning, quantities, resources, design information, and construction methodology.

OVERLAPPING RELATIONSHIPS
Horizontal, vertical and diagonal relationships are not necessarily mutually exclusive. They may overlap, meaning that the same pair of project documents can be connected through more than one type of relationship.
For example, Project Drawings may establish requirements and dimensional constraints that the Method Statement must respect when defining the construction sequence. At the same time, the same drawings may provide dimensional information used in calculations for determining concrete quantities, formwork requirements or lifting arrangements.
Thus, the relationship between the Project Drawings and the Method Statement may involve both compliance with design requirements and the use of design information for planning and technical calculations.
The classification of a relationship therefore depends on the nature of the information exchanged and the function it performs, rather than solely on the two documents involved.

KEY ANALYTICAL DIMENSIONS
Across all three relationship types, Relational Analysis examines:
• Consistency: Whether information, assumptions, and parameters across project documents are mutually consistent.
• Compliance: Whether the Method Statement and related documents comply with applicable requirements.
• Traceability: Whether requirements and information can be traced from their sources through to their incorporation into the Method Statement.
• Dependencies and Interdependencies: How project documents influence and depend on one another.
• Change Impact: How a change in one document affects other related project documents.

The analysis is not limited to identifying whether individual documents exist or are formally correct. It examines whether they function as a consistent and interconnected documentation system.
The primary unit of analysis is therefore not the Method Statement in isolation, but its relationships with other project documents.

HOW EACH RELATIONSHIP IS EXAMINED
Each relationship between the Method Statement and another project document can be examined through three aspects:
• Information, Requirements or Assumptions: What information, requirement, or assumption does the relationship carry?
• Dependencies: What dependencies or interdependencies does it create between the documents?
• Change Impact: What would need to be reconsidered if the information, requirement, or assumption changed?
This approach helps assess not only whether related documents are aligned, but also whether their underlying assumptions are adequate and whether changes in one document require reconsideration of others.

PRACTICAL EXAMPLES
The following examples illustrate how Relational Analysis can reveal inconsistencies, dependencies, and information flows between the Method Statement and other project documents.

Example 1 – Method Statement ↔ Project Schedule: Consistency
Hypothetical example based on a real construction situation

A massive river pier foundation required approximately 2,000 m³ of concrete. An initial average placing rate of 125–130 m³/h was anticipated, but the actual rate was approximately 70 m³/h, and concreting took around 28 hours.
The Method Statement indicated two concreting phases and a total duration of 24 hours. However, before the operation began, it was decided to carry out the concreting in one continuous phase, but the Method Statement was not revised. For illustration, the Project Schedule is assumed to have allocated 22 hours; this figure is not taken from the original project Schedule, which was unavailable.
Relational Analysis examines whether the Method Statement and Project Schedule remain consistent when the planned execution approach changes, including whether the relevant documents are updated to reflect the same construction sequence.

Example 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.

Example 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.

Example 4 – Interfaces between Construction Activities

Context:
On construction projects involving multiple contractors or work packages, individual construction activities may be covered by separate Method Statements, ITPs and inspection records. Each contractor may complete and verify its own scope of work, without necessarily ensuring that the interfaces between different work packages are adequately addressed.
Interfaces between construction activities
Individual work packages may each comply with their approved Method Statements, ITPs and inspection records. However, this does not necessarily ensure that the interfaces between them are properly managed.
For example, separate contractors may complete and verify their respective scopes, while the connection between their works remains insufficiently defined, coordinated or inspected.
Relational Analysis can help identify such gaps by examining whether the relevant documents, construction activities and responsibilities are properly aligned at their interfaces.
The issue may not lie within any individual document or work package, but in the relationship between them.
Key Observation:
A gap may exist even when individual documents are internally correct and mutually consistent, if an important interface or dependency between the activities they address is not adequately reflected in their content.
For Example:
• Method Statement A correctly defines the execution of the structural works.
• Method Statement B correctly defines the installation of the waterproofing system.
• Project Drawings correctly show the structural elements and the waterproofing details, including the penetration through the structure.
• The respective ITPs correctly define the inspection and verification requirements for each individual work package.
There may be no apparent contradiction between these documents. However, none of them adequately defines how the interface at the penetration through the structure is to be inspected and verified, particularly how the continuity and integrity of the waterproofing system are to be ensured at this location.
Relational Analysis Question:
Are the interfaces between different construction activities adequately addressed and coordinated across the Method Statements and related project documents?

COMPARATIVE ANALYSIS – CHANGE FROM TWO TO THREE CONCRETING STAGES
Consider a Method Statement revised to change riverbed pier concreting from two stages to three.
The same change can be examined from three different analytical perspectives:
• 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 Method Statement defines and guides the revised concreting sequence.
• Relational Analysis examines how this change affects the Risk Assessment, ITP, Project Schedule, and other related documents, and whether they remain consistent with the revised methodology.
This comparison illustrates the distinction between the three perspectives:
• Workflow Analysis focuses on the document's development and use.
• Functional Analysis focuses on the document's functions.
• Relational Analysis focuses on the relationships, dependencies, and consistency between documents.

WHAT RELATIONAL ANALYSIS CAN REVEAL
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.
avatar
Aleksandar Loncar Niš, Serbia
Nov 16, 2026 6:48 AM
Replying to Luis Branco
...
Thank you, Aleksandar. The new paragraphs give User Analysis a clearer analytical basis by connecting the document’s functions with users’ information needs, responsibilities and authority. Your clarification that different uses do not necessarily imply conflicting interests also strengthens the conclusion.

In my reading, this supports User Analysis as a distinct perspective. The next refinement would be to bring the retained role descriptions into closer alignment with that definition. For each participant, the analysis could identify the information needed, its intended use, the decision or action it supports, and the relevant responsibility and limits of authority. Not every user needs approval authority: consulting, executing, checking and recommending are also meaningful uses.

Your Engineer description already makes a useful distinction between providing a technical opinion and granting final approval. Applying similar precision to the Supervisor could clarify what information is needed to examine a discrepancy, what action the Supervisor may take, and what requires referral to someone else.

A few statements still move from intended use to an outcome that the description does not establish. An approved Method Statement may remove an approval-related constraint, where applicable, but it does not ensure execution without delays. Likewise, describing it as “technical proof” of safety and correctness or a “shield against professional liability” goes beyond explaining how the Supervisor uses it. Identifying its contribution to review, verification and documentation would keep these descriptions consistent with your analytical purpose.

A short illustrative example involving a foreperson or crew member could also develop your point about accessibility and comprehension: what instructions do they need, where can they obtain them, and whom should they consult when site conditions differ from those anticipated? Some information may come from related documents rather than the Method Statement itself.

Such an example would illustrate the perspective without requiring an empirical assessment of actual project performance. It could show what User Analysis adds beyond identifying participants: examining whether the information associated with the Method Statement is suited to the responsibilities and actions of those expected to use it.
Luis,

Based on your detailed and comprehensive comments, as well as your extensive email, I have further developed and strengthened my Relational Analysis.
I have revised Example 1 and, following Francisco Chagas's comment, added Example 4, which is presented below and is the most complex example in the analysis.
The revised analysis follows.

NEW FRAMEWORK FOR RELATIONAL ANALYSIS
Relational Analysis
Question: Which project documents is the Method Statement connected to, and how do the relationships between them influence their compliance, traceability, interdependencies, and consistency?

The Method Statement is not an isolated document but an integral part of the project documentation system.
My underlying idea is the following:
Project documents may be individually correct, yet inconsistencies, gaps, or conflicting requirements may only become apparent when their relationships are examined. This is one of the key contributions of Relational Analysis.
Relational Analysis examines the relationships between the Method Statement and other project documents, focusing on their consistency, compliance, traceability, dependencies, and the impact of changes across the documentation system.

Scope of Relational Analysis: Documents, Decisions and Actual Execution

Relational Analysis examines the relationships between project documents, decisions made during project execution, and the actual implementation of the works.
It also considers how decisions that change the originally established methodology, construction sequence or technical arrangements affect the relationships between relevant project documents. Such decisions may alter the assumptions and requirements on which existing documents are based, even before the relevant documents have been formally revised.
The analysis therefore examines whether these decisions are adequately reflected in the relevant documentation and whether the documented requirements and arrangements remain consistent with the work actually performed.
The objective is to identify inconsistencies, missing links or gaps between what was documented, what was decided and what was actually implemented. In this way, Relational Analysis provides an additional perspective for examining the coherence of project documentation and its relationship with project execution.
Relational Analysis can help identify inconsistencies, missing links and gaps between project documentation, decisions and actual execution. However, identifying such issues does not, by itself, establish the cause of a defect, determine whether a particular deficiency led to that defect, or assign responsibility. These conclusions require further investigation, supported by appropriate technical inspections, testing, examination of project records and evaluation of the relevant verification processes. Where a defect is identified, it may also be necessary to examine whether the established quality controls were appropriately designed, effectively implemented and capable of detecting the condition in question. Relational Analysis therefore provides an analytical basis for identifying issues that may require further investigation, rather than replacing technical investigation or determining liability.

HORIZONTAL RELATIONSHIP – Coordination and Alignment
The Method Statement is connected with documents that must remain mutually aligned during project execution:
• Risk Assessment (RA)
• Inspection and Test Plan (ITP)
MS, RA, and ITP are interdependent documents that must remain 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.

VERTICAL RELATIONSHIP – Requirements and Compliance
The Method Statement must reflect and comply with applicable project requirements and constraints arising from:
• Contract
• Applicable laws, regulations, and authority requirements
• Technical specifications
• Design documentation
• Applicable standards
• Project Management Plan
The analysis examines how these requirements are transferred into the Method Statement and whether their implementation can be traced and verified.
The analysis also considers:
• Authority requirements – requirements, permits, approvals, and conditions imposed by relevant authorities.
• Authority and hierarchy of project documents – the formal status and precedence of documents in the event of inconsistencies.

DIAGONAL RELATIONSHIP – Functional and Information Dependencies
The Method Statement also interacts with other project documents through functional and information flows, including:
• Project Schedule
• Project Drawings
• Bill of Quantities (BoQ)
• Resource Plan / Resource Allocation
These relationships involve the transfer, processing, and use of information, as well as dependencies between planning, quantities, resources, design information, and construction methodology.

OVERLAPPING RELATIONSHIPS
Horizontal, vertical and diagonal relationships are not necessarily mutually exclusive. They may overlap, meaning that the same pair of project documents can be connected through more than one type of relationship.
For example, Project Drawings may establish requirements and dimensional constraints that the Method Statement must respect when defining the construction sequence. At the same time, the same drawings may provide dimensional information used in calculations for determining concrete quantities, formwork requirements or lifting arrangements.
Thus, the relationship between the Project Drawings and the Method Statement may involve both compliance with design requirements and the use of design information for planning and technical calculations.
The classification of a relationship therefore depends on the nature of the information exchanged and the function it performs, rather than solely on the two documents involved.

KEY ANALYTICAL DIMENSIONS
Across all three relationship types, Relational Analysis examines:
• Consistency: Whether information, assumptions, and parameters across project documents are mutually consistent.
• Compliance: Whether the Method Statement and related documents comply with applicable requirements.
• Traceability: Whether requirements and information can be traced from their sources through to their incorporation into the Method Statement.
• Dependencies and Interdependencies: How project documents influence and depend on one another.
• Change Impact: How a change in one document affects other related project documents.

The analysis is not limited to identifying whether individual documents exist or are formally correct. It examines whether they function as a consistent and interconnected documentation system.
The primary unit of analysis is therefore not the Method Statement in isolation, but its relationships with other project documents.

HOW EACH RELATIONSHIP IS EXAMINED
Each relationship between the Method Statement and another project document can be examined through three aspects:
• Information, Requirements or Assumptions: What information, requirement, or assumption does the relationship carry?
• Dependencies: What dependencies or interdependencies does it create between the documents?
• Change Impact: What would need to be reconsidered if the information, requirement, or assumption changed?
This approach helps assess not only whether related documents are aligned, but also whether their underlying assumptions are adequate and whether changes in one document require reconsideration of others.

PRACTICAL EXAMPLES
The following examples illustrate how Relational Analysis can reveal inconsistencies, dependencies, and information flows between the Method Statement and other project documents.

Example 1 – Method Statement ↔ Project Schedule: Consistency
Hypothetical example based on a real construction situation

A massive river pier foundation required approximately 2,000 m³ of concrete. An initial average placing rate of 125–130 m³/h was anticipated, but the actual rate was approximately 70 m³/h, and concreting took around 28 hours.
The Method Statement indicated two concreting phases and a total duration of 24 hours. However, before the operation began, it was decided to carry out the concreting in one continuous phase, but the Method Statement was not revised. For illustration, the Project Schedule is assumed to have allocated 22 hours; this figure is not taken from the original project Schedule, which was unavailable.
Relational Analysis examines whether the Method Statement and Project Schedule remain consistent when the planned execution approach changes, including whether the relevant documents are updated to reflect the same construction sequence.

Example 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.

Example 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.

Example 4 – Interfaces between Construction Activities

Context:
On construction projects involving multiple contractors or work packages, individual construction activities may be covered by separate Method Statements, ITPs and inspection records. Each contractor may complete and verify its own scope of work, without necessarily ensuring that the interfaces between different work packages are adequately addressed.
Interfaces between construction activities
Individual work packages may each comply with their approved Method Statements, ITPs and inspection records. However, this does not necessarily ensure that the interfaces between them are properly managed.
For example, separate contractors may complete and verify their respective scopes, while the connection between their works remains insufficiently defined, coordinated or inspected.
Relational Analysis can help identify such gaps by examining whether the relevant documents, construction activities and responsibilities are properly aligned at their interfaces.
The issue may not lie within any individual document or work package, but in the relationship between them.
Key Observation:
A gap may exist even when individual documents are internally correct and mutually consistent, if an important interface or dependency between the activities they address is not adequately reflected in their content.
For Example:
• Method Statement A correctly defines the execution of the structural works.
• Method Statement B correctly defines the installation of the waterproofing system.
• Project Drawings correctly show the structural elements and the waterproofing details, including the penetration through the structure.
• The respective ITPs correctly define the inspection and verification requirements for each individual work package.
There may be no apparent contradiction between these documents. However, none of them adequately defines how the interface at the penetration through the structure is to be inspected and verified, particularly how the continuity and integrity of the waterproofing system are to be ensured at this location.
Relational Analysis Question:
Are the interfaces between different construction activities adequately addressed and coordinated across the Method Statements and related project documents?

COMPARATIVE ANALYSIS – CHANGE FROM TWO TO THREE CONCRETING STAGES
Consider a Method Statement revised to change riverbed pier concreting from two stages to three.
The same change can be examined from three different analytical perspectives:
• 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 Method Statement defines and guides the revised concreting sequence.
• Relational Analysis examines how this change affects the Risk Assessment, ITP, Project Schedule, and other related documents, and whether they remain consistent with the revised methodology.
This comparison illustrates the distinction between the three perspectives:
• Workflow Analysis focuses on the document's development and use.
• Functional Analysis focuses on the document's functions.
• Relational Analysis focuses on the relationships, dependencies, and consistency between documents.

WHAT RELATIONAL ANALYSIS CAN REVEAL
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.
...
1 reply by Luis Branco
Nov 19, 2026 5:51 AM
Luis Branco
...
Thank you, Aleksandar. This revision strengthens the framework in several specific ways. You now explicitly recognise overlapping relationships, clarify the illustrative status of the schedule figure, and distinguish identifying a gap from establishing causation or responsibility.

Example 4, developed following Francisco’s contribution, adds a particularly useful insight: documents can be mutually consistent while leaving an important interface insufficiently addressed. Consistency and adequate coverage are therefore distinct questions. This also shows that Relational Analysis can identify gaps that existed from the outset, without requiring a subsequent change to expose them.

Your example establishes the gap within the documents described. When applying the framework to an actual project, it would also be useful to define the scope of the review and check whether an applicable procedure or inspection requirement addresses the interface elsewhere. The analysis could then examine how that provision connects to the relevant work packages and whether responsibility for the required verification is clear. This would help distinguish an absent provision from one that exists but is insufficiently connected to the work.

The main conceptual clarification concerns scope. Your new section extends the analysis to relationships between documentation, decisions and actual execution, while the opening question and final definition remain focused on relationships between documents. Both can contribute, but it would help to state whether the broader examination is an application of the documentary perspective or part of its defining scope, then carry that choice through the framework.

Example 1 illustrates why this matters. The decision to move from two concreting phases to one continuous operation without revising the Method Statement now appears to be its strongest analytical feature. To establish a specific inconsistency with the illustrative schedule, readers would also need to know which execution sequence its 22 hours represent and whether the durations cover comparable activities.

One further distinction would strengthen the expanded scope: agreement between documents, decisions and execution does not, by itself, establish compliance with applicable requirements. A decision may require a change to the documentation without being sufficient to authorise a change to a requirement.

Similarly, your questions about assumptions could include what supports each assumption and under what conditions it remains applicable. This would help distinguish documents agreeing with one another from their shared assumptions being adequately supported.

These refinements would build on the contribution already visible in your examples: examining contradictions, missing connections and the coverage of interfaces, while keeping each conclusion within what the available information supports.
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
Nov 19, 2026 3:18 AM
Replying to Aleksandar Loncar
...
Luis,

Based on your detailed and comprehensive comments, as well as your extensive email, I have further developed and strengthened my Relational Analysis.
I have revised Example 1 and, following Francisco Chagas's comment, added Example 4, which is presented below and is the most complex example in the analysis.
The revised analysis follows.

NEW FRAMEWORK FOR RELATIONAL ANALYSIS
Relational Analysis
Question: Which project documents is the Method Statement connected to, and how do the relationships between them influence their compliance, traceability, interdependencies, and consistency?

The Method Statement is not an isolated document but an integral part of the project documentation system.
My underlying idea is the following:
Project documents may be individually correct, yet inconsistencies, gaps, or conflicting requirements may only become apparent when their relationships are examined. This is one of the key contributions of Relational Analysis.
Relational Analysis examines the relationships between the Method Statement and other project documents, focusing on their consistency, compliance, traceability, dependencies, and the impact of changes across the documentation system.

Scope of Relational Analysis: Documents, Decisions and Actual Execution

Relational Analysis examines the relationships between project documents, decisions made during project execution, and the actual implementation of the works.
It also considers how decisions that change the originally established methodology, construction sequence or technical arrangements affect the relationships between relevant project documents. Such decisions may alter the assumptions and requirements on which existing documents are based, even before the relevant documents have been formally revised.
The analysis therefore examines whether these decisions are adequately reflected in the relevant documentation and whether the documented requirements and arrangements remain consistent with the work actually performed.
The objective is to identify inconsistencies, missing links or gaps between what was documented, what was decided and what was actually implemented. In this way, Relational Analysis provides an additional perspective for examining the coherence of project documentation and its relationship with project execution.
Relational Analysis can help identify inconsistencies, missing links and gaps between project documentation, decisions and actual execution. However, identifying such issues does not, by itself, establish the cause of a defect, determine whether a particular deficiency led to that defect, or assign responsibility. These conclusions require further investigation, supported by appropriate technical inspections, testing, examination of project records and evaluation of the relevant verification processes. Where a defect is identified, it may also be necessary to examine whether the established quality controls were appropriately designed, effectively implemented and capable of detecting the condition in question. Relational Analysis therefore provides an analytical basis for identifying issues that may require further investigation, rather than replacing technical investigation or determining liability.

HORIZONTAL RELATIONSHIP – Coordination and Alignment
The Method Statement is connected with documents that must remain mutually aligned during project execution:
• Risk Assessment (RA)
• Inspection and Test Plan (ITP)
MS, RA, and ITP are interdependent documents that must remain 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.

VERTICAL RELATIONSHIP – Requirements and Compliance
The Method Statement must reflect and comply with applicable project requirements and constraints arising from:
• Contract
• Applicable laws, regulations, and authority requirements
• Technical specifications
• Design documentation
• Applicable standards
• Project Management Plan
The analysis examines how these requirements are transferred into the Method Statement and whether their implementation can be traced and verified.
The analysis also considers:
• Authority requirements – requirements, permits, approvals, and conditions imposed by relevant authorities.
• Authority and hierarchy of project documents – the formal status and precedence of documents in the event of inconsistencies.

DIAGONAL RELATIONSHIP – Functional and Information Dependencies
The Method Statement also interacts with other project documents through functional and information flows, including:
• Project Schedule
• Project Drawings
• Bill of Quantities (BoQ)
• Resource Plan / Resource Allocation
These relationships involve the transfer, processing, and use of information, as well as dependencies between planning, quantities, resources, design information, and construction methodology.

OVERLAPPING RELATIONSHIPS
Horizontal, vertical and diagonal relationships are not necessarily mutually exclusive. They may overlap, meaning that the same pair of project documents can be connected through more than one type of relationship.
For example, Project Drawings may establish requirements and dimensional constraints that the Method Statement must respect when defining the construction sequence. At the same time, the same drawings may provide dimensional information used in calculations for determining concrete quantities, formwork requirements or lifting arrangements.
Thus, the relationship between the Project Drawings and the Method Statement may involve both compliance with design requirements and the use of design information for planning and technical calculations.
The classification of a relationship therefore depends on the nature of the information exchanged and the function it performs, rather than solely on the two documents involved.

KEY ANALYTICAL DIMENSIONS
Across all three relationship types, Relational Analysis examines:
• Consistency: Whether information, assumptions, and parameters across project documents are mutually consistent.
• Compliance: Whether the Method Statement and related documents comply with applicable requirements.
• Traceability: Whether requirements and information can be traced from their sources through to their incorporation into the Method Statement.
• Dependencies and Interdependencies: How project documents influence and depend on one another.
• Change Impact: How a change in one document affects other related project documents.

The analysis is not limited to identifying whether individual documents exist or are formally correct. It examines whether they function as a consistent and interconnected documentation system.
The primary unit of analysis is therefore not the Method Statement in isolation, but its relationships with other project documents.

HOW EACH RELATIONSHIP IS EXAMINED
Each relationship between the Method Statement and another project document can be examined through three aspects:
• Information, Requirements or Assumptions: What information, requirement, or assumption does the relationship carry?
• Dependencies: What dependencies or interdependencies does it create between the documents?
• Change Impact: What would need to be reconsidered if the information, requirement, or assumption changed?
This approach helps assess not only whether related documents are aligned, but also whether their underlying assumptions are adequate and whether changes in one document require reconsideration of others.

PRACTICAL EXAMPLES
The following examples illustrate how Relational Analysis can reveal inconsistencies, dependencies, and information flows between the Method Statement and other project documents.

Example 1 – Method Statement ↔ Project Schedule: Consistency
Hypothetical example based on a real construction situation

A massive river pier foundation required approximately 2,000 m³ of concrete. An initial average placing rate of 125–130 m³/h was anticipated, but the actual rate was approximately 70 m³/h, and concreting took around 28 hours.
The Method Statement indicated two concreting phases and a total duration of 24 hours. However, before the operation began, it was decided to carry out the concreting in one continuous phase, but the Method Statement was not revised. For illustration, the Project Schedule is assumed to have allocated 22 hours; this figure is not taken from the original project Schedule, which was unavailable.
Relational Analysis examines whether the Method Statement and Project Schedule remain consistent when the planned execution approach changes, including whether the relevant documents are updated to reflect the same construction sequence.

Example 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.

Example 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.

Example 4 – Interfaces between Construction Activities

Context:
On construction projects involving multiple contractors or work packages, individual construction activities may be covered by separate Method Statements, ITPs and inspection records. Each contractor may complete and verify its own scope of work, without necessarily ensuring that the interfaces between different work packages are adequately addressed.
Interfaces between construction activities
Individual work packages may each comply with their approved Method Statements, ITPs and inspection records. However, this does not necessarily ensure that the interfaces between them are properly managed.
For example, separate contractors may complete and verify their respective scopes, while the connection between their works remains insufficiently defined, coordinated or inspected.
Relational Analysis can help identify such gaps by examining whether the relevant documents, construction activities and responsibilities are properly aligned at their interfaces.
The issue may not lie within any individual document or work package, but in the relationship between them.
Key Observation:
A gap may exist even when individual documents are internally correct and mutually consistent, if an important interface or dependency between the activities they address is not adequately reflected in their content.
For Example:
• Method Statement A correctly defines the execution of the structural works.
• Method Statement B correctly defines the installation of the waterproofing system.
• Project Drawings correctly show the structural elements and the waterproofing details, including the penetration through the structure.
• The respective ITPs correctly define the inspection and verification requirements for each individual work package.
There may be no apparent contradiction between these documents. However, none of them adequately defines how the interface at the penetration through the structure is to be inspected and verified, particularly how the continuity and integrity of the waterproofing system are to be ensured at this location.
Relational Analysis Question:
Are the interfaces between different construction activities adequately addressed and coordinated across the Method Statements and related project documents?

COMPARATIVE ANALYSIS – CHANGE FROM TWO TO THREE CONCRETING STAGES
Consider a Method Statement revised to change riverbed pier concreting from two stages to three.
The same change can be examined from three different analytical perspectives:
• 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 Method Statement defines and guides the revised concreting sequence.
• Relational Analysis examines how this change affects the Risk Assessment, ITP, Project Schedule, and other related documents, and whether they remain consistent with the revised methodology.
This comparison illustrates the distinction between the three perspectives:
• Workflow Analysis focuses on the document's development and use.
• Functional Analysis focuses on the document's functions.
• Relational Analysis focuses on the relationships, dependencies, and consistency between documents.

WHAT RELATIONAL ANALYSIS CAN REVEAL
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.
Thank you, Aleksandar. This revision strengthens the framework in several specific ways. You now explicitly recognise overlapping relationships, clarify the illustrative status of the schedule figure, and distinguish identifying a gap from establishing causation or responsibility.

Example 4, developed following Francisco’s contribution, adds a particularly useful insight: documents can be mutually consistent while leaving an important interface insufficiently addressed. Consistency and adequate coverage are therefore distinct questions. This also shows that Relational Analysis can identify gaps that existed from the outset, without requiring a subsequent change to expose them.

Your example establishes the gap within the documents described. When applying the framework to an actual project, it would also be useful to define the scope of the review and check whether an applicable procedure or inspection requirement addresses the interface elsewhere. The analysis could then examine how that provision connects to the relevant work packages and whether responsibility for the required verification is clear. This would help distinguish an absent provision from one that exists but is insufficiently connected to the work.

The main conceptual clarification concerns scope. Your new section extends the analysis to relationships between documentation, decisions and actual execution, while the opening question and final definition remain focused on relationships between documents. Both can contribute, but it would help to state whether the broader examination is an application of the documentary perspective or part of its defining scope, then carry that choice through the framework.

Example 1 illustrates why this matters. The decision to move from two concreting phases to one continuous operation without revising the Method Statement now appears to be its strongest analytical feature. To establish a specific inconsistency with the illustrative schedule, readers would also need to know which execution sequence its 22 hours represent and whether the durations cover comparable activities.

One further distinction would strengthen the expanded scope: agreement between documents, decisions and execution does not, by itself, establish compliance with applicable requirements. A decision may require a change to the documentation without being sufficient to authorise a change to a requirement.

Similarly, your questions about assumptions could include what supports each assumption and under what conditions it remains applicable. This would help distinguish documents agreeing with one another from their shared assumptions being adequately supported.

These refinements would build on the contribution already visible in your examples: examining contradictions, missing connections and the coverage of interfaces, while keeping each conclusion within what the available information supports.
< 1 2 3 4 >

Please login or join to reply

Content ID:

"A good composer does not imitate; he steals."

- Igor Stravinsky

Sponsors