Method Statement

A method statement is where a supplier translates capability into credibility. Any supplier can claim to be experienced and professional; a well-written method statement demonstrates specifically how the work will be done, who will do it, what controls will be in place, and what the buyer can expect at each stage. In European public procurement evaluations, method statements are among the most heavily weighted scored quality sections in service and works contracts.

What is a method statement?

A method statement is a structured narrative within a technical proposal that sets out a supplier's planned approach to delivering a defined element of the contract. It answers the question: not just what will be done, but how, by whom, in what sequence, and with what safeguards.

A method statement for a mobilisation phase, for instance, would typically cover:

• The key activities and their sequencing from contract award to go-live.
• Roles and responsibilities of named individuals or defined roles.
• Interfaces with the contracting authority during transition.
• Risks and their mitigations specific to this contract.
• Quality and assurance checkpoints.
• Measurable milestones and evidence of readiness.

The depth and focus of a method statement depend on the scoring criteria. If the invitation to tender allocates 25 marks for mobilisation methodology, the method statement should be proportionately detailed. If it allocates 5 marks, a concise, evidence-led paragraph may suffice.

Method statements are a core component of the bid library. A standard mobilisation method statement, a quality management method statement, or a workforce training method statement can be maintained as reusable templates and tailored to each contract rather than drafted from scratch. The tailoring matters: a generic method statement that makes no reference to the specific contract context, the buyer's sector, or the particular delivery challenges scores significantly lower than one that integrates those specifics.

Under Directive 2014/24/EU, technical quality criteria are scored against the subject matter of the contract. A method statement that is written for the wrong type of contract, or at the wrong level of complexity, signals that the supplier has not read the specification carefully. Evaluators notice this.

Why method statements matter for bidders

Method statements typically represent a large proportion of the quality marks available in a service or works tender. A supplier who understands the marking scheme and writes method statements that directly address each sub-criterion, with supporting case study evidence where available, can outperform larger, more experienced competitors who submit generic responses.

The method statement also functions as a commitment. Evaluators and contract managers will return to it after award as the baseline for what was promised. Writing a method statement that the organisation cannot actually deliver creates risk post-award.

Example

A Danish construction management firm is bidding for a public building refurbishment contract in Sweden. The evaluation criterion for project methodology is worth 35 marks and has three sub-criteria: programme management (15 marks), stakeholder communication (10 marks), and quality assurance (10 marks). The bid team writes three distinct method statement sections, each opening with a direct answer to the sub-criterion, embedding a specific example from a comparable Norwegian contract, and quantifying the proposed approach (weekly progress meetings, monthly client reports, four inspection hold points). The methodology section scores 31 out of 35.

Frequently Asked Questions

How long should a method statement be?

Long enough to address every element of the evaluation criterion fully, and no longer. Many buyers set page limits per section. Where no limit is set, a useful guide is one to two pages per significant criterion sub-heading. Padding reduces clarity and can cost marks if evaluators cannot quickly locate the relevant evidence.

Should method statements include diagrams or tables?

Yes, where they improve clarity. A timeline diagram for a mobilisation plan, a RACI matrix for governance, or a risk register table can communicate complex information more efficiently than prose. Check the buyer's format requirements: some e-procurement portals have restrictions on embedded graphics.

What is the difference between a method statement and a technical specification?

A technical specification describes what the buyer requires. A method statement describes how the supplier will meet that requirement. The method statement is always written by the supplier in response to the specification.