Asset Management Documentation Standards
Executive Summary
Key Takeaways
- ✓ An infrastructure asset's operating life frequently outlasts the original model builder's and asset manager's own tenure by decades, making documentation an institutional continuity requirement here more acutely than in most shorter-horizon financial models.
- ✓ Every material assumption, condition data source, renewal cost estimate, discount rate, should be documented with its specific source and the date it was established, not left as an unattributed input figure in the model itself.
- ✓ Documentation should record not just the current assumption but the history of prior assumption changes and the reason for each change, since understanding why an assumption was revised is often as valuable as knowing its current value.
- ✓ Documentation quality should itself be assessed periodically, since documentation that was thorough at the model's original build can still degrade through successive undocumented updates over a long operating life.
- ✓ Poor documentation is itself a form of model risk distinct from a formula error, since even a structurally correct model becomes effectively unverifiable once its underlying assumption sourcing is lost.
Objective¶
This guide covers documentation standards specific to infrastructure asset management financial models, within Infrastructure Asset Management Financial Modelling, addressing an institutional continuity risk this pillar's models face more acutely than most.
Why This Pillar's Models Face an Elevated Documentation Risk¶
An infrastructure asset's operating life frequently spans thirty to eighty years, well beyond the tenure of the original model builder, asset manager, or even the commissioning organisation's current leadership. Undocumented assumptions — why a specific renewal timing was chosen, where a maintenance cost estimate originated — become effectively unverifiable once the individuals who set them have moved on, a risk considerably more acute here than in a transaction model that is built, used, and closed out within a few years.
Documenting Assumption Sourcing¶
Every material assumption — condition data, renewal cost estimates, the discount rate applied in a whole-life cost comparison — should be documented with its specific source (a condition survey reference, an independent technical adviser's report, a specific contract clause) and the date it was established. An assumption left as an unattributed figure embedded in the model itself, with no traceable origin, cannot be assessed by a future reviewer for whether it remains appropriate.
Recording the History of Changes, Not Just the Current Value¶
Documentation should record the history of prior assumption changes and the specific reason for each revision, not only the assumption's current value. Understanding why an assumption was revised — in response to new condition data, a changed regulatory standard, or a corrected earlier error — is often as valuable to a future reviewer as knowing the assumption's present figure, particularly when assessing whether a past change was itself well-founded.
Documentation Quality Degrades Without Active Maintenance¶
Documentation that was thorough at the model's original build can still degrade over a long operating life through successive updates that are not held to the same documentation discipline as the original construction. Documentation quality should itself be periodically assessed as part of Operations Model Assurance, rather than assumed to remain at its original standard indefinitely.
Poor Documentation as a Form of Model Risk¶
Poor documentation is itself a distinct form of model risk, separate from a structural formula error. Even a model that is entirely correctly formulated becomes effectively unverifiable once the sourcing behind its key assumptions is lost, since a reviewer, whether an internal successor, an external auditor, or a future acquirer's due diligence team, cannot assess whether an assumption remains appropriate without knowing its origin and rationale.
Common Construction Pitfalls¶
Unattributed assumptions. Embedding a material assumption in the model with no documented source leaves it unverifiable once the individual who set it has moved on.
Current value only, no change history. Recording only the present assumption value, without the history and rationale of prior revisions, loses information valuable to assessing whether the assumption trajectory itself has been sound.
Documentation discipline applied only at initial build. Allowing documentation quality to degrade through undocumented later updates undermines the value of a thorough original build.
Recommended Practices¶
- Document every material assumption's specific source and the date it was established.
- Record the history of prior assumption changes and the reason for each revision.
- Periodically assess documentation quality as part of ongoing model assurance.
- Treat documentation gaps as a distinct form of model risk warranting remediation.
Continue Reading¶
Related Pillars¶
Related Technical Guides¶
Related Glossary¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
Why does documentation matter more for asset management models than for many other financial models?
Because an infrastructure asset's operating life frequently outlasts the original model builder's and asset manager's own tenure by decades, and undocumented assumptions become effectively unverifiable once the institutional knowledge behind them is lost, a risk more acute here than in a shorter-horizon transaction model reviewed and closed within a few years.
What should be documented for each material assumption?
Its specific source, a condition survey, an independent technical adviser's report, a specific contract term, and the date it was established, rather than leaving the assumption as an unattributed figure embedded in the model with no traceable origin.
Why should documentation record the history of assumption changes, not just the current value?
Because understanding why an assumption was revised, in response to new condition data, a changed regulatory standard, or a corrected error, is often as valuable as knowing its current value, particularly for a reviewer trying to assess whether a past change was well-founded.
Why should documentation quality itself be periodically assessed?
Because documentation that was thorough at the model's original build can still degrade through successive undocumented updates over a long operating life, as later updates are made without the same documentation discipline applied to the original build.
Is poor documentation itself a form of model risk?
Yes. Even a structurally correct model becomes effectively unverifiable once its underlying assumption sourcing is lost, since a reviewer cannot assess whether an assumption remains appropriate without knowing where it came from and why it was set at its current value.
References
Related Articles
Infrastructure Asset Management Financial Modelling
Infrastructure asset management financial modelling is the discipline of modelling an infrastructure asset's ongoing operation, maintenance, and renewal across its full economic life, from the perspective of the owner or operator responsible for that asset once it is in service, rather than the transaction-close or lender perspective covered elsewhere. This page is the hub for the Knowledge Centre's asset management and operations modelling content: how a lifecycle model is structured across planning, construction, operations, renewal, and disposal, how whole-life cost and lifecycle cost analysis compare competing options, and how maintenance, renewal, and capital replacement should be planned and funded. Sector-specific operations models, performance and reliability modelling, and institutional assurance practice for this domain are indexed here as it expands.
Asset Register
An asset register is the structured inventory of an owner's infrastructure assets, recording each asset's identity, location, original cost, installation date, condition, and criticality, among other attributes. It is the foundational data source from which asset management plans, whole-life cost models, and renewal forecasts are all built, and its completeness and accuracy directly determine the reliability of every downstream financial model that depends on it.
Infrastructure Operations Audit
An infrastructure operations audit tests the structural integrity of an asset owner or operator's ongoing operations financial model, formula correctness across revenue, cost, reserve funding, and renewal forecasting, distinct from a project finance model audit scoped to a transaction and debt tenor. This guide covers what an operations audit tests, how it differs from the periodic asset performance review, and how findings should be reported to asset owners and their oversight bodies.
Long-Term Asset Governance
Long-term asset governance establishes the accountability structure, escalation path, and reporting discipline that keeps an infrastructure asset management financial model genuinely governed across a multi-decade asset life, well beyond the tenure of any individual asset manager or board member. This guide covers how governance should be structured so it survives personnel turnover, how a renewal funding gap should escalate to a body with actual funding authority, and what a governing board needs to see to exercise real oversight.
Model Documentation Standards for Financial Models
Model documentation standards define what written records must accompany an institutional financial model to enable its outputs to be understood, verified, and relied upon by parties other than its original developer. The minimum documentation package for an institutional financial model includes an assumption log recording the source and rationale for every input, a version history recording all material changes, a model map describing the structure and purpose of each worksheet, instructions for use, and a disclosure of known limitations. The ICAEW Financial Modelling Code and the FAST Standard both establish specific documentation requirements that define institutional expectations.