Knowledge Hub

Conceptual engineering

Conceptual engineering is the structured technical work that turns an idea into a defined project. It frames the principal technology, scale, location, and integration decisions, and produces the engineering basis that later phases build on. It is the highest-leverage stage of the project lifecycle.

What conceptual engineering actually is

Conceptual engineering is the structured technical work that turns a project idea into a defined project. It is the bridge between the moment when a project exists only as a concept (a slide, a paragraph, a business case) and the moment when it has enough definition to support feasibility-level engineering, techno-economic assessment, permitting, and external financing conversations.

The phrase is used loosely in industry, and different organisations apply different scopes to what they call conceptual engineering. In its narrow definition, conceptual engineering covers the work between technology selection and the start of feasibility engineering, sometimes called the FEL-1 to FEL-2 transition. In its broader definition, it includes the technology selection itself and may overlap with the early feasibility work. This page takes the broader view because the underlying activities are tightly coupled and because the project value depends on them being done well together.

A conceptual engineering study, regardless of exact scope boundaries, has a recognisable shape. It establishes the project basis (what the project produces, at what scale, with what feedstock, on what site). It identifies and screens the technology options for each principal conversion or unit operation. It selects a preferred configuration and justifies the selection against the alternatives. It develops the configuration to a level of detail that supports preliminary equipment sizing, plot planning, utility requirements, mass and energy balance, and a Class 5 or Class 4 cost estimate. It identifies the principal risks and the principal external dependencies. It recommends the work that needs to happen in the next phase, with sufficient definition that the next phase can be scoped, costed, and resourced.

What conceptual engineering is not, and what it is sometimes mistaken for, is detailed engineering. The deliverables of a conceptual engineering study are preliminary, by design. The process flow diagrams are at block-flow or simplified-PFD level, not full P&IDs. The equipment list is sized to a level appropriate for cost estimation, not for procurement. The plot plan is an arrangement study, not a construction layout. Pushing the detail further at this stage produces work that will be redone, because the configuration choices that detailed work would lock in are still subject to change. Premature detail is one of the most common ways that conceptual engineering budgets get spent on work that creates no project value.

Equally, conceptual engineering is not optional, deferrable, or substitutable by an analytical model alone. A project that proceeds from concept to feasibility without disciplined conceptual engineering is a project carrying unresolved configuration choices into a phase that cannot easily resolve them. Conceptual engineering is where these choices get made, and the cost of making them later is substantially higher than the cost of making them at the right stage.

Why conceptual engineering matters: the leverage point

There is a quantitative argument for why conceptual engineering deserves more attention than it routinely receives. The cost of changing a project decision rises sharply as the project moves through its lifecycle. A configuration choice modified at the conceptual stage costs the engineering hours required to re-evaluate the alternatives, typically a few weeks of senior engineering time. The same configuration choice modified after FEED is complete costs the FEED rework plus any procurement commitments already made, often several percent of total project cost. The same configuration choice modified after construction has started costs the construction rework, the schedule delay, and the lost production over the delay window, frequently tens of percent of total project cost or more. The same configuration choice modified during operation usually cannot be made at all without a fundamental project redesign.

This asymmetry is well-known, and it has a familiar shape across industries. The energy and chemicals industries refer to it loosely as the "front-end loading" argument: the more decisions that are made and validated early, when changes are cheap, the fewer expensive changes the project will need to absorb later. The argument is robust to empirical scrutiny across project categories, and the body of evidence supporting it is one of the more durable findings in the industrial project management literature, with successive Independent Project Analysis benchmarks and the academic project-delivery literature both pointing in the same direction.

The implication for conceptual engineering specifically is that the leverage of this stage is high relative to its cost. A well-executed conceptual engineering study, costing in the order of a few hundred thousand dollars to a few million depending on project complexity, can identify and resolve issues that, if carried into FEED or execution, would cost orders of magnitude more to fix. The return on conceptual engineering effort, measured in avoided downstream rework, is typically among the highest in the project lifecycle, and is one of the principal reasons that sophisticated project owners invest substantially in this phase rather than rushing through it.

The argument cuts both ways. Conceptual engineering that is rushed, under-resourced, or focused on the wrong questions consumes the same calendar time as conceptual engineering done well, but produces decisions that are less robust. The downstream cost of these less-robust decisions is the project's exposure. The argument is not that conceptual engineering is automatically valuable. The argument is that conceptual engineering is one of the highest-leverage activities in the project lifecycle, and that the leverage is realised only when the work is done well.

Inside a conceptual engineering study

A conceptual engineering study has a recognisable scope, though the specific deliverables vary with project type, sector, and the requirements of the next-stage work. The components below are typical for industrial chemicals, energy, and process plant projects.

Project basis definition. A documented statement of what the project is supposed to do. Production capacity, product specifications, feedstock specifications, site location and characteristics, operating philosophy, target start-up date, scope boundaries, and the external interfaces (utilities, offtake, feedstock supply). The project basis is the reference document against which all later engineering work is measured. A weak project basis is a weak foundation for everything that follows.

Technology selection. The systematic comparison of the available technology options for each principal conversion or unit operation. For an integrated energy or chemicals project, technology selection happens at multiple layers: the electrolyser technology, the carbon capture technology, the synthesis technology, the upgrading technology, the auxiliary systems. Each layer has options with different cost, performance, maturity, and integration characteristics. The selection involves both technical analysis (which option best fits the project basis) and commercial analysis (which option has the right vendor support, licence terms, and execution track record). The selection should be documented with the reasoning, the alternatives considered, and the conditions under which the selection might be revisited.

Process configuration. The integrated arrangement of the selected technologies into a process train. At conceptual level, this is typically a block flow diagram with major streams labelled, supplemented by simplified PFDs for the principal units. The configuration captures the integration choices: what is co-located, what is at the same temperature and pressure level, what is recycled, where the buffer storage sits, how the auxiliary systems are arranged. Configuration choices interact with technology selection choices, and an integrated optimisation across the two is one of the substantive analytical activities of conceptual engineering.

Mass and energy balance. The quantification of the streams flowing through the process. At conceptual level, the balance is developed through process simulation tools (Aspen Plus, Aspen HYSYS, PRO/II, or simpler spreadsheet-based models for less complex processes) using rate data from the selected technologies. The balance is the principal input to the equipment sizing, the utility load determination, and the operating cost estimation. Errors in the mass and energy balance at conceptual stage propagate through every subsequent quantitative deliverable.

Preliminary equipment list and sizing. A list of the principal equipment items, sized to a level appropriate for cost estimation. The sizing uses standard rules of thumb, vendor reference data, or simplified design calculations as appropriate for the equipment type and the project complexity. Equipment that drives capital cost (large columns, reactors, compressors, heat exchanger trains, electrolyser stacks) receives more attention; ancillary equipment receives less.

Utility requirements. The aggregated demand for electricity, steam, cooling water, instrument air, nitrogen, hydrogen (where not produced internally), and other utilities. The utility requirements are the basis for the off-site or shared-utility scope that often dominates the OSBL capex.

Plot plan and site arrangement. A preliminary arrangement of the plant on the proposed site, sized for the equipment footprints and the operational access requirements. The plot plan is a screening tool, not a construction layout, and its principal value at conceptual stage is to confirm that the project fits the site and that the site has space for future expansion and for the required external interfaces.

Schedule and execution strategy. A preliminary project schedule from FID through start-up, with the principal milestones identified. The execution strategy addresses whether the project will be executed through a single EPC contract, an EPCM arrangement, owner-led with multiple contractors, or some hybrid; whether long-lead equipment will be ordered ahead of FID; and what the principal interfaces are between contractor and owner work.

Cost estimate. A Class 4 or Class 5 capital cost estimate prepared on the basis of the equipment list, the utility requirements, the plot plan, and the execution strategy. The cost estimate has an expected accuracy range of typically -50 to +100 percent at Class 5 or -30 to +50 percent at Class 4, and should be presented as a range rather than a point. The estimate is the principal input to the techno-economic assessment that runs alongside or after the conceptual engineering work.

Risk register. A documented set of the principal risks identified during the conceptual engineering work, with the proposed mitigation actions and the risks that require attention in the next phase. The risk register is the formal record of what the team has identified as uncertain and is the basis for the risk treatment in the next stage.

Recommendations for the next phase. A statement of what the conceptual engineering work has produced and what the next phase needs to do. The recommendations include the technology and configuration choices that have been made, the choices that remain open, the open questions that the next phase needs to answer, and the suggested scope and resourcing for the next phase.

These deliverables are interlocking. The mass and energy balance feeds the equipment list which feeds the cost estimate which feeds the techno-economic assessment which may, in iterations, prompt revisions to the technology selection or the configuration. The conceptual engineering team is responsible for managing this iteration in a disciplined way, with version control on the principal deliverables and with the rationale for each significant change recorded.

The principal decisions

If conceptual engineering's value is in framing decisions for downstream phases, then the question of which decisions it frames is the question of what conceptual engineering is for. The principal decisions, in approximate order of leverage, are the following.

Technology selection. The choice of conversion route, principal technology vendors, and configuration philosophy. For an integrated project with multiple unit operations, this is a multi-dimensional decision involving the electrolyser technology, the synthesis technology, the upgrading technology, the carbon capture or hydrogen storage technology, and the auxiliary systems. Technology selection at conceptual stage is the highest-leverage single decision in the project lifecycle, because it sets the configuration constraints for everything that follows.

Scale and capacity. The target production capacity and the corresponding scale of the principal unit operations. Scale selection involves trade-offs between economies of scale, market demand, capital intensity, technology maturity at scale, and the realistic supply of feedstock. A project that selects a scale at the upper end of demonstrated technology runs FOAK risk; a project that selects too small a scale forfeits the economies of scale that may be essential to clearing the market. Scale is rarely decided in isolation: it is decided as part of a configuration with the technology and the feedstock supply.

Site selection. The location of the plant. Site selection involves feedstock and utility access, offtake market access, regulatory environment, workforce availability, infrastructure quality, and political stability. For some projects, the site is fixed by the host company's existing footprint, in which case site-related design constraints rather than site selection are the relevant question. For others, particularly large new projects in emerging energy categories, site selection is one of the most consequential decisions and is often made on partial information that conceptual engineering should help to systematise.

Integration strategy. Whether the project is standalone or integrated with adjacent operations, and what the integration interfaces are. Integration can be physical (shared utilities, co-located logistics), commercial (offtake contracts with adjacent operators), or organisational (joint operations agreements). Each form of integration creates value through shared costs or risk pooling but also creates dependencies that complicate project execution.

Phasing strategy. Whether the project is built at full scale in one phase or modularly with planned expansions. Phasing reduces initial capex and de-risks the early operations but commits the project to construction and operation overlaps that have their own risks. Phasing decisions are often made for financing reasons (smaller initial capex is easier to fund) but have substantial technical implications that the engineering team needs to evaluate.

Execution strategy. The contracting and project delivery approach: EPC, EPCM, or owner-led with multiple contractors. The execution strategy is sometimes treated as a project management decision separate from engineering, but it has substantial engineering implications: the contract structure shapes the engineering deliverable handover, the procurement strategy, the construction sequencing, and the commissioning approach. Conceptual engineering work that has been done without consideration of the execution strategy is harder to translate into a contractable scope of work.

Procurement strategy for long-lead items. Some equipment in modern energy projects (large electrolysers, specialist reactors, large compressors, certain catalysts) has lead times measured in years. The decision of whether to commit to long-lead items ahead of FID, accepting the cost risk if the project does not proceed, or to wait until FID and accept the schedule risk, is one that conceptual engineering should explicitly address.

These decisions are interrelated. Technology selection conditions scale; scale conditions site; site conditions execution; execution conditions procurement. A conceptual engineering study that addresses each decision in isolation will produce a set of locally optimal choices that do not necessarily integrate. The substantive analytical work is the joint optimisation across decisions, and it requires a team with sufficient breadth to hold the trade-offs in view simultaneously.

Where conceptual engineering goes wrong

The failure modes in conceptual engineering are recurrent and recognisable across the industry. They are not exotic, and the project teams that fall into them are not careless. They reflect structural features of how conceptual engineering is commissioned, resourced, and reviewed, and they recur because the structural features have not changed. There are six failure modes worth naming.

Premature detail. The team spends conceptual engineering effort on engineering detail (full PFDs, sized line lists, detailed instrument schedules) that is appropriate for FEED but inappropriate for the level of decision maturity at the conceptual stage. The detail is then either redone when the configuration changes (waste) or used to defend the configuration against change (anchoring). Premature detail is most common when the conceptual engineering team is staffed with engineers whose default working depth is detailed engineering and who have not internalised the discipline of working at conceptual depth.

Premature commitment. The team commits to a technology, vendor, or configuration choice before the alternatives have been seriously evaluated, often because of relationships, prior project experience, or pressure from a technology provider. Premature commitment turns conceptual engineering from a decision-framing exercise into a decision-justifying exercise. The output looks like a balanced assessment but is in fact a documented case for a choice that was made before the work started. This is one of the most damaging failure modes because it is invisible to readers who were not in the room when the implicit commitment was made.

Underspecified project basis. The team starts conceptual engineering work without a clear, agreed, documented statement of what the project is supposed to do. The work proceeds on shifting assumptions, and the team finds itself reworking the analysis as the basis is clarified incrementally. The output may be technically competent but is not directed at the right question. Underspecified project basis usually reflects upstream weakness in the business case rather than weakness in the engineering team, but it is the engineering team that lives with the consequences.

Integration neglect. The team focuses on the principal unit operations and pays inadequate attention to the integration: utility interfaces, shared infrastructure, control philosophy, transient operation, start-up and shut-down. Integration is harder to scope than individual unit operations and often runs across multiple engineering disciplines, which makes it easy to defer. Deferred integration tends to surface as expensive problems in FEED or construction, often as scope additions that exceed contingency. For integrated emerging-energy projects, where the integration interfaces are themselves novel, this is the most common single source of downstream cost overrun.

Optimism about emerging technology. The team selects an emerging technology on the basis of vendor claims, pilot-scale data, or assumed learning trajectories, without adequately discounting for the FOAK risk. The conceptual engineering work then proceeds as if the technology were mature, and the cost and performance assumptions reflect a NOAK plant. When the actual FOAK performance differs (either in cost, in achievable yield, or in operational stability), the project economics shift, sometimes fatally. This failure mode is particularly common in the energy transition, where many projects are by their nature first-of-a-kind in some respect.

Insufficient handover to the next phase. The team produces conceptual engineering deliverables that are technically competent but that the FEED team cannot easily pick up. Recommendations are vague, open questions are unsurfaced, configuration rationale is undocumented. The FEED team starts by redoing parts of the conceptual engineering work, which adds time and cost and erodes the value of the conceptual engineering investment. The handover is one of the most under-attended parts of conceptual engineering practice and is one of the highest-leverage areas for improvement.

These six failure modes are familiar to anyone who has worked in industrial project development. They are not avoidable in the absolute sense; some degree of each will appear in almost any project. The discipline is in recognising them early, in actively countering the structural pressures that produce them, and in designing the conceptual engineering process to make them less likely. A conceptual engineering deliverable that has been prepared with active attention to these failure modes, with explicit findings on each, is substantially more valuable than one that has not, regardless of the technical sophistication of the underlying engineering.

The conceptual engineering failure modes

Failure mode	Typical trigger	Signs in the deliverables	Downstream consequence	Principal mitigation
Premature detail	Engineering team staffed at detailed-engineering depth.	P&IDs and full datasheets at conceptual stage.	Conceptual rework when configuration changes.	Discipline working depth to match decision maturity; resist detail until decisions are stable.
Premature commitment	Vendor or relationship pressure during selection.	Alternatives section is short and asymmetric.	Locked-in configuration is suboptimal under later information.	Document alternatives explicitly with reasoning; resist commitment until evaluated.
Underspecified project basis	Weak upstream business case.	Project basis is missing or thin.	FEED start delayed while basis is clarified.	Insist on documented project basis before engineering work begins.
Integration neglect	Cross-discipline coordination underweighted.	Utility, control, and start-up sections are underweight.	Scope additions in FEED or construction exceed contingency.	Allocate explicit budget to integration; staff cross-discipline review.
Optimism about emerging technology	Vendor projections taken at face value.	FOAK premium absent from cost estimates.	Cost and performance shortfall at FOAK operation.	Apply explicit FOAK premium and uncertainty range to emerging technology costs.
Insufficient handover	Handover treated as documentation rather than transfer.	Open questions and rationale not documented.	FEED team redoes parts of conceptual work.	Design handover as transfer not documentation; involve the next-phase team early.

The failure modes named here are recurrent in industrial project development and are not exotic risks. Some degree of each appears in almost any project. The discipline is in recognising them early and in designing the conceptual engineering process to make them less likely.

Options thinking

A specific approach to conceptual engineering that addresses several of the failure modes simultaneously is what is sometimes called options engineering or options thinking: the deliberate preservation of alternative configurations through the conceptual stage, rather than premature commitment to a single configuration.

Options thinking starts from the observation that early-stage decisions are made under uncertainty, and that the uncertainty resolves over time as the project develops. Information that is unavailable at conceptual stage (firm vendor pricing, detailed soil conditions at the site, the specific terms of offtake contracts, the actual policy framework that will apply) becomes available later. A configuration choice locked in at conceptual stage on partial information cannot adapt easily to the better information that arrives later. A configuration left open, with the work that allows it to be resolved later kept available, preserves the project's ability to incorporate new information.

The challenge with options thinking is that it costs more in the short run. Carrying two viable configurations through conceptual engineering requires roughly 50 percent more engineering effort than committing to one. The benefit is that the additional information arriving during FEED can be applied to a real comparison, rather than to a justification of the chosen path. For projects in technology-fluid environments, where multiple viable routes exist and the relative attractiveness of the routes shifts with market and policy conditions, options thinking is often the right approach.

The practical implementation involves identifying which decisions need to be made at conceptual stage (the decisions whose downstream lock-in is severe) and which decisions can be deferred (the decisions whose downstream impact is contained). For each deferrable decision, the conceptual engineering work develops the alternatives to a level of detail that allows comparison, but stops short of committing. The recommendations for the next phase explicitly identify which choices remain open and what information would be needed to close them.

Options thinking is not a substitute for decision-making. Projects that defer all decisions in the name of preserving options never make progress. The discipline is in distinguishing between decisions that benefit from deferral and decisions that benefit from early resolution. Technology selection at the foundational layer (which family of conversion to use) typically benefits from early resolution because it conditions everything else. Configuration choices within a selected technology family often benefit from deferral. Scale typically benefits from early resolution because it interacts with site and offtake. Phasing strategy often benefits from deferral because it interacts with financing structure that resolves later.

Applied well, options thinking does not slow projects. It changes the shape of the work, with more parallel evaluation in the early phases and faster resolution as information arrives. Applied poorly, it produces conceptual engineering deliverables that everyone can interpret to support their preferred conclusion, which is worse than premature commitment.

Interfaces with adjacent disciplines

Conceptual engineering does not operate in isolation. It is bracketed by upstream and downstream activities, and runs in parallel with adjacent analytical activities, and the quality of the conceptual engineering work depends substantially on the quality of these interfaces.

Upstream, conceptual engineering depends on the business case and the project basis. A conceptual engineering team cannot define a project that the business has not defined. The principal upstream interface is therefore with the project sponsor and the business development team, who own the project basis and who are responsible for keeping the basis current as the project develops. Weak coupling at this interface, where the engineering team and the business team work on different versions of the project, is one of the more common dysfunctions in early-stage project development.

Parallel to conceptual engineering, techno-economic assessment work is typically being done in parallel iteration. The TEA depends on the engineering inputs (equipment list, utility requirements, mass and energy balance, capex and opex estimates), and the engineering decisions depend on the TEA outputs (project metrics under different configurations). The two activities are tightly coupled and the team structure needs to support tight iteration. A conceptual engineering deliverable handed to a TEA team after the engineering is fixed produces a worse joint outcome than continuous iteration during the engineering phase.

Also parallel, technology selection and vendor engagement work runs alongside the engineering. Vendor information feeds the engineering; engineering questions feed back to vendors; the vendor evaluation matrix and the technical evaluation matrix should converge to a recommendation that has both technical and commercial defensibility. Where vendor engagement is run separately from engineering, the two often diverge, with the technical and commercial recommendations not aligned.

Downstream, conceptual engineering hands over to FEED engineering. The FEED team builds on the conceptual deliverables, develops them to a level supporting FID, and produces the engineering basis for procurement and construction. The handover is the principal value-transfer point: what the FEED team receives is what they build on, and what is missing or unclear in the handover becomes their first-phase work. Conceptual engineering deliverables that are designed with the FEED team's needs in mind transfer cleanly. Deliverables that are designed for internal-team consumption transfer poorly and require substantial rework in the FEED start-up phase.

For projects in regulated industries or with significant environmental and social dimensions, conceptual engineering also interfaces with permitting work, environmental and social impact assessment, stakeholder engagement, and grant or policy application processes. Each of these has its own information needs, its own timeline, and its own gating effect on the project. A conceptual engineering process designed with all of these interfaces in mind will produce deliverables that serve multiple users with appropriate adjustments; one that is designed only for internal engineering use will require parallel rework to serve the external interfaces.

The integrative skill at the conceptual engineering stage is therefore less in the depth of any individual deliverable and more in the orchestration across interfaces. Good conceptual engineering managers spend much of their time on interface management, often more than on technical content. This is one of the under-appreciated features of effective conceptual engineering practice.

Conceptual engineering for emerging technologies

The energy transition involves the deployment of many technologies that are commercially novel at scale. Conceptual engineering for these projects has features that distinguish it from conceptual engineering for established industrial categories, and these features merit specific attention.

The reference base is thin. Most emerging energy technologies (large-scale electrolysis, integrated Power-to-X projects, advanced biofuels, direct air capture at scale, novel battery technologies, advanced nuclear) have few or no operating commercial-scale plants to benchmark against. The conceptual engineering team is therefore working with pilot-scale or demonstration-scale data, with vendor projections, and with analogies to related technology categories. Each of these has its own reliability and its own typical biases. Pilot-scale data is real but does not capture the scaling effects that matter at commercial size. Vendor projections reflect the vendor's commercial interests. Analogies are useful for orientation but break down at the details. The conceptual engineering team needs to be explicit about which data sources are being used for which decisions, and what the residual uncertainty is.

Integration is the dominant challenge. The individual technologies in most emerging energy projects are typically more mature than the integration of them is. Electrolysers are commercial; methanol synthesis is a century old; Fischer-Tropsch synthesis is industrialised. What is new is the integration of these at scale, on intermittent renewable supply, with specific carbon accounting requirements, in specific regulatory contexts. The conceptual engineering work for an integrated emerging-energy project therefore concentrates disproportionately on integration, and the principal cost and performance risk lives at the interfaces between technologies rather than within any individual technology.

The regulatory and policy environment is unsettled. Most emerging energy projects depend, for their commercial viability, on regulatory frameworks (RFNBO, CORSIA, RED III, mandate schemes, carbon credit schemes, grant programmes) that are themselves evolving. The conceptual engineering work needs to anticipate this evolution, to characterise the project's exposure to alternative regulatory outcomes, and to design configurations that are robust across reasonable variations. A configuration that works only under one specific regulatory outcome carries an unhedged regulatory risk that the conceptual engineering work should make explicit.

The cost and schedule data is unreliable. Cost and schedule estimates for emerging energy projects routinely overrun substantially, with the FOAK premium typically not adequately reflected in the headline numbers. The conceptual engineering work should therefore present cost and schedule with explicit FOAK treatment, with sensitivity to the principal cost drivers, and with honest representation of the uncertainty bands. A conceptual engineering deliverable for an emerging-energy project that presents Class 4 accuracy on a Class 5 information base is misrepresenting certainty in a way that will damage the project later.

The vendor landscape is in flux. Many emerging energy technology vendors are themselves at an early commercial stage. Their cost projections, their reference data, and their commercial terms are evolving as they build their own scale. The conceptual engineering team should evaluate vendor information with awareness of these dynamics and should not anchor on any single vendor's projections without cross-checking against alternatives.

The implication, across all of these, is that conceptual engineering for emerging energy projects requires more explicit treatment of uncertainty, more disciplined attention to integration, and more active engagement with the regulatory and commercial context than conceptual engineering for established industrial categories typically does. The discipline is not different in kind, but the failure modes are sharper and the consequences of getting it wrong are more severe.

Outlook

The discipline of conceptual engineering is being reshaped by three forces over the next decade.

First, the dominance of integrated energy projects. The energy transition increasingly involves integrated projects across multiple technology categories: renewable generation plus electrolysis plus synthesis plus upgrading plus storage, often co-located with carbon capture or biogenic feedstock supply. Each layer of integration adds complexity, and the conceptual engineering work has to manage an integrated system rather than a single plant. The skills required for this work, particularly cross-disciplinary integration and system-level optimisation, are in increasing demand and are not yet broadly available across the industry.

Second, the integration of carbon and policy accounting into the engineering work. Traditional conceptual engineering treated carbon and policy as commercial considerations to be handled separately. Modern energy projects integrate them into the engineering decisions: the choice of carbon source affects the synthesis configuration, the certification requirements affect the measurement and traceability architecture, the policy environment affects the offtake structure that affects the scale. The conceptual engineering practice required to handle this integrated treatment is more demanding than the traditional practice, and the skill set is still developing.

Third, the maturation of digital tools. Process simulation, integrated mass and energy balance models, digital twin technology, and machine-learning-assisted equipment sizing are increasingly being applied to conceptual engineering. The tools are useful but do not substitute for engineering judgement, and the most common failure mode in their use is over-reliance on the tool output without disciplined questioning of the input assumptions. The conceptual engineering practice of the next decade will use these tools more heavily, and the discipline required to use them well will be one of the differentiators between high-quality and low-quality conceptual engineering work.

The honest assessment is that conceptual engineering practice is improving, but the structural pressures that produce shortcomings have not been resolved. The under-investment in this phase relative to its leverage, the staffing patterns that bring detailed-engineering habits to conceptual work, the time pressure that produces premature commitment, all remain. A careful project sponsor in 2026 should hold the same critical disposition towards conceptual engineering quality as a careful sponsor in 2010 or 1995. The methodological frameworks have matured. The structural challenges have not.

Frequently asked questions

What is the difference between conceptual engineering and FEED?

Conceptual engineering produces the project definition at a level supporting feasibility decisions and Class 4 or 5 cost estimates. FEED (front-end engineering design) produces the project definition at a level supporting final investment decision and Class 2 or 3 cost estimates. The principal differences are in the engineering depth (block flow versus complete P&IDs), in the equipment specification level (preliminary sizing versus full datasheets), and in the cost estimate accuracy. Conceptual engineering is the bridge between concept and FEED.

What does a conceptual engineering study typically cost?

The cost ranges with project complexity, with the scope of work, and with the level of detail required. A conceptual engineering study for an integrated process plant in the energy or chemicals sector typically costs in the range of several hundred thousand dollars to a few million dollars. The cost is a small fraction of total project capex (typically less than 1 percent) and is among the highest-leverage investments in the project lifecycle.

How long does conceptual engineering take?

Typical conceptual engineering studies take three to nine months, with simple projects at the shorter end and complex integrated projects at the longer end. The duration is driven more by the time required for technology evaluation, vendor engagement, and project basis stabilisation than by the engineering effort itself. Compressing the timeline below the natural duration produces shortcuts in technology evaluation and integration analysis that downstream phases then have to recover from.

What is FEL, and how does it relate to conceptual engineering?

FEL (front-end loading) is a framework that divides the early project phases into FEL-1 (concept identification), FEL-2 (conceptual engineering and selection), and FEL-3 (FEED). The framework is widely used in the petrochemicals and oil and gas industries and is increasingly applied in the energy transition. Conceptual engineering corresponds approximately to FEL-2, with some overlap into FEL-1 for technology selection. The specific terminology varies by company and by industry.

Should conceptual engineering be done before or after techno-economic assessment?

The two should be done in parallel iteration rather than sequentially. TEA depends on engineering inputs (equipment, utilities, mass and energy balance, cost estimate). Engineering decisions depend on TEA outputs (project metrics under different configurations). Sequential separation produces worse joint outcomes than iterative co-development. The team structure and contracting structure should support tight iteration.

What is the most common failure mode in conceptual engineering?

The six failure modes named on this page (premature detail, premature commitment, underspecified project basis, integration neglect, optimism about emerging technology, insufficient handover) are all recurrent. In integrated emerging-energy projects, integration neglect and optimism about emerging technology are the most consequential, because the project value depends on the integration working and on the emerging technology performing.

Can conceptual engineering be done internally or does it need an external party?

Both models work. Internal teams have the advantage of context and stakeholder relationships; external teams have the advantage of methodological discipline and freedom from internal commitments. Many sophisticated project sponsors use both: internal teams for the integration with the business and for the upstream interfaces, supplemented by external technical specialists for specific deliverables (technology evaluation, process simulation, cost estimation). The structure should reflect the project's specific risks and the team's specific gaps.

How does conceptual engineering interact with permitting?

Permitting typically requires engineering information at a maturity that conceptual engineering reaches: process description, plot plan, principal emissions sources, water and waste flows, principal hazards. The conceptual engineering work can be designed to produce deliverables that serve both internal project use and external permitting submission, which is more efficient than developing them separately. The timeline for permitting often determines when conceptual engineering needs to produce specific deliverables, regardless of the internal project schedule.

What is options engineering?

A specific approach to conceptual engineering that deliberately preserves alternative configurations through the conceptual stage rather than committing to a single configuration. Options engineering recognises that early-stage decisions are made under uncertainty that resolves over time, and that preserving alternatives allows the project to incorporate better information as it arrives. The approach costs more in the short run (typically 50 percent more engineering effort to carry two viable configurations through to comparable detail) and pays back when the additional information allows a real comparison rather than a justification of the locked-in path.

What is the role of conceptual engineering for emerging energy technologies?

Conceptual engineering for emerging energy technologies is structurally similar to conceptual engineering for established categories but requires more explicit treatment of uncertainty, more disciplined attention to integration, more active engagement with the regulatory and commercial context, and more honest representation of the FOAK risk in cost and schedule estimates. The discipline is not different in kind, but the failure modes are sharper and the consequences are more severe.

How is the quality of a conceptual engineering deliverable assessed?

A reviewer's first questions should concern the project basis (is it documented, agreed, and current?), the alternatives analysis (have alternatives been seriously evaluated rather than justified after the fact?), the integration treatment (are utilities, control, and start-up addressed alongside the principal units?), the FOAK treatment (is the emerging-technology premium explicit and reasonable?), the cost estimate (is it presented as a range with the AACE class declared?), and the handover (are open questions and rationale documented for the next phase?). A deliverable that scores well on these questions is substantially more useful than one that has more pages of detail but does not.

What does Ionect typically work on in conceptual engineering?

Conceptual engineering studies across the Power-to-X, Waste-to-X, e-Fuels, hydrogen, and adjacent project categories. We work with project developers, technology providers, financiers, and policy bodies. Our scope typically includes technology selection, process configuration, mass and energy balance, equipment list and sizing, utility requirements, plot plan, Class 4 or 5 cost estimation, risk register, and recommendations for FEED. The interfaces with TEA and with technology selection are part of the integrated work rather than separate activities.