Model Handover
Executive Summary
Key Takeaways
- ✓ Model handover is the structured transfer of a financial model, its documentation, and operational responsibility from one owner to another.
- ✓ Inadequate handover is one of the most common sources of model risk in organisations relying on Excel-based models.
- ✓ A complete handover includes the model file, documentation, input data sources, version history, and a formal knowledge transfer process.
- ✓ Handover failures manifest as operational errors, assumption drift, broken model updates, and compliance failures in ongoing reporting.
- ✓ Auditors should verify documentation completeness, version continuity, data source access, and evidence of structured knowledge transfer.
Definition¶
Model handover is the structured process by which responsibility for a financial model — including operational ownership, update obligations, and decision-making authority — is formally transferred from one individual or team to another. It encompasses the transfer of the model file, all associated documentation, version history, and the knowledge required to operate the model correctly and safely.
Model handover occurs in several contexts: when a staff member leaves an organisation, when a project transitions from development to operations, when an advisory firm concludes an engagement and returns a model to the client, or when model ownership is reassigned within a team.
Why It Matters¶
Financial models are frequently built by individuals who develop deep contextual knowledge of the model's structure, assumptions, and limitations over time. This knowledge typically exists in the builder's head rather than in the model's documentation. When the builder leaves or transitions to another role, the organisation loses access to that knowledge simultaneously with losing the person.
The consequences of an inadequately documented model handover include:
- Operational errors: The new owner makes incorrect updates because they do not understand the model's mechanics
- Assumption drift: Key assumptions are changed by the new owner without understanding their basis or implications
- Broken model: Structural changes to the model by an inexperienced new owner render it unreliable
- Decision risk: Decisions made using a model that the decision-maker does not understand or that has been incorrectly modified
- Audit failure: An independent reviewer cannot verify a model that has no documentation
Model handover failures are one of the most common and underappreciated sources of model risk in organisations that rely heavily on Excel-based financial models.
Technical Background¶
What a Complete Model Handover Includes¶
A complete model handover package covers five categories:
1. The Model File The current approved version of the model, in a format that the recipient can open and operate. If the model is version-controlled, the version history should be included or accessible. If the model is macro-enabled, the VBA code should be documented separately.
2. Model Documentation A document (separate from the model itself) that describes: - The purpose of the model and the decisions it is used to inform - The structure of the model: worksheets, sections, and their relationships - The key assumptions, their sources, and the basis for each - Any known limitations, edge cases, or conditions under which the model should not be used - Instructions for operating the model: inputs, outputs, update procedures - Contacts for questions about the model's methodology or assumptions
3. Input Data Sources Documentation of all external data inputs used by the model: where the data comes from, how frequently it is updated, and what the update procedure is. If the model connects to external files or databases, this dependency must be documented.
4. Version History and Change Log A record of material changes made to the model over its history, who made each change, when, and why. This enables the new owner to understand how the model evolved and to assess whether any historical change may have introduced an issue.
5. Handover Meeting and Knowledge Transfer Documentation of a formal handover meeting at which the outgoing owner walked the incoming owner through the model, answered questions, and confirmed that the incoming owner understood the model sufficiently to operate it. A handover checklist completed and signed by both parties provides evidence of this process.
Model Documentation Standards¶
The model documentation produced as part of a handover should address the following at minimum:
| Section | Description |
|---|---|
| Purpose and scope | What the model does and what decisions it supports |
| Model structure | Overview of sheets and their functions |
| Input register | List of all key inputs, their current values, and their sources |
| Assumption register | List of key assumptions, the basis for each, and when they were last reviewed |
| Output summary | Description of key outputs and how they should be interpreted |
| Update procedure | Step-by-step instructions for performing routine model updates |
| Known limitations | Conditions or inputs outside the model's tested range |
| Contact list | Who to contact with questions about methodology, data, or assumptions |
Handover in Advisory and Transaction Contexts¶
When a financial adviser builds a model during a transaction and then hands it to the client at engagement end, the handover process is particularly important because:
- The client may have had limited involvement in building the model
- The client will need to update and operate the model without access to the adviser
- The model may be used for ongoing covenant compliance, refinancing analysis, or investor reporting long after the adviser is no longer engaged
Best practice in an advisory context is to conduct the handover before the end of the engagement, while the adviser is still available to answer questions and assist with any issues identified by the client during initial operation.
Handover in Project Finance¶
In project finance, model handover typically occurs at financial close, when the financial adviser's model transitions to the project company's ongoing operational model. The project company is then responsible for:
- Running the model to calculate covenant compliance at each test date
- Updating the model with actual cash flows and revised forecasts
- Presenting the model outputs to lenders in compliance certificates
- Maintaining the model under the change management provisions of the loan agreement
A project company that receives an inadequately documented model at financial close faces the risk of compliance errors in the operational phase — including incorrect DSCR calculations or missed covenant tests.
Audit Considerations¶
1. Documentation Completeness¶
When reviewing a model that has recently been handed over, confirm whether a handover package was prepared and whether it is current. A model with no documentation is a governance finding regardless of the quality of the model itself.
2. Knowledge Transfer Evidence¶
Confirm whether the handover was a structured process with documented evidence of completion, or an informal transfer (the previous owner emailed the file and left). The latter creates significant operational risk.
3. Version Continuity¶
Confirm that the model currently in use is the same version as the one that was validated or certified. Version drift — where the model has been informally modified since the last formal review — is a common handover failure.
4. Input Source Documentation¶
Verify that the new model owner can identify and access all input data sources used by the model. A model whose inputs depend on data sources that only the previous owner had access to is operationally broken.
5. Update Procedure Testing¶
Where possible, confirm that the incoming model owner has successfully performed the model's routine update procedure. A handover that has not been tested by the new owner in practice is not complete.
Common Errors¶
| Error | Description | Risk |
|---|---|---|
| No documentation prepared | Model transferred as a file only with no supporting documentation | New owner cannot understand or safely operate the model |
| Outdated documentation | Documentation describes a previous version of the model | Documentation is misleading |
| Verbal-only handover | Knowledge transferred verbally with no written record | Knowledge is lost when the recipient also leaves |
| Data source access not transferred | New owner cannot access data sources used by the model | Model cannot be updated |
| No handover testing | Incoming owner not confirmed to have operated the model successfully | Handover appears complete but is not |
| Macro code undocumented | Model contains VBA macros with no documentation of their purpose | New owner cannot assess or safely modify the automation |
Best Practices¶
Treat model documentation as a mandatory deliverable at every stage of the model lifecycle, not only at handover. A model that is documented as it is built requires minimal additional effort to hand over. A model that has never been documented requires significant reconstruction effort before it can be handed over safely.
Conduct handovers with sufficient notice to allow time for the new owner to develop familiarity with the model before the outgoing owner is unavailable. Handovers conducted under time pressure — when a staff member is leaving immediately — rarely produce complete knowledge transfer.
Use a standardised handover checklist that both the outgoing and incoming owners sign. This creates accountability, ensures completeness, and provides evidence that the handover process was followed.
Continue Reading¶
Prerequisites¶
- What Is Financial Model Governance? — the parent pillar
Related Pillars¶
Related Glossary¶
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
What is the minimum documentation required for a model handover?
At minimum: the purpose of the model, the structure of the sheets, the key inputs and their sources, the update procedure, and the known limitations. A model handed over without these elements creates operational risk for the new owner.
Who is responsible for model handover documentation?
The outgoing model owner is responsible for preparing the handover documentation. The organisation's model governance framework should specify documentation standards and require their completion before a handover is considered complete.
How long should a model handover process take?
This depends on model complexity. A simple operational model might require a single documented meeting. A complex project finance or investment model may require several sessions over one to two weeks. The test is whether the incoming owner can operate the model independently at the end of the process.
Does a model handover require re-validation?
Not necessarily. Handover does not change the model's content. However, if the incoming owner makes material changes during or after handover, those changes should be subject to the applicable change management and validation requirements under the model governance framework.
Related Articles
Model Governance
Model governance is the organisational framework through which an institution defines, implements, and enforces policies and controls for the development, approval, use, validation, change, and retirement of financial models. It establishes accountability for model quality, a structured process for model oversight, and a documented record of model use and validation history. Effective model governance ensures that decisions made using financial models are based on outputs that have been developed to an appropriate standard, validated by a party independent of the developer, and used within the bounds for which they were designed.
Model Inventory
A model inventory (also referred to as a model register or model catalogue) is a centralised, maintained register of all financial models in active use within an organisation. It records, for each model, the information required to govern it effectively: its purpose, owner, developer, validation status, approved use cases, material limitations, and review schedule. The model inventory is the foundational document of a model governance framework. Without a complete inventory, an organisation cannot systematically apply governance controls, cannot assess its aggregate model risk exposure, and cannot demonstrate oversight to investors, lenders, or regulators.
What Is Model Risk?
Model risk is the risk that a decision is wrong not because the underlying business or investment case was flawed, but because the model used to evaluate it was. It is a distinct category of risk from market risk, credit risk, or operational risk, and it applies to any organisation that relies on a financial model, spreadsheet or otherwise, to support a material decision. Most published model risk content addresses statistical and regulatory capital models used inside banks. This page defines model risk specifically as it applies to Excel based financial models, the kind used every day for investment decisions, lending, and transaction evaluation, which is a related but distinct problem from the quantitative model risk literature most search results return.
What Is Financial Model Governance?
Financial model governance is the set of policies, roles, and controls an organisation puts in place to manage the risk that comes from relying on financial models for material decisions. It is the organisational layer that sits above any individual financial model audit: governance determines when a model gets audited, who owns that decision, how versions are tracked, and what happens to findings once they exist. Most published governance content online is written for large, tier one banks operating under formal regulatory regimes. A private equity firm, a family office, or a mid market corporate finance team rarely has that scale of infrastructure, and does not need it, but still carries real exposure if no governance exists at all. This page defines governance at the level that actually applies to most organisations relying on Excel models, not just the largest ones.