iPMP: How to Assess Project Maturity Before Procurement

Understand how the TCU iPMP assesses public-project maturity across 46 actions and how to turn gaps into engineering actions before procurement.

Check it out!

The iPMP — Project Maturity Perception Indicator is a tool developed by Brazil’s Federal Court of Accounts (TCU) to assess, in a structured way, the robustness of planning for public infrastructure projects before execution. The indicator does not merely measure whether certain documents exist. It seeks to verify whether the elements supporting the investment decision are sufficiently developed, mutually consistent, and supported by technical evidence capable of demonstrating that the project has been structured with a level of maturity compatible with its complexity.

In the methodology published by the TCU in 2026, the iPMP uses the Five-Dimension Model — M5D — and evaluates 46 actions distributed across the strategic, economic, commercial, financial, and managerial dimensions. The logic is to follow the decision-making process from definition of the need and alternatives through preparation for procurement, risk management, governance, and the reviews that precede execution. The score ranges from zero to one: the closer to one, the greater the degree of compliance with the maturity elements assessed.

This does not mean that a high score guarantees success or that a low score, by itself, proves failure or infeasibility. The TCU itself treats the iPMP as an instrument for perception, diagnosis, and guidance. The technically correct reading is not merely to ask “what was the score?”, but which actions were not fulfilled, which dimensions concentrate weaknesses, what evidence is missing, and what consequences those gaps may have for cost, schedule, procurement, execution, and project delivery.

For engineering, this distinction is decisive. A project may have drawings, an estimate, a schedule, and formal documents and still be immature because the need was poorly characterized, alternatives were not compared, assumptions were not verified, risks were not treated, interfaces remained open, or the procurement strategy is incompatible with the available level of definition. Maturity is not document volume. It is the ability to demonstrate that important decisions were made at the appropriate time, with sufficient information and traceability.

Applied before bidding, the iPMP can function as a preventive reading of the investment: it highlights points that deserve correction before uncertainties are transferred to the bidding documents, estimate, contract, and ultimately to construction. Its greatest value, therefore, is not in producing a score, but in creating a structure for asking whether the project is truly ready to proceed.

What the iPMP actually measures

The iPMP measures a structured perception of the maturity of planning for a public project. The word perception is relevant because the assessment involves technical judgment about the evidence, content, and quality of the elements presented. The methodology parameterizes this judgment to reduce arbitrariness, but it does not turn the analysis into a purely automatic check.

The TCU developed the indicator in the context of Fiscobras and consolidated its methodology in a dedicated guide. The tool is based on the premise that the decision to execute a significant investment should be preceded by a coherent chain of studies, analyses, choices, validations, and governance mechanisms. This is the chain the indicator seeks to examine.

The assessment is not limited to formal legal compliance. A document may exist and still be technically insufficient. A feasibility study may be outdated. A risk matrix may list events without quantifying them or connecting risks to the contracting strategy. An estimate may be detailed but based on quantities derived from an incomplete design. A schedule may show dates without reflecting permitting, land acquisition, critical supplies, or interfaces among disciplines.

This is the point of contact between the iPMP and the broader concept of planning the procurement of engineering works and services. The preparatory phase should not be treated as a bureaucratic succession of isolated documents. Studies, requirements, design, estimate, risks, procurement strategy, and management mechanisms need to form a coherent system.

The indicator helps make this coherence assessable. Instead of merely asking whether the process contains a preliminary technical study, design, estimate, or risk matrix, the analysis asks whether these elements were developed to a compatible depth, whether they are consistent with one another, and whether they support the decision to proceed.

The five iPMP dimensions and what each one seeks to answer

The 2026 methodology organizes the 46 actions into five complementary dimensions. They do not correspond to isolated departments. The same engineering deliverable may support more than one dimension, and a weakness in one dimension may affect decisions made in the others.

Dimension	Central question	Examples of evidence and decisions
Strategic	Does the project respond to a clear public need and align with priorities?	problem, objectives, demand, institutional alignment, expected outcomes
Economic	Does the selected alternative provide an adequate relationship among costs, benefits, and impacts?	alternatives analysis, cost-benefit analysis, social and environmental impacts, preferred option
Commercial	Can the solution be procured in a viable manner compatible with the market?	procurement strategy, delivery model, market interest, contractual risks, requirements
Financial	Can the project be funded throughout implementation and operations?	CAPEX, OPEX, funding sources, estimate, funding capacity, financing
Managerial	Are governance, team, risks, controls, and delivery capacity in place?	decision structure, risk management, schedule, responsibilities, controls, monitoring

The strategic dimension comes before the discussion of which technical solution will be designed. It asks whether there is a sufficiently characterized need and whether the intended investment is connected to verifiable public objectives. When this basis is weak, the risk is technically optimizing a solution to a problem that was not correctly formulated.

In the economic dimension, the focus shifts to comparing alternatives and justifying the selected option. It is not enough for an alternative to be executable. It is necessary to demonstrate why it is preferable to the other possibilities considered, taking into account costs, benefits, impacts, constraints, and risks. This logic directly relates to the Preliminary Technical Study for engineering works and services, particularly when the study is used to structure alternatives before prematurely locking in a solution.

The commercial dimension examines the ability to turn the investment decision into a feasible procurement. This stage includes the delivery model, allocation of responsibilities, risk allocation, supply strategy, market conditions, requirements, and contract structure. A technically sound solution may fail if the market cannot offer it under the established conditions or if risks are allocated to parties that do not have the ability to manage them.

The financial dimension seeks to determine whether the project is compatible with the resources needed for implementation and sustainment. An estimate is not merely a sum of services. It depends on the stage of definition, assumptions, quantities, productivity, reference prices, schedule, risks, and boundary conditions. The article on public works estimating explores this relationship among technical definition, cost, and traceability in greater depth.

Finally, the managerial dimension examines whether there is capacity to turn planning into delivery. Governance, responsibilities, team, risk management, schedule, controls, decision-making, interfaces, and monitoring stop being accessory elements and become part of project maturity.

The five dimensions are useful precisely because they prevent a narrow view. A project does not become mature merely because its Basic Design is detailed. There may be an excellent set of drawings associated with a poorly justified economic alternative, an unfeasible commercial strategy, or a managerial structure incapable of controlling implementation.

How the 46-action assessment works

The iPMP Practical Application Guide describes 46 actions that function as structural elements of the decision-making process. They span three major phases: study of alternatives, refinement of the selected alternative, and public consultation, reviews, and updates.

The assessment should not be reduced to checking “exists” or “does not exist.” For each action, the guide directs the reviewer to examine documentary evidence, the content produced, and the expected degree of compliance. The central question is whether the documentation demonstrates that the action was effectively developed with sufficient quality to support a decision.

This distinction is easy to see in engineering. Consider an action related to risk management. The existence of a spreadsheet called a “risk matrix” does not, by itself, demonstrate maturity. A robust analysis should make it possible to understand the identified events, causes, consequences, probability, impact, responsible party, response, residual risk, and relationship with the contract, estimate, or schedule. The risk allocation matrix in engineering contracts has a specific purpose and should not be confused with a generic project risk register.

The same applies to schedules. A formally present schedule may have little value if it does not represent execution logic, constraints, interfaces, external milestones, and critical dependencies. An estimate may exist without a traceable calculation basis. A preliminary technical study may exist without comparing real alternatives. Maturity lies in the content and consistency among the deliverables.

Therefore, a technically useful assessment usually requires more than administrative reading. Documents must be cross-checked and relationships traced. Study assumptions need to appear in the design. Quantities need to be consistent with drawings and design narratives. Risks need to influence the estimate and contracting strategy. Dates need to consider permits, procurement, and interfaces. Performance criteria need to reach procurement and acceptance documents.

The sequence above shows why the iPMP can be read as an investment readiness tool. Its value is not in shifting decision responsibility to an index, but in making explicit what needs to be supported before resources are committed to the next stage.

How to interpret the score without turning the iPMP into a certification seal

The iPMP score ranges from zero to one, but its interpretation requires caution. The TCU emphasizes that there is not yet a sufficiently broad historical database to turn the indicator into a deterministic mechanism for predicting project success or failure.

The methodology identifies extreme ranges as relevant signals: very low scores indicate significant planning weaknesses, while very high scores indicate the presence of most structural maturity elements. Even so, the guide itself warns that a high score does not eliminate exogenous risks or replace qualitative analysis.

This is because an average can hide asymmetries. Imagine a project with a good overall score but very low performance in the managerial dimension. The aggregate result may appear comfortable while serious weaknesses remain in risk management, governance, team structure, or delivery capacity. The reverse may also occur: a lower score may result from actions that, at that stage or for that specific project type, have limited material impact.

Professional use of the indicator should therefore operate at three levels:

1. overall score, for a synthetic reading of the whole;
2. score by dimension, to identify concentrations of weakness;
3. action-by-action analysis, to locate missing, partial, or inconsistent evidence and assess its materiality.

The third layer is the most important for engineering. It makes it possible to turn an assessment into an action plan. Instead of merely concluding that “the project has low maturity,” the team should be able to record, for example, that a given design interface remains undefined; that the estimate did not incorporate quantitative risk; that the selected solution lacks sufficient economic comparison; or that the bidding documents intend to transfer to the contractor a risk over which it has no control.

This care also prevents inappropriate punitive use. The iPMP is a tool to support investigation, planning, and improvement. The score alone does not replace technical demonstration of a concrete deficiency, its cause, and its impact.

Document maturity is not the same as engineering maturity

One of the most dangerous mistakes is interpreting maturity as document quantity. Complex projects may accumulate hundreds of files without stabilizing essential decisions.

The difference becomes clear when the traceability chain is assessed. A requirement should have an identifiable origin, be translated into a design criterion, appear in the solution, have a verification method, and reach acceptance. A risk should be identified, analyzed, allocated, treated, and reflected in the documents that depend on it. A cost assumption should have a source, calculation basis, and consistency with the design. A change should make it possible to trace the cause, decision, responsible party, and effect.

This reasoning brings the iPMP close to Design Review practices in engineering projects. Independent technical review is not limited to finding drawing errors. It can verify completeness, consistency among disciplines, interfaces, assumptions, constructability, requirements, risks, and readiness to proceed to the next phase.

There are three recurring situations in which the documentation appears complete but maturity remains low.

Detailed design based on weak assumptions

The team develops drawings and design narratives before stabilizing demand, existing conditions, surveys, or performance criteria. The level of detail increases, but the decision basis remains uncertain. If a fundamental assumption changes, a large portion of the work needs to be redone.

An estimate that is precise only in appearance

Spreadsheets may contain dozens of decimal places and thousands of line items, but that does not mean economic precision. If quantities depend on an incomplete design, productivity assumptions do not reflect execution conditions, or relevant risks were not addressed, the final number communicates a degree of certainty the project does not yet possess.

Procurement prepared before the solution is ready

Pressure to bid may cause bidding documents, Terms of Reference, design, and estimate to advance in parallel without a maturity gate. The result is the transfer of undefined issues into the contract. During execution, these gaps reappear as RFIs, changes, amendments, claims, rescheduling, or disputes over responsibility.

Maturity, therefore, should be assessed as decision quality, not as the quantity of paperwork produced.

Relationship among iPMP, estimating, risks, and the probability of deviation

The TCU connects the maturity discussion with international front-end planning experience: the poorer the definition of the investment before execution commitment, the greater the tendency toward exposure to cost and schedule deviations. The guide presents this relationship as a conceptual basis, but also makes an important qualification: the Brazilian historical database still needs to be expanded before the iPMP can develop its own predictive capability.

This caution needs to remain. It is not technically correct to state that a given score will produce a specific percentage of cost overrun. What can be stated is that maturity gaps create known risk mechanisms.

An insufficiently defined project can produce:

• quantities subject to large variations;
• incomplete or contradictory requirements;
• low comparability among bids;
• poorly sized contingencies;
• schedules without real constraints;
• unassigned interfaces;
• inappropriately transferred risks;
• greater need for decisions during execution;
• greater exposure to scope changes, rework, and claims.

Risk management in public works is precisely the mechanism that turns these uncertainties into events, responsible parties, responses, controls, and evidence. The iPMP does not replace that management; it helps verify whether it exists within a broader planning structure.

The same reasoning applies to estimating. As technical definition improves, some uncertainties cease to be unknown, quantities become more reliable, and the estimate can move from broad ranges toward greater precision. This does not mean eliminating risk. It means making explicit which portion of uncertainty has been resolved and which remains exposed.

How to use the iPMP before bidding

Preventive use is particularly valuable because it allows gaps to be treated before they are crystallized in the bidding documents and contract. An organization does not need to wait for an audit to use the indicator’s logic as a self-assessment and governance instrument.

An application workflow can be structured in six steps.

1. Define the scope and timing of the assessment. The team identifies which project will be assessed, which decision is approaching, and which set of documents represents the current stage.
2. Map evidence by action. For each iPMP requirement, identify studies, minutes, designs, spreadsheets, decisions, analyses, and records that may demonstrate compliance.
3. Assess content, not merely existence. The team verifies consistency, currency, depth, coherence, and correspondence among deliverables.
4. Score and record the rationale. The score needs to be accompanied by an assessment record. Without justification, the ability to review and improve is lost.
5. Classify the materiality of gaps. Not every open item has the same effect. Identify which deficiencies may compromise feasibility, cost, schedule, procurement, safety, performance, or operations.
6. Create an action plan and decision gate. Critical gaps receive an owner, expected deliverable, deadline, and closure criterion before proceeding.

This process can be combined with an independent technical review of designs and documents before procurement. The advantage of an independent reading is to compare the documentation against maturity criteria without being conditioned by decisions made by the team that produced the original documents.

An essential point is to define the gate. The assessment should not end in an archived report. The objective is to establish which conditions need to be met so that the project can proceed with acceptable risk. Some gaps may be monitored during the next phase; others need to be closed before bidding because they directly affect the scope, price, or competition.

How to turn the diagnosis into an engineering action plan

A score only creates value when it produces corrective action. For that, each deficiency should be translated into a verifiable deliverable or decision.

Identified weakness	Possible technical action	Closure evidence
selected alternative without sufficient comparison	review alternatives study and decision criteria	approved comparative analysis
existing conditions insufficiently known	perform survey, inspection, or Due Diligence	existing-condition report and updated assumptions
design with open interfaces	perform Design Review and coordination	interface matrix and closed open items
estimate without traceability	review quantities, cost build-ups, and calculation records	revised estimate with calculation basis
generic risks	structure the risk register and allocation matrix	risks with causes, impacts, owners, and responses
bidding documents incompatible with maturity	review strategy, delivery model, and documentation	technically consistent bidding documents/attachments
insufficient acceptance criteria	define performance, testing, and documentation	verifiable criteria incorporated into procurement

This table shows a central difference between merely descriptive auditing and engineering consulting. Identifying that something is missing is only the beginning. The next step is to define what needs to be produced to close the deficiency.

The action plan should also preserve relationships among documents. If a survey changes quantities, the estimate needs to be revised. If the design changes, the schedule and risks may change. If the contracting strategy changes, responsibilities and the risk matrix need to be reassessed. Closing an item in isolation without reviewing its effects can create a false sense of completion.

When an independent maturity assessment makes sense

Not every project needs a heavy assurance structure. The intensity of the review should be proportional to size, complexity, materiality, and risk exposure. There are, however, objective signs that an independent assessment can add value.

These include multidisciplinary projects with many interfaces, procurement based on documentation produced by different suppliers, significant scope changes, projects restarting after stoppage, investments whose value is high relative to the public entity’s institutional capacity, integrated or semi-integrated contracting, compressed schedules, requirements still being consolidated, and significant decisions made with incomplete information.

Another sign is divergence among documents. If the design, estimate, schedule, risk matrix, and bidding documents appear to have been produced as separate pieces, a maturity review can function as an integration mechanism.

Independent assessment is also useful when there is strong pressure to proceed. In that situation, the internal team may be technically capable but subject to the same schedule and assumptions that need to be challenged. An external review creates an additional layer of challenge, records qualifications, and helps distinguish acceptable open items from gaps that should block the gate.

How to procure a maturity assessment or Design Review

A well-structured procurement should not merely request “evaluate the project.” The scope needs to translate expectations into verifiable activities, evidence, and deliverables.

Depending on complexity, the scope may include:

• kickoff meeting and definition of the project stage;
• document inventory and matrix;
• assessment of applicable iPMP dimensions and actions;
• review of studies, designs, estimate, schedule, risks, and procurement documents;
• comment and nonconformity matrix;
• criticality and materiality classification;
• clarification workshops with responsible teams;
• action plan to close gaps;
• review of submitted corrections;
• maturity report and technical recommendation regarding the gate.

The procurement should also define limits of responsibility. The review team does not replace design authors and does not assume the administrative decision. Its role is to examine evidence, identify weaknesses, record risks, and recommend technical actions. Responsibility for approval and the decision to proceed remains with the competent authorities.

Measurement criteria may be linked to deliverables: document matrix, preliminary report, technical workshop, final report, and action-plan review. This is generally more verifiable than measuring only hours spent, especially when the objective is to produce a traceable technical conclusion.

It is also advisable to require a team compatible with the project’s critical disciplines. A multidisciplinary review cannot be solved by a checklist alone. The reviewer needs sufficient understanding of design, estimating, planning, risks, procurement, and interfaces to recognize when formal evidence does not support the decision it is intended to demonstrate.

When the problem is concentrated in the preparatory phase, Technical Planning for Engineering Procurement can organize requirements, strategy, risks, and documentation. When the gap is earlier and involves need, alternatives, and feasibility, the Preliminary Technical Study for Engineering is a more appropriate deliverable. When the need is to challenge the consistency of the overall package before proceeding, Design Review becomes the central service.

iPMP as a bridge between oversight and engineering

The greatest value of the iPMP for engineering organizations is not to turn the TCU into a design manual. It is to translate an external-oversight concern — the maturity of the investment decision — into questions that engineering itself can address preventively.

This approach changes the timing of control. Instead of discovering during execution that the solution had gaps, the organization seeks to verify before procurement whether the structural elements are sufficiently mature. Instead of discussing only who is responsible for the problem after it materializes, the organization seeks to reduce its probability while decisions are still less expensive to correct.

The content connects directly with the cycle described in From Preliminary Technical Study to Technical Acceptance: maturity is not an isolated check, but a condition that needs to be built and preserved throughout the investment.

For the manager, this means better evidence. For inspection, it means receiving more verifiable documentation. For the market, it means competing for a clearer scope. For engineering, it means fewer late decisions, less rework, and less contractual ambiguity.

Final considerations

The iPMP provides a consistent framework for assessing whether a public project has sufficient elements to proceed, but its application should preserve the technical and diagnostic character defined by the TCU itself. The score is a synthesis; the real value lies in analyzing the five dimensions, the 46 actions, the available evidence, and the materiality of the gaps identified.

In complex projects, the most effective use of the indicator is preventive: assess maturity, record weaknesses, turn each relevant deficiency into an engineering action, and only then decide on the next gate. This process does not eliminate uncertainty, but makes more explicit what has been resolved, what remains open, and what requires additional control before procurement.

Technical references

[1] BRAZILIAN FEDERAL COURT OF ACCOUNTS. Project Maturity Perception Indicator: practical application guide. Brasília: TCU, 2026. Available at: https://portal.tcu.gov.br/publicacoes-institucionais/cartilha-manual-ou-tutorial/maturidade-de-projetos

[2] BRAZILIAN FEDERAL COURT OF ACCOUNTS. Decision 2718/2025 — Plenary. TC 000.866/2025-3. Session of Nov. 18, 2025. Available at: https://pesquisa.apps.tcu.gov.br/resultado/acordao-completo/%2A/COLEGIADO%253A%2522Plen%25C3%25A1rio%2522%2520NUMACORDAO%253A2718%2520ANOACORDAO%253A2025

[3] 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

Frequently asked questions

What does iPMP mean?

iPMP stands for Project Maturity Perception Indicator. It is a TCU tool for assessing, in a structured way, the maturity of planning for public infrastructure projects.

Does a high iPMP score guarantee project success?

No. The TCU itself emphasizes that the indicator is diagnostic and advisory. A high score indicates the presence of most structural elements, but does not eliminate exogenous risks, specific deficiencies, or later execution problems.

Does a low iPMP score automatically prevent bidding?

Not automatically. A low score functions as a technical warning signal. The analysis should identify which actions and dimensions are weak, the materiality of those gaps, and which corrections are necessary before deciding to proceed.

Is the iPMP merely a document checklist?

No. The methodology requires analysis of the content, intent, and quality of the evidence. The mere existence of a preliminary technical study, design, estimate, or risk matrix does not prove that the corresponding action was adequately fulfilled.

How many actions does the iPMP assess?

The TCU guide published in 2026 uses 46 actions distributed across the strategic, economic, commercial, financial, and managerial dimensions.

Can the iPMP be used as a self-assessment before bidding?

Yes. The guide also presents the tool as support for governance, management, and self-assessment. Preventive use makes it possible to identify gaps and structure corrective actions before they are transferred to the bidding documents and contract.

What is the relationship between iPMP and Design Review?

The iPMP provides a broad investment-maturity framework. Design Review can materialize part of the technical response by reviewing design consistency, interfaces, requirements, risks, and documents before proceeding to the next phase.

Additional technical materials

Related services

• Design Review in Engineering Projects: revisão técnica, interfaces e maturidade do projeto
• Preliminary Technical Study for Engineering Works and Services
• Technical Planning for Engineering Procurement
• Technical Review of Bidding Documents and Attachments for Engineering Procurement

Core content on this topic

• What the TCU Reviews in Procurement of Engineering Works and Services
• Planning the Procurement of Engineering Works and Services
• Preliminary Technical Study for Engineering Works and Services
• Risk Management in Public Works

Related technical content

• Public Works Estimating
• Risk Allocation Matrix in Engineering Contracts
• Design Review in Engineering Projects
• From Preliminary Technical Study to Technical Acceptance
• 7 Maturity Gates for Public Engineering Investments