Final Receipt Certificate: Why Completed Installation Does Not Mean Accepted Delivery

Learn how to structure a final receipt certificate under Brazilian Law 14,133, distinguishing installation, delivery, provisional receipt, commissioning, acceptance, and contract closeout.

Check it out!

The final receipt certificate should not be treated as a simple administrative closeout document. In engineering works, services, and systems, it formalizes that the object has been verified against contractual requirements and that sufficient evidence exists to support the decision to receive it. An installation that is physically complete, energized, or apparently operating may still not have been technically delivered or be ready for acceptance.

This distinction is especially important when the contractor concentrates its planning on installation and leaves documentation, testing, As-Built drawings, photographic records, corrections, and the formal receipt request for the final days of the contract. If a contract lasts 90 days, this does not mean the company has 90 days to install. The period must accommodate physical completion, documentary delivery, the formal receipt request, verification by the client, commissioning, issuance of outstanding items, corrections, and the technical decision that precedes final receipt.

In practice, substantial completion is not final receipt. The object may be almost entirely installed and still lack the technical and documentary basis for the client to state that the requirements have been met. The difference between “we finished the installation” and “the object was accepted” is exactly the space in which inspection, Owner’s Engineering, QA/QC, document management, and commissioning protect the client’s interests.

What is a final receipt certificate under Brazilian Law 14,133?

Article 140 of Brazilian Law No. 14,133/2021 establishes two distinct stages for works and services. Provisional receipt is carried out by the person responsible for monitoring and inspection, through a detailed certificate, when compliance with technical requirements has been verified. Final receipt is carried out by a public employee or commission appointed by the competent authority, also through a detailed certificate demonstrating compliance with contractual requirements.

The Law itself allows the object to be rejected, in whole or in part, when it does not comply with the contract. It also requires the deadlines and methods for provisional and final receipt to be defined in regulation or in the contract. This means that closeout does not begin on the last day of execution: it must have been designed from the procurement stage onward.

To deepen the conceptual distinction among physical completion, technical delivery, and acceptance, see Installed System Is Not a Delivered System. Here, the focus is different: how to organize the contractual and technical process that leads to final receipt.

Milestone	What it represents	What may still be missing
Physical completion	Installation or material execution completed	Documentation, tests, corrections, and validation
Technical delivery	Technical package formally submitted for analysis	Verification, commissioning, and closure of outstanding items
Provisional receipt	Object submitted and verified under the defined terms	Corrections, final analysis, and full demonstration of compliance
Technical acceptance	Conformity opinion based on requirements and evidence	Administrative formalization when applicable
Final receipt	Detailed certificate demonstrates contractual compliance	Legal and warranty responsibilities remain
Contract closeout	Administrative, documentary, and financial closure	Management of warranties and post-delivery responsibilities

The contractual period is not an installation-only period

One of the most recurrent errors in engineering contract execution is interpreting the total term as time available exclusively to produce or install. This interpretation shifts all verification to the end and creates a predictable problem: the client receives the acceptance request when there is no longer enough time to test, identify failures, and require corrections within the planned operating term.

A 90-day contract, for example, needs to reserve windows for activities that are not “installation” but are part of the obligation to deliver the object properly. The actual distribution depends on the contract, regulation, complexity, and defined receipt methods, but the planning logic must be explicit.

If the contractor uses practically the entire term for installation, any nonconformity identified by the client tends to fall within a critical window. This can generate extension requests, disputes over responsibility for delay, pressure to receive with incomplete documentation, or attempts to treat relevant outstanding items as mere later adjustments.

Technical procurement planning must therefore define when the contractor needs to be ready to deliver, not merely the final contract date. The schedule needs milestones for documentation, testing, delivery for inspection, analysis time, corrections, and reverification.

Substantial completion is not final receipt

Some project environments use the concept of substantial completion to indicate that a large portion of the object has been executed and outstanding items remain. This concept may be useful for management or contractual purposes when expressly defined, but it should not be confused with final receipt under Brazilian Law 14,133 or with full technical acceptance.

An implementation may be 95% complete and the remaining 5% may be exactly what prevents safe use, traceability, warranty, or proof of performance. Physical percentage does not automatically reflect technical criticality.

In an electronic security system, for example, IP cameras, access-control controllers, switches, racks, and operator workstations may be installed, while the following are still missing:

• coverage and image-quality testing;
• recording and retention validation;
• verification of integration among CCTV, access control, and the VMS;
• configuration and parameterization evidence;
• physical and logical identification of assets;
• network and PoE power test records;
• configuration backups;
• software licenses and keys;
• serial-number register;
• As-Built documentation consistent with execution;
• organized and traceable photographic report;
• operation manuals and procedures;
• warranties linked to installed equipment;
• training and qualification records;
• Data Book or final dossier;
• closure of outstanding items identified by inspection.

The system may even “show an image on the screen” and still be technically incomplete. Likewise, a work may appear visually complete and still lack sufficient documentation, tests, or evidence for receipt.

Delivered, received, and accepted are different states

The word “delivery” is often used imprecisely. For the contractor, it may mean that the field team completed the services. For the manager, it may mean that an email with documents was received. For inspection, a safe decision can only be made when there is a verifiable set of requirements and evidence.

A more robust sequence separates the states:

1. Completion of execution: the contractor closes the productive activity specified for the object.
2. Preparation for delivery: it consolidates documents, reports, drawings, tests, warranties, records, and other evidence.
3. Formal receipt request: it communicates that the object is available for verification and submits the contractually defined package.
4. Receipt and verification: inspection, the technical team, the commission, or specialized support performs the required checks.
5. Commissioning and testing: when applicable, performance and integrations are demonstrated.
6. Issuance of outstanding items: deviations are recorded, classified, assigned, and given a correction deadline.
7. Correction and reverification: the contractor demonstrates closure of each outstanding item.
8. Technical opinion: consolidates the condition of the object and supports the acceptance decision.
9. Final receipt certificate: formalizes compliance with contractual requirements.
10. Closeout: consolidates documentation, warranties, responsibilities, payments, and transition to operations.

This architecture avoids a common error: treating the date when the contractor’s team left the site or put away its tools as the date on which the client accepted the object.

What the contractor needs to deliver before requesting receipt

The contract, tender documents, Terms of Reference, Detailed Design, and other procurement documents should define the delivery package. There is no single list applicable to every object, but in engineering the formal receipt request must be accompanied by evidence compatible with the nature of the service.

A consistent package may include:

• letter, transmittal, or formal delivery and receipt request;
• identification of the contract, Service Order, stage, or milestone being delivered;
• technical execution report;
• photographic report identifying locations, assets, dates, and relevant interventions;
• revised As-Built documentation consistent with the condition actually executed;
• lists of installed equipment and materials;
• serial numbers, logical addresses, and asset identification when applicable;
• inspection and test reports;
• FAT, SAT, or other specified test records;
• required certificates and technical reports;
• ART/RRT and other applicable professional-responsibility records;
• software licenses, configuration files, and backups;
• manuals, data sheets, and manufacturer documentation;
• training plan and records;
• warranty terms and activation conditions;
• updated outstanding-items matrix;
• evidence of correction of previous nonconformities;
• Data Book, Quality Dossier, or equivalent documentary package;
• the contractor’s own declaration that the object is ready for the verification provided for in the contract.

The Engineering Data Book should not be seen as a file assembled after execution has ended. It is the result of document management that preserved evidence throughout the contract.

The same applies to the As-Built. Reconstructing it in a rush at the end, without traceability of executed changes, increases the likelihood of delivering drawings that do not represent field conditions.

Low-quality documentation is also a delivery nonconformity

A contractor may have performed good field work and still make a technically weak delivery. This occurs when execution knowledge remains with the installation team and is not converted into documentation that allows the owner to operate, maintain, audit, and modify the asset.

A photographic report, for example, does not gain value merely by containing many images. It must make it possible to trace what was done, where it was done, the resulting condition, and which requirement, asset, circuit, device, or location each record relates to. Loose photographs without captions, identification, or documentary logic create volume but little evidence.

Likewise, an As-Built that merely reproduces the original design while ignoring field changes does not fulfill the function of recording the constructed condition. A test report without identification of the instrument, criterion, sample, result, and responsible person may fail to support an acceptance decision.

In higher-criticality contracts, document review needs to consider not only the existence of the file, but also:

• completeness;
• internal consistency;
• adherence to what was executed;
• traceability;
• correct version and revision;
• identification of the responsible person;
• link to a requirement or acceptance criterion;
• sufficient quality for operation and maintenance;
• ability to support future audits.

The Technical Audit of Data Book and Final Engineering Documentation exists precisely to test this consistency before an incomplete documentary package is treated as a final delivery.

The formal receipt request must occur with sufficient lead time

The formal receipt request is a management milestone. It creates traceability regarding the moment when the contractor states that the object is ready for the verification provided for in the contract.

This request should not arrive after the term has expired or with only a few hours remaining before the final date. The client must have the analysis period provided for in the contract or regulation and operational time compatible with inspections, commissioning, issuance of outstanding items, and possible corrections.

For this reason, the schedule should include a receipt-readiness milestone. From the beginning, the company knows that it needs to complete production before this milestone in order to prepare the documentation and undergo verification.

When this is not provided for, a false equivalence arises:

> “I completed the installation within the deadline; therefore, I delivered within the deadline.”

Technically, this conclusion is insufficient when the scope itself requires documentation, testing, validation, and acceptance. The contractual obligation is not reduced to the physical act of installing.

How provisional receipt should work

Under Article 140, for works and services, provisional receipt is the responsibility of the person in charge of monitoring and inspection, through a detailed certificate, when compliance with technical requirements has been verified.

This reinforces two points. First, provisional receipt should not be automatic. Second, it needs to be detailed, not merely a signature on a generic form.

Depending on the object and contract, the provisional certificate may record:

• precise identification of the object and milestone received;
• documents examined;
• inspections carried out;
• available test results;
• status of the As-Built;
• status of the Data Book;
• open outstanding items;
• blocking and non-blocking nonconformities;
• reservations;
• deadline and person responsible for corrections;
• need for new tests;
• condition for progressing to final receipt.

The article The Contractor Completed the Works. What Now? examines the checks the client can perform before considering the delivery technically mature.

Commissioning cannot be compressed into the last day of the contract

Commissioning is a verification process. In systems, installations, and projects that depend on performance, integration, and functionality, it is one of the main sources of evidence for acceptance.

Brazilian Law 14,133 establishes in Article 140, §4, that unless otherwise provided in the tender documents or in a regulatory act, inspections, tests, and other evidence for assessing proper execution required by official technical standards are borne by the contractor. This reinforces the need to plan testing as part of contractual execution, rather than as an improvised activity after alleged completion.

Owner’s Engineering needs access to a condition ready for testing, adequate documentation, and sufficient time to perform or monitor verifications. In an electronic security system, this may involve tests of recording, coverage, failover, alarms, events, integrations, access control, contingency, network, power supply, and VMS operation. In other disciplines, the tests will differ, but the logic remains.

The Commissioning guide details this transition among construction, testing, and readiness for operation.

Anonymized case: electronic security system substantially installed but not ready for acceptance

Consider an electronic security implementation composed of IP CCTV, access control, support network, racks, workstations, and management software. At the end of the field phase, the contractor believes it performed good work: equipment is installed, cameras display images, and access devices respond to commands.

From the contractor’s perspective, the service appears complete. From the Owner’s Engineering perspective, different questions still need answers:

• does the installed quantity match the contracted quantity and approved design?
• were locations changed? Were the changes formally approved?
• does the As-Built represent the actual condition?
• do the images meet the defined field-of-view and purpose?
• do resolution, frame rate, bitrate, retention, and storage meet the requirements?
• are cameras, controllers, and other devices correctly identified?
• were institutional configurations and credentials transferred to the owner?
• do configuration backups exist?
• are licenses correctly assigned?
• were integrations among CCTV, VMS, and access control tested?
• does the photographic report allow implementation to be traced?
• were test reports and evidence of corrections delivered?
• are warranties and serial numbers consolidated?
• were final documents formally submitted at the proper revision?
• is there enough time to correct the identified deviations?

The existence of video on a screen does not answer these questions. Therefore, apparent installation and demonstrated performance are different things; demonstrated performance and complete documentary delivery are also different things.

The case applies across disciplines. Structured cabling may be installed and certified but lack traceability or As-Built documentation. An electrical installation may be energized and still have pending documentation or tests. An automation system may operate in basic mode while not all sequences and alarms have been validated. The principle is transversal.

Punch lists and nonconformities need a real correction window

The receipt process needs to assume that inspection may find deviations. If planning starts from the assumption of “zero outstanding items,” it has no contingency for reality.

The list of outstanding items — the punch list — should classify items according to criticality and impact on acceptance. Blocking items need to be resolved before progressing to milestones that presume conformity. Minor items may, when contractually permitted and technically justified, be addressed through reservations and defined deadlines.

Management should record:

Field	Purpose
Identification	Allow the outstanding item to be traced
Affected requirement	Show which obligation was not met
Evidence	Record the condition found
Criticality	Distinguish a blocking issue from a minor adjustment
Responsible party	Define who corrects it
Deadline	Avoid indefinite outstanding items
Correction evidence	Demonstrate treatment
Reverification	Confirm that the correction worked
Status	Control formal closure

The Engineering Outstanding Items Matrix should connect directly to the contractual schedule. An outstanding item identified with no time for correction is a closeout-planning problem.

The final receipt certificate must demonstrate, not presume

Final receipt under Article 140 is carried out by a public employee or commission appointed by the competent authority and must be formalized through a detailed certificate demonstrating compliance with contractual requirements.

The word demonstrating matters. The final document must be supported by a set of verifiable evidence. It is not enough to state generically that “the services were satisfactorily performed” when the contract involved dozens or hundreds of technical requirements.

A robust certificate may reference:

• contract, tender documents, Terms of Reference, and relevant appendices;
• Service Order and formalized changes;
• approved design and applicable revisions;
• inspection reports;
• inspection records;
• commissioning and test results;
• technical acceptance opinion;
• closed outstanding-items matrix or formalized reservations;
• approved As-Built documentation;
• accepted Data Book or final documentation;
• warranties and post-delivery obligations;
• training and operations-transfer records;
• other documents provided for in the contract-management model.

The certificate does not need to reproduce all technical documentation, but it should allow a future auditor to reconstruct why the Administration decided to receive the object.

What should not happen at closeout

Some practices weaken receipt and transfer risk to the client:

• signing final receipt merely because the contractual term has ended;
• accepting incomplete documents with an informal promise of future supplementation;
• considering energized equipment sufficient evidence of performance;
• receiving As-Built documentation without comparing samples or critical points against the field;
• ignoring discrepancies among design, contracted quantities, and executed condition;
• allowing the contractor itself to be the only source of validation of its work;
• closing a punch list without correction evidence;
• leaving licenses, passwords, backups, or warranties exclusively in the supplier’s possession;
• treating training, manuals, and documentation as “administrative” items without impact on acceptance;
• performing commissioning after contract closeout without provision for corrections.

These practices are especially dangerous in systems that will enter operation immediately, because continuity pressure can turn an incomplete delivery into a fait accompli.

Why Owner’s Engineering needs to enter before the end of the contract

Owner’s Engineering is not a last-minute inspection. Its greatest value occurs when it follows the chain from defining what will be contracted through receipt.

Each stage reduces a different class of risk:

• Design and requirements: define what must be delivered and how it will be demonstrated.
• Tender support: converts requirements into verifiable documents and criteria.
• Technical qualification: reduces the risk of selecting a company without compatible experience.
• Detailed Design Review: identifies deviations before they become installations.
• Owner’s Engineering: monitors interfaces, decisions, quality, schedule, and changes during execution.
• QA/QC: records inspections, nonconformities, and evidence.
• Document management: prevents execution knowledge from disappearing with demobilization.
• Commissioning: verifies performance, integration, and readiness.
• Technical opinion: consolidates evidence and outstanding items to support the manager.
• Receipt: formalizes the administrative decision based on traceable technical evidence.

Owner’s Engineering works as the continuity line among these stages. Its role is not to replace the contract inspector, but to create independent technical capacity so that the owner does not depend exclusively on the contractor’s interpretation and documentation.

The contract inspector may have specialized technical support

Article 117 of Brazilian Law 14,133 requires execution to be monitored and inspected by representatives of the Administration and allows third parties to be hired to assist them and provide pertinent information. The Law preserves the inspector’s duties and responsibilities, while recognizing the possibility of specialized support.

This is especially relevant when the object requires multidisciplinary knowledge, design analysis, specialized inspections, commissioning, interpretation of test reports, verification of integrated systems, or document auditing.

The article Can the Contract Inspector Have Technical Support? examines this possibility from a Consulting Engineering perspective.

Technical support may produce elements such as:

• inspection reports;
• independent photographic records;
• conformity opinions;
• As-Built review;
• Data Book analysis;
• outstanding-items matrix;
• commissioning monitoring;
• assessment of corrections;
• technical recommendation for acceptance, acceptance with reservations, or rejection.

The administrative decision remains with the competent agents. The value of independent engineering lies in technically qualifying the information that supports that decision.

Receipt begins in the Terms of Reference, not in the last month

A sound closeout process is designed before contracting. The Terms of Reference, tender documents, contract, and design should define what “ready for receipt” means.

This includes, when applicable, providing for:

• mandatory documentary deliverables;
• file format and standards;
• revisions and approvals;
• acceptance criteria;
• test plan;
• responsibilities for testing;
• commissioning milestones;
• deadline for requesting receipt;
• Administration’s analysis period;
• contractor’s correction period;
• reverification procedure;
• documents required for provisional receipt;
• documents required for final receipt;
• method for handling reservations;
• warranties and post-delivery obligations.

For this reason, the receipt process connects directly to the Preliminary Technical Study, Tender Documents for Engineering Works and Services, and technical review of the Terms of Reference. If the Administration only begins thinking about acceptance after the contractor requests final measurement, part of the problem has already been created during planning.

How to structure a receipt flow with time to correct

The model below does not replace the contract or applicable regulation, but it helps structure management logic:

1. Define criteria during procurement. What will be verified, which documents will be required, and who participates in the process.
2. Establish a readiness milestone. The contractor must complete installation and documentation before the final contract date.
3. Perform pre-inspections. Relevant nonconformities should be identified while execution is still underway.
4. Receive the document package. Check whether the request includes the minimum deliverables.
5. Perform inspection and commissioning. Validate requirements, performance, integration, and documentary condition.
6. Issue a punch list. Record deviations and correction deadlines.
7. Verify corrections. Require evidence and repeat tests when necessary.
8. Issue a technical opinion. Consolidate object condition, documents, and outstanding items.
9. Formalize receipt. Follow the agents, deadlines, and method provided for in the contract and legislation.
10. Transfer to operations. Ensure the organization has the documentation, warranties, access, and knowledge required.

This process makes acceptance a consequence of evidence rather than a last-minute negotiation.

A construction delivery certificate and a receipt certificate are not necessarily the same thing

Searches for “construction delivery certificate” usually mix two different acts. One document may record that the contractor delivered the object or made it available for evaluation. Another act, performed by the client under the applicable governance, records that the object was received.

Separating these acts reduces ambiguity. Delivery is a declaration by the contractor accompanied by the required package. Receipt is a decision by the client after the appropriate verifications.

In simpler contracts, documents may be consolidated when permitted by the applicable rule. In complex contracts, preserving the documentary sequence facilitates auditing and delineates responsibilities.

Final receipt does not eliminate later responsibilities

Article 140, §2, makes clear that provisional or final receipt does not exclude civil liability for the solidity and safety of the work or service, nor ethical-professional responsibility for proper execution, within legal or contractual limits.

Therefore, final receipt does not mean declaring that no defect can ever emerge. It means that, based on the available verifications and evidence, the object met the conditions required for receipt at that milestone, without excluding warranties and responsibilities that remain in force.

This is another reason to preserve consistent final documentation: when a problem appears months later, records of design, execution, testing, configuration, approval, and warranty are essential for diagnosing causes and assigning responsibilities.

Warning signs for the manager before signing the certificate

The manager, inspector, or commission should increase the level of verification when signs such as the following are present:

• the contractor states that it “finished” but did not formally submit the delivery;
• the final package arrives in the last days of the contract;
• the As-Built is delivered together with the acceptance request, with no time for review;
• photographic reports lack identification or traceability;
• tests were performed by the installation team itself without verifiable records;
• there are discrepancies among design, quantities, and installation;
• configurations, licenses, or backups have not yet been transferred;
• the outstanding-items matrix contains items without deadlines or closure evidence;
• warranties are not linked to the assets actually installed;
• operations began before commissioning was closed;
• the contractor conditions corrections on a time extension that could have been avoided with adequate planning;
• the Administration lacks a team with sufficient technical competence to verify the complex object.

None of these signs, in isolation, determines automatic rejection. They indicate that the decision requires additional evidence and careful technical management.

When to hire Consulting Engineering support for receipt

The need is greater when there is technical asymmetry between the client and contractor, when the system is highly critical or has complex integration, when documentation is extensive, when there is a history of nonconformities, or when the organization does not internally have all the necessary specialties.

A3A Engenharia can support this process at different points without replacing the legal authority of public agents:

• structuring requirements and acceptance criteria;
• technical review of Terms of Reference and tender documents;
• support for technical qualification analysis;
• Design Review and Detailed Design analysis;
• Owner’s Engineering during implementation;
• inspections and QA/QC monitoring;
• document control and review;
• commissioning monitoring or execution according to scope;
• audit of As-Built and Data Book;
• outstanding-items matrix and correction verification;
• technical opinion to support receipt and acceptance.

The Technical Receipt of Engineering Works and Services service focuses precisely on the stage in which the owner needs to transform physical execution, documents, tests, and outstanding items into a technically defensible decision.

Final considerations

The final receipt certificate is the endpoint of an engineering chain that begins long before the document is signed. Design, procurement, qualification, inspection, quality, documentation, commissioning, and corrections determine the quality of the receipt decision.

The contractor does not complete its obligation merely because it finished installing. It must deliver the object in the contracted condition, support the delivery with the required documentation, and make it available for verification with sufficient lead time. The client, in turn, must organize technical capacity, methods, and deadlines to verify, test, record outstanding items, require corrections, and formalize its decision.

Substantial completion is not final delivery; physical delivery is not acceptance; and the end of the deadline does not replace the receipt process. The more complex the object, the more important it is to have Owner’s Engineering and Consulting Engineering involved before the final day of the contract turns foreseeable outstanding items into a closeout dispute.

Technical references

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

[2] FEDERAL COURT OF ACCOUNTS. Procurement and Contracts: Technical Inspection and Provisional Receipt. Brasília: TCU. Available at: https://licitacoesecontratos.tcu.gov.br/6-1-4-fiscalizacao-tecnica-e-recebimento-provisorio-2/

[3] FEDERAL COURT OF ACCOUNTS. Procurement and Contracts: Contract Management and Final Receipt. Brasília: TCU. Available at: https://licitacoesecontratos.tcu.gov.br/6-1-6-gestao-do-contrato-e-recebimento-definitivo-2/

[4] FEDERAL COURT OF ACCOUNTS. Procurement and Contracts: Contract Management Model. Brasília: TCU. Available at: https://licitacoesecontratos.tcu.gov.br/4-3-6-modelo-de-gestao-do-contrato/

Frequently asked questions

What is a final receipt certificate?

It is the document that formalizes receipt of the object after the specified verifications. For works and services under Brazilian Law 14,133, Article 140 provides for a detailed certificate demonstrating compliance with contractual requirements, issued by a public employee or commission appointed by the competent authority.

Can the company request final receipt on the last day of the contract?

The procedure must follow the deadlines and methods provided in the contract or regulation. In engineering, leaving the request until the end may make inspections, testing, commissioning, corrections, and reverification impracticable. The schedule should reserve time for the delivery and receipt process.

Does completed installation mean the object has been delivered?

Not necessarily. In addition to physical execution, the contract may require documentation, As-Built drawings, reports, tests, configurations, warranties, training, a Data Book, and other evidence. Delivery must meet the full set of contracted obligations.

What is the difference between provisional and final receipt?

For works and services, Article 140 provides for provisional receipt by the person responsible for monitoring and inspection, through a detailed certificate and verification of technical requirements; final receipt is performed by an appointed public employee or commission and must demonstrate compliance with contractual requirements.

Is substantial completion the same as final receipt?

No. Substantial completion may be a management or contractual concept when defined, but it does not replace the formal and technical requirements of final receipt. Documentary outstanding items, testing, or critical items may prevent acceptance even with a high physical completion percentage.

Is As-Built documentation required for receipt?

When required by the procurement documents, yes. As-Built documentation is central evidence of the executed condition and must represent the field. Its absence or low quality may prevent the owner from having an adequate technical basis for operation, maintenance, and future interventions.

Who performs final receipt under Brazilian Law 14,133?

For works and services, Article 140 provides for final receipt by a public employee or commission appointed by the competent authority, through a detailed certificate demonstrating compliance with contractual requirements.

Can the contract inspector have support from an engineering company?

Yes. Article 117 permits third parties to be hired to assist and support the inspector with pertinent information without transferring the inspector’s own duties. This support may involve inspections, document analysis, commissioning, and technical opinions.

Complementary technical materials

Related solutions

• Requirements, Evidence, and Acceptance Criteria Management
• Project, Program, and Portfolio Governance
• Engineering Document Management: GED, EDMS, Revisions, and Traceability

Related services

• Technical Receipt of Engineering Works and Services
• Technical Audit of Data Book and Final Engineering Documentation
• Technical Review of Terms of Reference for Engineering Works and Services
• Technical Support for Qualification of Engineering Bidders

Main content on this topic

• Installed System Is Not a Delivered System: Physical Completion, Technical Delivery, and Acceptance
• The Contractor Completed the Works. What Now? What to Verify Before Receipt and Acceptance
• Can the Contract Inspector Have Technical Support? The Role of Consulting Engineering Under Brazilian Law 14,133
• Technical Acceptance Certificate in Engineering: Validation, Outstanding Items, and Closeout

Related technical content

• Engineering Data Book: Structure, Traceability, Documents, and Acceptance Criteria
• QA/QC in Engineering Works: Assurance, Control, Inspections, NCRs, and Technical Acceptance
• Technical Handover in Engineering: Delivery, Documentation, Acceptance, and Transition to Operations
• Owner’s Engineering: Technical Governance for Engineering Works, Critical Systems, and Multidisciplinary Integration