Skip to content

EPC and turnkey engineering

What Is EPC: How an Engineering Contract Works

What is EPC in industrial projects? Learn how engineering, procurement and construction work under one contractor and when this contract model fits.

Direct answer

EPC stands for Engineering, Procurement and Construction. In an industrial EPC contract, one contractor designs the facility, buys the equipment and materials, and builds and commissions the plant. The owner deals with a single point of responsibility for the integrated scope. Authomathika has offered full EPC since 1999.

Institutional content: Authomathika

Published:

Industrial owners often split a new plant or a major expansion into separate contracts for design, equipment and site work. EPC is the alternative: one contractor takes the integrated scope. This guide explains what the acronym covers, how the three phases connect, who is accountable for what, and where the model fits.

What does EPC mean in industrial projects?

EPC is a contracting model in which a single contractor is responsible for Engineering, Procurement and Construction of a facility, usually through commissioning and handover. The owner defines what the plant must do, and the contractor defines and delivers how it gets built.

The contractor answers for the interfaces between design, supply and site work. That is the main difference from contracting each discipline separately, where the owner coordinates those interfaces. When the contract also includes startup and delivery of a plant ready to operate, it is commonly called turnkey. For that variant, read Turnkey Contract: What It Is and How It Works.

What are the three phases: engineering, procurement and construction?

The three phases are linked and often overlap. Engineering defines the solution, procurement buys it, and construction installs and commissions it.

PhaseWhat happensTypical deliverables
EngineeringDesign of process, civil, mechanical, electrical and automation disciplinesBasic and detailed design, data sheets, drawings, lists, specifications
ProcurementSpecification, quotation, purchase, expediting and inspection of equipment and materialsPurchase orders, inspection records, delivery schedules, vendor documents
ConstructionSite works, assembly, installation, testing and commissioningInstalled systems, test records, as-built documents, handover package

Engineering is itself usually staged. Basic engineering fixes the concept and the main parameters, as explained in Basic Engineering: What It Is and What It Should Include. Detailed engineering turns that into the documents needed to buy and build, covered in Detailed Engineering: What It Is and Typical Deliverables.

Who is responsible for what in the contract?

Under EPC, the contractor is responsible for delivering the defined scope, while the owner is responsible for defining requirements, providing data and approving key decisions. Clear boundaries between those two sides prevent most disputes.

TopicOwnerEPC contractor
Performance requirements and basis of designDefines and approvesInterprets, develops and delivers
Site data, permits and utilities availabilityProvides, as agreed in the contractUses and coordinates
Design, purchasing and constructionReviews and approves at agreed milestonesExecutes and answers for results
Changes after contract signingRequests or approvesAssesses impact on cost and schedule
Testing and acceptanceWitnesses and acceptsPlans, executes and documents

The exact split depends on the contract text. The detailed allocation is discussed in EPC Turnkey Contracts: Scope and Responsibility Allocation.

When does EPC make sense?

EPC makes sense when the owner wants one accountable party, the scope can be defined well enough to be contracted as a package, and the owner prefers not to manage many separate suppliers.

Typical situations include:

  1. New plants (greenfield) where design, supply and construction need to move together.
  2. Large expansions or modernizations (brownfield) with many disciplines involved.
  3. Projects with a tight schedule, where overlapping engineering and procurement helps.
  4. Owners with a lean internal engineering team.

It fits less well when the scope is still unclear, when the owner wants close control over every design decision, or when the work is a small isolated package. In those cases, separate contracts or a management model may be better. The comparison is in EPC vs EPCM: Contract Differences and Responsibilities.

What risks and interfaces must be controlled?

The main risks come from an undefined scope, unclear interfaces and late changes. EPC concentrates responsibility, but it does not remove the need for the owner to define requirements and follow progress.

Common points of attention:

  • Scope gaps: items that nobody priced because the documents did not mention them.
  • Basis of design: incomplete or changing requirements that reopen engineering.
  • Owner furnished items and data: late information that delays the contractor.
  • Interfaces with existing plant: tie ins, shutdown windows and operating constraints in brownfield work.
  • Electrical and automation integration: panels, instruments, control system and field wiring must match the process design.
  • Acceptance criteria: tests, documents and performance measures that must be agreed before construction.

Where do you start when contracting EPC?

Start by defining the scope and the information you can give the bidders, then ask for proposals on the same basis. A comparable proposal depends on a comparable set of inputs.

Gather before requesting a proposal:

  1. Project objective, capacity and performance requirements.
  2. Basic engineering or a basis of design, if available.
  3. Site information, existing plant documents and utilities.
  4. Applicable standards and owner specifications, always in their current edition.
  5. Desired schedule, shutdown windows and constraints on operation.
  6. Interfaces you will keep under your own responsibility.
  7. Acceptance and handover criteria.

Criteria for comparing proposals:

  • Clear scope with explicit inclusions and exclusions.
  • Demonstrated experience in similar projects.
  • Integration between electrical, automation and assembly disciplines.
  • Defined documentation, testing and handover.
  • Support after startup.

The contract scope checklist is in EPC Turnkey Contract Scope: What Must Be Defined.

Authomathika, an engineering integrator founded in 1999 in Sertãozinho, São Paulo, offers complete EPC covering projects, administration, construction and production. You can see the offer on the EPC Engineering page, and send scope information through the contact page. Services are evaluated by scope and budget.

Frequently asked questions

What does EPC stand for?
EPC stands for Engineering, Procurement and Construction. It describes a contract in which one contractor handles design, purchasing and building of a facility.
Is EPC the same as turnkey?
Not exactly. EPC describes the integrated scope of engineering, procurement and construction, while turnkey emphasizes delivering a plant ready to operate. In practice the two terms overlap, so the contract text must state what is included.
Does the owner have no role in an EPC project?
The owner still defines requirements, provides site data, approves key milestones and accepts the result. EPC moves execution risk and coordination to the contractor, not the owner's responsibility to define the project.
Can EPC be used in brownfield projects?
Yes, for expansions, revamps and modernizations. Brownfield work needs extra care with existing plant data, shutdown windows and tie ins to operating systems.
What is the difference between EPC and EPCM?
In EPC the contractor executes the scope and carries responsibility for the result. In EPCM the contractor manages engineering, procurement and construction on behalf of the owner, who contracts the work packages. The responsibility allocation differs between the two.

Send your scope and receive a technical assessment from the Authomathika team.

Discuss your project ↗
What Is EPC: How an Engineering Contract Works | Authomathika