The Difference Between Doing And Demonstrating
One of the interesting things about marathon timing chips is that their value only becomes obvious after the race is finished.
During the race, the chip sits quietly in the background. The runner is focused on the course ahead, not the small piece of technology attached to a shoe or race bib.
Only afterwards does the timing chip become important.
A runner can still complete a marathon without one.
What becomes harder is demonstrating the result.
Completing something and being able to demonstrate completion are not the same thing.
The same distinction appears in property and asset management more often than people realise.
The Leak Was Never The Beginning
Consider a property with a large gum tree growing close to a building.
For years, it attracts little attention. Then one autumn brings more leaves than expected, a gutter blocks, and months later water appears where it shouldn't.
When the leak is discovered, it naturally becomes the focus.
People want to know what caused it.
How serious it is.
What should happen next.
Yet the more interesting questions often point in the opposite direction.
Was the risk visible before the leak occurred?
Did anyone notice it?
Was anything done about it?
The leak may be the first visible sign of a problem, but it is rarely the first chapter.
Looking Back
One thing that stands out in property operations is that important questions often arrive later.
Not when an inspection takes place.
Not when maintenance work is completed.
Not even when a decision is made.
The questions arrive when somebody looks back and tries to understand what happened.
By then, the conversation is no longer about what should have happened.
It is about what actually happened.
What was known at the time?
What action was taken?
Can we show it?
Why Evidence Matters
Across this series we have explored efficiency, structured data and visibility.
At first glance, those ideas may seem unrelated.
They are not.
One of the realities of property and asset management is that important questions often arrive much later than expected.
By the time they do, the discussion is rarely about what should happen next.
It is usually about understanding what happened before.
Was the risk identified?
Was action taken?
What do we know for certain?
The answer often depends on something surprisingly simple.
The quality of the records that already exist.
That is why inspections matter more than they first appear.
They do more than identify issues on a particular day.
They create a record of events while they are still fresh, visible and understood.
Months or years later, that record may be the only reliable way to understand what happened.
Good organisations do the work.
Increasingly, they are also expected to demonstrate that the work was done.
And that process often begins with something as simple as an inspection.