Before you fix the problem, diagnose the environment. The Fixed Asset Health Assessment evaluates the applicable lifecycle and operating environment, identifies root causes rather than symptoms, and produces a prioritized roadmap for remediation and improvement.
It exists because the most expensive fixed asset decisions are usually made without a current, evidence-based picture of how the environment actually works. A balanced register is not the same thing as a healthy one, and a clean audit is not the same thing as a controlled process.
A balanced register is not a healthy environment
Most organizations discover their fixed asset environment is fragile at the worst possible moment: mid-implementation, mid-audit, mid-acquisition, or the week after the one person who understood the process gave notice.
The assessment is designed to surface that fragility while there is still time to act on it — and to do it with evidence, so the findings are something leadership can fund and sequence rather than argue about.
What leadership receives
Findings written to be acted on, not filed.
Current-state health & maturity view
Where the environment stands across the dimensions that apply to you, in language finance and operations leadership can both use.
Material findings & supporting evidence
What we found, where we found it, and why it matters — with the evidence attached so the finding stands on its own.
Root-cause themes
The small number of underlying causes that explain the long list of symptoms.
Risk & consequence prioritization
What to address first, based on exposure and consequence rather than on what is easiest to fix.
Cross-functional dependencies
The upstream and downstream relationships that determine whether a fix will hold.
Quick wins
The changes that are worth making immediately, independent of any larger program.
Future-state recommendations
A defensible target operating environment for people, process, data, systems and controls.
Sequenced transformation roadmap
The order of operations: what has to be true before the next thing can succeed.
How the assessment runs
Structured, evidence-based, and built to avoid disrupting the close.
-
01
Scoping
Define which entities, systems, asset classes and lifecycle stages are in scope, and who needs to be part of the conversation.
-
02
Evidence gathering
Working sessions with the people who do the work, plus review of policy, documentation, system configuration, data extracts and reporting.
-
03
Analysis
Findings tested against the register, the general ledger and the process as it actually runs — not as it is described.
-
04
Root-cause synthesis
Symptoms grouped into causes, and causes traced to the part of the environment that produces them.
-
05
Prioritization & roadmap
Findings sequenced by risk, dependency and effort into a roadmap leadership can fund.
-
06
Readout & handoff
A leadership readout, the supporting detail, and a clear recommendation on what should happen next.
When an assessment is the right next step
- A software implementation, migration or upgrade is being considered, planned or recovered.
- CIP is aging, project closeout is slow, or capitalization timing is inconsistent.
- The register no longer reliably reconciles, or reconciliation has become a manual event.
- An audit, acquisition, divestiture or restructuring is putting weight on fixed asset data.
- A key person has left, is leaving, or is the only one who knows how something works.
- Leadership does not trust the fixed asset numbers it is being given, and cannot say why.
Investment
Fixed Asset Health Assessment engagements start at $25,000. Enterprise environments — multi-entity, multi-system, or unusually complex lifecycles — are scoped after a conversation and typically range from approximately $50,000 to $100,000+.
Scope drives price. The health conversation establishes complexity before anything is quoted.
Common questions
How is a Fixed Asset Health Assessment different from an audit?
An audit tests whether the reported numbers are materially correct. The assessment examines whether the environment producing those numbers is sound — governance, policy, process, data, systems, controls, security, reporting, documentation and knowledge dependency — and what it will cost you if it isn't.
How long does an assessment take?
Timeline depends on scope: how many entities, systems and asset classes are in play, and how available the people who do the work are. Focused assessments run in weeks; enterprise assessments across multiple systems and entities run longer. Duration is agreed during scoping, before the engagement begins.
Do we need to fix everything the assessment finds?
No. The output is prioritized on purpose. Findings are sequenced by risk, consequence and dependency, with quick wins separated from work that belongs in a funded program, so leadership can decide what to act on and in what order.
Can the assessment be limited to one system or one area?
Yes. Scope can be narrowed to a single system, entity, asset class or lifecycle stage — a Sage Fixed Assets environment, for example, or CIP and project closeout only. Narrower scope still follows the same method.