The month closes. The pack gets assembled. Someone presents it, and everyone in the room treats the numbers as a picture of the business.

They're not, quite. They're a picture of the business as it was, and some of those numbers stopped being true well before anyone printed them. Not because anybody made an error. The figures are accurate. They've simply passed their half-life, and nothing on the page tells you which ones.

Every number in your portfolio has one: a period after which it stops describing reality closely enough to be worth acting on. Some of your numbers have half-lives measured in years. Others are finished within a week. And most property companies report all of them, indiscriminately, on the same monthly cycle.

Not All Data Decays At The Same Speed

This is the part that gets missed, and it's the whole argument.

Think about the actual shelf life of the things in your reporting pack. A lease term signed in March is still the lease term in September. Your entity structure hasn't moved in years. That data is close to permanent, and reporting it monthly is a mild waste of everyone's attention.

Now look at the other end. A maintenance backlog from three weeks ago tells you almost nothing about the backlog today; the queue has turned over several times. Delinquency shifts daily. A prospect who inquired on Tuesday has, by Friday, either toured somewhere else or gone quiet. This data has a half-life measured in days, sometimes hours.

So your portfolio contains information with useful lives ranging from an afternoon to several years, and you push all of it through one pipe, on one schedule, at one speed. Which means the monthly pack is simultaneously too frequent for half your data and far too slow for the other half. The slow numbers clutter it. The fast ones arrive long past their useful life.

Why You're Always a Step Behind

There's a useful frame for this from an unlikely place. John Boyd was a US Air Force fighter pilot and strategist who built a model of how decisions actually work under pressure: observe, orient, decide, act, then loop back and do it again. It's usually just called the OODA loop, and it's been borrowed by everyone from military planners to executives.

Here's a good overview connecting Boyd's loop to data.

Boyd's real insight wasn't that faster is better in some vague motivational sense. It was sharper: what wins is your tempo relative to the environment. If you can cycle through observe-orient-decide-act faster than the situation changes, you shape it. If the situation changes faster than you can complete a loop, you spend your life reacting to something that has already gone.

Apply that to a property company. Your Observe step is the reporting pack. If it arrives three weeks after the events it describes, and your portfolio meaningfully changes every week, you never complete a loop against current reality. You orient on a snapshot whose half-life expired before it reached you, decide about conditions that have already shifted, and act into a situation you can't see. You're not slow, exactly. You're operating in a different time period from your own company.

The Month is an Accounting Convention, Not a Fact About Your Business

Ask why you report monthly and the honest answer is: because that's how accounting works. The month is a closing period, a rhythm inherited from the ledger.

Somewhere along the way that rhythm got adopted as the rhythm of management, and nobody stopped to check whether the business actually changes on a monthly beat. It doesn't. It changes on a dozen beats at once, and none of them is thirty days. The accounting calendar is a compliance requirement, and nothing about it was ever designed to match the half-life of your maintenance queue.

Nothing On The Page Tells You Which Numbers Are Still Alive

Here's what makes this genuinely dangerous rather than merely annoying: a decayed number looks exactly like a fresh one.

Occupancy and delinquency sit side by side, same font, same two decimal places, carrying the same air of authority. One of them is still broadly true. The other passed its half-life a fortnight ago. Nothing distinguishes them, so nobody discounts anything, and every figure gets acted on with the confidence its precision implies.

If the pack came stamped with a decay rate beside each line, people would read it correctly and ask for something fresher before committing. It doesn't, so they don't.

A Slow Close Deletes Decisions, It Doesn't Just Delay Them

Finance tends to treat a slow close as an inconvenience: the information lands late. That badly understates it.

A twenty-five-day close doesn't postpone decisions. It removes them. Anything that needed deciding inside that window either got decided without numbers, on instinct and memory, or never got decided at all, and you never see the second category. There's no line item for the intervention you couldn't make because you didn't know in time.

Which means the payoff from closing faster isn't the speed. It's that a whole class of decisions moves from unavailable to available.

Match The Cadence To The Half-Life

The fix isn't "make everything real-time." That's the vendor answer, and it's wrong, because it treats all data as equally urgent when most of it isn't.

The actual discipline is to match how often you look at a number to how fast it decays:

• Long half-life (lease terms, entity structure, capital plans) can genuinely wait for the periodic pack. Looking more often adds noise, not insight.

• Medium half-life (rent roll, occupancy, renewal pipeline) wants a weekly rhythm. A month is long enough for it to drift somewhere you'd want to know about.

• Short half-life (delinquency, maintenance backlog, active inquiries) needs to be continuously visible, because by the time it reaches a monthly pack it has been through several half-lives and has almost no information left in it.

And keep two things separate that most firms have quietly merged. The accounting close is a compliance rhythm; it happens monthly because it must. Operational visibility is a decision rhythm, and it should run at whatever speed the underlying reality moves. When those two collapse into one, the compliance rhythm wins, and your operational data inherits a cadence it was never suited to.

Half-Life Versus How Often You Actually Look

Every row reports at the same frequency. Only two of them should.

How To Tell If You're Running on Expired Numbers

• Pick a figure from your last pack and ask how old the underlying event actually is, not when the report was produced. The gap is usually wider than anyone assumes.

• Notice which decisions get made without reference to any number at all. Those are the ones where the data arrives after its half-life, so people default to instinct. That's where the cost is.

• Ask whether anything in the pack is ever surprising. If the numbers only confirm what the team already knew from being on the ground, the reporting isn't informing decisions. It's documenting them afterward.

• Look at what people actually read. The parts nobody opens are usually the long half-life data. The parts they wish they'd had sooner are the short half-life data. Your team has already diagnosed the cadence problem; nobody has written it down.

The Takeaway

Accuracy is not the same as usefulness. A number can be perfectly correct and completely worthless, because the reality it described moved on and the number stayed where it was.

So the question worth asking isn't whether a number is correct. It's whether it's still alive. Sort your data by how fast it decays, look at each kind at the speed it actually changes, and stop letting a closing convention set the tempo at which you see your own business. Boyd's point holds: what determines whether you're in control isn't the quality of your plan, it's whether you can see and respond faster than the ground moves underneath you. Collapsing that gap, so operational reality and the financial record are one live record rather than one being reassembled from the other weeks later, is much of what a connected operating model, and platforms like RIOO, are for. The separate question of which numbers you should be watching, and how choosing them quietly reshapes your team's behavior, is taken up in the metrics you report are shaping the business you get.

FAQ

1. What does it mean that portfolio data has a half-life?
It means every number has a period after which it stops describing reality closely enough to act on. The figure isn't wrong; it has simply decayed. Lease terms stay accurate for years, while a maintenance backlog or delinquency figure can be meaningfully out of date within days.

2. Why is reporting everything monthly a problem?
Because your data decays at very different rates, and a single cadence can't serve all of it. Monthly is unnecessarily frequent for slow-moving data like lease terms, and far too slow for fast-moving data like delinquency or the maintenance queue, which has passed through several half-lives before the pack is even printed.

3. Doesn't this just mean we need real-time dashboards?
Not exactly. Making everything real-time treats all data as equally urgent, which it isn't. The discipline is to match how often you look at a number to how fast it decays: leave long half-life data on the periodic pack, move medium data to a weekly rhythm, and make genuinely short half-life data continuously visible.

4. What does the OODA loop have to do with reporting?
John Boyd's model, observe, orient, decide, act, holds that control comes from your tempo relative to how fast the environment changes. Your reporting is the observe step. If it describes conditions from three weeks ago while the portfolio shifts weekly, you're orienting and deciding against a business that no longer exists.

5. What is the real cost of a slow month-end close?
More than delay. A slow close removes decisions from the table entirely, because anything that needed deciding during the closing window either happened without numbers or didn't happen at all. Those missing decisions never appear as a cost anywhere, which is exactly why the true price of a slow close is routinely underestimated.