What Brazil’s Federal Court of Accounts (TCU) Reviews in Construction and Engineering Services Procurement

Understand how Brazil’s Federal Court of Accounts (TCU) structures oversight and control of construction and engineering services procurement, from planning through acceptance.

Check it out!

Brazil’s Federal Court of Accounts (TCU) reviews public procurement through a logic that is much broader than checking whether the tender documents correctly cite Law No. 14,133/2021. In construction and engineering services, the analysis may cover procurement governance, definition of the need, planning, design maturity, cost estimating, supplier selection, contract formalization, risk allocation, inspection, measurements, payments, contract changes, and acceptance of the scope. The common element across these stages is the need to demonstrate that administrative decisions were prepared, substantiated, executed, and controlled through evidence consistent with the risk and complexity of the project.

The 5th edition of the TCU Manual on Public Procurement & Contracts: Guidance and Case Law, published in 2025, organizes this view into three broad dimensions: procurement governance, the public-procurement metaprocess, and contract management. The document has a pedagogical and preventive purpose. Instead of functioning only as a catalog of irregularities, it brings together normative references, case law, risks, controls, models, and guidance that can be used to structure more robust processes before a failure turns into a challenge, delay, amendment, overbilling, stoppage, or accountability proceeding.

For construction and engineering services, this means that the so-called “TCU benchmark” is not limited to a documentary checklist. A process may contain a Preliminary Technical Study (ETP), terms of reference, basic design, and an estimate and still be technically weak if those documents are not consistent with one another. Likewise, a procurement may have an apparently advantageous total price and still remain exposed to risk if quantities are deficient, measurement criteria are poorly defined, the risk matrix is inconsistent, unit prices are unbalanced, or inspection is unable to produce evidence about execution.

The most useful way to apply the TCU Manual is to view it as a control framework throughout the procurement lifecycle. At each phase, the Public Administration needs to answer four questions: what decision is being made; what information supports that decision; what risks can prevent the expected outcome; and what documents or evidence demonstrate that the controls were actually performed. This chain — decision, basis, risk, and evidence — is what transforms formal documents into governance instruments. The 7-Gate Maturity Framework for Public Engineering Investments organizes this logic into formal advancement, hold, and evidence criteria throughout the investment lifecycle.

How to read the TCU Public Procurement and Contracts Manual as a control benchmark

The TCU Manual was not structured as a sequence of provisions from Law No. 14,133/2021. Its organization follows the actual procurement lifecycle: first governance, then foundations and the metaprocess, followed by planning, supplier selection, contract formalization, and finally contract management and termination.

This organization is particularly useful in engineering because contractual problems rarely arise only during execution. A disputed measurement may originate in a poorly defined criterion in the terms of reference. An amendment may result from an incomplete design. An unfeasible bid may have been favored by a deficient reference estimate. A stoppage may be the consequence of procurement initiated without sufficient technical maturity or without resources compatible with the schedule.

The Manual uses four mechanisms that help turn abstract rules into operational controls:

• normative references, showing the legal and regulatory basis of the topic;
• case law, presenting TCU interpretations and how concrete situations were analyzed;
• identified risks, structured as cause, event, and consequence;
• models and guidance from governing or oversight bodies, where available.

There are also suggested search expressions for the Court’s portal. This matters because case law should not be treated as a frozen snapshot. A decision may be important for understanding a line of reasoning, but an administrative decision needs to consider current legislation, the procurement context, and later applicable interpretations.

For the engineering team, the value lies in using the Manual as a matrix of questions. If the planning chapter identifies the risk of inadequate quantity estimates, for example, merely recording that the risk exists is not enough. It is necessary to verify where the quantities came from, who calculated them, which designs support them, which assumptions were used, and how the review was documented.

This approach avoids a recurring error: turning compliance into an accumulation of documents. The TCU itself emphasizes that governance should not be confused with bureaucracy. Controls need to create value and be proportional to risk. A form without analysis is not a control; a signature without verification is not validation; a spreadsheet without a calculation memorandum is not traceability.

Governance comes before the tender

Under Law No. 14,133/2021, senior management is responsible for procurement governance. The TCU Manual unfolds this responsibility into leadership, strategy, and control mechanisms intended to evaluate, direct, and monitor the procurement function.

In practice, this means that the performance of a public works contract does not depend only on the inspector appointed after contract execution. The organization needs structure, competencies, processes, planning, risk management, monitoring instruments, and accountability mechanisms before a specific procurement reaches the market.

Procurement governance includes, among other practices, promoting integrity, risk management, strategic management, defining planning instruments, monitoring performance, transparency, and internal-audit activities. The Annual Procurement Plan is part of this system as an instrument connecting needs, administrative capacity, and the schedule of acquisitions and contracting actions.

In the engineering context, this organizational dimension has a direct effect on projects. If an agency concentrates several construction projects in one period without enough staff to develop designs, review estimates, and inspect contracts, the risk is not merely administrative. Insufficient capacity can result in superficial technical documents, incomplete tender packages, and reactive inspection.

The Annual Procurement Plan in Engineering should therefore also be understood as a capacity-preparation instrument. It helps identify when studies, designs, permits, surveys, and support contracts need to begin so that construction is not tendered prematurely.

Mature governance also defines who decides, who prepares, who reviews, and who controls. Segregation of duties reduces undue concentration of powers and helps preserve independence among preparation, approval, selection, and inspection. In engineering, a second line of review can be decisive in detecting inconsistencies that the document author, because of familiarity with their own work, may not notice.

From the need to the ETP: the TCU checks whether procurement started with the right problem

Procurement planning during the preparatory phase should not begin with a solution that has already been predetermined. The Preliminary Technical Study exists to characterize the need, examine alternatives, estimate quantities and value, evaluate the solution as a whole, and demonstrate the suitability of the procurement.

In engineering, ETP quality depends on the quality of available information. A generic demand such as “renovate the building” or “modernize the system” is insufficient to compare alternatives consistently. Existing conditions, current performance, constraints, business requirements, interfaces, risks, and intended outcomes need to be understood.

The Preliminary Technical Study for construction and engineering services needs to build the bridge between the administrative need and the solution that will later be specified. When this bridge is weak, later decisions tend to be justified retrospectively rather than deriving from prior analysis.

The TCU pays attention to elements such as description of the need, inclusion in the Annual Procurement Plan, requirements, quantity estimates, market survey, value estimate, solution description, lotting or division strategy, intended outcomes, administrative actions, related procurements, and environmental impacts. This is not about filling isolated fields: these elements should form a coherent line of reasoning.

If the market survey concludes that there are three technological alternatives but the requirements section is written so that only one can comply, the decision needs to be technically explained. If ETP quantities are not tied to a survey or historical series, the value estimate is weak from the outset. If the intended outcome is not measurable, it will later be difficult to structure acceptance criteria.

The ETP’s function is to reduce enough uncertainty to decide whether, how, and under what conditions to procure. The more complex the project or system, the greater the likely need for preliminary studies, inspections, surveys, geotechnical investigations, tests, interface analysis, and technical characterization.

Risk analysis needs to produce controls, not just a matrix

The TCU Manual addresses risk management both at the governance level and in the planning of each procurement. The practical value of this approach lies in connecting risks to the controls that need to exist in documents and processes.

A matrix that classifies “construction delay” as a high risk, for example, adds little value if it does not identify specific causes. Delay may result from incomplete design, pending expropriation, environmental licensing, an unrecorded interference, delivery of long-lead equipment, contractor financial incapacity, a late decision by the Public Administration, or an external event. Each cause requires a different treatment.

The Risk Allocation Matrix in Engineering Contracts serves another complementary function: allocating contractual responsibility for specific events. Risk management and the risk-allocation matrix are not synonyms. The former helps identify and address uncertainties; the latter establishes how certain risks will be allocated between the parties and which contractual consequences arise from that allocation.

For control purposes, a well-treated risk needs to leave a trail. If geotechnical risk has been identified, there should be a corresponding investigation or contractual strategy. If there is interference risk, surveys and field procedures need to be planned. If the risk lies in the specification, performance and validation criteria should appear in the procurement documents.

The central point is to convert risk into verifiable action. Without that, the matrix functions only as a declaratory record.

The terms of reference turn the decision into an enforceable contractual obligation

Once the need, solution, and risks are sufficiently understood, the Terms of Reference organize the procurement conditions. The TCU Manual details definition of the scope, rationale, description of the solution, requirements, execution model, management model, measurement and payment criteria, supplier selection, and value estimate.

For construction and engineering services, each of these parts has technical impact. The scope needs clear boundaries. Requirements need to be verifiable. The execution model should reflect interfaces and responsibilities. Measurement criteria should be associated with deliverables or quantities that can be objectively demonstrated. The management model needs to define how evidence will be produced, analyzed, and accepted.

Weak Engineering Terms of Reference create a dangerous asymmetry: the Public Administration knows the outcome it wants, but the contract does not translate that outcome into measurable obligations. During execution, disputes arise over what was or was not included, which document prevails, and which criteria determine acceptance.

Preventive control seeks precisely to eliminate ambiguities before the bidding process. The technical review of Terms of Reference should confront scope, requirements, designs, worksheets, schedules, responsibilities, and measurement criteria to determine whether the procurement package functions as a coherent system.

In engineering, the TCU looks at design maturity

Law No. 14,133/2021 distinguishes preliminary design, basic design, and detailed design and relates these artifacts to delivery models. The Manual dedicates a specific section to planning construction and engineering services, including surveys, geotechnical investigations, technical solutions, identification of services, materials and equipment, construction methods, inputs for management, and detailed estimating.

The control question is not merely whether a file called “Basic Design” exists. It is whether its content has maturity compatible with the procurement that will be launched.

Incomplete designs compromise quantities, budget, schedule, construction method, measurement criteria, and risk assessment. The deficiency propagates: an omitted quantity may become a new service; an unidentified interference may cause a stoppage; a generic specification may produce incomparable bids; an incompatibility between disciplines may appear only during construction.

The TCU has historically consolidated the relationship between design quality and estimate quality. Under the modern practice of Law No. 14,133/2021, this relationship remains essential: the estimated value is reliable only when the scope is sufficiently characterized.

The article on design errors in public works shows how engineering failures can create contractual and accountability consequences. Preventing the problem requires reviewing maturity before publication of the tender, rather than relying exclusively on inspection to correct the design during execution.

The estimate is simultaneously a planning tool, evaluation benchmark, and control instrument

In public works, the estimate is not used only to obtain financial authorization. It establishes the estimated value, supports bid analysis, guides acceptability criteria, and later participates in measurement, control of changes, and preservation of the economic-financial equation.

For this reason, the TCU has historically paid close attention to Cost Engineering. Quantities, cost compositions, SINAPI, SICRO, market research, BDI, site administration, mobilization, temporary facilities, and the physical-financial schedule need to form a coherent whole.

Price Research for Construction and Engineering Services under Law 14,133 explains the hierarchy and treatment of references. SINAPI, in turn, functions as one of the central reference bases for building construction when applicable.

Control becomes even more important when the project includes non-standardized items, specific local conditions, or adapted cost compositions. In these cases, the calculation memorandum and documentation of assumptions are essential. The absence of a direct reference does not eliminate the obligation to demonstrate price reasonableness; it only changes the methodology required to build that demonstration.

The estimate should also align with the schedule. A balanced total price may conceal an inadequate distribution among phases, creating incentives for front-loaded payments or schedule manipulation. Inspection needs to be able to relate physical progress, measured value, and actual delivery.

The tender must preserve competition without losing technical precision

The tender documents transform planning decisions into bidding rules. At this stage, control checks whether participation conditions, evaluation, qualification, acceptability, guarantees, deadlines, and contractual obligations are aligned with the scope and legislation.

In engineering, there is a legitimate tension between specifying enough and unduly restricting competition. Technical requirements need to derive from the need and expected performance. Requirements for experience, certificates, capabilities, or models should have justification proportional to the criticality of the scope.

Qualification and Technical Capability in Engineering Procurement should filter relevant capability without creating artificial barriers. Likewise, evaluation criteria and quality demonstrations need to be structured to distinguish proposals objectively.

When inconsistencies exist, bidders may use requests for clarification and challenges. These mechanisms should not be viewed only as obstacles to procurement. They often reveal scope, budget, or tender-rule failures that can still be corrected before contract execution.

Preventive control seeks precisely to reduce this rework: review the documents as a single package and test whether a third party can understand what is being procured, calculate its proposal, and demonstrate compliance without resorting to contradictory interpretations.

The TCU reviews feasibility and value for money without reducing the analysis to a single percentage

Law No. 14,133/2021 contains specific rules for bids involving construction and engineering services, including parameters for unfeasible prices and additional guarantees. Price analysis, however, should not be confused with mechanical application of an isolated percentage.

A proposal below 75% requires understanding of the applicable legal regime and the circumstances of the proposal. Where due diligence is appropriate, productivity records, quotations, contracts, commercial strategies, and cost memoranda may be necessary to substantiate a decision.

Feasibility Due Diligence is relevant because the Public Administration needs to decide based on evidence, avoiding both acceptance of a proposal that cannot be performed and elimination of a competitive proposal without sufficient basis.

Conversely, overpricing and overbilling are distinct concepts. The analysis needs to distinguish an inadequate estimated price, an excessive proposal, payment for quantities not executed, and other forms of loss. This conceptual precision is necessary for control to be technically defensible.

Contract formalization needs to preserve what was planned

After selection, formalization is not merely an administrative step. Clauses, guarantees, the risk matrix, payment conditions, responsibilities, contract documents, and change mechanisms need to preserve the logic built during planning.

An inconsistency among the tender documents, proposal, design, Terms of Reference, and contract can create interpretive conflict from day one. The document structure therefore needs to establish clear hierarchy and integration among attachments.

Contract, Scope, and Deliverables Management helps treat the contract as a technical baseline: what was contracted needs to be decomposable into obligations, deliverables, criteria, deadlines, and evidence.

The risk matrix also needs to remain operational. If a particular event was allocated to the Public Administration, inspection needs to know how to recognize its occurrence and which records will be required. If the risk was assigned to the contractor, the contract should not later transfer its consequence informally through unsubstantiated decisions.

Technical inspection needs to produce contemporaneous evidence of execution

A construction project is not adequately inspected merely through periodic visits. Inspection is a continuous process of verifying compliance with requirements, quantities, quality, schedule, documentation, and contractual obligations.

The TCU Manual distinguishes technical inspection, administrative inspection, and contract-management activities, and also addresses provisional and final acceptance. This separation helps distribute responsibilities and avoid concentrating controls in one person beyond their capacity.

Evidence-based inspection in public works starts from a decisive premise: later records do not replace contemporaneous evidence. Dated photographs, reports, tests, inspection records, site diaries, approvals, NCRs, measurements, and delivery documents make it possible to reconstruct what occurred.

This record set protects both the Public Administration and the contractor. Without evidence, technical disagreements turn into conflicting versions of past facts.

Inspection also needs decision-making capacity. When a nonconformity is found, there should be a flow to record it, classify it, require correction, verify the rework, and close the issue. When a potential scope change is identified, informal execution should not be permitted with an attempt to regularize it only afterward.

Measurement and payment depend on criteria defined before execution

The TCU treats measurement and payment as a relevant part of the contract-management model. In engineering, this topic requires a connection among the cost worksheet, schedule, measurement method, supporting documentation, and technical acceptance.

Engineering documentation as a condition for measurement and acceptance shows that physical delivery and documentary delivery are often inseparable. Installed equipment without a test report, a network installed without certification, or a system delivered without As-Built documentation may not represent full completion of the contractual obligation.

Vague criteria create pressure at the time of measurement. The contractor understands that it has executed the work; inspection considers that evidence is missing; the manager needs to decide payment without a sufficiently clear rule. The better solution is to anticipate this discussion during planning and associate each measurable installment with objective evidence.

In lump-sum contracts, the structure of stages in the physical-financial schedule becomes particularly relevant. Measurement should represent actual progress and avoid advance payments incompatible with execution.

Amendments are consequences to be controlled, not the normal method for completing scope

Contract changes may be legitimate and necessary, but control seeks to distinguish a justified change from late correction of a deficiency that should have been resolved during planning.

A Contract Amendment in Construction and Engineering Services involves analysis of cause, need, limits, price, schedule impact, and preservation of economic conditions.

When new services arise, negotiating a value is not enough. It is necessary to structure a reference price, verify proportionality, and prevent changes from destroying the advantage obtained in the bidding process. When reductions and additions occur, the combined effect on the overall discount needs to be analyzed.

The article on price diving and bid-sheet manipulation shows why unbalanced unit prices can become critical precisely when the contract is changed.

The technical analysis of the change should answer at least: was the event foreseeable; did it result from a design error; who assumed the risk; was the service implicitly included; is a revised design required; how was the new quantity calculated; what reference supports the price; and what impact occurs on the schedule and the economic-financial equation.

Economic-financial rebalancing requires causation, not merely a cost increase

The economic-financial balance protects the relationship initially agreed between obligations and remuneration. However, an isolated price variation does not automatically demonstrate a right to restoration.

The analysis needs to identify the event, contractual classification, unpredictability or risk allocation, causal nexus, actual impact, and quantification methodology. The article on Economic-Financial Rebalancing in Engineering Contracts details this evidentiary construction.

This is another point where the quality of contemporaneous records is decisive. Without a baseline for schedule, prices, productivity, site conditions, and administrative decisions, it becomes difficult to separate an extraordinary impact from the contractor’s normal operational performance.

Provisional and final acceptance should not function as automatic sign-off

Acceptance is the moment when the Public Administration verifies whether the scope was delivered under the contracted conditions. This involves inspection, testing, documentation, punch-list items, warranties, manuals, final drawings, and other specified requirements.

The TCU Manual integrates inspection and acceptance within contract management. In engineering, the correct approach is to prepare acceptance from the planning stage. Acceptance criteria should appear in the Terms of Reference, design, specifications, and test plan rather than being invented at the end of construction.

Technical Acceptance of Construction and Engineering Services organizes inspection, documentation, outstanding items, and acceptance as a verifiable process. For complex systems, commissioning and functional testing may constitute essential evidence that the required performance has been achieved.

Accepting without complete documentation transfers risk to operations. Rejecting without a previously contracted criterion creates another problem. Robust control depends on objective requirements defined in advance.

What the TCU Manual’s risk tables teach

One of the most useful contributions of the 5th edition is the systematization of risks throughout the processes. The logic used describes cause, risk event, and consequence. This form of writing helps avoid generic matrices.

Consider the difference between two formulations:

Weak formulation	Control-oriented formulation
“Risk of poor design”	Absence of an existing-conditions survey may lead to design incompatible with actual conditions, resulting in scope changes, delay, and additional cost
“Risk of delay”	A permit not obtained before mobilization may prevent a work front from starting, causing idle resources, schedule extension, and a claim
“Risk of overpricing”	Price research without comparability and equivalent scale may overstate unit cost, increasing the reference estimate and reducing the ability to identify excessive proposals

The second form already points to possible controls. In the first case, survey and design review. In the second, a readiness gate before mobilization. In the third, price-research and validation methodology.

This is the most productive way to use the TCU’s 113 risk tables: not as a list of threats, but as a catalog of failures that can be converted into process requirements, documents, and checks.

The documentation supporting each procurement phase

Control becomes more objective when each decision has a minimum set of evidence. The table below summarizes one possible architecture for construction and engineering services.

Phase	Main decision	Typical technical evidence
Governance	prioritize and prepare the procurement	Annual Procurement Plan, planning, team capacity, guidelines, responsibility matrix
Need	demonstrate the problem to be solved	DFD, operational data, diagnosis, records of existing conditions
ETP	select the appropriate solution	alternatives, market survey, estimates, risk analysis, intended outcomes
Design	technically characterize the scope	surveys, geotechnical investigations, technical memoranda, drawings, calculations, specifications, coordination
Estimate	estimate the reference value	quantities, cost compositions, research, SINAPI/SICRO, BDI, charges, ABC Curve, base date
Tender	establish bidding rules	evaluation criteria, qualification, acceptability, guarantees, attachments, and draft contract
Contract	form the execution baseline	proposal, contract worksheet, schedule, risk matrix, obligations, and document hierarchy
Execution	verify compliance	site diary, inspections, tests, NCRs, photos, approvals, reports, field records
Measurement	recognize progress and amount due	measured quantities, phase acceptance, required documentation, measurement memorandum
Change	justify modification	cause, revised design, quantities, reference price, schedule and risk impact
Acceptance	verify full delivery	tests, commissioning, As-Built, Data Book, manuals, warranties, punch list, and acceptance record

This table is not a universal checklist. The depth of each item of evidence should be proportional to the scope. It nevertheless demonstrates a constant principle: relevant engineering decisions need to be reconstructable from the official records.

What evidence-based inspection means in practice

Imagine that, two years after a project is completed, an oversight body asks why a material different from the original design was accepted. An answer based on team memory is weak. An answer based on an RFI, technical opinion, formal approval, comparative specification, supply record, and performance test is auditable.

The same applies to quantities. If piping increased by 400 meters, the measurement needs to be connected to a revised drawing or field survey. If unusually low productivity was used for a new price, there should be a basis for it. If the Public Administration extended the schedule, the chronology of the event and responsibility need to be documented.

Engineering Contract Management: from baseline to technical acceptance shows how baseline, changes, measurement, and acceptance form a single information system.

How to reduce the gap between control and engineering

One of the greatest problems in complex procurement is fragmentation. The requesting area describes the need, engineering produces the design, estimating builds the cost worksheet, procurement prepares the tender, the committee conducts selection, and inspection receives the contract. If each stage works in isolation, inconsistencies are passed forward.

The solution is to create maturity gates between phases. Before publishing the tender, for example, a formal review may verify:

• alignment among the need, ETP, and selected solution;
• consistency among Terms of Reference, design, and estimate;
• completeness of surveys and required permits;
• traceability of quantities;
• compatibility between physical and financial schedules;
• measurement and acceptance criteria;
• risks, responsibilities, and allocation matrix;
• qualification and evaluation requirements;
• readiness of the team that will receive and inspect the contract.

This gate does not replace legal responsibilities. It creates a technical barrier to prevent known open items from being pushed into execution.

How to procure technical support without transferring administrative decision-making

The Public Administration may hire specialized support to produce studies, designs, reviews, estimates, analyses, and inspection support. Technical support should increase decision-making capacity and quality while keeping decision authority with the responsible public agents.

A well-structured support scope needs to define deliverables. Generic expressions such as “assist inspection” make the service difficult to measure. It is more precise to procure activities such as design review, submittal analysis, measurement verification, inspections, opinions on changes, schedule analysis, NCR management, review of final documentation, and acceptance support.

Authority and interfaces also need to be defined. The consultant recommends; the competent authority decides. The executing contractor remains responsible for the scope; technical support does not assume its obligations. Inspection uses the technical products to perform its duties with greater confidence.

Measurement criteria for the support service itself should be associated with verifiable products or capabilities, avoiding a contract whose remuneration depends only on the presence of personnel without a clear relationship to results.

Further reading in the TCU 2026 cluster

The framework above organizes the complete cycle. The content below explores topics that gained relevance with the TCU’s 2026 Guide to Cost Engineering in Public Works and with more recent case law, without replacing consultation of primary sources.

Planning, maturity, and procurement structuring

• Capital Projects in Public Works: how to structure public investments from need to operations
• Poorly prepared ETP in public works: how planning failure propagates to project stoppage
• From ETP to Technical Acceptance: the complete engineering lifecycle of a public investment
• Planning the Procurement of Construction and Engineering Services: how to structure before bidding
• iPMP: how to assess project maturity before procurement
• Best-efforts and result obligations in engineering: how to structure the Technical Document
• Event Schedule in Public Works: 10 precautions when defining payment stages

Cost engineering, price, risk, and estimating

• Public Works Estimating: how to structure quantities, costs, BDI, and risks
• Risk Management in Public Works: integrating planning, contract, and execution
• Geological Risk in Construction: GBR, geotechnical risk, and risk matrix
• Tax Reform in Construction: IBS, CBS, and impacts on construction BDI
• Engineering Consulting Fees: how to use DNIT, RAIS, and CBO in estimating
• SINAPI and SICRO Prices: 5 effects that may distort market value
• AI in Construction: 8 precautions in base estimating for construction
• Gross Error in Construction Estimating: when it creates liability and when it can be corrected
• Public Works Insurance: engineering risk, insurability, and BDI
• Risk Allowance in Construction: how to measure, pay, and address it in amendments
• Split Payment under Tax Reform: impacts on public works, measurements, and BDI
• Price Acceptability Criteria in Public Works: unit price, total price, and TCU Precedent 259

Execution, inspection, measurement, and contract governance

• Public Works Inspection: how to control quality, progress, measurements, and evidence
• Engineering Contract Inspection: how to control obligations, changes, payments, and acceptance
• Construction Supervision: 25% limit, extension, and remuneration under Law 14,133
• Excessive Burden in Construction: defining the rebalancing trigger in the tender
• Variable Remuneration under Law 14,133: 7 precautions for construction and engineering services
• Schedule Manipulation in Public Works: how to identify, prevent, and control it according to the TCU

Final considerations

The TCU Manual on Public Procurement & Contracts offers an end-to-end view of public procurement. For construction and engineering services, its usefulness lies less in memorizing hundreds of pages and more in transforming its concepts of governance, risks, case law, and controls into operational questions applied to the project.

A technically robust procurement leaves a chain of evidence from the need through acceptance. The ETP explains the solution; the design characterizes the scope; the estimate translates the design into value; the tender turns decisions into rules; the contract establishes the baseline and responsibilities; inspection records execution; measurement recognizes only demonstrated progress; changes are substantiated; and acceptance confirms performance and documentation.

This chain reduces the room for improvised decisions. When an audit occurs, the Public Administration does not need to reconstruct afterward the reasoning that should have existed beforehand. The documents and records themselves demonstrate why each decision was made, which risks were considered, and which controls were performed.

When these control points need to be organized as a continuous journey — from initial maturity through acceptance — the Engineering for Public Investments solution integrates planning, design, procurement, inspection, Assurance, and acceptance within a single line of technical governance.

Technical references

[1] 1. BRASIL. Tribunal de Contas da União. Licitações & Contratos: Orientações e Jurisprudência do TCU. 5th ed. Brasília: TCU, 2025. Available at: https://licitacoesecontratos.tcu.gov.br/

[2] 2. BRASIL. Tribunal de Contas da União. Portaria-TCU nº 202, de 19 de setembro de 2023. Approves the 5th edition of the Manual de Licitações & Contratos and governs its updating. Available at: https://pesquisa.apps.tcu.gov.br/documento/portaria/*/NUMPORTARIA%253A202%2520ANO%253A2023/

[3] 3. BRASIL. Presidência da República. Lei nº 14.133, de 1º de abril de 2021. Lei de Licitações e Contratos Administrativos. Available at: https://www.planalto.gov.br/ccivil_03/_ato2019-2022/2021/lei/l14133.htm

[4] 4. BRASIL. Tribunal de Contas da União. Orientações para elaboração de planilhas orçamentárias de obras públicas. Brasília: TCU, 2014. Available at: https://portal.tcu.gov.br/biblioteca-digital/orientacoes-para-elaboracao-de-planilhas-orcamentarias-de-obras-publicas.htm

[5] 5. BRASIL. Presidência da República. Decreto nº 7.983, de 8 de abril de 2013. Estabelece regras e critérios para elaboração do orçamento de referência de obras e serviços de engenharia. Available at: https://www.planalto.gov.br/ccivil_03/_ato2011-2014/2013/decreto/d7983.htm

Frequently asked questions

Is the TCU Manual on Public Procurement and Contracts a law?

No. The Manual is an institutional document with a preventive and educational purpose that systematizes legislation, regulation, case law, risks, controls, and models. Concrete decisions must observe current rules and the context applicable to the procurement.

Does the TCU review only the bidding phase?

No. The Manual’s approach covers governance, planning, supplier selection, contract formalization, execution, inspection, payment, changes, economic-financial balance, acceptance, and contract termination.

Does having an ETP, Terms of Reference, and Basic Design guarantee adequate planning?

No. Formal existence of the documents is insufficient when they are incomplete or inconsistent. Control needs to verify information quality, decision traceability, and compatibility among the need, requirements, design, estimate, risks, and execution criteria.

What is engineering’s main role under the TCU control benchmark?

To transform requirements and decisions into verifiable technical evidence: surveys, studies, designs, technical memoranda, quantities, estimates, measurement criteria, inspections, tests, execution records, and acceptance documentation.

Can inspection correct planning failures during construction?

Some situations require adjustments during execution, but inspection should not be used as a substitute for adequate planning. Deficiencies in design, scope, and estimating tend to create greater risk of amendments, delays, disputes, and loss of value for money.

How should the risks presented in the TCU Manual be used?

Risks should be converted into proportionate controls. Cause and consequence help identify which study, requirement, approval, check, or evidence needs to exist to reduce the probability or impact of the event.

Can state and municipal agencies use the TCU Manual?

The Manual itself states that it is primarily directed at federal public organizations, but managers from other levels of government may use its guidance where applicable, while observing their own legislation and regulations.

Complementary technical materials

Related solutions

• Project, Program, and Portfolio Governance
• Process, Workflow, and Technical Approval Management
• Contract, Scope, and Deliverables Management
• Document Governance and Document Management System

Related services

• Preliminary Technical Study for Construction and Engineering Services
• Technical Review of Terms of Reference for Construction and Engineering Services
• Engineering Risk Management
• Technical Support for Inspection of Construction and Engineering Contracts
• Technical Support for Clarifications, Challenges, and Appeals in Engineering Procurement

Main content on the topic

• Complete Guide to Procurement and Contracts for Construction and Engineering Services
• Annual Procurement Plan in Engineering
• Risk Allocation Matrix in Engineering Contracts
• How to inspect a public works project

Related technical content

• Evidence-based inspection in public works
• Economic-Financial Rebalancing in Engineering Contracts
• Contract Amendments in Construction and Engineering Services
• Stalled Public Works: manager’s guide
• Complete Guide to Cost Engineering and Estimating