ETA and DoP Explained for Anchoring Systems

Understanding ETA and DoP is part of choosing the right anchoring system

In anchoring applications, product selection is not only about dimensions, load values or installation method. Documentation and approval status also play a critical role in making sure the chosen fixing system is suitable for the application.

Two of the most important terms in this area are ETA and DoP. They are often referenced in technical discussions, project specifications and compliance checks, but they are not the same thing.

For engineers, buyers and QA teams, understanding the difference helps support correct specification, smoother audits and greater confidence when selecting anchoring systems for construction projects.

The right documents support the right project decisions

In steel and construction projects, incorrect assumptions around approvals or missing documentation can create unnecessary delay, confusion and compliance risk. A product may look suitable on paper, but that does not automatically mean it is supported by the right technical route for the application.

ETA and DoP are important because they help connect product selection with documented performance and declared use. That matters not only for engineers and designers, but also for procurement teams, quality functions and anyone responsible for project records or handover files.

Understanding what each document does helps reduce uncertainty and supports more confident decisions from specification through to supply and installation.

What is an ETA?

ETA stands for European Technical Assessment and provides a documented basis for the performance of a construction product in a defined application area.

An ETA is a European Technical Assessment. In simple terms, it is a document that provides a technical assessment of a product’s performance for specific intended uses.

For anchoring systems, an ETA can include important information about application scope, substrate conditions, performance characteristics and the basis on which the product can be used in design and specification.

It is not simply a marketing statement or a basic product data sheet. It is a technical reference point used to support specification, performance understanding and compliance review.

What is a DoP?

DoP stands for Declaration of Performance and sets out the performance that the manufacturer declares for the product.

A DoP is a Declaration of Performance. This is the document in which the manufacturer declares the performance of the product in relation to the relevant essential characteristics.

In anchoring systems, the DoP is important because it gives visibility of the declared performance route linked to the product. It is one of the key documents that buyers, engineers and QA teams may need when checking compliance, documentation packs or project files.

While the ETA provides the technical assessment framework, the DoP communicates the declared performance of the specific product against that basis.

ETA vs DoP

These documents are closely linked, but they do not serve the same purpose.

ETA = technical assessment for intended use

DoP = manufacturer’s declared performance for the product

The simplest way to understand the difference is this: the ETA provides the technical basis and scope for the product’s assessed use, while the DoP sets out the performance the manufacturer declares for that product.

In practice, they work together. The ETA helps define where and how the product can be technically considered, while the DoP helps communicate the declared performance route that sits behind the product placed on the market.

A common mistake is to assume they are interchangeable documents. They are not. They support different parts of the compliance and specification process.


ETA and DoP at a glance

Topic	ETA	DoP
Full meaning	European Technical Assessment	Declaration of Performance
Main role	Provides technical assessment basis	Declares product performance
Relevance in anchor selection	Helps define assessed use and scope	Supports declared performance visibility
Typical project use	Specification and technical review	Compliance files and product declaration review
Risk if misunderstood	Product may be assumed suitable outside its assessed scope	Missing or unclear declared performance can affect compliance review

When ETA should be checked

ETA should be part of the review where the application depends on approved use, technical scope or product suitability for a defined anchor scenario.

ETA review is especially useful when the project team needs to understand whether the anchor system is assessed for the intended use.

ETA should typically be reviewed when the application needs more than a basic product match. This is particularly relevant where substrate conditions, load case, cracked concrete use, edge conditions or design assumptions matter to specification.

ETA is especially relevant where:

• the design depends on approved anchor use

• substrate and load conditions need technical confirmation

• the product must align with project specification and application scope

• technical and compliance teams need a stronger basis for selection

When DoP should be checked

DoP is especially important when the project requires declared performance information as part of procurement, documentation review or handover preparation.

DoP review is often relevant where the project team needs visibility of the manufacturer’s declared performance for the product being supplied.

DoP should typically be checked when the project requires documentation to support compliance files, product declarations or handover packs. It can also be important for procurement and QA teams who need clarity on the declared performance route of the supplied anchor product.

DoP is especially relevant where:

• the project file requires declared performance documents

• QA teams need product declaration evidence

• procurement teams are checking product documentation before supply

• handover readiness and traceability matter to the project

What buyers, engineers and QA teams should check

Before ordering anchoring systems, it is worth checking the application scope, declared performance route, document availability, installation relevance and project file requirements.

Correct anchor selection depends on more than the product alone. It also depends on whether the right documents support the intended use and declared performance.

1	Is the product supported for the intended application? The project team should check whether the anchor system aligns with the technical scope required for the application.
2	Are ETA and DoP available? Availability of the right documentation is important for technical review, procurement confidence and project records.
3	Do the documents match the product being supplied? Project teams should avoid relying on generic documents that do not clearly correspond to the selected anchor system.
4	Does installation align with the intended use? Anchor performance depends on the application and installation route being consistent with the documented basis behind the product.
5	What documentation needs to go into the project file? In many projects, compliance packs, handover files and QA documentation require more than a product code alone.

Common mistakes to avoid

Documentation issues often begin when teams assume approval, declaration and product suitability are all covered by the same file.

Assuming ETA and DoP are the same

They are linked, but they do different jobs. One supports the technical assessment basis and the other states declared performance.

Relying on generic product information alone

A basic product sheet may not provide the technical and declaration detail needed for project-level review.

Not checking whether the documents match the application

A document may exist, but that does not automatically mean it covers the required use case or the exact product route being supplied.

Overlooking project file requirements

Missing documentation can create delay later, especially when procurement, QA or handover teams need evidence that was not gathered earlier in the process.

How Fabory supports documentation confidence

The right support goes beyond product availability. It also includes helping customers navigate approvals, documentation and specification confidence.

Fabory helps customers reduce uncertainty around anchoring documentation, application suitability and project readiness.

Fabory supports steel construction and anchoring customers with more than product supply alone. The wider approach is built around helping teams make more confident choices by combining product availability with stronger documentation awareness and technical support.

Fabory support can include:

• support for anchor product selection

• guidance around documentation availability

• support for engineers, procurement teams and QA functions

• availability and continuity of supply

• a more complete route to project documentation readiness

The aim is to help customers reduce uncertainty around both product choice and the supporting documentation needed for project execution.

Need support with anchor documentation and selection?

Talk to Fabory about anchoring systems, documentation support and the right route for compliant product selection.

Talk to Fabory

ETA and DoP explained for anchoring systems