top of page
Search

The Guardian Structural Repair Series — GSR-013 What Is a Structural Repair Method Statement? A Practical Site Guide for Planning, Executing & Controlling Concrete Repairs.

Aug 19
6 min read

Updated: Sep 14

By The Guardian


The Chief Technical Advisor


GUGAFIX® Construction Chemicals


A Repair Should Not Begin With a Trowel

One of the most overlooked aspects of structural repair is planning the work before execution begins.

A contractor may have:

  • The repair material

  • Skilled workers

  • Mixing equipment

  • Tools

Yet the repair can still go wrong if nobody has clearly documented:

What is being repaired?

Why is it being repaired?

How will it be repaired?

What materials will be used?

What quality checks are required?

This is where a Structural Repair Method Statement becomes important.

What Is a Method Statement?

A method statement is a documented procedure describing how a particular construction or repair activity is intended to be carried out safely and in accordance with the approved project requirements.

For structural repair, it can provide a common reference for:

  • Site engineers

  • Contractors

  • Applicators

  • QA/QC personnel

  • Consultants

  • Project managers

It helps convert an engineering requirement into a controlled site execution process.

The Guardian's Principle

"If the repair method exists only in someone's head, it is difficult to control, inspect or reproduce."

A properly prepared method statement creates a common understanding before work begins.

1. Define the Scope of Repair

The first section should clearly establish:

  • Structure / building

  • Structural element

  • Location

  • Type of deterioration

  • Approximate repair area

  • Repair objective

For example:

RCC column — concrete spalling and localized section loss — rehabilitation according to approved structural repair design.

The scope should be specific enough that the site team understands exactly what work is covered.

2. Describe the Existing Condition

The method statement should explain the condition that led to the repair.

This may include:

  • Spalling

  • Honeycombing

  • Cracking

  • Exposed reinforcement

  • Concrete deterioration

  • Localized section loss

Where relevant, supporting inspection records, photographs or test reports may form part of the project documentation.

3. Establish the Repair Methodology

This is the heart of the document.

It should explain the sequence of work.

A typical sequence might be:

1. Identify & Mark

Define the repair zone.

↓

2. Remove Unsound Concrete

Expose suitable sound substrate.

↓

3. Inspect Reinforcement

Assess exposed reinforcement and follow the approved treatment.

↓

4. Prepare Substrate

Clean and prepare according to the repair system.

↓

5. Install Formwork / Reinforcement

Where required by the repair design.

↓

6. Mix Repair Material

Follow the manufacturer's specified procedure.

↓

7. Place Repair Material

Use the approved placement method.

↓

8. Cure

Follow the specified curing procedure.

↓

9. Inspect

Record the completed repair.

4. Identify the Materials

The method statement should identify the materials being used.

Depending on the repair system, this could include:

  • Repair mortar

  • Micro Concrete

  • Bonding system

  • Reinforcement treatment system

  • Formwork materials

  • Curing materials

The product should be identified by its actual approved product name and specification.

Avoid vague descriptions such as:

"Use good-quality repair material."

A professional document should identify exactly what has been approved.

5. Reference the Technical Data Sheet

The method statement should not replace the product Technical Data Sheet.

It should work together with it.

Important product-specific information may include:

  • Mixing procedure

  • Water requirement

  • Application thickness

  • Working time

  • Placement method

  • Curing requirements

  • Storage conditions

  • Applicable limitations

The manufacturer's current Technical Data Sheet should always be treated as the controlling reference for product-specific application requirements.

6. Explain Surface Preparation

Surface preparation should be described clearly.

Depending on the approved repair system, the process may include:

  • Removing unsound concrete

  • Cleaning the substrate

  • Removing dust and loose particles

  • Preparing exposed reinforcement

  • Achieving the specified substrate condition

The objective is to establish the appropriate interface for the repair system.

7. Define the Mixing Procedure

A good method statement should remove guesswork.

It should identify:

Material → Equipment → Water → Mixing Sequence → Mixing Time → Placement

The exact parameters must come from the approved product documentation.

Never write:

"Add water as required."

That creates uncontrolled variation.

Instead, specify the manufacturer's approved mixing procedure.

8. Define the Placement Procedure

The document should explain:

  • Where placement starts

  • How material will reach the repair zone

  • Whether formwork is required

  • How the repair zone will be filled

  • How interruptions will be handled

  • How reinforcement congestion will be addressed

For flowable Micro Concrete applications, placement planning becomes particularly important where the repair geometry is deep or confined.

9. Include Curing Requirements

Curing should be a specific section—not an afterthought.

The method statement should identify the curing procedure appropriate to the approved product and project conditions.

The repair team should know:

When curing begins → how the repair is protected → how long the required procedure continues.

10. Quality Control & Inspection

A professional method statement should establish the inspection points.

Before repair


Repair area identified

Unsound concrete removal verified

Reinforcement inspected

Substrate condition checked

Before placement

Material approved

Batch checked

Mixing equipment ready

Formwork checked

Water measurement controlled

During placement

Mixing procedure followed

Placement monitored

Formwork monitored

Repair zone adequately filled

After placement

Curing completed

Surface inspected

Defects recorded

Final acceptance documented

11. Include Responsibilities

This is often overlooked.

A method statement should make responsibilities clear.

For example:

Structural Engineer / Consultant

Design and technical approval where applicable.

Site Engineer

Execution supervision.

Contractor

Resources, manpower and execution.

QA/QC Team

Inspection, documentation and testing as specified.

Applicator

Correct execution of the approved procedure.

Clear responsibility reduces the possibility of:

"I thought someone else was checking it."

12. Safety Should Be Part of the Method Statement

Structural repair can involve:

  • Breaking concrete

  • Exposed reinforcement

  • Working at height

  • Dust

  • Power tools

  • Heavy materials

  • Wet cementitious materials

  • Restricted working areas

The project-specific safety requirements should therefore be incorporated into the approved work procedure.

13. What a Good Method Statement Should NOT Do

A method statement should not:

Invent product specifications

Override the Technical Data Sheet

Replace structural design

Give workers freedom to improvise critical parameters

Use vague instructions

Ignore site-specific conditions

The method statement is a control document, not a piece of generic marketing literature.

The Guardian's Method Statement Structure

A practical structural repair method statement can be organized as:

01 — Project & Location

02 — Scope of Work

03 — Existing Condition

04 — Repair Objective

05 — Approved Materials

06 — Equipment & Tools

07 — Surface Preparation

08 — Reinforcement Treatment

09 — Formwork / Reinforcement Installation

10 — Mixing Procedure

11 — Placement Procedure

12 — Curing

13 — Quality Control & Inspection

14 — Safety Requirements

15 — Responsibilities

16 — Records & Acceptance

This structure creates a much more disciplined repair process.

The Difference Between a Method Statement and a Product TDS

This distinction is important.

Technical Data Sheet

Answers:

"What is this product and how should this product be used?"

Method Statement

Answers:

"How will this particular project repair be executed and controlled?"

They are complementary—not interchangeable.

GUGAFIX® Micro Concrete

When GUGAFIX® Micro Concrete is specified for an appropriate repair application, the project method statement should incorporate the current product documentation and project requirements.

The formulation uses carefully selected cementitious materials, graded aggregates, admixtures and German-origin specialty polymers.

But the material is only one component of the repair system.

Design + Methodology + Material + Workmanship + QC

must work together.

The Guardian's Site Checklist

Before approving a structural repair method statement, ask:

Is the repair clearly defined?

Has the cause of deterioration been considered?

Is the structural methodology approved where required?

Are the materials clearly identified?

Is the product TDS referenced?

Is surface preparation defined?

Is the mixing procedure defined?

Is placement defined?

Is curing defined?

Are inspection points defined?

Are responsibilities clear?

Are safety requirements included?

If several answers are "No", the document isn't ready for controlled execution.

Frequently Asked Questions

Is a method statement required for every concrete repair?

Requirements vary by project and organization. For significant structural repairs, a documented method statement is an important tool for controlled execution.

Who prepares the method statement?

Typically the contractor or executing organization prepares it, subject to the project's approval process and technical requirements.

Does a method statement replace structural drawings?

No. It should work alongside the approved structural design, drawings, specifications and product documentation.

Can a contractor modify the method statement at site?

Any significant change should follow the project's change-control and approval procedure rather than being made informally.

Should the product TDS be attached to the method statement?

Where required by the project, it is good practice to reference or include the applicable current product documentation.

The Guardian's Advice

"A method statement turns a repair from an activity into a controlled process."

— The Guardian, The Chief Technical Advisor of GUGAFIX® Construction Chemicals

"I don't sell construction chemicals. I help people build stronger, safer, and longer-lasting structures."

The Guardian Structural Repair Series

Foundation Series

GSR-001 — Why Engineers Choose Micro Concrete for Structural Repairs

GSR-002 — Micro Concrete vs Conventional Concrete

GSR-003 — 10 Common Mistakes During Micro Concrete Repairs

GSR-004 — Why Surface Preparation Is Critical Before Micro Concrete Repairs

GSR-005 — How to Repair RCC Columns Using Micro Concrete

GSR-006 — How to Repair Honeycombs in Concrete Structures

GSR-007 — Why Non-Shrink Micro Concrete Matters

GSR-008 — Structural Repair Quality Control Checklist

GSR-009 — Common Structural Repair Failures

GSR-010 — The Complete Guide to Micro Concrete

Advanced Series

GSR-011 — Micro Concrete vs Structural Repair Mortar

GSR-012 — Selecting Structural Repair Material by Repair Depth

GSR-013 — What Is a Structural Repair Method Statement?

Next

GSR-014 — RCC Beam Repair: Key Engineering Considerations Before Rehabilitation

This will move into a different structural element and a different engineering problem, rather than recycling the Micro Concrete fundamentals.



"From meticulous planning to precise execution: ensuring structural repair is both strategic and effective with GUGAFIX."
"From meticulous planning to precise execution: ensuring structural repair is both strategic and effective with GUGAFIX."

 
 
 

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating

Copyright © 2024 by Gugafix Construction Chemicals. All Rights reserved. Proudly created in India.

bottom of page