What Is a Methodology Statement?

A Methodology Statement sets out the steps a task or scope of work requires from start to finish. Simple enough, right?

But its real purpose goes beyond listing actions.

A methodology statement is not political, and it is not documentation for documentation’s sake. Its purpose is to require the vendor’s stakeholders—including managers and workers—to think through the work before arriving on site.

It asks the “what if?” questions along the way and answers them in advance.

This is not a sales document. There is no sugar-coating, no benefits or feature lists. Instead, it focuses on:

  • Raw actions and sequences
  • Possible consequences
  • Follow-up actions
  • Timelines
  • Safety strategies
  • Controls and contingencies

All presented clearly, logically, and honestly.


Why Write a Methodology Statement?

“We cannot solve our problems with the same thinking we used when we created them.”
— Albert Einstein

In facility management, suppliers and contractors are often asked to provide a methodology statement detailing how their work will be completed.

This may relate to:

  • A tender, proposal, or project
  • Scheduled or planned maintenance
  • Reactive or corrective maintenance
  • Repairs requiring coordination, access, or risk controls

Procurement teams request methodology statements for several important reasons.


Methodology Statements in Tender Submissions

A methodology statement is commonly requested as part of a Request for Tender (RFT) process.

It allows the procurement team to gain insight into a vendor’s:

  • Business systems and processes
  • Planning capability
  • Safety awareness
  • Compliance maturity

The statement gives the vendor an opportunity to demonstrate how the work will be delivered:

  • On time
  • Safely
  • In compliance with legislation, site rules, and best practice

Safety and the Methodology Statement

A Safe Work Method Statement (SWMS) has a specific legal and safety agenda, focusing on high-risk activities and worst-case scenarios.

While a methodology statement is broader, safety must still be embedded throughout.

Procurement teams are actively identifying and mitigating risk, including risks to:

  • People
  • Property
  • Finances
  • Tenants and occupants
  • Business continuity
  • Reputation

A well-written methodology statement demonstrates that these risks have been identified, considered, and controlled.


Risk: The Primary Driver

Risk control is the primary motivation behind requesting a methodology statement.

From the procurement perspective, the document supports internal risk management policies and governance obligations.

From the vendor’s perspective, it encourages discussion and inquiry into scenarios that may not have been previously considered—before they become problems on site.


Why Facility Managers Require Method Statements

Risk Management

From a Facility Manager’s point of view, a methodology statement that clearly demonstrates:

  • Competence
  • Safety awareness
  • Industry knowledge
  • Consideration for people and property

…significantly increases confidence in issuing a purchase order.

Vendors may argue that a methodology statement is “just a document” and that on-site reality can differ.

While this can be true, it rarely occurs to any meaningful extent.

Why?

Because methodology statements sit alongside:

  • Vendor vetting
  • Safety documentation
  • Compliance checks
  • Performance reviews

A contractor who consistently deviates from their own methodology:

  • Will not receive further work
  • Will face payment delays or disputes
  • Will quickly lose credibility

A competent vendor does not invest time in writing a compliant methodology statement only to ignore it later.

Vetting complete.


Don’t Write a Novel

Some vendors feel uncomfortable and overcompensate by writing a novel—chapters and verses included.

Phrases like “gained access to the floor” add no value.
We know you caught the lift and opened the door.

What we want:

  • Clear steps
  • Relevant detail
  • Logical sequencing
  • Practical controls

What we don’t want:

  • Fluff
  • Storytelling
  • Unnecessary narration

Dot points are preferred.
Be concise. Be precise. Get to the point.


See you on site.

Leave a Reply

Your email address will not be published. Required fields are marked *


Math Captcha
21 − = 16


G-SLGPRTJ2RY