How to Inspect a Public Works Project: Method, Responsibilities and Evidence under Law 14,133

Complete method for public-works inspection under Law 14,133: responsibilities, inspections, RDO, measurements, evidence, nonconformities and acceptance.

Check it out!

Inspecting a public works project does not mean merely visiting the construction site, checking visible services and signing measurement certificates. Contract inspection is a technical, documentary and decision-making process that must verify whether the scope is being executed in accordance with the design, contract, specifications, standards, schedule, budget and acceptance criteria. Under Law 14,133/2021, execution must be monitored and inspected by one or more specially appointed contract inspectors, with occurrences recorded and necessary measures taken in a timely manner.

In construction, effective inspection must turn physical execution into verifiable evidence. This requires a clear contractual baseline, an inspection routine, quality control, traceability of materials and services, verification of quantities, schedule monitoring, recording of deviations, treatment of nonconformities and sufficient documentation to support measurements, payments, deductions, amendments, acceptance and potential accountability.

The safest method is to structure inspection as a system: define in advance what will be controlled, which evidence proves each requirement, who verifies it, at what frequency, what tolerance is accepted and what happens when there is a deviation. Inspection quality depends less on the number of visits and more on the ability to produce a coherent chain of evidence linking design, execution, measurement and administrative decision.

What Law 14,133 requires from public-works inspection

Art. 117 of Law 14,133 establishes that contract execution must be monitored and inspected by one or more contract inspectors, representatives of the Administration who are specially appointed. The same provision requires the inspector to record occurrences related to execution, determine what is necessary to correct faults or defects and promptly inform superiors of situations requiring decisions beyond the inspector’s authority.

This structure creates three practical obligations for public-works inspection.

First, monitor. The inspector needs to know what is being executed and compare actual progress with contractual obligations. Inspection cannot begin only when a problem occurs or when a measurement request arrives.

Second, record. The inspector’s knowledge must be converted into traceable documentation. An irregularity observed but not recorded tends to become, weeks later, a dispute based on memory or interpretation.

Third, act or escalate. When correction falls within the inspector’s authority, there should be an objective instruction and deadline. When the situation requires a contractual, financial, legal or administrative decision, the inspector must produce sufficiently structured information for the contract manager or competent authority to decide.

In practice, these three verbs — monitor, record and act — form the core of inspection.

Public-works inspection begins before the first site visit

A recurring mistake is to imagine that inspection begins when the contractor mobilizes. In reality, the work starts earlier, with preparation of the baseline that will be used throughout execution.

Before the notice to proceed, the inspection team should know and organize, at a minimum:

• contract and appendices;
• applicable basic and detailed design;
• descriptive memoranda and technical specifications;
• contractual cost spreadsheet;
• physical-financial schedule;
• risk matrix, where applicable;
• contractor proposal and documents that conditioned the award;
• quality and performance requirements;
• measurement and payment criteria;
• provisional and final acceptance criteria;
• documentation, testing, commissioning and as-built obligations;
• required permits, authorizations and professional responsibilities.

Without this preparation, the inspector arrives in the field with fragmented information and begins inspecting by perception. The comparison stops being between executed vs. contracted and becomes executed vs. the inspector’s personal expectation.

Build an inspection matrix before execution

An inspection matrix is a simple way to turn the contract into verifiable controls. It can be organized by work package, discipline, system or measurement item.

Element	Control question	Expected evidence	Responsible party	Frequency
Design	Does execution match the current revision?	Approved drawing + inspection	Technical inspector	By work front
Material	Does the material meet the specification?	Invoice, certificate, datasheet, inspection	Technical inspector	By batch
Service	Does the executed method comply with the procedure?	Checklist + photos + test	Technical inspector	By stage
Quantity	Was the measured quantity actually executed?	Field survey + measurement calculation	Technical inspector	By measurement
Schedule	Is progress tracking the baseline?	Updated schedule + physical evidence	Manager/inspector	Weekly/monthly
Quality	Are there open nonconformities?	NCR + action plan	Technical inspector	Continuous
Documentation	Are records complete?	RDO, minutes, reports, tests	Inspector/manager	Continuous

The matrix reduces two weaknesses: omission of important controls and variation in criteria among different inspectors or different periods of the project.

Differentiate technical inspection, contract management and specialized support

The technical inspector monitors execution of the scope and verifies whether quantity, quality, timing and method of execution comply with the contract. The contract manager coordinates inspection activities and conducts or prepares broader administrative decisions such as changes, economic-financial rebalancing, payments, sanctions and closeout.

This distinction is particularly important in complex projects. An engineer inspecting an electrical installation, for example, may identify a technical nonconformity, record the occurrence, indicate the violated clause or requirement and request correction. But a scope change with financial impact should not be handled informally on site as though it were merely technical guidance.

Law 14,133 also allows third parties to be hired to assist and support inspectors with technical information. This support may include consulting engineering, supervision, testing, surveys, document analysis, measurement verification and specialized assistance. The inspector’s own decision-making responsibility, however, is not transferred to the consultant.

Establish an inspection routine proportional to risk

Not every service requires the same intensity of control. An efficient method directs attention to points of greater technical, financial, operational or irreversibility criticality.

Inspection frequency should consider:

• criticality of the system or element;
• ease or difficulty of later inspection;
• economic value of the item;
• impact of failure on safety or performance;
• contractor track record;
• speed of execution;
• dependency among stages;
• risk of the service becoming concealed after closure or finishing;
• need for testing or witnessing before work continues.

Services that will be concealed, such as grounding systems, embedded piping, waterproofing, reinforcement, dry infrastructure and certain foundation elements, require controls before closure. If inspection misses the inspection window, later verification may require indirect tests, openings, rework or, in some cases, become practically impossible.

Use inspection, witness and release points

In projects with stricter quality requirements, it is useful to structure controls similar to Inspection and Test Plans — ITPs. Even if the contract does not use this terminology, the principle applies.

The main points are:

• inspection point: the moment when the service is checked against defined criteria;
• witness point: a stage at which the inspection team must be notified so it may, if desired, witness a test or relevant activity;
• hold point: execution cannot proceed without formal release of the previous stage;
• documentation point: continuation depends on submission or validation of a document, certificate, test or approval.

This model prevents inspection from operating only after the fact. The objective is to insert controls at moments when the process can still be corrected at low cost.

The RDO should record facts, not generic narratives

The Daily Work Report or Construction Daily Report — RDO in Brazilian practice — is one of the main sources of execution traceability. It should record facts that allow reconstruction of what occurred on site.

A technically useful RDO normally includes:

• date and relevant weather conditions;
• mobilized teams and resources;
• active work fronts;
• services executed and location;
• equipment used;
• materials received;
• inspections and tests performed;
• occurrences affecting productivity or sequence;
• stoppages and their causes;
• formal instructions from the inspection team;
• nonconformities;
• interferences and constraints;
• photographic records with context.

Expressions such as “work proceeding normally” or “services according to schedule” have little evidentiary value. The record should make it possible to identify what, where, when, by whom and under what condition a particular service was executed.

A photograph becomes evidence only when it has context

A folder containing thousands of photos is not necessarily a good inspection system. A photograph must be related to a requirement, location, date, work front or occurrence.

A robust photographic record uses, as applicable:

• identification of the area or room;
• reliable date and time;
• reference to the service item or system;
• before, during and after sequence;
• scale or an element that allows dimensions to be interpreted;
• objective caption;
• link to RDO, checklist, measurement or nonconformity.

When the image is used to prove quantity, the methodology must allow auditing. Photographing a stack of materials, for example, does not automatically prove that the quantity was incorporated into the project.

Inspect materials before they are incorporated into the work

Material control should not occur only at measurement. Depending on criticality, inspection must verify specification, origin, batch, certificates, datasheets, storage conditions and compatibility with the design.

For equipment and systems, it may be necessary to verify model, manufacturer, version, capacity, interfaces, accessories and conformity documents. In multidisciplinary projects, an apparently equivalent substitution may change infrastructure, integration, maintenance or performance requirements.

Acceptance of material in the field should not be confused with final acceptance of the system. A piece of equipment may be individually compliant and still be incompatible with the solution architecture or other subsystems.

Quality control must produce verifiable evidence

Inspection does not replace the contractor’s quality control. The contractor remains responsible for correct execution, inspecting its own work, performing required tests and correcting defects. Inspection verifies whether this system is functioning and whether results meet contractual criteria.

Depending on the scope, evidence may include:

• material certificates;
• laboratory tests;
• field tests;
• test reports;
• inspection checklists;
• calibration records;
• certificates for measuring equipment;
• commissioning reports;
• stage release records;
• nonconformity and closure records.

The principle is simple: if a requirement is relevant to acceptance, there should be proportional evidence that it was verified.

How to handle nonconformities without turning everything into a contract dispute

A nonconformity is the objective difference between what was executed and the applicable requirement. The record should separate fact, requirement, impact and required action.

A good record contains:

1. identification of the occurrence;
2. location and date;
3. applicable contractual or technical requirement;
4. objective description of the observed condition;
5. associated evidence;
6. deadline for response or correction;
7. contractor’s proposed disposition, where applicable;
8. validation of the correction by inspection;
9. closure date.

The inspector should avoid informal instructions that alter solution, quantity or scope without analysis of the effects. Correcting a defect covered by the contract is different from changing the contracted scope.

Measurement must arise from evidence of execution

Measurement is not a simple transcription of the percentage reported by the contractor. The measurement certificate must reflect quantities actually executed and accepted in accordance with the criteria defined in the contract.

For each measured item, inspection should be able to answer:

• where the service was executed;
• what quantity was completed;
• how the quantity was determined;
• which document proves execution;
• whether there are quality punch items;
• whether the measurement is consistent with the schedule and physical progress;
• whether materials or equipment were accepted under the contractual rules;
• whether there were justified deductions or retentions.

The measurement calculation should be sufficiently clear for later review by another professional, auditor or oversight body.

Physical and financial progress must be consistent

A contract may be financially advanced and physically delayed. This occurs, for example, when high-value items are measured early while critical execution activities remain behind schedule.

Inspection should simultaneously monitor:

• planned physical progress;
• actual physical progress;
• planned financial progress;
• actual financial progress;
• critical path;
• contract milestones;
• active constraints;
• forecast completion.

The analysis should not be limited to the overall percentage. A project with 70% overall progress may be in a critical situation if the remaining 30% is concentrated in integration, testing, energization, licensing or commissioning activities.

Record causes of delay before they become claims

Delays are among the main points of conflict in engineering contracts. Inspection should record facts and causality from the outset, without waiting for a rebalancing or extension request.

For each relevant event, record:

• start and end date;
• affected activity;
• responsible party or origin of the event;
• observed impact;
• mitigation measures adopted;
• related documents;
• relationship with the critical path;
• any subsequent recovery.

This history makes it possible to distinguish contractor delay, Administration-caused impediment, third-party event, unforeseeable condition and simple productivity variation with no impact on final completion.

Design changes cannot circulate only through site conversations

Technical changes are part of the reality of many projects, but they must be governed. A verbal instruction may solve an immediate issue and create a contractual problem months later.

Every relevant change should go through a process that identifies:

• need;
• origin;
• proposed solution;
• technical impact;
• cost impact;
• schedule impact;
• impact on interfaces;
• contractual responsibility;
• competent approval;
• corresponding document revision.

The technical inspector can provide inputs for the decision, but should not turn the construction site into an informal forum for contract changes.

Construction meetings must generate traceable decisions

Periodic meetings are useful when they organize information and remove blockers. Good construction-meeting minutes record decision, responsible party and deadline, not merely the sequence of what each participant said.

The agenda may track:

• safety and field conditions;
• physical progress;
• critical path;
• constraints;
• engineering and design revisions;
• critical procurement;
• nonconformities;
• measurements;
• changes and claims;
• testing and commissioning;
• final documentation;
• pending decisions.

Meeting minutes should not replace formal notices required by the contract, but they serve as an important element of governance and operational memory.

When the inspector should escalate an occurrence to the contract manager

Not every occurrence needs to be escalated. Escalation is necessary when the solution exceeds the inspector’s technical or operational authority.

Typical examples include:

• significant financial impact;
• request for economic-financial rebalancing;
• scope change;
• need for a contract amendment;
• risk of stoppage;
• serious default;
• possibility of sanction;
• conflict over contract interpretation;
• need for an extension;
• event that significantly affects schedule or contract outcome.

Escalation should be accompanied by organized information. The contract manager needs to receive the fact, documentary basis, impact, alternatives and required action — not merely a message that “there is a problem on the project.”

Provisional acceptance is not a formality

The acceptance stage should verify whether the scope is actually in a condition to be accepted. Law 14,133 distinguishes provisional and final acceptance, and federal regulation assigns the technical inspector a relevant role in provisional acceptance and the contract manager in final acceptance.

In public works, provisional acceptance may involve:

• final inspection of services;
• verification of punch items;
• punch list;
• functional testing;
• commissioning;
• verification of as-built documents;
• manuals and data books;
• ARTs/RRTs and professional responsibility documents;
• training;
• certificates and warranties;
• operation and maintenance documentation;
• validation of nonconformity corrections.

A project that is physically “finished” may not be contractually ready for acceptance.

What should exist in the inspection dossier

At the end, the inspection process must allow a third party to understand what happened during execution and why each decision was made.

A robust dossier may contain:

• appointments and responsibilities;
• reference contract documents;
• inspection matrix;
• RDOs;
• inspection reports;
• meeting minutes;
• formal correspondence;
• nonconformity records;
• tests and inspections;
• photographic records;
• measurements and calculations;
• schedules and updates;
• change records;
• decisions and approvals;
• acceptance documents;
• final documentation and as-built records.

This set is the technical memory of execution. Without it, even technically correct inspection may be difficult to demonstrate years later.

Sampling in inspection: when it works and when it does not

Inspection does not need to physically verify every unit of every service, but sampling must be technically defensible. It works best when the process is repetitive, contractor quality is stable, lots are homogeneous and a reliable self-control system exists.

Inspection intensity should increase when:

• repeated nonconformities arise;
• there is a change of team or supplier;
• the service is irreversible or will become concealed;
• the consequence of failure is high;
• contractor records have low reliability;
• the process is out of control;
• the item has high financial impact.

Sampling should not be used as a generic justification for lack of inspection of critical items.

Indicators for monitoring inspection quality

The inspection process itself can be monitored. Some useful indicators are:

Indicator	What it reveals
Open vs. closed NCRs	speed of deviation treatment
Average NCR closure time	correction efficiency
Percentage of measurements with reservations	quality of execution and documentation
Physical schedule variance	delay trend
Documentary punch items by period	document-management maturity
Recurrence of nonconformities	effectiveness of corrective actions
Critical items without evidence	control exposure
Decision response time	governance capacity

The objective is not to turn inspection into KPI bureaucracy, but to identify early deterioration in execution or in the control process itself.

Errors that weaken public-works inspection

The most recurring problems are not only technical. Many result from process failures.

• inspecting without knowing the current design revision;
• accepting generic records without location;
• measuring by estimated percentage without a verifiable calculation;
• treating scope changes as field instructions;
• failing to record the cause of delay when the event occurs;
• accumulating nonconformities without deadlines and responsible parties;
• leaving tests and documentation until the end of the project;
• confusing outsourced technical support with transfer of the inspector’s role;
• granting final acceptance without consolidating punch items and evidence;
• producing extensive reports without linkage to contractual requirements.

Practical example: inspection of a technical installation

Consider a public project that includes electrical infrastructure, data networks and security systems. The design defines routes, equipment, installation standards, tests and final documentation.

An inspection based only on visual visits may conclude that “the equipment has been installed.” A structured method verifies a much larger chain: design revision used, installed models, physical identification, electrical power, network infrastructure, configuration, integration, testing, capacity, redundancy, documentation, training and acceptance.

If the measurement provides for payment after “installation completed,” the criterion must be interpreted according to the contract. Physically installing equipment without configuration, integration or testing may not represent completion of the item. This difference needs to be defined before reaching the measurement stage.

Final considerations

Inspecting a public works project means building a chain of trust between contractual obligation, physical execution and administrative decision. The inspector needs to stay close to the field, but also close to the contract, design, schedule and documentation.

The best inspection is not the one that produces the most paperwork or interferes most in execution. It is the one that can detect deviations early, record facts objectively, require corrections within the proper authority, support measurements and payments with evidence and preserve the traceability required for future decisions.

When the project is complex, multidisciplinary or includes critical systems, the Administration can structure specialized technical support to increase inspection, document-analysis, measurement, testing and evidence-management capacity. This support strengthens the inspector but does not replace the inspector’s statutory role.

Inspection should be designed from the preparatory phase. The Terms of Reference or Basic Design must state how the scope will be monitored, measured, tested and accepted. The clearer these mechanisms are before contracting, the less likely inspection will need to improvise criteria during execution.

Technical references

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

[2] BRAZIL. Decree No. 11,246, of October 27, 2022. Regulates the activities of contract managers and inspectors at the federal level. 2022. Available at: https://www.planalto.gov.br/ccivil_03/_ato2019-2022/2022/decreto/d11246.htm.

[3] FEDERAL COURT OF ACCOUNTS — TCU. Procurement and Contracts: TCU Guidance and Case Law. 5th ed. 2025. Available at: https://licitacoesecontratos.tcu.gov.br/6-gestao-de-contrato/.

[4] FEDERAL COURT OF ACCOUNTS — TCU. Public Works in 10 Steps. 2nd ed. 2025. Available at: https://portal.tcu.gov.br/publicacoes-institucionais/cartilha%2C%20manual%20ou%20tutorial/obras-publicas-em-10-passos.

[5] FEDERAL COURT OF ACCOUNTS — TCU. Public works: basic recommendations for contracting and inspection of public building works. Available at: https://portal.tcu.gov.br/publicacoes-institucionais/cartilha-manual-ou-tutorial/obras-publicas-recomendacoes-basicas-para-a-contratacao-e-fiscalizacao-de-obras-de-edificacoes-publicas.

Frequently asked questions

Who is responsible for inspecting a public works project under Law 14,133?

Execution must be monitored and inspected by one or more contract inspectors specially appointed by the Administration. The inspector records occurrences, determines corrections within the inspector’s authority and informs the contract manager or superior of situations requiring decisions beyond that authority.

Does the inspector need to be on site every day?

The Law does not establish daily presence as a general rule. Frequency should be compatible with complexity, risk, speed of execution and critical points of the scope. Services that will be concealed, irreversible stages and relevant tests require specific inspection planning.

Can the Administration hire a company to support inspection?

Yes. Law 14,133 allows third parties to be hired to assist and support inspectors with relevant information. The third party cannot exercise duties that are the inspector’s own exclusive responsibility, and the engagement does not eliminate the inspector’s responsibility within statutory limits.

What should a public-works inspection report contain?

The report should record the inspected object, location, period, reference requirement, observed condition, evidence, deviations, required actions, deadlines, responsible parties and closure status. It should allow the occurrence to be technically reconstructed.

Does the RDO replace the inspection report?

Not necessarily. The RDO records the project’s routine and daily occurrences. Inspection may require specific reports for inspection, measurement, quality, nonconformity, testing and schedule monitoring according to contract complexity.

How should the inspector validate a construction measurement?

Measurement should be based on quantities actually executed and accepted, with calculations and sufficient evidence to link each item to physical execution. Services with quality punch items or that do not meet contractual criteria should not automatically be treated as complete.

Complementary technical materials

Related services

• Technical Support for Public-Works and Engineering-Contract Inspection
• Owner’s Engineering
• Engineering Project Management
• Technical Acceptance of Public Works and Engineering Services

Main content on the topic

• Daily Work Report (RDO): how to record execution, inspect contracts and produce technical evidence
• Construction Measurement Certificate: how to measure services, validate evidence and release payments

Related technical content

• Construction management, inspection and Owner’s Engineering: differences and when to hire
• Quality Plan for Engineering Projects and Works
• Complete Guide to Procurement and Contracts for Public Works and Engineering Services
• Owner’s Engineering: executive framework for procurement, governance and acceptance