Learn how to define the contracting architecture of an Engineering project through package strategy, contract model selection, interfaces, responsibilities and risk allocation.
Check it out!
An Engineering contracting strategy defines the contractual architecture of an undertaking: how scope will be divided into packages, which contract models will be used, how interfaces and responsibilities will be distributed, which risks belong to each party, and which decisions must be made before going to market. It uses the market analysis produced by Strategic Sourcing and precedes the procurement plan, but it is not the same as either: sourcing addresses the market and suppliers; the plan operationalizes dates, owners and Procurement milestones.
In complex projects, strategy is not limited to deciding whether to “buy” or “contract.” It connects Engineering maturity, the owner’s internal capability, market structure, interfaces between disciplines, schedule, long lead items, operating constraints, delivery model, selection criteria and contract governance. The expected result is a defensible contracting logic in which each package has a purpose, boundaries, owners, risks and gates for moving to the next phase.
A robust strategy reduces excessive fragmentation, gaps between contracts, overlapping responsibilities, inappropriate risk concentration and competitions launched before the object is sufficiently mature. It also helps determine when to use RFI, RFP or RFQ and when contracting requires prequalification, TBE, technical negotiation or additional controls.
What a contracting strategy needs to decide
A contracting strategy is not a purchasing list. It defines the undertaking’s architecture of responsibilities: how packages, market, interfaces, risks and selection criteria will be combined before any RFP or RFQ is issued.
Contracting strategy starts with the relationship between what the undertaking needs to deliver and how the market will be mobilized to produce that result. The World Bank treats this phase as part of the Project Procurement Strategy for Development (PPSD): before inviting offers, the buyer should analyze market, operating environment and project risks to select a Procurement approach suited to the objective and expected value.
In Engineering, the strategy should answer at least five groups of decisions:
- object structure: what will be contracted and which deliverables compose each package;
- delivery model: separate contracting, design-build, EPC, EPCM, turnkey, discipline contracts or other combinations;
- market: how many suppliers exist, how they are structured, which capabilities are scarce and where manufacturer dependency exists;
- risks and interfaces: who controls each risk and which party is best positioned to manage it;
- selection process: RFI, RFP, RFQ, prequalification, shortlist, mandatory criteria, scored criteria and negotiation.
Contracting strategy is not a procurement plan
The two documents are related but have different responsibilities. Strategy defines why and how the undertaking will contract; the procurement plan turns that logic into who, when, in which package and through which process.
| Dimension | Contracting strategy | Procurement plan |
| central question | how should contracting be structured? | how should acquisitions be executed and controlled? |
| horizon | structural decisions of the undertaking | operational Procurement planning |
| focus | packages, models, market, risks, criteria | dates, owners, milestones, status and deliveries |
| result | contracting architecture | Procurement execution baseline |
| update | at gates and relevant changes | continuously during the project |
This separation prevents a schedule spreadsheet from being called a “strategy” when structural decisions have not yet been resolved.
Engineering maturity constrains the strategy
The lower the technical maturity of the object, the greater the risk of attempting to contract a solution whose extent is not yet known. Conceptual Design, FEED, Basic Design, specifications, Basis of Design, equipment lists and functional requirements progressively improve the ability to create comparable packages.
This does not mean every contract must wait for Detailed Design. The model must be compatible with the available maturity. An RFP may admit differentiated solutions when the problem and performance requirements are clear, while an RFQ assumes a more standardized and sufficiently stable object for price to have comparable meaning.
When Engineering still cannot define boundaries, interfaces and acceptance criteria, the priority should be to mature the object or consult the market through an RFI rather than prematurely launch a formal competition.
Make-or-buy and the owner’s internal capability
One decision that precedes Procurement is determining which activities should remain under the owner’s direct responsibility and which should be acquired externally. PMBOK treats this as make-or-buy analysis and recommends considering resources, competencies, the need for independent specialization and risks.
In Engineering undertakings, this decision also involves governance. An owner may outsource design, implementation, inspection or management, but still needs enough capability to define requirements, make decisions, accept deliverables and manage risks that were not contractually transferred.
Total outsourcing of technical capability can create dependency on the very supplier that will be evaluated. Therefore, Owner’s Engineering, Consulting Engineering or an independent Technical Authority may be needed to preserve the contracting party’s decision-making capability.
How to define the package strategy
Package breakdown is one of the most sensitive decisions. Larger packages reduce direct contractual interfaces but concentrate responsibility and may reduce competition. Smaller packages increase specialization and competition but transfer more integration effort to the owner.
The decision should consider:
- technical and physical interfaces;
- construction sequence;
- uneven maturity between disciplines;
- market concentration;
- the owner’s coordination capability;
- long lead items;
- integration risks;
- standardization opportunities;
- availability of suppliers capable of assuming integrated scopes.
EPC, EPCM, design-build and separate contracting
There is no universally superior model. The delivery model should reflect risks, maturity, management capability and project objectives.
EPC or turnkey
Suitable when the owner seeks greater concentration of responsibility for Engineering, Procurement and construction and can define performance requirements and boundaries clearly enough. Contractual transfer does not eliminate risk: incomplete scope, late changes and ambiguous requirements may reappear as contingency pricing, claims or change orders.
EPCM
Preserves greater owner participation in contracting and enables integrated management by a specialized agent. It requires governance, decisions and capability to manage multiple contracts and interfaces.
Design-build
Integrates design and execution and can reduce interfaces between designer and constructor. It requires functional requirements and performance criteria capable of guiding the solution without depending on complete owner detailing.
Separate contracting
Design, supply, installation and integration may be contracted in separate packages. This increases control and specialization but makes interface coordination a critical responsibility of the contracting party.
Market analysis before selecting the model
A contracting strategy designed only internally may fail when it encounters a market different from what was assumed. The World Bank PPSD recommends structured market and supply-chain analysis to determine a fit-for-purpose approach.
The team should understand:
- number and size of capable suppliers;
- concentration or manufacturer dependency;
- barriers to entry;
- production capacity;
- location and logistics;
- market appetite for the proposed risk;
- usual contractual practices;
- availability of specialized personnel;
- warranty and support conditions;
- price and lead-time trends.
An RFI can be used to test these assumptions before the strategy is frozen.
Risk allocation: transferring is not eliminating
Contracts often attempt to shift as much risk as possible to the supplier. This can produce higher pricing, lower competition or risks that, although written into the contract, remain materially under the owner’s control.
Allocation should consider which party is best positioned to prevent, control, absorb or insure the risk. Examples:
| Risk | Party with greater possible influence | Strategic treatment |
| incomplete field data | owner/Engineering | survey and due diligence before competition |
| equipment performance | supplier | functional specification, warranties and tests |
| integration between contracts | owner/EPCM/OE | interface matrix and cross-cutting governance |
| manufacturing and delivery | supplier | milestones, expediting and inspections |
| requirement change | owner | change control and formal baseline |
| hidden brownfield condition | shared | surveys, contingencies and discovery rules |
Contractual transfer without actual control capability is not mitigation.
Selection strategy: when to use RFI, RFP and RFQ
The strategy should define the instrument appropriate to the object. RFI is useful for reducing market uncertainty; RFP is more suitable when solutions may vary and technical quality must be evaluated; RFQ works better for standardized and sufficiently defined objects.
This decision affects schedule, market effort, the need for technical criteria and the evaluation method. For complex objects, issuing an RFQ too early can produce prices that appear comparable but actually reflect different scopes.
The content on RFI vs RFP vs RFQ explores this boundary in more depth, while the article on TBE in Engineering addresses the formal technical evaluation process after proposals are received.
Prequalification and shortlist
When the supplier universe is large or the object requires specific capabilities, the strategy may provide for prequalification. The objective is to verify organizational capability before requesting detailed proposals.
Supplier qualification should be proportional to risk and based on evidence of experience, technical capability, structure, quality, supply chain, support and other criteria genuinely related to the object.
A poorly constructed shortlist limits competition before proposals are even evaluated. Criteria therefore need to be justified and documented.
Evaluation criteria need to originate in the strategy
Selection criteria should not be invented after the RFP has been issued. The World Bank recommends that evaluation factors be proportionate to the nature, complexity, risk and objective of the procurement and be defined in Procurement documents.
The strategy determines which aspects genuinely differentiate alternatives: performance, methodology, risk, specific experience, schedule, integration capability, sustainability, lifecycle or other factors.
This also prevents automatic use of corporate scoring templates that do not correspond to the package’s actual risk.
Long lead items and early procurement
Long-manufacturing-lead equipment may require Procurement before other parts of the project. The strategy needs to assess whether early procurement reduces schedule risk or creates the risk of purchasing before Engineering interfaces are stabilized.
When early purchase is necessary, define:
- parameters already frozen;
- interfaces still open;
- responsibility for later changes;
- manufacturer data required by the design;
- documentation and approval milestones;
- FAT, inspections and expediting;
- logistics and preservation until installation.
Brownfield and operating environments
In retrofit, expansion and modernization, existing-condition risk is central. Strategy should consider surveys, shutdown windows, coexistence with operating systems, migration, contingency, testing and reversibility.
Packages that work well in greenfield projects may be unsuitable in operating plants because the main risk lies not in supply but in interfaces with existing assets.
Contracting governance and stage gates
The strategy should define when a package is authorized to advance. Gates may verify scope maturity, budget, requirements, market, risks, internal approval, solicitation documents and evaluation criteria.
An illustrative flow may use the following points:
- need and objective confirmed;
- package strategy approved;
- technical baseline ready for the market instrument;
- suppliers qualified when applicable;
- RFP/RFQ approved for issue;
- technical and commercial evaluation completed;
- recommendation and contracting conditions approved;
- contract issued and management plan mobilized.
This governance links Procurement to approval authorities and to the project’s general stage gates.
Contracting strategy deliverables
A sufficiently mature strategy may be recorded in a report, executive plan or chapter of the Project Execution Plan. Regardless of format, it should consolidate:
- Procurement objectives;
- Engineering assumptions;
- make-or-buy analysis;
- package structure;
- market analysis;
- delivery and contract model;
- risk allocation;
- selection strategy;
- need for RFI or prequalification;
- evaluation criteria;
- long lead items;
- sequence and interfaces between packages;
- governance and gates;
- major decisions still open.
How the strategy becomes a procurement plan
After structural decisions are approved, the procurement plan converts each package into an executable sequence: requisition dates, RFI/RFP/RFQ, bid receipt, TBE, negotiation, award, submittals, manufacturing, inspections, FAT, expediting, logistics and delivery.
This sequence is essential because Procurement does not end at contract award. For critical equipment and systems, supply quality depends on technical control throughout execution.
Final considerations
Contracting strategy is an Engineering and governance decision before it is an administrative purchasing activity. It determines what will be bought, what the market must be capable of supplying, where the owner will retain control, how risks will be distributed and which instruments will be used to form a comparable decision.
The earlier these choices are addressed in an integrated manner with design, risks, schedule and market, the lower the probability that the undertaking will try to correct through the contract problems that originated in its own contracting architecture.
Transferring risk through a contract clause does not mean transferring the capability to control it. Strategy should place each risk with the party best positioned technically and operationally to manage it.
Technical references
[1] PROJECT MANAGEMENT INSTITUTE. A Guide to the Project Management Body of Knowledge (PMBOK® Guide). 8th ed. Newtown Square: PMI, 2025. Available at: [https://www.pmi.org/standards/pmbok](https://www.pmi.org/standards/pmbok)
[2] WORLD BANK. Project Procurement Strategy for Development: PPSD Long Form Detailed User Guidance. Washington, DC, 2025. Available at: [https://thedocs.worldbank.org/en/doc/b6bd32d73ca9f00f9cd83c90550d8a63-0290012025/original/PPSD-Procurement-Guidance-FINAL-aug-25.pdf](https://thedocs.worldbank.org/en/doc/b6bd32d73ca9f00f9cd83c90550d8a63-0290012025/original/PPSD-Procurement-Guidance-FINAL-aug-25.pdf)
[3] WORLD BANK. Procurement for Borrowers. Washington, DC. Available at: [https://www.worldbank.org/ext/en/what-we-do/project-procurement/for-borrowers](https://www.worldbank.org/ext/en/what-we-do/project-procurement/for-borrowers)
[4] INFRASTRUCTURE AND PROJECTS AUTHORITY; HM TREASURY. Project Routemap: Procurement Module. London. Available at: [https://www.gov.uk/government/publications/improving-infrastructure-delivery-project-initiation-routemap](https://www.gov.uk/government/publications/improving-infrastructure-delivery-project-initiation-routemap)
Frequently asked questions
It is the structured definition of how the undertaking will be divided into packages, which delivery and contract models will be used, how risks will be allocated, which market will be accessed and how suppliers and proposals will be selected.
Strategy defines the contracting architecture and principles. The procurement plan converts those decisions into packages, dates, owners, milestones and Procurement execution status.
The decision depends on requirement maturity, owner capability, available market, interfaces, risks and the need to concentrate or distribute responsibilities. There is no universally superior model.
Yes. The RFP is an execution instrument of the strategy. Packages, contract model, risks, criteria and market need to be sufficiently defined before issue.
It is the analysis that compares performing an activity with internal resources versus acquiring it externally, considering competence, capacity, costs, risks and the need for specialization.
They may require early packages or specific Procurement milestones, but early purchase must be reconciled with technical-interface maturity to avoid later changes and rework.
Complementary technical materials
Related solutions
- Requirements, Evidence and Acceptance Criteria Management
- Contract, Scope and Deliverables Management
Related services
- Technical Procurement: specification, equalization, suppliers and contracting support
- Owner’s Engineering: technical governance, inspection and acceptance
Core content on the topic
- Procurement in Engineering Projects: what it is, stages, criteria and supplier management
- RFI vs RFP vs RFQ: differences and when to use each document in Engineering
