Why Information Without Context Creates Problems

Last month, a manager sent a body corporate committee a copy of an electrical safety inspection report.

That’s good. Reports matter. But here’s what came with it: the report. That’s it.

No covering email. No summary. No “Here’s what this means.” Just the report.

The committee didn’t know if the report was showing a minor issue or a major problem. They didn’t know if they needed to act urgently or if it could wait. They didn’t know if the issue was covered by insurance or if the body corporate was exposed.

So they asked the manager about it. The manager replied three days later with a summary. The committee still wasn’t sure if this was something to decide immediately or something to budget for next year.

That’s information without context. And it creates more questions than it answers.

The pattern

This happens constantly in body corporate schemes.

A compliance notice arrives. It gets forwarded to the committee. Nobody explains what compliance means in this context or what happens if you don’t respond.

A contractor’s quote comes in. It gets shared. Nobody outlines the options, the risks, or why the manager is recommending this contractor over the other two.

A legal report is received. It’s forwarded as-is. Nobody explains what the findings mean for the body corporate or what decisions need to happen.

A sinking fund assessment is completed. It’s filed. Nobody explains what it means for owner levies or the building’s long-term financial health.

Information gets moved from point A to point B without the translation layer that would help people understand it.

Why context matters

The problem isn’t that the information exists. It’s that committees are expected to process it without enough scaffolding.

A compliance notice without context feels like a threat. A compliance notice with a sentence explaining “This is a standard annual inspection and the issue is minor” becomes manageable.

A contractor’s quote without context is just numbers. A contractor’s quote with a paragraph saying “We got three quotes. This contractor was middle price but has the best warranty and references. They can start in March” becomes a real decision.

The difference is one paragraph. Sometimes just one sentence.

What “context” actually means

It’s not over-explanation. It’s the layer of meaning that lets people understand why they’re looking at this information.

What is this? A compliance notice is a routine annual safety check. A quote is one of three options we’re comparing. An assessment is a snapshot of the building’s condition at this point in time.

Why does it matter? This affects when we need to act. This affects the budget. This affects how owners experience the building. This affects risk.

What are the options? For some things, you have multiple paths. For others, there’s only one. Make that clear.

What do you recommend and why? The person sending the information usually has a view. They think Option A is better than Option B. Say it. Explain the thinking.

What’s the deadline? When does this need a decision? When does it need action? This context prevents both panic and procrastination.

One paragraph. That’s usually all it takes.

The cost of information without context

Committees spend time trying to interpret things that should be explained. That’s wasted time.

Owners get confused and start asking questions. That’s escalation.

Decisions get delayed because the committee didn’t understand what they were deciding. That’s friction.

Bad decisions happen because the committee thought the information meant something it didn’t. That’s risk.

Or managers end up just deciding things independently because the committee is too confused to weigh in. That’s a breakdown of governance.

All of this comes from forwarding information instead of explaining it.

How to fix this

If you’re managing a body corporate scheme, build a habit:

Before you send anything to the committee, ask: Would they understand what this is and why it matters? If the answer is no, add a covering email. One paragraph explaining context and recommendation.

Make it your standard practice. Always include context.

If you’re on a committee and you receive information that doesn’t include context, ask for it. “What does this mean?” “Why are we looking at this?” “What do you recommend?” Make it clear that raw information isn’t enough.

If you’re an owner and you’re confused by something that’s been communicated, ask. Don’t assume you’re missing something obvious. The information was probably just shared without context.

The difference in practice

Here’s the same electrical report with and without context:

Without context: [Report attached.]

With context: “The annual electrical safety inspection came back showing some wear on the switchboard. It’s not an immediate safety issue, but we should plan to replace it within the next 18 months. I’d recommend budgeting around $8,000 and scheduling it for mid-next year during the normal maintenance window. I’ll bring three quotes to the next meeting for the committee to decide.”

Same information. Different clarity.

The second version takes five minutes to write. It prevents a week of questions and confusion.

The broader principle

Information is only useful when it’s understood. Forwarding something isn’t the same as communicating it.

In body corporate management, your job isn’t to move information from point A to point B. It’s to help people understand what the information means so they can make good decisions.

That’s the difference between information management and genuine communication.

---

Jeff Blaszkowski spent more than two decades in business development before going deep into the body corporate and strata world. Working with Smarter Communities and then Bright & Duggan Group across South East Queensland and Northern New South Wales, he saw the same gaps come up again and again: committees without good options, and owners without clear information. That experience inspired Body Corporate Gold Coast. Jeff is a strata owner, a father of five, and the founder of BCGC. This blog reflects his personal experience and observations from working in the industry and is not legal advice.

If you’d like to talk about how your scheme is managed, or explore what better management could look like for your community, get in touch.