Planning the Procurement of Engineering Works and Services: How to Structure It Before Bidding

Learn how to structure engineering procurement planning before bidding, integrating need, design maturity, estimate, schedule, risks, delivery strategy, inspection, and acceptance.

Check it out!

Planning the procurement of engineering works and services is the process that transforms a public need into a procurement that is technically defined, estimated, analyzed for risk, aligned with the delivery strategy, and prepared for bidding, inspection, acceptance, and entry into operation. Under Brazilian Law No. 14,133/2021, the preparatory phase is characterized by planning and must address the technical, market, and management considerations that may affect the procurement.

In engineering, this means planning does not end with the Preliminary Technical Study and is not limited to assembling bidding documents. Coherence must be demonstrated among need, requirements, surveys, selected solution, design maturity, quantities, estimate, schedule, risks, delivery model, measurement criteria, responsibilities, inspection, and acceptance. When these elements are produced in isolation, the bidding process may still be published, but the investment remains technically immature.

Procurement planning begins before the bidding documents

Bidding is one stage of the process; procurement planning is the decision system that should make that stage possible. Article 18 of Brazilian Law No. 14,133/2021 requires the preparatory phase, where applicable, to be compatible with the Annual Procurement Plan and budget laws and to consider technical, market, and management aspects.

For engineering works and services, this requirement has a practical consequence: the process needs to move from identifying the problem toward a progressively more verifiable definition of what will be procured. The public authority needs to know not only what it intends to build or implement, mas também why that solution was selected, what interfaces it has, how much it costs, which risks remain, how it will be executed, how it will be measured, and how it will be accepted.

This chain is the link among the Preliminary Technical Study, a bidding preparatory phase e o ciclo mais amplo de Capital Projects in Public Works.

The central question should not be “do all the documents exist?” but rather: is the procurement sufficiently mature to be taken to market without transferring avoidable uncertainties into bidding and execution?

Planning is not a document: it is a chain of coherence

Procurement planning is often treated as a document sequence: demand-formalization document, preliminary technical study, design, estimate, terms of reference, bidding documents, and contract. The sequence exists, but process quality depends primarily on coherence among those documents.

A preliminary technical study may select one solution while the Basic Design develops a different assumption. The estimate may quantify a scope different from the design narrative. The schedule may assume productivity incompatible with logistics. The risk matrix may allocate to the contractor a risk that depends on information not surveyed by the public authority. Measurement criteria may not reflect the estimate structure. Acceptance may require tests that were neither included in the scope nor priced.

For this reason, technical planning should function as an integrated procurement baseline.

Dimension	Maturity question
Need	Is the public need defined without prematurely prescribing the solution?
Requirements	Is expected performance objective, verifiable, and aligned with the need?
Engineering	Do surveys and designs have maturity compatible with the delivery model?
Quantities	Are there calculation records and traceability between design and estimate?
Costs	Does the estimate reflect location, base date, productivity, logistics, BDI, and risks?
Schedule	Is the schedule compatible with construction method, interfaces, and critical supplies?
Risks	Have risks been identified, treated, and incorporated into the contracting strategy?
Procurement	Are delivery model, award criteria, qualification, and guarantees coherent with the scope?
Execution	Are measurement, changes, communication, and inspection defined?
Acceptance	Are there objective criteria for testing, documentation, acceptance, and handover?

This view avoids false maturity: the formal existence of a document does not prove that the technical information is ready to support a decision.

Architecture of the preparatory phase under Brazilian Law 14,133

Article 18 organizes the preparatory phase around a set of related decisions. For engineering, they can be read as a system with five groups: need and feasibility; technical definition; estimate and resources; risks and strategy; execution conditions and governance.

The first function of planning is to characterize the need and demonstrate procurement feasibility. The Preliminary Technical Study should demonstrate the problem to be solved and the preferred solution, considering quantities, market alternatives, costs, related procurements, impacts, and intended results.

The second function is to turn that conclusion into sufficient technical definition. Depending on the scope and delivery model, this may involve Terms of Reference, Preliminary Design, Basic Design, or Detailed Design. Law No. 14,133 does not treat these documents as synonyms; each performs a specific role in definition and allocation of responsibility.

The third function is to establish the cost and schedule baseline. In engineering works and services, the estimate and schedule are not administrative attachments: they materialize quantities, productivity, methods, sequencing, and engineering assumptions.

The fourth function is to structure risks and procurement strategy. This includes risk analysis, a risk-allocation matrix where applicable, delivery model, procurement procedure, award criteria, qualification, guarantees, and material bidding conditions.

The fifth function is to prepare execution governance: contract-management model, inspection, measurement, payment, changes, documentation, testing, and acceptance.

The benefit of this reading is straightforward: the preparatory phase is treated as decision engineering rather than merely procedural documentation.

From need to solution: the first risk is defining too much too early

A recurring error occurs when the demand is framed from the outset as a specific product, technology, or closed solution before the problem has been technically characterized. This reduces the Preliminary Technical Study’s ability to compare alternatives and may lead to overly restrictive or inadequate specifications.

The need should explain the expected public outcome, existing conditions, constraints, and criticality. In engineering, this often requires field surveys, operational data, failure history, inventories, interfaces with existing assets, and user requirements.

The more complex the project, the more important it is to separate three levels:

• problem: what needs to be solved;
• required outcome: what performance needs to be achieved;
• technical solution: which alternative delivers that performance with the best balance among cost, schedule, risk, and lifecycle.

This separation reduces premature prescription and makes subsequent justifications more robust.

The Preliminary Technical Study needs to drive a decision, not merely complete a step

The Preliminary Technical Study is the bridge between the need and the definition of the solution. Its value lies in the quality of evidence used to compare alternatives and demonstrate technical and economic feasibility.

For engineering works and services, the Preliminary Technical Study should be grounded in actual surveys, site conditions, interfaces, existing infrastructure capacity, normative requirements, implementation constraints, future operations, and related procurements. Without this basis, the study risks merely formalizing a solution already selected.

The article Poorly developed Preliminary Technical Studies in public works explains how failures at this stage propagate into design, bidding, and construction. The content From Preliminary Technical Study to Technical Acceptance shows why the preliminary study needs to be read as the beginning of a maturity chain.

In procurement planning, the conclusion of the Preliminary Technical Study should produce decisions usable by subsequent stages: performance requirements, reference solution, assumptions, critical interfaces, relevant risks, and information that still needs to be developed before bidding.

Preliminary study, design, and estimate need to form a single technical baseline

In public works, one of the greatest procurement risks arises when design, design narrative, quantities, estimate, and schedule are developed as independent products.

The design defines geometry, capacities, materials, equipment, interfaces, and requirements. Quantities translate those definitions into measurable units. Cost build-ups convert quantities into resources and costs. The schedule distributes execution over time. Bidding documents and the contract use this information to define responsibilities, measurement, and payment.

If any link is misaligned, the problem reappears during execution.

Maturity should be verified through traceability:

1. Every material estimate item should have an identifiable source in the design, design narrative, or requirement.
2. Every critical quantity should have a reproducible calculation basis.
3. Every relevant cost build-up should reflect a plausible execution method and productivity.
4. The schedule should consider field constraints, interfaces, and lead times.
5. Measurement criteria should correspond to the scope actually procured.
6. Tests and deliverables required for acceptance need to be included in scope and price.

O artigo Public Works Estimating details this integration from a Cost Engineering perspective.

Design maturity depends on the delivery strategy

There is no single level of design definition appropriate for every procurement model. Sufficiency of technical definition depends on the selected delivery model and how responsibility for engineering development will be allocated.

Under unit-price or lump-sum contracting, the public authority normally needs sufficiently consistent definition to enable comparable competition and reduce scope ambiguity. In integrated and semi-integrated contracting, part of design development may be transferred, but this increases the importance of performance requirements, preliminary design, acceptance criteria, risk allocation, and design governance.

Planning should therefore answer the following before publication:

• which technical information is the public authority’s responsibility;
• which development will be the contractor’s responsibility;
• which assumptions are binding;
• which solutions allow optimization;
• how changes will be evaluated;
• which interfaces cannot remain undefined.

Selecting the delivery model without considering engineering maturity creates a structural mismatch: the contract begins operating with a level of uncertainty that was not recognized in the strategy.

Quantities, estimate, and base date support procurement decisions

The owner’s estimate influences budget availability, price-acceptability criteria, delivery model, bid evaluation, assessment of potentially unfeasible bids, measurements, and future changes.

For this reason, simply applying prices from an official database is not enough. It is necessary to verify whether services, cost build-ups, and productivity assumptions actually represent the scope.

In public works, the estimate should consider, as applicable:

• SINAPI, SICRO, or another applicable reference;
• properly justified project-specific cost build-ups;
• direct and indirect costs;
• labor burden;
• BDI and taxes;
• freight, logistics, and access conditions;
• mobilization and demobilization;
• site overhead;
• base date and location;
• interferences and execution-environment conditions;
• risks that should be priced or contractually addressed.

Consistency between estimate and design should be auditable. A detailed spreadsheet based on an immature design remains a low-reliability estimate.

Schedule is not a date: it is a consequence of the execution strategy

Another common mistake is setting duration based on administrative expectations without verifying construction logic and project constraints.

The baseline schedule should reflect sequencing, work fronts, resources, dependencies, approvals, fabrication, critical supplies, testing, and commissioning. For projects in existing facilities, it should consider operational windows, shutdowns, permits, contingencies, and coexistence with ongoing operations.

A duration incompatible with the execution method distorts competition and may encourage bids based on unfeasible assumptions. During execution, the problem tends to reappear as rescheduling, extensions of time, claims, and changes.

Therefore, schedule planning and Cost Engineering should use the same productivity and scope assumptions.

Risks should influence the procurement strategy

The risk analysis required by Article 18 of Law No. 14,133/2021 should not be produced after all material decisions have already been made. Risk needs to inform the decision.

If the geotechnical investigation is insufficient, additional investigation before bidding may be required, the delivery model may need to change, or specific contractual treatment may be necessary. If equipment has a long lead time, the schedule and procurement strategy need to reflect that condition. If construction occurs in a critical operating environment, inspection and intervention-authorization criteria need to be strengthened.

It is important to distinguish procurement risk management from the risk allocation matrix. The first is a process of identification, analysis, treatment, and monitoring. The second, where applicable, contractually defines which risks will be borne by each party and how certain events will be treated.

O artigo Risk Management in Public Works explores this distinction in greater depth and shows how to integrate risks with cost, schedule, design, and governance.

Delivery model, award criteria, and qualification need to respond to the scope

The procurement strategy should not be a default choice replicated from previous bidding documents. It should derive from the characteristics of the scope and the identified risks.

Planning needs to justify the delivery model, award criterion, and qualification requirements in relation to the project’s actual complexity.

Insufficient requirements may allow procurement of a supplier without adequate capability. Excessive requirements may unduly restrict competition. The balance depends on identifying the most technically relevant portions, necessary competencies, critical resources, and performance risks.

Likewise, the choice among lowest price, highest discount, quality-and-price, or another applicable criterion should consider how much technical quality can vary and the impact of that variation on the intended outcome.

Procurement strategy is therefore simultaneously an engineering, governance, and market decision.

Terms of Reference and Basic Design should translate decisions that are already mature

The Terms of Reference or Basic Design should not be where the public authority discovers what scope it intends to procure. They should consolidate decisions developed in earlier stages.

A technically mature document should allow a diligent bidder to understand:

• the scope and its boundaries;
• performance requirements;
• known existing conditions;
• each party’s responsibilities;
• reference documents;
• relevant methods or constraints;
• interfaces with third parties;
• measurement criteria;
• document deliverables;
• tests and acceptance criteria;
• schedule and milestones;
• payment conditions;
• change management.

When these definitions appear only after contract award, execution becomes the stage in which the public authority has to clarify the scope itself.

Interfaces and interdependent procurements need to be addressed before bidding

Works and systems rarely operate in isolation. Power, telecommunications, automation, security, HVAC, structures, architecture, IT, utilities, and operations may depend on one another.

Article 18 includes related and interdependent procurements among the elements of the Preliminary Technical Study. In practice, this analysis should continue through consolidation of the contracting strategy.

It is necessary to identify, for example:

Interface	Risk if not addressed
Civil x building systems	incompatible shafts, openings, supports, and access
Electrical x automation	uncoordinated power supply, protection, and communications
Equipment x infrastructure	inadequate load, dimensions, or environment
Construction x operations	unplanned interruptions and work windows
Contract A x Contract B	scope gaps or overlaps
Design x utility provider	external approvals and timelines not incorporated

Governance of these interfaces needs to define the responsible party, input information, deadline, closure criterion, and evidence. Otherwise, the interface tends to be pushed into execution, when the ability to correct it is lower and the cost is higher.

Measurement and payment criteria need to originate in planning

Measurement is a scope-control rule, not merely a financial routine. Inadequate criteria may allow payment for unverified progress, create disputes over quantities, or make it difficult to correlate physical progress with disbursement.

Planning should define units, evidence, completion criteria, required documents, verification responsibilities, and treatment of partially completed work.

In complex contracts, it may be necessary to structure payment milestones linked to verifiable deliverables, such as design approval, FAT, equipment delivery, installation, SAT, commissioning, and acceptance.

The logic should be defined so that payment follows value actually delivered and remaining risk, avoiding economic front-loading that is incompatible with the physical maturity of the scope.

The procurement needs to be inspectable and objectively acceptable

A scope can be technically sound and still be difficult to inspect if the requirements are not verifiable. Terms such as “high quality,” “robust solution,” or “top-tier equipment” do not constitute acceptance criteria.

Requirements need to be translated into observable evidence: technical characteristics, tolerances, performance, tests, certificates, inspections, records, and documentation.

Planning should anticipate the inspection and acceptance model. This includes defining, where applicable:

• field inspections;
• inspection and test plans;
• hold and witness points;
• daily or periodic reports;
• material traceability;
• nonconformity records;
• functional and integrated tests;
• FAT e SAT;
• punch list;
• As-Built;
• Data Book;
• training;
• assisted operation;
• criteria for provisional and final acceptance.

This structure connects planning to execution and reduces subjectivity in acceptance.

Os artigos Public Works Inspection e Engineering Contract Inspection explore these two layers of control in greater depth.

Change governance needs to be defined before the first change

Every construction project has some level of uncertainty, but this does not mean change management should be improvised.

The contract should establish communication channels, decision authority, records, minimum documentation, technical assessment, cost and schedule impact, approval, and baseline updates.

Without this workflow, changes may be executed before authorization, field decisions may lose traceability, and claims may be analyzed without a reliable baseline.

Planning also needs to distinguish scope change, correction of a design error, unforeseen condition, allocated-risk event, and discretionary decision by the public authority. Each case has distinct technical and contractual implications.

The team and governance need to match complexity

Planning is not the isolated responsibility of the person drafting the Preliminary Technical Study. Engineering procurement requires integration among the requesting unit, technical team, estimating, legal, procurement, contract management, and, depending on the scope, operations and maintenance.

O conteúdo Procurement Planning Team details this composition. The key point is that governance should preserve segregation of duties without fragmenting technical information.

A sound structure defines:

• who produces each piece of information;
• who reviews it;
• who approves it;
• which interfaces require multidisciplinary validation;
• how decisions and assumptions are recorded;
• which document is the source of truth for each baseline.

In larger projects, formal gates can reduce the risk of proceeding to bidding with critical open items.

Readiness gate before publishing the bidding documents

An engineering procurement should undergo a readiness review before being released to the market.

The objective is not to create additional bureaucracy, but to determine whether the main sources of ambiguity have been reduced to a level compatible with the contractual model.

A readiness gate can verify, among other points:

Gate	Expected evidence
Need	problem, expected outcomes, and institutional alignment
Solution	completed preliminary study and justified alternative
Engineering	surveys and documentation compatible with the delivery model
Scope	defined boundaries, interfaces, and responsibilities
Estimate	auditable quantities, calculation records, references, BDI, and base date
Schedule	schedule coherent with method, supplies, and constraints
Risks	updated register, treatments, and coherent allocation
Market	strategy compatible with market capacity and competition
Contract	defined measurement, payment, changes, guarantees, and communications
Inspection	planned structure, resources, and evidence
Acceptance	established tests, documentation, and objective criteria

Open items may exist, but they need to be classified and controlled. The problem is publishing the bidding documents without knowing that certain gaps exist or understanding their impact.

This approach brings public-sector planning closer to Project Readiness e Project Assurance practices used in complex capital investments.

Signs that the procurement is not ready yet

Some symptoms indicate low maturity even when the process contains many documents:

• quantities without calculation records;
• estimate inconsistent with drawings;
• absence of field surveys for existing infrastructure;
• schedule defined only by an administrative deadline;
• specifications naming brands or technologies without technical justification;
• design with open interfaces among disciplines;
• generic risk matrix copied from another contract;
• measurement rules incompatible with the estimate;
• absence of testing and acceptance criteria;
• lack of definition regarding who will develop a given part of the engineering;
• bidding process dependent on clarifications to explain its own scope.

These signs do not automatically mean the procurement should be stopped. They indicate that the public authority should assess the criticality of the gaps and consciously decide whether more engineering needs to be developed, the strategy changed, or contractual treatment of the risk made explicit.

Proportional planning: not every procurement needs the same level of depth

Required maturity should be proportional to the scope’s complexity, value, criticality, innovation, interfaces, and risk.

A simple, repetitive intervention does not require the same structuring effort as an industrial plant, substation, hospital, data center, operations center, or multidisciplinary infrastructure in an existing environment.

The principle, however, remains the same: available information needs to be sufficient for the decision to be made.

The greater the uncertainty and consequence of error, the more robust the surveys, studies, validations, designs, estimates, and governance mechanisms should be.

Specialized technical planning can reduce risk before bidding

In multidisciplinary procurements, the public authority may need technical support to structure or review documentation before the bidding documents are published.

This support does not replace institutional responsibilities or the manager’s decision. Its function is to produce technical evidence, integrate disciplines, test coherence, and reduce avoidable ambiguity.

Possible activities include maturity assessment, Due Diligence, surveys, Preliminary Technical Study, program of needs, requirements, Preliminary Design, Basic Design, estimate, schedule, risk analysis, contracting strategy, Terms of Reference, review of bidding documents, and definition of measurement, inspection, and acceptance criteria.

A3Engenharia structures this work as technical procurement planning, connecting engineering, documentation, risks, and governance to the full investment lifecycle.

Final considerations

Planning the procurement of an engineering work or service means deciding, before bidding, how to transform a need into a technically defined, economically referenced, contractually governable, and operationally acceptable scope.

The preparatory phase should not be assessed by the number of documents produced. The most useful measure is the coherence among the decisions those documents record. Preliminary Technical Study, design, estimate, schedule, risks, delivery model, bidding documents, contract, inspection, and acceptance need to describe the same project from different perspectives.

The greater this coherence, the less execution needs to be used to resolve definitions that could have been addressed during planning. In public investments, maturity before bidding is one of the most effective ways to protect schedule, cost, quality, governance, and public outcomes.

This logic is applied across the full lifecycle in the Engineering for Public Investments, solution, which connects Assessment, planning, Preliminary Technical Study, design, estimating, procurement, inspection, Assurance, and technical acceptance.

Technical references

[1] BRAZIL. Law No. 14,133, of April 1, 2021. Public Procurement and Administrative Contracts Law. Article 18 and related provisions. Available at: [https://www.planalto.gov.br/ccivil_03/_ato2019-2022/2021/lei/l14133.htm](https://www.planalto.gov.br/ccivil_03/_ato2019-2022/2021/lei/l14133.htm)

[2] BRAZIL. Ministry of Management and Innovation in Public Services. Federal Government Procurement Portal. Procurement Planning. Available at: [https://www.gov.br/compras/pt-br/nllc/legislacao-14-133-por-tema/planejamento-da-contratacao-pgc-e-pca](https://www.gov.br/compras/pt-br/nllc/legislacao-14-133-por-tema/planejamento-da-contratacao-pgc-e-pca)

[3] BRAZIL. National Department of Transport Infrastructure. Preparatory Phase: elements, regulations, and responsibilities under Law No. 14,133/2021. Available at: [https://www.gov.br/dnit/pt-br/acesso-a-informacao/licitacoes/implantacao-da-lei-14.133/fase-preparatoria](https://www.gov.br/dnit/pt-br/acesso-a-informacao/licitacoes/implantacao-da-lei-14.133/fase-preparatoria)

[4] BRAZILIAN FEDERAL COURT OF ACCOUNTS. Procurement and Contracts: TCU Guidance and Case Law. Preliminary Technical Study. Available at: [https://licitacoesecontratos.tcu.gov.br/4-1-estudo-tecnico-preliminar-etp/](https://licitacoesecontratos.tcu.gov.br/4-1-estudo-tecnico-preliminar-etp/)

[5] OFFICE OF THE ATTORNEY GENERAL OF BRAZIL. Templates under Law No. 14,133/2021 for competitive procurement, including engineering works and services. Updated in 2026. Available at: [https://www.gov.br/agu/pt-br/composicao/cgu/cgu/modelos/licitacoesecontratos/14133/pregao-e-concorrencia](https://www.gov.br/agu/pt-br/composicao/cgu/cgu/modelos/licitacoesecontratos/14133/pregao-e-concorrencia)

Frequently asked questions

What is procurement planning for engineering works and services?

It is the process that transforms a need into a procurement that is technically defined, estimated, analyzed for risk, and structured for bidding, execution, inspection, measurement, and acceptance. Under Law No. 14,133/2021, the preparatory phase is characterized by planning.

Is procurement planning the same as a Preliminary Technical Study?

No. The Preliminary Technical Study is a central part of planning because it characterizes the problem, compares alternatives, and supports selection of the solution. Planning continues with technical definition of the scope, designs, estimate, risks, procurement strategy, execution conditions, inspection, and acceptance.

Which documents form part of planning the procurement of a construction project?

Depending on the scope and delivery model, the process may include demand formalization, annual procurement planning, Preliminary Technical Study, surveys, program of needs, Preliminary Design, Basic or Detailed Design, design narratives, specifications, quantities, estimate, schedule, risk analysis and allocation matrix, Terms of Reference, bidding documents, draft contract, and measurement and acceptance documents.

When is an engineering procurement ready for bidding?

When critical information has maturity compatible with the delivery model and there is coherence among need, solution, design, scope, quantities, estimate, schedule, risks, responsibilities, measurement criteria, inspection, and acceptance. A readiness gate can formalize this verification.

What is the difference between procurement planning and the preparatory phase?

The preparatory phase is the legal phase of the procurement process characterized by planning. Procurement planning is the technical and managerial activity performed within that phase and, in a broader sense, begins with identification of the need and should also prepare future execution and contract management.

Is risk analysis performed before or after design?

It should accompany the development of the procurement. Early risks help define which surveys and studies are necessary; as design, estimate, and strategy evolve, the risk register should be updated and influence subsequent decisions.

Why are the estimate and schedule part of procurement planning?

Because both translate scope into cost and time and influence budget availability, delivery strategy, bid evaluation, measurement, payments, and change analysis. They should share the same technical assumptions as the design.

What is a bidding readiness gate?

It is a structured review before publication of the bidding documents to verify whether critical procurement elements are sufficiently mature, open items are known, and remaining risks are compatible with the contracting strategy.

Additional technical materials

Related services

• Technical Planning for Engineering Procurement
• Cost Engineering for Engineering Works and Services
• Terms of Reference for Engineering Works and Services
• Technical Review of Bidding Documents and Attachments for Engineering Procurement
• Engineering Risk Management
• Technical Support for Engineering Works and Contract Inspection

Core content on this topic

• Capital Projects in Public Works: From Need to Operations
• From Preliminary Technical Study to Technical Acceptance
• Preparatory Phase for Public Works Procurement

Related technical content

• Poorly Developed Preliminary Technical Studies in Public Works
• Public Works Estimating
• Risk Management in Public Works
• Procurement Planning Team
• Public Works Inspection
• Engineering Contract Inspection