Assumption Documentation explained: this guide covers what it means, who it applies to, the step-by-step process, documents required, fees, due dates and penalties in India — so you can stay compliant with confidence and avoid costly mistakes.
Defensible disclosures are the output of a disciplined process, not a drafting exercise. The distinction that matters is between contemporaneous professional judgement and retrospective justification.
The principle
Material assumptions should be documented as they are developed and evaluated, rather than reconstructed during report drafting or subsequent scrutiny.
A structured record of the assumption, the supporting evidence, the validation performed and the rationale for its adoption establishes a clear audit trail linking professional judgement to the valuation conclusion.
Documentation of this kind promotes consistency, facilitates review and quality control, and enables the valuer to demonstrate the basis on which material assumptions were adopted. But the reason given as most important is different in kind:
it helps ensure that the report reflects contemporaneous professional judgement rather than retrospective justification.
A reason constructed after a challenge may be entirely true and still be worthless as evidence, because nothing establishes that it was the reason at the time. This is the same standard that requires site inspection records to be prepared contemporaneously — and the reason a well-supported conclusion documented only after the event is difficult to defend.
The six assumption documentation tools
| Tool | What it does |
|---|---|
| C.1 Assumption Documentation Framework | A structured template for documenting material assumptions, supporting evidence, validation procedures and report disclosures |
| C.2 Assumption Classification Matrix | Categorises assumptions by materiality, uncertainty and disclosure requirements |
| C.3 Limiting Condition Review Matrix | Documents assignment-specific limitations, alternative procedures and residual risks |
| C.4 Discount Rate Documentation Template | A framework for the derivation, sources and justification of discount rate components |
| C.5 Materiality Assessment Matrix | Identifies assumptions requiring enhanced justification, disclosure and review |
| C.6 Assumption-Evidence Cross Reference Matrix | Links assumptions to supporting evidence, verification procedures and workpaper references |
How the assumption documentation tools fit together
- C.2 sorts the assumptions by materiality and uncertainty, so effort is allocated proportionately rather than evenly.
- C.5 confirms which of them cross the threshold for enhanced justification and review.
- C.1 records each material assumption with its evidence, validation and intended report disclosure.
- C.4 handles the discount rate separately, because it is the input most often disclosed as a single figure and most often challenged for it.
- C.3 captures the limitations that are not assumptions at all — the constraint, the alternative procedure, the residual risk.
- C.6 closes the loop, tying every assumption to the workpaper that supports it.
Why C.6 is the one that answers a challenge
The assumption-evidence cross reference is the assumptions equivalent of the work file traceability rule — that every material conclusion should be capable of being traced back to specific evidence. A reviewer who wants to know what supports a 1.5% company-specific risk premium should be able to move from the disclosure to the evidence in one step, not through a reconstruction of the valuer's reasoning.
Why C.4 exists as a separate tool
The discount rate is where the gap between weak and defensible disclosure is widest. A single sentence stating a rate "reflecting the risk profile of the company" is technically correct and analytically empty; a component-wise derivation naming the risk-free source and its date, the equity risk premium source, the peer group behind the beta, the re-levering, and each element of the company-specific premium answers the "So What?" test line by line. C.4 exists because that derivation has to be built during the analysis, not assembled afterwards.
Assumption documentation as part of the process
Collectively these tools are designed to integrate assumption development, validation, documentation and disclosure into a coherent and defensible valuation process — which is the same position documentation occupies generally: not an administrative requirement, but an integral part of the valuation itself.
Common mistakes
- Building the assumption documentation at drafting stage from memory.
- Recording the assumption and the evidence but not the validation performed.
- Disclosing a discount rate without retaining the component derivation.
- Keeping an assumption log with no cross reference to the workpapers.