Why strata councils keep falling back on Excel (and what it's costing them)

A new treasurer joins the council, eager and organized, and asks the obvious question: where do we keep track of all this? The answer arrives as an email attachment a few days later. Building_Tracker_2021.xlsx. It was built by an owner who rotated off council two years ago—a genuinely good spreadsheet, color-coded tabs, a maintenance log, a contractor list.

The new treasurer opens it and starts reading. The maintenance log stops in late 2022. There's a tab labelled "Quotes – DO NOT DELETE" with three rows and no dates. One contractor is listed twice under slightly different names. A column header just says "status," and every cell beneath it is blank. The person who knew what all of it meant is gone, and the file has been sitting in someone's inbox ever since, quietly going out of date.

So the new treasurer does the reasonable thing. They start a fresh spreadsheet. Building_Tracker_2024.xlsx. And the cycle begins again.

If you've been on a strata council in British Columbia, you know this file. Maybe you built it. The spreadsheet isn't the villain here—it's often the most competent thing a council has ever done. But it keeps failing strata councils in the same predictable way, and it's worth understanding why.

The spreadsheet is a genuinely good tool

Let's be fair to Excel. It's free or close to it. Everyone has used one. You can set up a maintenance tracker in an afternoon, and for a single person tracking a single building over a single year, it works really well. There's a reason councils reach for it instead of buying software—the spreadsheet is right there, and it does the job in front of you.

The problem isn't the tool. It's that a strata's records aren't a one-person, one-year job. They're a shared, multi-year, multi-handover responsibility—and that's exactly the situation a personal spreadsheet was never built for.

Where it quietly breaks

It lives with one person. A spreadsheet sits on whoever built it—their laptop, their personal cloud drive, their email. When they rotate off council, the file rotates off with them. Sometimes it gets forwarded along; sometimes it doesn't. Either way, the next person inherits a file they didn't design, with conventions they have to reverse-engineer.

It goes stale in the handover. This is the real killer. A spreadsheet is only as current as the last person who maintained it, and a handover is exactly when maintenance stops. The outgoing member's final weeks are busy. The file gets sent, then sits. By the time the new council opens it, it's months out of date and nobody's sure which parts are still true. A record that isn't continuously updated isn't a record—it's a snapshot of one moment that's already passed.

Versions multiply. "FINAL," "FINAL_v2," "FINAL_updated_Mar." The moment two people are editing two copies, you have two partial truths and no way to know which is right. Email attachments make this worse—every send creates a fork.

It captures the what, not the why. This is the deepest limitation, and no amount of formatting fixes it. A row reads: Roof repair – $14,200 – June 2023. That tells you it happened. It doesn't tell you the work was warranty-covered, that the contractor was excellent and worth calling again, or that the council chose a patch over a full replacement to buy time for budgeting. The number survives. The reasoning—the part a future council actually needs—doesn't fit in a cell, so it never gets written down.

What it's actually costing

It's tempting to think of a stale spreadsheet as a minor inconvenience. It isn't, because of what councils use these records to decide.

A strata council is a group of volunteers overseeing what's effectively a multi-million-dollar asset. In BC, strata fees commonly run from around $0.30 to $0.75 per square foot per month, and councils set those fees by approving an annual budget at the AGM. Since November 2023, they're also legally required to contribute at least 10% of the operating budget to the contingency reserve fund every year. These are real financial decisions, made annually, by people who often inherited a half-current spreadsheet and a vague sense of what's been done to the building.

When the record is stale or incomplete, the costs are quiet but real: paying for an inspection that was already done last year, re-hiring a contractor the previous council had crossed off, budgeting for a repair that was already handled, or deferring one that was more urgent than anyone realized. Every one of these traces back to the same root—the record didn't carry forward, so the council made the decision blind.

It was never the spreadsheet's fault

Here's the part worth sitting with. None of this means councils are disorganized or that Excel is bad. It means a personal tool is being asked to do an institutional job.

A spreadsheet belongs to whoever made it. A strata's history needs to belong to the building—a record that doesn't live or die with one volunteer, doesn't go stale the moment someone rotates off, and carries the reasoning forward, not just the numbers. That's a different kind of thing than a file in someone's inbox. The spreadsheet was never going to be that, no matter how good the color-coding was.

The next council shouldn't have to start Building_Tracker_2027.xlsx. They should be able to pick up exactly where the last one left off.