What to do after qualification in a Brazilian engineering pregão: PoC, pre-start gate, Design Review, execution plan, submittals, inspection and Owner’s Engineering.

Check it out!

After an electronic pregão for an engineering service reaches the qualification stage and the winning bidder proves the requirements established in the tender documents, the Administration does not gain freedom to create new qualification requirements or look for an unforeseen reason to remove that bidder. If qualification was regular and there is no objective basis for disqualification or rejection, the process must follow the rules of the procurement. The contracting authority’s protection then depends on the technical layers that were properly established for the transition between selection, contracting, mobilization and execution.

This is a critical point because technical qualification and operational readiness are not the same thing. Qualification verifies, according to objective criteria in the tender documents, whether the bidder demonstrates technical-professional and technical-operational capability compatible with the scope. By itself, it cannot demonstrate that every execution method is mature, that all proposed materials are approved, that the detailed schedule is feasible, that interfaces have been understood or that the detailed design under the contractor’s responsibility is ready for construction.

For this reason, well-structured engineering contracts use successive layers of control. The procurement selects the proposal and verifies qualification. Then, depending on the nature of the scope and provided that the procurement documents established the applicable requirements, there may be a proof of concept, compliance checks, submittals, detailed-design validation, execution plan, baseline schedule, quality plan, ITP/PIT, document matrix, kick-off meeting and a formal gate before the Notice to Proceed.

The logic is not to make contracting more difficult or create a second procurement. It is to prevent the first real opportunity to discover a technical incompatibility from occurring during construction, when correction costs, schedule impacts and conflict potential are higher.

What changes after qualification

The first distinction is between whether the procurement method is legally applicable and the technical controls that begin after selection. Under Brazil’s Law No. 14,133/2021, pregão is used when the object has performance and quality standards that can be objectively defined in the tender documents through usual market specifications; the law does not apply it to public works or specialized technical services of a predominantly intellectual nature, while allowing it for common engineering services when the legal requirements are met. This framework separates pregão for common engineering services from cases in which the method cannot be used.

Once that definition has been resolved, the method has been correctly selected, the tender has been published, proposals have been evaluated and the winner has met the qualification criteria. The question becomes: how do you transform a formally correct selection into technically controlled execution?

Two opposite distortions must be avoided. The first is believing that qualification alone guarantees operational success. The second is trying to correct a poorly structured procurement by creating new requirements after the bidding has ended. Neither produces good governance.

What technical qualification actually proves

Experience certificates and CATs are relevant evidence of prior experience, but the analysis must follow the published criteria exactly and produce a traceable decision.

Specialized support helps compare the scope, relevant portions, team, professional documents and clarification procedures without creating new criteria after the bidding stage.

Technical Qualification and Bidder Qualification Support

Technical qualification in engineering procurement should be understood as a risk-reduction stage based on previously defined evidence.

Brazil’s Law No. 14,133/2021, especially Article 67, allows technical-professional and technical-operational qualification to examine professional registrations, certificates or evidence of capability, team, facilities, equipment and other elements compatible with the object, within the legal limits. Under certain conditions, it also allows consideration of existing commitments that reduce the availability of technical personnel.

An experience certificate has an important function: it demonstrates that a company or professional previously performed an activity compatible with the requirement. But that evidence is not a universal guarantee of future performance.

Between two different dates, the following may change:

  • team composition;
  • availability of professionals;
  • suppliers and supply chain;
  • financial capacity and simultaneous contract workload;
  • internal processes;
  • mastery of a specific solution;
  • quality of documentation;
  • interpretation of that project’s interfaces;
  • ability to plan the specific mobilization.

This does not reduce the legal or technical value of the certificates. It simply defines correctly what they prove.

The mistake of trying to “disqualify later”

If the bidder submitted the required documents and met the tender criteria, the Administration should not turn subjective discomfort into a new qualification requirement.

The principle that the Administration and bidders are bound by the tender documents protects both sides. Criteria affecting participation, ranking or qualification must be known in advance and applied objectively.

In practice, a concern may be technically legitimate — for example, uncertainty about methodology, the team actually mobilized or the detailed solution — and still not constitute a basis for disqualification if that requirement did not belong to the qualification stage or was not defined in the tender documents.

The engineering response is to structure valid gates at the appropriate stage, not force qualification to answer every question.

Layer 1: proposal and technical compliance

When the scope involves technical interfaces, equivalencies, performance requirements or a large volume of documentation, proposal review must go beyond checking price.

A technical compliance matrix organizes requirements, evidence and conclusions before the procurement decision.

Technical Procurement Support and Proposal Analysis

The first barrier is ensuring that the commercial and technical proposal actually corresponds to the procured scope. In engineering objects, a low price or formally complete documentation does not replace an adherence analysis.

Technical Support for Procurement and Engineering Proposal Analysis can structure compliance matrices linking tender requirements to evidence in the proposal.

A simple matrix may include:

RequirementSource documentProposal evidenceStatusTechnical note
minimum performancespecificationdatasheet/modelcomplies/does not complycondition or reservation
key teamtender documentsprofessional listcomplies/does not complyrelationship and availability
critical materialdesign/ToRmanufacturer/modelcomplies/reviewtechnical equivalence
schedulereference scheduleproposalcompatible/incompatibleconstraints
mandatory testToRmethodologyincluded/missingstage and criterion

The purpose is not to replace the formal judgment, but to provide the person responsible for the procurement with an organized and traceable technical assessment.

Layer 2: proof of concept when legally applicable

Brazil’s Law No. 14,133/2021 allows, in Article 17, paragraph 3, proposal-compliance analysis through sample approval, compliance examination and proof of concept, among other tests, with respect to the provisionally successful bidder, provided these procedures are established in the tender documents.

Brazil’s Federal Court of Accounts (TCU) guidance on samples and proof of concept emphasizes that this instrument must have justification, objective criteria, a clear script and transparency. It must not become a subjective evaluation used to select unpublished preferences.

A proof of concept is especially useful when certain essential characteristics cannot be sufficiently confirmed merely by reading catalogs, declarations or technical descriptions. It tests the solution’s adherence to defined requirements.

However, not every contract should be turned into a laboratory. The cost and potential restriction on competition must be proportional to the risk and relevance of the characteristic being verified.

Layer 3: contract and pre-Notice-to-Proceed period

The transition between signature and physical start can be one of the best control opportunities.

Article 92, paragraph 2, of Brazil’s Law No. 14,133/2021 allows the contract to establish a period before issuance of the Notice to Proceed for checking pending items, releasing areas or taking other measures needed for a regular start of execution.

This period is not authorization to reopen qualification. It is an opportunity to confirm contractually established starting conditions.

A pre-start readiness matrix may verify:

  1. contract and guarantees formalized;
  2. technical professionals designated;
  3. key team available for mobilization;
  4. site, access and work areas released;
  5. detailed design or details required for the first work fronts;
  6. detailed schedule submitted and reviewed;
  7. execution plan approved;
  8. submittals for critical materials;
  9. inspection and test procedures;
  10. deliverables and document matrix;
  11. critical risks and interfaces updated;
  12. formal RFI, submittal and change channels defined.

The result should be an objective gate: released, released with conditions or not released due to a contractually blocking pending item.

Layer 4: detailed design as a technical gate

When execution depends on technical detailing, releasing construction before reviewing interfaces, materials and constructability transfers problems from the drawings to the field.

Design Review works as a maturity gate before decisions that are difficult to reverse are incorporated into the asset.

Technical Design Review and Validation — Design Review

When detailed design is the contractor’s responsibility — a possibility under certain contracting regimes and scopes — its existence should not be confused with automatic approval.

An Engineering Design Review verifies consistency with requirements, interfaces, constructability, interdisciplinary coordination, materials and acceptance criteria before affected execution is released.

Even when the detailed design is provided by the contracting authority, submittals, shop drawings, methods and fabrication details may require review before installation.

The gate may answer:

  • does the solution preserve the design and contract requirements?
  • are physical and functional interfaces resolved?
  • are proposed materials equivalent to the requirements?
  • are there conflicts between disciplines?
  • do the details allow execution without field improvisation?
  • do the proposed solution still allow the planned tests and acceptance criteria?
  • was there a change that needs to go through change control?

The benefit is moving the problem to a stage where it is still inexpensive to correct.

Layer 5: execution plan and baseline schedule

The execution plan should not be a generic text copied from another project. Its function is to demonstrate how the contractor intends to transform contractual requirements into a real sequence of work.

The document may integrate:

  • mobilization strategy;
  • team organization;
  • WBS;
  • detailed schedule;
  • execution methods;
  • work fronts;
  • interfaces with operations and third parties;
  • critical materials and supplies;
  • submittals;
  • quality controls;
  • inspections and tests;
  • progressive documentation;
  • risk management;
  • RFI and change processes;
  • handover and demobilization.

Project Controls turns the schedule into a verifiable baseline and allows variations to be tracked after execution is released.

If the schedule is not validated at the beginning, it becomes difficult to distinguish real delay, resequencing, third-party impact and mere retrospective updating.

Layer 6: submittals and material approval

High-quality materials can produce poor results when selected, installed or documented incorrectly. Likewise, a product different from the reference model may fully comply when the procurement uses properly specified functional and performance criteria.

For this reason, post-award evaluation must compare requirements, not personal preferences.

A critical-material submittal may include:

  • manufacturer and model;
  • official datasheet;
  • applicable certifications;
  • required versus offered performance;
  • compatibility with other components;
  • environmental conditions;
  • installation requirements;
  • warranty;
  • supporting documentation;
  • impacts on design and testing.

The approval should make clear whether the material is approved, approved with reservations or rejected, and which technical basis supported the decision.

Layer 7: quality plan, ITP/PIT and hold points

Another mistake is waiting until the end of execution to discover that relevant stages became hidden or inaccessible to inspection.

The Inspection and Test Plan — ITP/PIT distributes controls throughout the process and may establish review points, witness points and hold points for critical activities.

Control points should be selected based on risk. Irreversible or high-impact activities need to be verified before they are concealed or before the next sequence begins.

This layer also reduces the classic problem of turning commissioning into a late attempt to detect installation defects that could have been controlled during the work.

Layer 8: inspection and Owner’s Engineering during execution

After the Notice to Proceed, governance changes in nature. The challenge is no longer “is the contractor ready to start?” but “does execution remain compliant with the contract?”

Evidence-based inspection should record events, inspections, measurements, documents and nonconformities so that future decisions can be reconstructed.

Owner’s Engineering expands this protection when the owner needs to integrate design, suppliers, interfaces, changes, quality, documentation, tests and acceptance.

Under Brazil’s Law No. 14,133/2021, Article 117 provides for monitoring and inspection by the contract inspector or inspectors and allows third parties to be hired to assist them and provide relevant information. Specialized support does not replace the inspector’s authority or transfer administrative decision-making powers to the consultant.

Aggressive pricing is a risk signal, not automatic proof of unfeasibility

Pregão procedures can produce strong price competition. A significant discount deserves analysis, but does not justify presuming bad faith or incapacity.

Price diving in public-works procurement requires attention because aggressive discounts can interact with price composition, feasibility and amendment strategy. For a scope procured through pregão, the technically defensible approach is to verify feasibility under the applicable legal framework and, after contracting, maintain scope discipline and change control.

If a claim appears early, the correct question is not “the price was low, so the request must be denied.” The analysis must reconstruct the original obligation, event, responsibility, causal link and impact. Likewise, a low price cannot justify accepting execution below the required standard.

A post-qualification protection flow

Protection works best when the layers are established in the preparatory phase and organized as a coherent sequence.

Protection layers between qualification and execution of an engineering service

Qualification completed

Proposal compliance

PoC if required

Signature

Pre-start gate

Design and submittals

Execution plan

Notice to Proceed

Inspection and OE

Protection layers between qualification and execution of an engineering service

The diagram makes clear that later layers do not retroactively correct qualification. Each one answers a different question.

LayerQuestion
QualificationDoes the bidder prove capability according to the tender criteria?
ComplianceDoes the proposal comply with the scope?
PoCDoes the demonstrated solution meet the requirement that needs testing?
Pre-start gateAre the contractual starting conditions sufficiently mature?
Design ReviewIs the detailing technically ready for execution?
Execution PlanHow will the contractor organize execution?
Inspection/OEDoes the ongoing execution remain compliant with the contract?
CommissioningDoes the installed solution demonstrate performance and readiness?

How to write these barriers into the ToR, tender documents and contract

The time to think about post-award protections is before the tender is published.

A well-structured Terms of Reference for Public Works and Engineering Services should define the scope and also the execution model, conditions, obligations, measurement and acceptance applicable to the procurement.

For each barrier, it is necessary to establish:

  • objective;
  • stage of application;
  • party responsible for submission;
  • party responsible for review;
  • deadline;
  • documents or evidence;
  • objective approval criterion;
  • consequence of rejection or pending status;
  • possibility and deadline for correction, when applicable;
  • relationship with Notice to Proceed, measurement or acceptance.

What must not happen is publishing a simple tender and, after the result, trying to add controls that would materially alter the conditions of competition.

When to hire specialized technical support

The need increases when the scope involves multiple disciplines, critical technology, systems integration, detailed design, a large number of submittals, tests, technical equivalencies or significant interface risks.

Technical Qualification Support helps structure and apply defensible technical criteria at the proper stage. After the procurement, Design Review, inspection, Project Controls and Owner’s Engineering can assume different functions throughout the journey.

Consulting support should preserve segregation of duties: specialized engineering analyzes and recommends; the procurement officer, committee, contract manager, inspector and competent authority perform the acts within their respective powers.

Final considerations

The technical risk of an engineering pregão is not solved by trying to turn qualification into absolute proof of operational maturity. Nor is it solved by creating new criteria after bidding.

The solution is to design the procurement as a sequence of valid and proportionate barriers: objective requirements, appropriate technical qualification, proposal compliance, proof of concept when applicable and established in advance, a pre-Notice-to-Proceed period, Design Review, execution plan, submittals, ITP/PIT, baseline, evidence-based inspection and Owner’s Engineering.

When these layers are planned from the ToR and tender documents onward, the contracting authority can preserve competition without giving up technical control. Qualification does what it is supposed to do; later stages do what qualification was not designed to do.

This is the central principle: do not create an artificial reason to prevent execution by a contractor that was regularly selected; instead, establish in advance the conditions under which execution advances only when each critical requirement has been objectively demonstrated.

After the Notice to Proceed, the owner needs to integrate inspection, designs, suppliers, changes, quality, documents and tests without losing decision-making authority.

Owner’s Engineering provides this independent technical layer throughout implementation.

Learn about Owner’s Engineering

Technical references

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

[2] BRAZILIAN FEDERAL COURT OF ACCOUNTS. Procurement & Contracts — Samples and proof of concept. Available at: https://licitacoesecontratos.tcu.gov.br/5-4-1-2-amostra-e-prova-de-conceito/.

[3] OFFICE OF THE ATTORNEY GENERAL OF BRAZIL. Models under Law No. 14,133/2021 — Pregão and Competitive Tendering. Available at: https://www.gov.br/agu/pt-br/composicao/cgu/cgu/modelos/licitacoesecontratos/14133/pregao-e-concorrencia.

Frequently asked questions
After a company is qualified in a pregão, can technical checks still be performed?

Yes, provided they are checks established in the tender documents, Terms of Reference or contract and applied at the proper stage. A new qualification requirement cannot be invented after the result to remove a bidder that met the published criteria.

Does technical qualification guarantee that the company will perform the contract well?

No. Qualification demonstrates capability based on evidence and criteria defined in the tender documents. Future performance also depends on the mobilized team, planning, materials, design, quality, management and inspection.

Can a proof of concept be required in a pregão?

Brazil’s Law No. 14,133/2021 allows a proof of concept for the provisionally successful bidder when established in the tender documents. The criteria must be objective, justified and transparent.

What should be verified before the Notice to Proceed?

Depending on the contract, the team, detailed design, execution plan, schedule, submittals, critical materials, quality plan, ITP/PIT, document matrix, released areas and interfaces may be verified.

Does a very low price allow automatic rejection of a proposal?

No. Feasibility must be analyzed according to the legal and tender criteria. An aggressive discount is a risk signal to be examined, not automatic proof of incapacity or bad faith.

What is the role of Owner's Engineering after contracting?

To technically represent the owner and integrate design review, inspection, interfaces, changes, quality, documentation, testing and acceptance, without replacing the decision-making powers of the responsible public agents.

Supplementary technical materials

Related solutions

Related services

Main content on the topic

Related technical content