Eratherm İzolasyon A.Ş.
Sequence · Hold points · HSE · Acceptance

Insulation Method Statement preparation and approval

A method statement is the document that says how the work will actually be done, in what order, by whom, with what checked at which point. Written properly it settles arguments before they happen on site. Written as a formality it gets approved, filed and ignored, and the first dispute has nothing to refer to.

Work sequence and interfacesHold and witness pointsHSE and permit requirementsAcceptance criteria
Insulation method statement preparation for site execution
1,000,000+ m²Completed insulation application
15,000+ MWPower plant capacity insulated
20+ yearsEngineering and site experience
3 continentsProject delivery
Scope

What it has to settle before work starts

A method statement that only describes the materials is a product list. These are the sections that make it a usable site document.

01

Sequence and interfaces

The order of work and its dependency on other trades: surface preparation, hydrotest, painting, electrical tracing and scaffolding each gate the insulation activity.

02

Hold and witness points

Where work stops for inspection and who has to attend. Agreed in the document so the schedule already carries the time the inspection needs.

03

Acceptance criteria

What finished work has to look like and measure, stated as a criterion rather than as a reference to a standard nobody has on site.

The interface section is the one that saves money

Most insulation delay is not insulation work. It is waiting for a hydrotest certificate, a paint cure or a scaffold handover. Naming those dependencies and their owners in the method statement is what turns them into schedule items.

Insulation method statement sequence and hold point definition
Method

How we build it

We start from the approved specification and drawings, walk the actual work front where access allows, and write the sequence that the site can execute rather than the sequence the schedule assumes. The document is written for the supervisor, in the language the crew uses.

  • Written against the issued specification and drawing revision, both cited
  • Sequence confirmed against the real work front, not just the schedule
  • Hold points agreed with the client and the inspection body before issue
  • HSE section covers the permits, access and hazards specific to the scope
  • Acceptance criteria stated as measurable conditions, not standard references
Deliverables

What you receive as a submittal package

Formatted for submission into the project document control system, with the revision structure approvals need.

Method statement

Scope, sequence, resources, hold points, HSE and acceptance, fully referenced.

Risk assessment

Hazards specific to the insulation scope, with controls and residual risk stated.

Resource and tool schedule

Crew composition, qualifications and the equipment each activity needs.

Interface register

Every dependency on another trade, with the owner and the gating condition.

Inspection reference

The ITP activities this method statement satisfies, cross-referenced.

Revision log

Change history, so an approved version is never confused with a draft.

Approved method statement in use at the insulation work front
Approval

A method statement is approved once and used every day

The value is not in approval. It is in whether the supervisor can open it on the work front and find the answer to the question being argued about. That is a writing problem, and it is why we keep the sequence section concrete and the standard references in an annex.

  • Written so the supervisor can use it, not only so the client can approve it
  • Standard references collected in an annex rather than inline
  • Sketches used wherever a sentence would need to be read twice
  • Revision control so the version on site matches the version approved
  • Toolbox talk content derived directly from the document

Industrial Insulation Catalogue

Engineering scope, calculation and documentation services, material families and application capability in a single document.

Open the 2026 catalogue

Working worldwide

ERATHERM works as an engineering partner for operators, EPC contractors and equipment manufacturers. Calculation, design, documentation and specification work is delivered remotely under the client's document control procedure; inspection, site supervision and application teams are mobilised to site.

  • Europe, the Middle East, Asia, Africa and the Americas
  • EPC-level deliverable documentation
  • Client document control procedure
  • Remote engineering and site mobilisation
Questions

Method statements questions we are asked

Can you write a method statement for work another contractor will perform?

Yes, and it is a common owner's engineering request. We write it against your specification and the contractor's declared resources, which has the useful side effect of exposing where their proposed method does not meet the specification.

How does a method statement differ from an ITP?

The method statement says how the work is done; the ITP says how it is verified. They share hold points and acceptance criteria, which is why they should be written together rather than by different people at different times.

Does it need to be rewritten for every project?

The structure carries over; the content does not. Sequence, interfaces, hazards and acceptance criteria are site-specific, and a generic document reused across projects is the main reason method statements stop being read.

What makes one get rejected?

Usually a missing interface, an acceptance criterion written as a bare standard reference, or a hold point the client's inspection body never agreed to attend. All three are avoidable by settling them before issue rather than in review.

Send the specification and the work front

We will write a method statement your supervisor can use and your client can approve, with the interfaces and hold points settled before issue.