Audit Trail
For reviewers and governance teams: understand which question, sources and review steps shaped a result.
Traceability
Sources and version changes belong beside the result. Export formats, retention periods and hash procedures require separate evidence.
Example
Illustrative example · fictional documents
Until when is the anchor tenant’s rent secured at Lindenhof?
Lease · v1 · p. 8 · §12
The addendum is signed by the tenant only and the rent roll still shows 2030. Check whether the addendum is effective before it enters the WALT or the valuation.
The fixed term until 2030 is linked to Lease v1, p. 8, § 12.
Lease · v1 · p. 8 · §12
The addendum is signed by the tenant only and the rent roll still shows 2030. Check whether the addendum is effective before it enters the WALT or the valuation.
The 2nd addendum extends to 2033 with a break option in 2031; the rent roll shows 2030. The deviation stays open.
Lease v1, p. 8 / 2nd addendum v2, p. 2
The addendum is signed by the tenant only and the rent roll still shows 2030. Check whether the addendum is effective before it enters the WALT or the valuation.
A specialist confirms whether the addendum is effective before the lease end enters the WALT.
Lease v1, p. 8 / 2nd addendum v2, p. 2
The addendum is signed by the tenant only and the rent roll still shows 2030. Check whether the addendum is effective before it enters the WALT or the valuation.
Handover
Give the reviewer the question, sources, version changes and open points. The example does not establish legal admissibility or immutable storage.
Next step
Scope, source quality and access rights are agreed before deployment. Pricing and implementation time are clarified individually.
Product principles, not a production or legal assurance.
Public positioning and illustrative examples. Individual deployment requires separate verification.
