Category: Uncategorized

If you sit on a Management Corporation Strata Title (MCST) council or work as a Building Manager (BM) in Singapore, you already know estate management is a constant game of whack-a-mole. Pumps fail, lights go out, cleaning crews push through their checklists.

But there’s a quieter problem draining money from developments across the island: ghost maintenance. Some in the industry call it phantom billing, and at its worst it crosses into falsified invoicing — where an estate pays for work that was done poorly, done partially, or never done at all.

The contractors involved aren’t always acting in bad faith. The real issue is that the system MCSTs use to verify vendor work is broken by design.

How Ghost Maintenance Happens: The WhatsApp and Service Sheet Loophole

Here’s the standard operating procedure at a typical estate today:

1. The proof: A vendor fixes a corridor light or services an exhaust fan, snaps a “before” and “after” photo, and sends it to the BM over WhatsApp.
2. The sign-off: The technician fills out a paper service sheet and asks the BM to sign it on the spot.
3. The invoice: Weeks later, the vendor’s HQ sends the MCST an invoice, stapled to that signed service sheet as proof of work.

It looks like a paper trail. In practice, it’s a sieve — and each gap is exactly where ghost maintenance and falsified invoicing get through.

• The WhatsApp illusion. A photo of a working pump sent over WhatsApp carries no real context. Was it taken today? At this estate, or the one down the road? Before-and-after photos are trivial to recycle, which makes them a weak defense against falsified invoicing.
• The blind sign-off. BMs are stretched thin. When a technician is standing at the desk asking for a signature, there’s rarely time to climb ten storeys or check the basement first. The BM signs on trust — and once that signature is down, the MCST is on the hook for the invoice.
• The missing history. WhatsApp photos live on personal phones. Service sheets get buried in ring binders. When management changes hands or a new council comes in, that operational history disappears with it. Nobody can tell if a pump was serviced six times or just billed six times — which is exactly how ghost maintenance stays invisible for years.

This process doesn’t protect the estate. It runs entirely on blind trust, and blind trust is what makes ghost maintenance and falsified invoicing possible in the first place.

Closing the Loopholes: How Basementgrid Stops Ghost Maintenance and Falsified Invoicing

We built Basementgrid because property maintenance shouldn’t run on a handshake and a prayer. An estate needs the equivalent of a digital medical record: a permanent, tamper-proof history of the building’s health that no MA transition or lost binder can erase.

Here’s how the platform is designed to shut down ghost maintenance and falsified invoicing at each step of the process.

1. Verified capture stops recycled photos

Vendors can’t upload photos from a camera roll or reuse old images. Every completed job requires a live, in-app photo taken on-site, with a GPS coordinate and a tamper-proof timestamp baked into the file. The system checks that the technician was actually standing next to the asset when the photo was taken — closing off the single easiest way ghost maintenance gets faked.

2. Digital service sheets tied to real asset history

No more paper sheets that get lost or signed without a second look. Service sheets are generated digitally and linked to the asset’s full maintenance history. When a BM reviews a job for approval, they see the verified photos and the technician’s exact check-in and check-out times, not just a line of text asking for a signature.

3. Smart guardrails before payment

Basementgrid connects operations to finance directly, so an invoice can’t slip through unchecked. Every invoice is matched against a verified, closed work order. If a vendor tries to bill for a service with no GPS-verified checkout or no digital sign-off, the system flags it automatically — catching falsified invoicing before payment, not after.

Moving MCSTs from Trust to Data

Trust matters, but it shouldn’t be the main control an MCST relies on to protect its sinking fund. When council members and BMs work from data-verified records instead of paper trails, everyone comes out ahead: good vendors get paid faster because their work is documented beyond dispute, and MCSTs stop losing money to ghost maintenance and falsified invoicing.

It’s time to move past WhatsApp groups and paper binders. Give your estate an operating system that protects both its history and its budget.

Basementgrid is the mobile-native operating system for Singapore’s MCST sector, built to give estates a permanent digital record instead of a folder of loose paperwork.

If you’re a building manager, your day rarely goes the way it’s supposed to. You’re measuring vendor KPIs, staying on top of statutory compliance, handling occupant work requests, walking the estate. If you’re under a managing agent, add agendas, minutes, and council relationships to that list. And somewhere in between all of it, you’re also the person two neighbours call when they’re not speaking to each other anymore.

Estate maintenance is supposed to take up 70% of your time. In reality, you spend more of it patching relationships and calming people down than actually maintaining the estate. That’s not a reflection of how you prioritise, it’s just what the job demands of you. But here’s the part that isn’t fair: owners don’t grade you on how well you kept the peace. They grade you on whether the corridor is clean, the lift works, and there’s no water leak outside their door. You could be quietly holding the estate together and still feel like you’re falling behind, because the visible scorecard is maintenance, not everything else you’re carrying.

Why MAs Actually Get Replaced

90% of the time, an MA isn’t let go because they couldn’t resolve disputes. It’s because work got delayed, something shady was uncovered, or an owner felt brushed off. Slow response, no follow-up, no visibility into what’s happening with their request. Councils rarely fire an MA over a disagreement. They lose trust when things go quiet.

And that’s the frustrating part of this job. You can be doing 80% of it well, handling people, managing relationships, keeping things civil, and still lose the account because the 20% that owners actually see is where the cracks show.

Basementgrid as Your Autopilot

This is the piece Basementgrid takes off your plate. Think of it less like another tool to manage, and more like putting your maintenance process on autopilot. Once the workflow is set up, requests get logged, routed to the right vendor, and tracked automatically. You’re no longer the one manually pushing every ticket forward or holding the whole schedule in your head.

That doesn’t mean you disappear from the process. A pilot on autopilot isn’t asleep at the wheel, they’re watching the instruments, ready to step in the moment something looks off. That’s your role too. You’re not chasing every work order by hand anymore. You’re watching for the extraordinary, a vendor who’s gone quiet, a job that’s overdue, a compliance certificate about to lapse, a pattern of complaints from the same unit. Those are your tell-tale signs, and they’re exactly where your attention is worth the most.

That shift matters more than it sounds, and it’s meant to give you something back, not take your job away. So much of BM work today is invisible admin: remembering which vendor services which asset, whether that leak report from three weeks ago actually got closed, whether a certificate is quietly about to expire. None of it is visible to an owner, but all of it weighs on you, and it’s exactly where things slip through unnoticed. When the system carries that memory instead of you, you get that time and headspace back for what actually needs a person, like walking the estate yourself, or having a harder conversation with an owner who needs to be heard, not just processed.

Technology Isn’t Optional Anymore

We’ve written before that AI can’t replace skilled trades, and that still holds. No algorithm is unblocking a choked pipe or rewiring a faulty DB. But the managing agent industry is a different story. Downsizing of onsite admin staff is a real and ongoing trend, and it isn’t slowing down. That means the BM who’s still doing everything on paper, or purely from memory, is the one most exposed when headcount gets cut further. Getting comfortable with technology now isn’t optional, it’s how you stay valuable when the admin load around you keeps shrinking. The part of you that can’t be automated, and shouldn’t be, is your relationship management. Reading a tense council meeting, calming an upset owner, knowing when to push back and when to let something go. That’s still entirely on you. Technology should be freeing up space for that, not competing with it.

What Changes When Something Goes Wrong

Things will still go wrong. Estates are never problem-free, and no system changes that. But it changes what happens next. Instead of an owner emailing the council saying nothing’s being done, there’s a record waiting for you: this vendor was assigned this date, here’s the current status, here’s the photo of completed work. The conversation shifts from “why hasn’t anyone done anything” to “here’s exactly where we are.” That’s not just easier for you, it’s the difference between an owner who trusts you and one who’s already looking for your replacement.

Flying the Estate on Autopilot

Think of it like a pilot flying a long haul route. Autopilot handles the steady, repetitive work of keeping the plane on course, so the pilot isn’t manually adjusting every control the whole flight. But the pilot never actually leaves. They’re watching for turbulence ahead, an instrument reading that doesn’t look right, anything that needs a human judgment call. That’s what Basementgrid is trying to give you: the routine work running quietly in the background, so your attention goes to the moments that genuinely need you. Not because every dispute gets resolved perfectly, but because the estate runs, and is seen to run, every single day, and you’re the one steering it, not chasing it.

Spend enough time around Singapore’s strata management scene and a pattern shows up everywhere, in estate after estate, regardless of who’s running it.

Take the Building Manager. On paper, the job looks simple: keep the estate running, get repairs done, report back. In practice, it isn’t. A good chunk of a BM’s time, often the majority, goes into relationship management rather than maintenance management — keeping the council happy, smoothing over egos, responding to whatever surfaced in the WhatsApp group that day. The work residents actually notice keeps getting pushed down the list.

Part of the reason is that there’s often no real process behind the job. No defined system for how a repair gets requested, approved, and closed out. So whoever is physically on-site ends up calling the shots by default — dealing with leaks, lift breakdowns, and tenant complaints at 7pm on a Friday, making decisions on the fly because someone has to.

Then there’s the council. Well-meaning owners volunteering their evenings, but their main point of engagement is usually questioning the repair bill after it’s already been paid. “Why did this cost so much?” “Did we need this vendor?” Fair questions — except most council members aren’t maintenance experts. They can’t easily tell if a quote is fair, if an invoice matches the scope of work, or if a vendor is even legitimate. So scrutiny lands on cost, after the fact, instead of on process, before the fact.

Nobody in this setup is doing anything wrong. The BM is doing their best under pressure. The council is doing what they believe their duty requires. But with no structure in place, every decision runs on memory, trust, and whoever picks up their phone first.

That’s not a people problem. It’s a systems problem. That was the first reason Basementgrid needed to exist.

The software that already exists wasn’t built for this

The natural next step was to look for software that solves it. CMMS tools exist, just not for this world. Almost all of them are built for an internal maintenance team — employed by the building, using the same system daily because they have no choice. Log a ticket, assign an in-house technician, close it out. That works fine when you’re giving orders to your own staff.

And to be clear, this isn’t a gap that apps like iCondo or iPlusLiving fill either. Those platforms are built for communal living — facility bookings, visitor management, resident announcements, the social side of condo life. Useful, but aimed at residents, not at the operational backbone of how repairs get requested, approved, and closed out.

But that isn’t how strata management works. An MCST doesn’t run on an internal crew — it runs on external vendors: plumbers, electricians, lift technicians, cleaners, landscapers, dozens of contractors moving between many buildings, not just one. The MA’s real job isn’t fixing things. It’s coordinating the vendors who do.

That’s where every existing CMMS falls apart. You can’t force a vendor to log into your system. They have no reason to. They’re not your employee — they’re doing jobs for twenty other buildings this week, each possibly running a different system, if any. Ask a vendor to create an account and update ticket statuses for a job worth a few hundred dollars, and the answer is a WhatsApp message instead. Every time.

So estates end up back where they started: coordinating over calls, texts, and memory — the same chaos as before, except now there’s also an expensive piece of software nobody uses sitting in the background.

That was the second reason Basementgrid was founded. Not “another CMMS,” but one built around the reality that MCSTs run on vendors, not employees — where getting vendors to actually participate is the core design problem, not an afterthought.

The part that only shows up over years

The third issue takes longer to see, because it doesn’t show up in a single site visit — it shows up over years. Managing Agents change, a lot. And the new one is often a company already familiar, recycled from another estate down the road.

It’s musical chairs. A new MA comes in, there’s a fresh start for a while, then a year or two later they’re let go too, and the whole cycle resets from zero: onboarding, learning the estate, rebuilding vendor relationships.

Most of the time, MAs aren’t let go over maintenance competence. It comes down to the Building Manager’s relationship with the council — and council members, however well-intentioned, usually aren’t professionals in this space. They’re volunteers with day jobs. So the relationship becomes the deciding factor, not the work. A BM who is well-liked survives. A BM who is competent but blunt, or slow to reply at 9pm, doesn’t. Maintenance work stalls not because it can’t get done, but because the relationship managing it keeps falling apart.

That’s not to say every BM is blameless either. Plenty aren’t well-equipped for the job. It’s something of an open secret that many BMs are retirees, hired to fill a headcount rather than for hands-on experience. So you get a BM who isn’t strong on process, managing a relationship with a council that isn’t strong on maintenance, with nothing structural holding the estate steady when the relationship sours.

That’s the third reason Basementgrid was founded. An estate’s operational history shouldn’t live and die with whichever MA happens to be in the chair this year. The work orders, vendor records, approval trail, maintenance history — that should belong to the building, not to whichever company or BM currently holds the relationship together. When the MA changes, and it will, the estate shouldn’t have to start from zero.

(More to come — this is where Basementgrid’s story really begins.)