What it means
Under IFRS, IAS 16 calls for review of residual value and useful life at least each financial year-end, with changes accounted for as changes in estimates under IAS 8, although other accounting frameworks may differ. Define the in-scope assets first, since land, work in progress and disposed assets may not follow the same depreciation review, and use the entity's reporting date and policy to set the review period rather than an arbitrary annual sticker.
For assets acquired late in the year, distinguish the first estimate on recognition from a subsequent review, and do not force an asset not yet available for use into an in-service depreciation assessment. Maintenance trends, operating hours, planned upgrades and obsolescence can inform estimates, and a technical manager can provide condition evidence while finance decides accounting treatment under the entity's applicable standards.
Preserve both inputs and the final judgement, and document expected usage rather than relying on age alone, because age does not prove an asset has exactly two years remaining. Compare real utilisation and maintenance history with the assumptions behind the estimate, since unused equipment may still age while heavy use can shorten expected service even if the model is unchanged.
A review does not require a changed estimate to be complete, since an unchanged estimate can be supported by current evidence and a signed explanation, and the review should cover residual value too. When expected use changes, the revised depreciation estimate is normally applied prospectively under the applicable framework, so document the supporting evidence and approval date and involve the accounting owner rather than quietly rewriting prior results.
Watch for assets still in use after their recorded life ends, which can signal a stale estimate but does not automatically prove earlier depreciation was erroneous. Impairment is a separate question, because an adverse event can require an impairment assessment even if a useful-life review is otherwise current.
Consider components, since major components may have different depreciation patterns, and group assets carefully, since a homogeneous asset class can use a documented collective review if you show why units have similar usage and expected replacement cycles. High-value outliers and material exceptions need individual attention even when a fleet-level trend looks stable.
Reconcile reviewed assets to the financial fixed-asset register and note additions and disposals, and review disposals separately from assets held for sale because the classification and depreciation treatment can change under the applicable framework. Record the review date, assumptions, evidence source, who provided expected use, physical wear and technological changes, and finance approval, retaining the prior estimate, the newly approved estimate and the date of change so a reader can see how the next depreciation charge was derived.
An unchecked annual checkbox without updated evidence should not meet the checklist. Coverage is a process metric, not a valuation opinion, so flag overdue reviews and report coverage both by count and by carrying amount, since a high count rate can hide one large unreviewed asset.
Make due status transparent, because a review performed after year-end may resolve a backlog without establishing that the year-end control ran on time. Set an evidence threshold for old but fully working assets, where operations can show maintenance and planned continued use while finance decides whether the remaining life estimate should be extended.
In practice
Real-world examples.
Example
A fleet review documents revised operating hours and leaves the current estimate unchanged.
Example
An obsolete machine receives a shorter estimated life after finance reviews the technical case.
Example
A newly acquired asset is added to the next scheduled review population under policy.
Formula
Calculation
Coverage = In-scope depreciable assets with completed useful-life reviews by the due date / All in-scope assets due for review x 100. Report material values separately.
Worked example. A company has 400 in-scope assets due for review with a total carrying amount of $20,000,000. Reviews with documented evidence are completed by the due date for 340 assets with a carrying amount of $16,000,000.
- Coverage by count: 340 / 400 x 100 = 85%
- Coverage by carrying amount: $16,000,000 / $20,000,000 x 100 = 80%
- One unreviewed asset with a carrying amount of $2,500,000 is 12.5% of the total ($2,500,000 / $20,000,000), so it is reported as a material exception.Case study
Seen in the real world.
This entirely fictional case follows Harbor Milling. Production hours fell after a product change. Maintenance supplied service-life evidence and finance reviewed the estimates. One machine's life was revised; the others retained their assumptions with reasons documented. No actual depreciation calculation or accounting conclusion follows from this fictional example.
Watch out
Common mistakes.
- Marking every asset reviewed without recorded assumptions.
- Treating a completed review as proof useful life must change.
- Confusing useful-life review with an impairment conclusion.
Questions
People also ask.
Must useful life change each year?
No. Review the estimate; change it when new evidence supports a change.
Can a class be reviewed together?
Possibly, with a documented method and attention to material exceptions.
Does this apply under every accounting standard?
No. Check the entity applicable framework and policy.
From the founder's library

Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related
