Nobody is hiding anything. That's the problem.

A resident reports a leaking tap in the car park on a Tuesday.

Eleven weeks later it is still leaking, and by now four separate people have reported it, one of them twice. At the AGM someone finally says it out loud, and the room does the thing every strata room does: it looks for a villain. The building manager? The committee? The body corporate manager? Somebody must have dropped this.

Here is the uncomfortable truth. Usually nobody dropped it. Usually the tap sat in a completely reasonable queue, behind a completely reasonable set of steps, and every single person in the chain did roughly what you would have done. It just took eleven weeks, because nothing anywhere told anybody how long it had been sitting or who was holding it.

That is not a people problem. That's a process problem wearing a people problem's clothes.

The anatomy of eleven weeks

Trace it backwards and it's almost always the same shape.

Week 1. The tap is reported verbally to the building manager in the lift. No record exists anywhere. It is now stored in exactly one human brain.

Week 2. The BM has forty other things in flight and gets to it. Plumber comes, quotes $3,400 for the isolation valve and the pipework behind it.

Week 3. The BM emails the quote to the chairperson, because that's who they deal with. The chairperson reads it on a phone at a soccer game and means to forward it. The chairperson is a good person having a busy month.

Week 5. The chairperson forwards it. Two committee members reply "seems high, can we get another one?" Two do not reply at all, not because they object, but because it arrived in a thread they were only cc'd on.

Week 7. Second quote obtained: $3,900. Nobody says anything for a while, because there is now a decision to make and no obvious moment at which to make it.

Week 9. Committee meeting. Someone asks whether the first quote is still valid. Nobody knows. Action item: check.

Week 11. First quote has expired. Back to the start.

Read that list again and find the villain. There isn't one. There is a chain of reasonable people, each of whom could only see their own link.

The law already assumes you have a process

This is the part that surprises people.

In Queensland, the framework is built on the assumption that a scheme is running an orderly process, and it puts clocks and thresholds around it:

• The committee spending limit defaults to the number of lots multiplied by $200, for a 30-lot building, $6,000. Beyond that, the committee can't simply authorise it.
• The major spending limit defaults to the number of lots multiplied by $1,100, capped at $10,000. Above that, at least two quotes must be obtained, and they have to go out with the meeting notice.
• A motion submitted by an owner must be decided within six weeks. The committee can buy more time only by writing to that owner inside the six weeks, saying why it needs longer and giving a reasonable new deadline, and only by up to another six. Miss it and the motion is taken to have not passed.
• A committee vote outside a meeting requires the secretary, or a committee member the others have authorised, to notify all committee members in writing, and all owners, at the same time. Members get 21 days to return written votes, and a record of the motion has to reach every committee member and owner within 21 days of it being decided.

Now go back to the eleven-week tap. At which point did anyone know which threshold applied? At which point could anyone have told you what day the clock started?

The obligations are already precise. It's the buildings that are vague.

Why this happens to good committees

Because the committee is quite possibly the last job in Australia that carries a legal duty, a budget, and no handover.

You get elected at an AGM. Nobody gives you the list of open jobs, because there is no list of open jobs. The knowledge lives in whoever has been there longest, in a personal inbox, on a whiteboard in a plant room, or in the head of a building manager who has been carrying this building's memory unpaid for six years.

Then a resident asks you, in the lift, what's happening with the tap, and you have three options. Guess. Say you'll find out. Or say the honest thing, which is that you have no idea, and watch the trust in the building drop another notch.

Do that four or five times and people stop reporting things. Not because they've stopped caring, but because reporting felt like shouting into a well. And a building where people have stopped reporting things is quietly accumulating deferred maintenance that nobody has written down.

Now the dirty word

Say "transparency" in a strata meeting and watch the temperature change.

It lands as an accusation. It implies concealment, and therefore a concealer, and everyone starts working out whether it's meant to be them. Committees stiffen. Managers get careful. Perfectly good people start saying "appropriate" and "in due course."

Which is a shame, because operationally transparency is not an audit and not a charge. It means something dull: anyone affected by a job can see what state that job is in.

Not the money. Not the emails. Not the personalities. Just: reported, being triaged, quotes coming, recommended, at vote, approved, done.

And it does the opposite of what committees fear. Visibility doesn't invite attack, it absorbs it. When residents can see a job is at "waiting on second quote," they stop emailing about it. When they can see nothing, they assume nothing is happening, and they email repeatedly, and now the committee has a second job: managing the emails about the first job.

Opacity doesn't protect a committee. It just moves the work.

So we built the boring version

I run NaloHub, a resident portal for strata buildings. It isn't a strata management platform and it doesn't replace your body corporate manager. It does one narrow thing seriously: it gives a building a defined maintenance process and a visible record, and it takes the two worst delays out of it.

Every job runs through six named stages, and it can only be in one at a time:

Reported → Triaged → Quotes in → Recommended → At vote → Contractor confirmed.

A resident reports it in the portal with a photo, so it starts life as a record instead of a memory. The building manager triages it, attaches quotes, and writes a recommendation, a real sentence, on the record: "Recommend Harrison at $2,800; higher, but they hold the parts locally and can be here Thursday." Every stage change is timestamped with who made it. Residents see where their report is up to and what it's waiting on.

And then the part that actually kills the eleven weeks

When the job needs a committee decision, the building manager clicks Send to vote. That's it, the motion is created straight off the maintenance job and stays linked to it, so the decision and the thing it was about never come apart.

Every committee member sees it at once. Nobody is merely cc'd on somebody else's email thread. They vote from a phone in about twenty seconds, and they can attach a question, a comment, or a condition of approval, "approved subject to the drain being scoped first", which is how committees actually decide things, rather than a bare yes or no.

The moment the required majority is reached, it executes itself, and the outcome stays attached to the maintenance job. When someone asks about that decision at an AGM three years later, it's still sitting next to the quotes it relates to.

To be clear about what this is and isn't: it runs and records the committee's decision. Your secretary still gives owners their notice and their record of the motion, and it's still worth checking the entitled-to-vote count when a member has declared a conflict. This removes the chasing, not the obligations.

Then there's a Maintenance Report, pick a date range, get a Word document. Every issue, its updates, its quotes, the works approved, the committee decision, the full trail, and the photos. Minute-ready. That's the thing that replaces forty minutes of a committee meeting spent reconstructing what happened.

Week 3 to week 9 in the story above becomes an afternoon. Not because anyone worked harder, because nobody had to be found, reminded, or forwarded anything.

The test

Take these four questions to your next meeting. They sound administrative. They aren't.

1. How many maintenance items are open in this building right now? If nobody can answer within a minute, the building doesn't have a list. It has several partial lists in different people's heads.
2. What's the oldest one, and what is it waiting on? The oldest open job in a building is the most honest thing about it.
3. When we approve spending between meetings, where does that decision live? If the answer is "an email thread," you're one phone upgrade away from having no record of it.
4. If our building manager left on Friday, what would we lose? Write the list. It's normally longer and more alarming than anyone expects.

Buildings don't get better because someone tries harder. Everyone is already trying hard. They get better when the process gets defined and the state gets visible, and the same effort starts producing a different result.

You can walk through a fully populated demo building at demo.nalohub.com, no signup, nothing to install. Poke at it. Break it. Tell me what your building does that it doesn't handle.