Learn how technical due diligence for assets and facilities works: scope, documentation, site inspection, condition, risks, CAPEX, priorities and action plan.
Check it out!
Technical due diligence for assets and facilities is a structured, evidence-based assessment designed to reduce uncertainty before a significant decision: acquisition, investment, modernization, contracting, renewal, expansion, or assumption of responsibility for existing infrastructure. The work cross-checks documentation, physical condition, performance, compliance, criticality, and risks to transform an unfamiliar installed base into a technical assessment with priorities and recommendations.
Due diligence should not be confused with a simple visual inspection, a document audit, or a single-discipline technical report. The scope must be proportional to the decision to be made and to the consequences of incorrect or missing information. In complex facilities, the result may guide CAPEX, upgrades, engineering design, contingencies, contracts, maintenance, and asset management.
What is technical due diligence for assets and facilities?
Technical due diligence seeks to determine whether the actual condition of the assets is compatible with the intended use, which risks are present, which gaps must be addressed, and which technical and financial commitments may arise after the decision.
In an acquisition, it reduces the risk of purchasing infrastructure with hidden technical liabilities. In a modernization project, it helps identify what can be retained and what requires upgrading. In operations, it can establish a baseline for a master plan, asset management, or renewal strategy.
The term is broad. RICS uses technical due diligence for technical assessments of commercial and industrial property and emphasizes that the scope should be adapted to the asset type, purpose, and jurisdiction. ASTM E2018-24, focused on property condition assessments, likewise treats the process as a baseline subject to uncertainty and adjustable to user objectives. These references are useful as methodological principles, but they do not replace Brazilian standards, legal requirements, or discipline-specific specialists where applicable.
Due diligence is a decision process, not a form
A checklist may support data collection, but it is not the primary intellectual product. The value lies in interpreting evidence and distinguishing isolated defects, systemic risks, obsolescence, nonconformities, missing documentation, and investment needs.
Two facilities with the same defect may receive different recommendations if their criticality, redundancy, future use, and recovery capability differ.
When to perform technical due diligence
The most familiar timing is before acquiring an asset or property, but there are several other applications.
| Situation | Main question | Decision supported by the assessment |
| Acquisition or investment | Does the asset have significant technical liabilities? | Buy, negotiate, condition the deal, or withdraw |
| Modernization | What can be safely reused? | Define scope and CAPEX |
| Operations/maintenance contracting | What baseline is being handed over to the contractor? | Define responsibility and SLA |
| Expansion | Can the existing infrastructure support new demand? | Reinforce, replace, or expand |
| Operator transition | What condition and documentation are being received? | Handover and technical acceptance |
| Master planning | Which systems require intervention first? | Investment roadmap |
| Asset management | What risks and conditions exist across the installed base? | Prioritize maintenance, renewal, and contingency |
The decision determines the depth of the scope
A major acquisition may require a multidisciplinary investigation, document review, specialist inspections, and investment estimates. A retrofit decision may focus on interfaces, capacity, condition, and implementation risks.
A scope that is too narrow creates false confidence. An excessive scope consumes resources without changing the decision. The definition must make clear what will be assessed and what will remain outside the engagement.
Due diligence, technical reports, inspections, audits and assessments: differences
These terms may appear together, but they are not equivalent.
| Type of work | Focus | Typical output | Limitation when used alone |
| Inspection | Observe condition and anomalies | Field records and findings | May not assess risk, documentation, or the decision itself |
| Technical report | Answer a defined technical question | Conclusion and professional technical responsibility | Usually has a specific scope |
| Audit | Verify adherence to defined criteria | Conformities and nonconformities | May not prioritize CAPEX or alternatives |
| Technical assessment | Explain condition and causes | Technical understanding and recommendations | May not be linked to a transaction or executive decision |
| Due diligence | Reduce uncertainty for a decision | Risks, gaps, priorities, limitations, and action plan | Strongly dependent on scope and available evidence |
Due diligence may incorporate inspections, technical reports, and audits when required.
How to define the technical scope
When a decision involves acquiring, assuming responsibility for, or modernizing existing infrastructure, the main risk is contracting or investing before understanding liabilities, capacity, condition, and documentation gaps. Due diligence establishes a technical baseline before the commitment is made.
The scope should start from the objective, the nature of the assets, and the risk profile. In building, industrial, or mission-critical facilities, disciplines may include civil, architecture, electrical, lightning protection, HVAC, plumbing, fire protection, automation, telecommunications, electronic security, utilities, and power systems.
The list should be calibrated. There is no need to include every possible discipline when it does not affect the decision.
Physical scope and information scope
Assessing only the field condition is not sufficient when the decision requires evidence of capacity, compliance, or history. Likewise, up-to-date documents do not guarantee that the actual installation matches the design.
The scope should state which documents will be reviewed, which areas will be inspected, which systems will be sampled, and whether testing or measurements will be performed.
Materiality criteria
Materiality defines what deserves attention in proportion to the decision. A cosmetic defect may be irrelevant in an industrial acquisition; a seemingly small issue in electrical protection may have a critical consequence.
Materiality may consider safety, continuity, cost, correction lead time, regulatory impact, spare-parts availability, obsolescence, and expansion capacity.
Document review: what to look for before going to site
Documents help build hypotheses and prepare the site inspection. Drawings, diagrams, technical specifications, certificates, technical records, reports, contracts, maintenance history, plans, work orders, tests, failure records, warranties, and asset inventories can reveal the maturity of the installed base.
Missing documentation is also a finding. However, the absence must be qualified: which document is missing, why it matters, which decision is impaired, and what action is required.
As-built documentation must be checked against actual conditions
In brownfield environments, documents may have been technically correct when issued and become outdated after years of modifications. The value of due diligence lies in comparing records with field conditions.
Discrepancies can affect safety, maintenance, future engineering design, and investment estimates.
Site inspection: evidence, sampling, and limitations
The site inspection should be guided by the scope and by hypotheses developed during document review. Photographs, asset tags, readings, access conditions, signs of degradation, and system interfaces help build traceability.
A basic due diligence does not require dismantling or testing every asset. However, when a material condition cannot be determined visually, the team should recommend additional investigation rather than imply a level of certainty that the evidence does not support.
Sampling must be disclosed
In large facilities, inspecting every component may be impractical. Sampling should be technically coherent and explicitly described in the report.
A sample may prioritize critical assets, different ages, manufacturers, areas, and operating conditions. Recurring findings may justify expanding the sample.
Condition assessment: more than “good, fair, or poor”
Generic ratings are fast, but they are not very actionable without defined criteria. Condition should be related to function, degradation, evidence, and consequence.
An old piece of equipment is not automatically in poor condition. A new one may also be inadequate because of installation, specification, or operating regime.
Condition, obsolescence, and capacity are different dimensions
An asset may be physically well preserved and technologically obsolete. Another may still have vendor support but operate close to capacity. A third may perform well but lack redundancy compatible with its criticality.
Separating these dimensions improves the recommendation.
| Dimension | Question | Typical evidence |
| Physical condition | Is there degradation or a defect? | Inspection, testing, history |
| Performance | Does it deliver the required function? | Measurements, logs, indicators |
| Capacity | Can it support current and projected demand? | Load data, calculations, margin |
| Obsolescence | Are support, spare parts, and updates available? | Manufacturer, market, contracts |
| Compliance | Does it meet applicable requirements? | Design, standards, documentation, field evidence |
| Maintainability | Can it be adequately inspected and repaired? | Access, procedures, spares |
| Resilience | How does it respond to failures and component loss? | Redundancy, contingency, tests |
How to analyze technical risks
ISO 31000:2018 provides principles and a process for risk management and remains current. It is not a standard specific to due diligence, but it offers a useful basis for identifying, analyzing, evaluating, and treating risks in a structured way.
Technical risk must be described as a scenario. “Old switchboard” is not a complete risk statement. A better formulation might be: failure of an obsolete component with no available spare part could prolong the outage of a critical system beyond the period compatible with the operational objective.
Probability, consequence, and exposure
Matrices help communicate risk, but they should not replace the scenario description. Consequences may involve safety, operations, finance, the environment, compliance, or schedule.
High uncertainty must also be communicated. Sometimes the greatest risk is not having sufficient evidence to determine the condition.
How to turn findings into priorities
Recurring findings, critical assets without redundancy, or failures whose consequences exceed routine maintenance require reliability analysis and, in many cases, an engineering decision on redesign, renewal, or contingency.
A list of hundreds of findings without prioritization simply transfers the problem to the client. The report must distinguish urgency, materiality, and intervention horizon.
System criticality, finding severity, likelihood of deterioration, redundancy, cost, and correction lead time help determine priority.
Not every finding requires immediate construction work
Some findings call for monitoring, complementary testing, or document updates. Others require maintenance, engineering design, component replacement, or capital intervention. The action should correspond to the failure mechanism and the risk.
| Type of finding | Possible treatment | Example output |
| Insufficient evidence | Investigate | Testing, opening, measurement, survey |
| Documentation discrepancy | Update documentation | As-built, asset records, technical file |
| Isolated defect | Correct through maintenance | Planned work order and acceptance criterion |
| Systemic risk | Develop engineering solution | Study, design, retrofit |
| Obsolescence | Plan renewal | Roadmap and CAPEX |
| Insufficient capacity | Expand or redistribute | Load study and design |
| Significant nonconformity | Upgrade and control risk | Prioritized action plan |
The chart below is illustrative and hypothetical; it does not represent an actual facility. It shows how consolidating findings by severity can make a long findings list more useful for executive decision-making.
Reading the chart does not replace the risk matrix. Two findings with the same severity may require different intervention horizons if one has redundancy and the other represents a single point of failure. The grouping helps direct attention, while the final decision must return to the technical scenario and the evidence.
CAPEX: how to estimate without creating false precision
Due diligence often needs to indicate the order of magnitude of required investments. This estimate is not a detailed construction budget when there is no completed design, full quantity takeoff, or final specification.
The maturity of the estimate must be stated. Values may be parametric, conceptual, or based on market references, but assumptions and contingencies must be consistent with the level of uncertainty.
Immediate CAPEX, short-term investment, and lifecycle needs
Separating investments by time horizon improves decision-making. Critical corrections may require immediate expenditure; obsolescence may justify renewal in two or three years; expansions may depend on demand growth.
The report should avoid adding every identified risk as though all investments were simultaneous and certain.
How to consider OPEX and maintenance
An installed base with high maintenance cost, recurring downtime, or fragile service contracts may require a different decision from a technically similar base with good operational predictability.
Backlog, failure, spare-parts, consumption, and contract data help estimate future operational effort.
Poor history may matter more than a good snapshot
Equipment may appear well maintained during an inspection yet have a history of recurring failures. Due diligence must combine observed condition with behavior over time.
Due diligence and asset management
ISO 55000:2024 and ISO 55001:2024 help connect findings to lifecycle management. When an organization already has, or intends to implement, an asset-management system, due diligence can feed asset registers, criticality assessments, risk registers, renewal plans, and decision criteria.
The work then stops being a report that quickly becomes outdated and becomes a baseline for continuous management.
Asset registers and hierarchy improve report traceability
Each finding should be associated with the relevant asset, system, or location. Asset tags and hierarchy allow actions to be converted into engineering projects, work orders, or portfolio items without losing context.
Due diligence for electrical installations
For electrical systems, the scope may include distribution architecture, capacity, selectivity, protection, switchboard condition, substations, grounding, lightning protection, documentation, safety, and technical records as applicable.
Thermography can be useful as a complementary technique, but it is not synonymous with electrical due diligence. Testing and engineering studies should be defined according to risk and objective.
Inspection safety may limit access
Opening energized panels or accessing hazardous areas requires procedures, qualifications, and safe conditions. If a necessary inspection cannot be performed, the limitation should be recorded and treated as uncertainty.
Due diligence for mission-critical systems
Data centers, hospitals, industrial plants, and essential infrastructure require a strong focus on continuity. In these environments, it is not enough to verify that equipment operates; teams must understand dependencies, single points of failure, redundancy, autonomy, recovery, and testability.
The same philosophy applies to telecommunications, electronic security, automation, and critical utilities.
Due diligence before retrofit and modernization
Brownfield projects fail when engineering begins without understanding existing conditions. Due diligence reduces this risk by mapping interfaces, capacity, documentation, access, obsolescence, and operational constraints.
The result may indicate additional studies before detailed design, preventing incorrect assumptions from being incorporated into the procurement scope.
Due diligence and procurement
In procurement processes, due diligence can help structure the technical scope or terms of reference. By understanding actual conditions, the client reduces ambiguity, separates existing liabilities from new scope, and establishes measurement and acceptance criteria.
This also improves proposal comparability. Suppliers respond to a technically described problem rather than a generic request.
How to structure the final report
The report should allow a decision-maker to understand material issues quickly while enabling the technical team to trace each conclusion back to supporting evidence.
A robust structure includes objective, scope, limitations, methodology, documents reviewed, condition, findings, risks, evidence, recommendations, and an action plan.
The executive summary should not hide uncertainty
The summary may classify critical issues, but it must preserve relevant limitations. If a system could not be tested or essential documents were unavailable, that information should be visible at the executive decision level.
The action matrix should have an owner and a time horizon
Each significant action should indicate the expected owner, priority, time horizon, dependencies, and type of deliverable: maintenance, testing, engineering design, procurement, CAPEX, or monitoring.
How to specify a technical due diligence engagement
A well-defined engagement states the objective, scope, disciplines, assets, available documentation, access conditions, measurement requirements, report format, classification criteria, and expectations regarding CAPEX.
It should also clarify exclusions. If invasive testing, detailed structural analysis, or legal-compliance validation are not included, this must be stated.
Avoid requiring a conclusion that the scope cannot support
It is not technically reasonable to ask for certification that everything is compliant when the work provides only a sample-based visual inspection. The conclusion must be compatible with the evidence obtained.
Limitations and uncertainty: mandatory parts of good due diligence
Every due diligence engagement has limits. Systems may be in operation, areas may be inaccessible, documents may be missing, and defects may be hidden.
The professional must distinguish fact, evidence, inference, and recommendation. Disclosing uncertainty does not weaken the report; it increases its reliability.
A finding not observed does not mean the problem is absent
Sampling and nondestructive inspection have limitations. The report should avoid generalizations beyond what the evidence supports.
Common mistakes in technical due diligence
A common mistake is using a generic checklist without considering the intended use of the asset. Another is assessing risk only by visual appearance. It is also common to mix opinion, fact, and hypothesis in the same conclusion.
Other failures include CAPEX without assumptions, lack of photographic evidence, no linkage between findings and assets, vague recommendations, and omission of access limitations.
When due diligence should evolve into engineering design or Owner’s Engineering
When due diligence reveals multiple upgrade workstreams, the next step is not simply to execute construction. Risks must be transformed into requirements, studies, engineering designs, procurement packages, and acceptance criteria with technical governance.
After the assessment, the most material findings may require studies, surveys, engineering designs, and specifications. At that point, due diligence ends and solution development begins.
Owner’s Engineering can support procurement, technical bid evaluation, implementation, supervision, testing, and acceptance, preserving the logic of the assessment through delivery.
Continuity between assessment and execution reduces the risk of the report becoming merely a reference file.
Final considerations
Technical due diligence for assets and facilities is a tool for reducing uncertainty before decisions that commit risk, capital, and operational performance. Its value depends on a proportionate scope, traceable evidence, multidisciplinary analysis, and the ability to turn findings into priorities.
For existing assets, the most useful conclusion is rarely simply compliant or noncompliant. A better deliverable shows what exists, what is unknown, which risks matter, what actions are required, and when they should enter maintenance, engineering, or CAPEX.
Technical references
[1] ROYAL INSTITUTION OF CHARTERED SURVEYORS. Technical due diligence of commercial property, 1st edition. 2023. Available at: https://www.rics.org/profession-standards/rics-standards-and-guidance/sector-standards/real-estate-standards/technical-due-diligence-of-commercial-property.
[2] ASTM INTERNATIONAL. ASTM E2018-24 — Standard Guide for Property Condition Assessments: Baseline Property Condition Assessment Process. 2024. Available at: https://store.astm.org/standards/e2018.
[3] INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 31000:2018 — Risk management — Guidelines. 2018. Available at: https://www.iso.org/standard/65694.html.
[4] INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 55000:2024 — Asset management — Vocabulary, overview and principles. 2024. Available at: https://www.iso.org/standard/83053.html.
[5] INTERNATIONAL ORGANIZATION FOR STANDARDIZATION. ISO 55001:2024 — Asset management — Asset management system — Requirements. 2024. Available at: https://www.iso.org/standard/83054.html.
Frequently asked questions
It is a structured assessment of documentation, condition, performance, compliance, and risks designed to reduce uncertainty before a decision involving assets, facilities, or investments.
It is useful for acquisitions, expansions, modernization, operator transitions, maintenance contracting, CAPEX planning, master planning, and other decisions involving existing infrastructure.
No. A technical report normally answers a defined technical question. Due diligence integrates different types of evidence and disciplines to support a broader decision.
No. The need for testing depends on the objective, risk, and limitations of visual inspection. When condition cannot be determined with available evidence, the report should recommend additional investigation.
Yes, provided that the maturity of the estimate and its assumptions are stated. Without detailed design, values are typically conceptual or parametric rather than a detailed construction budget.
Due diligence is the investigation and analysis process. The report is the document that consolidates the evidence, risks, limitations, recommendations, and action plan resulting from that process.
Additional technical resources
Related services
Key content on this topic
- Technical Due Diligence Report: evidence, risk matrix, and action plan
- Brownfield Projects: engineering in existing facilities, surveys, as-built documentation, and retrofit
