Your fixed assets are always telling you something. A handoff that stalls every quarter and gets rescued by the same person every quarter. A report nobody double-checks anymore because it has always looked about right. A process that, followed all the way back, turns out to live entirely in one person's head — and they are excellent, and they are also retiring in eighteen months.

Most of it goes unheard, and I want to be clear about why: not carelessness. These signals are quiet, they arrive in the middle of a close, and there is always something louder happening in the same week. So they wait patiently until they turn up as an audit finding, a write-off, or the one that actually costs the most — a capital decision made confidently on information nobody knew had drifted.

Here is the genuinely encouraging part, and it is the reason I love this work: the signals are consistent. Across twenty-seven years, hundreds of environments, every platform and every industry, the early warning signs show up in the same fourteen places. Fourteen is a short enough list to actually listen at. You do not need a project, a budget cycle or a vendor to start — you need fourteen honest questions and an afternoon.

The fourteen places to listen

1. Governance & ownership

Is it clear who owns a decision when an asset needs one — or does it get passed around until someone acts?

This is the first place I look, and it is almost always the most productive. Decisions that belong to nobody still get made; they just get made by whoever is standing closest to the deadline. Naming an owner for each stage of the lifecycle is the cheapest structural improvement available in this entire field.

2. Policy

Do your written policies match what people actually do day to day?

Written policy and practiced policy drift apart slowly and without anyone deciding to let them. When they do, the practiced version usually reflects real operating pressure the written one never accounted for — which means the fix is often to update the document, not to discipline the practice.

3. Process

Where do handoffs stall, get skipped, or survive purely on someone's memory?

The seams are where fixed asset environments break, not the steps. Projects to accounting, procurement to the register, facilities to finance. Every seam that runs on a person remembering is working beautifully right up until the week they are out.

4. People

Do the people running this process have the capacity and the standing to do it right?

Capability and authority are two different questions, and both matter. I meet extraordinarily talented fixed asset people who know exactly what should happen and have no standing to require it of another department. That is an organizational design issue, and it is very fixable once it is named out loud.

5. Data

Can you trust where a number in your asset register actually came from?

Lineage is the quiet hero of asset data. A cost you can trace to a source document is defensible; a cost that appeared during a conversion four systems ago is a story you will be telling an auditor without notes. This is also why dirty data in still means dirty data out, no matter how capable the system you move it into.

6. Systems

Are your systems configured to catch a problem, or only to record it after the fact?

Modern fixed asset platforms can enforce a great deal — thresholds, required fields, approval paths, in-service logic. Most are configured to accept whatever they are handed. The capability is usually already licensed and simply never switched on, which makes this one of the most satisfying findings to deliver.

7. Controls

If an entry were missing or wrong, would anything catch it — or would it pass through?

The useful test is not whether you have controls. It is whether you can name the specific control that would stop a specific error. Reconciliations that always tie are worth a second look; sometimes they tie because they are genuinely clean, and sometimes because they are being balanced to.

8. Documentation

Are your procedures and work instructions still current, or do they describe how things used to work?

Documentation that describes a prior system is not neutral — it actively trains new people into the wrong process. Current documentation, on the other hand, is the mechanism by which good practice outlives the person who invented it.

9. Integration

What breaks when two systems need to agree with each other and don't?

Integration is where I find the most manual bridges: the export, the reformat, the paste, the reconciliation nobody has automated because the workaround has been holding fine. Each bridge is a person's judgment standing in for a rule, and judgment does not scale across a portfolio.

10. Knowledge dependency

How much of this depends on tribal knowledge that isn't written down anywhere?

Tribal knowledge is evidence of expertise, and the people carrying it are usually the reason the environment works at all. The risk is not the knowledge — it is that the organization has no copy. Capturing it is a way of honoring that expertise, not auditing it.

11. Security & access

Who can change a number that affects the balance sheet, and should they be able to?

Access tends to be granted generously during an implementation and reviewed approximately never. The question is not who you trust; it is whether a change can be attributed after the fact. Traceability protects the people doing the work as much as it protects the numbers.

12. Reporting & information delivery

Does the report someone is making decisions from reflect what's actually true today?

Reporting is where symptoms surface, which is exactly why it is a poor place to look for causes — the whole argument in The Fixed Asset Problem Isn't Always in Fixed Assets. Consistent definitions, a known refresh cadence, and a number leadership can ask a second question about: that is the standard.

13. Risk

What's the real exposure if this one thing goes unnoticed for another year?

This question converts a long list of imperfections into a short list of things that matter. Some gaps are genuinely cosmetic and deserve to stay open. Others carry audit, tax, insurance or capital-decision consequences that grow quietly with every reporting cycle. Sizing them is what makes prioritization possible.

14. Performance

Is this taking longer, costing more, or getting redone more often than it should?

Rework is the most honest metric in fixed assets. When the same reconciliation is rebuilt every month, or a close step expands year over year, the environment is paying interest on an unresolved decision upstream. That effort is recoverable, and teams feel the difference immediately.

Most organizations are listening in two places

Almost every environment I walk into is watching Data and Reporting closely — which makes complete sense, because those are the two that generate visible pain. The other twelve are where the gaps accumulate, and they surface later, further downstream, wearing a costume: a reconciliation issue that began in project setup, a software complaint that turns out to be configuration and training, a data problem that is really a governance question nobody has been asked to answer.

That is also why sequencing matters more than speed here. Automating on top of an unexamined environment produces a faster version of what you already have, which is the case I make in Don't Automate a Broken Fixed Asset Process. And as live building models and AI-assisted tooling reach this space, they will be generous to organizations that fixed the handoffs first and merciless about coordination for the ones that did not.

Listening at all fourteen

You can start this yourself today. Take the fourteen questions to the people who actually touch the lifecycle — projects, procurement, accounting, tax, facilities, IT — and ask them plainly. The answers you get quickly are your strengths. The ones that produce a pause, or three different answers from three departments, are exactly where the signal is.

A Fixed Asset Health Assessment is the structured version of that conversation: all fourteen dimensions, across the full lifecycle, with evidence attached and a sequence for what to address first. Not a verdict on your team — a clear read on an environment, while there is still plenty of room to move.

Your assets have been talking the whole time. Fourteen places, and the listening is the easy part.