The Grid

Building Smarter Communities

Expert insights on compliance, workflow efficiency, and modern estate management built for Singapore property councils.

  • Your MA Recommends the Work, Does the Work, and Signs It Off. Who Checks?

    Your MA Recommends the Work, Does the Work, and Signs It Off. Who Checks?

    Have you heard of the principal-agent problem? It shows up whenever one person hires another to act for them, and the two don’t want exactly the same thing. The agent usually knows more than the principal and can’t be watched all the time, so the agent’s choices end up suiting the agent a little more than the principal. In an MCST, the council is the principal and the managing agent is the agent, which makes MCST managing agent oversight harder than it looks.

    The MA advises and executes the work

    In most professions, the person who recommends what to do is not the person who does it. You hire an architect to design and a contractor to build. You hire a consultant to recommend and someone else to implement.

    In an MCST, the MA does both. It tells the council what needs fixing, which vendor to use, how much it should cost, and when to do it. Then it runs the job, checks the work, and processes the payment. Planning and execution sit with the same organisation, so nobody is positioned to ask “did we really need to do this, and was it done properly?”

    When the same party writes the brief, delivers the work and signs it off, the council ends up reviewing a conclusion rather than an analysis.

    MA fees don’t reward the best advice

    Consulting firms charge well because they are paid for the quality of the advice. MA fees in Singapore are not set up that way. The work is operational and the fees are modest. Where there is a year-end bonus or a performance target, it is usually tied to keeping the account, not to whether the estate is better off.

    So the advice that is easiest and safest for the MA often differs from the advice that is best for the estate. Sticking with the familiar vendor avoids friction. Recommending the bigger job can be easier than defending a smaller one. Not raising an awkward issue keeps the relationship smooth. None of this requires anyone to act in bad faith. People respond to the incentives in front of them, and the council would do the same in their shoes.

    MCST council members are volunteers with little at stake

    A company’s board has a reason to care. Directors are paid, hold shares, or have a reputation riding on the outcome. Even in charities and religious organisations, volunteers get something back, whether it’s a sense of purpose, a community, or a cause they believe in.

    MCST council members mostly get none of this. There’s no pay and no equity. Whether the estate is run well or badly is rarely felt personally, beyond the usual annoyances every resident has. Most are busy people who took the role because someone had to. It’s not realistic to expect volunteers like this to dig into quotations, chase defects, and cross-check invoices on top of their day jobs.

    So the principal who is supposed to keep the agent honest has the least time, the least information and the least reason to do it. That is the dilemma.

    What actually helps: independent MCST council oversight

    We don’t think the answer is replacing the MA or asking council members to try harder. People change MAs all the time and the same problems tend to follow. Our view is to fix the process, not the people.

    The idea is simple: give the council an independent record of what’s happening, one that doesn’t depend on the MA telling them. Information is power, and right now most of it sits on one side of the table.

    Basementgrid acts as that independent layer, an operating system for the estate that sits alongside whoever the current MA is. Around 70% of an MA’s work is day-to-day maintenance coordination, which we’ve written about here. That work runs through the app:

    • Every job has a record. A work order is raised, assigned to a vendor, and tracked through each status, so the council can see what’s happening without asking.
    • Spending above the council’s threshold needs approval inside the app. No more “I thought you approved it” and “I thought you knew” after the fact.
    • Vendors submit quotes and invoices in the system. The amounts and documents are on file, and the invoice is matched against the approved work order.
    • Proof of work comes first. Vendors clock in with GPS verification and submit photos and a completion record before the job can be reviewed and paid.
    • The history stays with the estate. If the MA changes, the records don’t leave with them.

    The MA still does its job, and that part is light: creating work orders and verifying completed work in the app. What changes is that the work now leaves a trail the council can see. Council members don’t have to review every job. They just have to know that the information is there when they want it, and that approvals actually passed through them.

    That’s the part that closes the gap. The MA can still advise and execute, but it no longer does so in a way the council can’t see. The volunteers don’t have to become experts, because the process does the watching.

    If you’re on an MCST council and want to see how it works, you can set up a workspace in about 3 minutes and run a first work order with your existing vendor. Book a 15-minute demo or check the help centre.

    FAQs

    What is the principal-agent problem in an MCST? It’s the gap between what the council wants and what the managing agent has an incentive to do, made worse because the MA both advises and executes.

    How can an MCST council oversee its managing agent? By keeping an independent record of work orders, quotes, approvals and proof of work, so the council doesn’t depend on the MA to report what happened.

    Do we need to change our MA to fix this? Usually not. Changing agents tends to carry the same problems over unless the process itself changes.

  • Set Up in 3 Minutes, Paid in One Workflow: Running Your First Work Order on Basementgrid

    Set Up in 3 Minutes, Paid in One Workflow: Running Your First Work Order on Basementgrid

    Most software for building maintenance asks you to change how you work before it does anything for you. You import data, configure modules, train the team, and three months later you’re still not sure it’s running.

    Basementgrid works the other way. You can start with the vendor you already use, on the next job that comes up. Here’s what that looks like, from setting up your workspace to getting the vendor paid.

    Step 1: Set up your workspace (about 3 minutes)

    Basementgrid New Workspace Onboarding

    A building manager or a council member can create the workspace. You enter the estate details and set the approval threshold, which is the amount above which a work order needs council sign-off. Then you invite the council members.

    That’s the whole setup. You don’t need to load your assets or build your vendor list first. You can add those as you go.

    Step 2: Create your first work order

    Create a work order for whatever needs doing, invite your existing vendor, and assign the job to them. Your vendor doesn’t need to be on Basementgrid already, and they don’t pay to use it.

    If the amount is above your threshold, the work order waits for council approval. Council members get the request, see the amount and the vendor, and approve it. Nobody has to chase anyone on WhatsApp to find out whether the job was authorised.

    Step 3: The vendor dispatches a technician

    Once the work order is issued, the vendor manager invites their technician and dispatches them to the job. The vendor runs their own side, so the building manager doesn’t have to coordinate who is turning up.

    Step 4: The technician does the job, and proves it

    GPS-verification check in

    When the technician arrives on site, they clock in with GPS verification. They do the work, take photos that are also GPS verified, write a work summary, and submit the form.

    The photos have to be taken on the spot, so you’re not relying on a picture sent later that could be from anywhere. The building manager gets a record of who was there, when, and what they did, without having to be on site.

    Step 5: Accept the job

    After the technician submits, the building manager reviews the work and accepts it. The invoice comes only after that, so you’re never paying for something you haven’t checked.

    Step 6: Invoice and payment

    QR code payment is tagged to approved work order amount and vendor UEN

    Once the job is accepted, the vendor manager submits the invoice. Basementgrid generates a PayNow QR code for it.

    Whoever makes payments for the MCST account can use that QR code to create the payment record in the bank, and then approve it. The second approver approves it after that. Most MCSTs need two approvers, and the process fits that. The QR code just means nobody is retyping the vendor’s details or the amount.

    The work order stays on file

    When the work order is completed, it’s filed and tagged to the asset it was for, whether that’s a lift, a pump or a fire panel. The building manager and council members can go back to it later.

    That matters when the council starts asking whether to keep repairing something or replace it. Instead of relying on someone’s memory or a box of old invoices, you can pull up every job done on that asset, what each one cost and who did it. It also stays with the estate when the managing agent or building manager changes.

    Why this counts as plug and play

    You didn’t migrate anything. You didn’t wait for an implementation. You set up a workspace, created a work order, invited the vendor you already work with, and ran one real job through the whole process, from approval to payment to filing.

    Want more control?

    If you want something more customised, such as a form the vendor has to complete before a job can be closed, you can set that up. The guides are at help.basementgrid.com.

    If you’d like someone to walk you through it first, you can book a 15-minute demo.

  • The 70% Problem: Why Most Condos Think They Need a Managing Agent (They Don’t)

    The 70% Problem: Why Most Condos Think They Need a Managing Agent (They Don’t)

    BCA is pretty clear about this on their own site: a Managing Agent “may be employed” by an MCST — it’s optional, not a requirement under the Building Maintenance and Strata Management Act. The council is empowered, and expected, to manage its own affairs. What trips most councils up isn’t the law. It’s that maintaining shared property — lifts, pools, water tanks, cleaning, security, landscaping — genuinely takes a system to run well, and most self-managed estates never build one.

    We broke this down before: an MA’s job is roughly 70% maintenance coordination and 30% admin work (books, minutes, AGMs). We briefly covered how to handle the 30% with outsourced bookkeeping and AI-assisted minutes. This article is about the 70% — the shared-facility maintenance most councils assume needs an MA’s staff to chase. It doesn’t. It needs a system.

    And it’s worth being precise about what “system” means here. Basementgrid isn’t a checklist you hand your building manager and hope he ticks off. A checklist still depends on someone remembering to open it, fill it in honestly, and flag it if something’s wrong. The maintenance process — schedules, thresholds, sign-offs, proof of work — is built into the platform itself. It’s not a document your BM checks. It’s the thing that checks on your building for you. That’s the difference between hoping your BM caught something and actually having eyes on every lift, pool, and vendor whether or not anyone remembered to look.

    1. Lifts: The One Thing You Can’t Afford to Get Wrong

    Monthly Lift Maintenance

    Lifts are the one area where the compliance stakes are highest and the least optional. BCA requires all lifts to be maintained by a BCA-registered Fixed Installation contractor, at a minimum monthly if no manufacturer schedule applies, plus an annual inspection and test by that contractor with an independent examiner present. Get this wrong and it’s not just a fine — it’s a safety issue and it affects your Permit to Operate (PTO).

    On Basementgrid, every lift is set up as an asset with its own digital record: commissioning date, warranty status, and a full history of every work order raised against it. When the monthly service or annual test comes due, the reminder goes to whoever’s tracking compliance instead of living in someone’s head or a shared spreadsheet. And because every WO ties an amount to a specific piece of work, the council can see that the invoice paid to the lift contractor actually matches what was issued and done — not just “lift maintenance, $X” on a bank statement with no paper trail behind it.

    2. Cleaning Contractors: Paying for a Checklist, Not a Promise

    Cleaning contracts usually promise a scope — daily lobby cleaning, weekly common corridor mopping, quarterly deep clean — that nobody actually checks against. Basementgrid lets you build a custom checklist matched to what’s in the contract, whether it runs monthly or quarterly, so the contractor has a defined list to complete rather than a vague expectation, and the council has something concrete to hold them to.

    Once the cleaners mark the checklist complete, it goes to the BM for review before anything gets billed. If the BM isn’t satisfied, they can reject it and send it back for rework — no invoice goes out until the BM actually accepts the work. Only once it’s accepted can the cleaning vendor submit their invoice. Every step, checklist completion, rejection, rework, acceptance, is timestamped, so there’s no after-the-fact argument over whether the work was done properly or on time.

    3. Security: From Watchman to Watch System

    Security: From Watchman to Watch System

    If your estate has a stationed guard, patrols usually turn up faults that never get logged anywhere formal — a broken gate sensor, a flickering corridor light, a leaking pipe in the basement. On Basementgrid, the guard can report a fault directly during patrol, and it converts straight into a work order that goes to the right vendor. The guard can hold the role of raising the WO itself, so a fault gets logged the moment it’s spotted rather than waiting for the BM to be free to do it. Acceptance of the completed work still stays with the BM, so the guard’s job is just to flag it fast, not to sign off on it. That split keeps the BM’s workload lighter without losing the checkpoint that matters. For anything above a set spending threshold, it doesn’t go out automatically — it needs a majority vote from council members first, using the same approval threshold that already governs other spending on the platform. Small stuff gets fixed fast; anything material still needs the council’s sign-off.

    Worth noting too: CCTV is increasingly the new guard. The Singapore Police Force itself has been moving in this direction in our own neighbourhoods, expanding its PolCam network to more than 200,000 cameras with officers running “virtual patrols” from a command centre rather than relying solely on boots on the ground. If your estate is weighing whether it still needs a stationed watchman or concierge, that’s the direction worth considering — CCTV coverage feeding into a system like Basementgrid, rather than a person whose only record of a patrol is their word for it.

    The one gap CCTV alone doesn’t close is telling a false alarm from a real one before it escalates. For that, the best bet is still a resident volunteer in the community, someone who can eyeball the footage or the site itself and confirm whether it’s worth acting on, rather than every alert automatically triggering a callout.

    4. Water Tank Washing: The Annual Deadline Nobody Remembers Until It’s Late

    Annual water tank washing

    This one has real teeth. PUB requires every MCST with a water storage tank to engage a Licensed Plumber to inspect, and where needed clean, disinfect and certify the tank at least once every 12 months. Miss the deadline and it’s an offence under the Public Utilities (Water Supply) Regulations — a fine of up to $10,000, or up to 12 months’ imprisonment, or both. PUB sends reminder emails, but they explicitly tell MCSTs not to rely on that alone.

    Basementgrid tracks each tank’s certification date and reminds council members well ahead of renewal, not the week it’s due, so there’s enough runway to engage a Licensed Plumber and get it done instead of scrambling against the deadline.

    5. Swimming Pool: One Missed Test Away from a Compliance Headache

    NEA licenses swimming pools as Aquatic Facilities, and licensees have to send water samples to an SAC-accredited lab and submit results to NEA on a regular cycle — monthly submissions are the norm, alongside daily on-site testing for things like pH and chlorine. It’s easy for this to quietly lapse when it’s sitting on a pool contractor’s checklist and nobody’s cross-checking it. Basementgrid tracks the pool contractor’s testing and submission cadence against what NEA expects, so the council can catch a missed cycle before it becomes a compliance problem instead of finding out after the fact.

    6. Landscaping, Pest Control, Electrical: Proof They Actually Showed Up

    These are lower-stakes but higher-frequency — monthly visits that either happen properly or quietly don’t. Every vendor clock-in on Basementgrid is GPS-verified against the property, so there’s a real record that the landscaper, pest control technician, or electrician actually showed up rather than just submitting an invoice. Anything they flag as needing repair goes through the same work order flow as everything else — one process, not a different tracking method for every vendor type.

    7. Other Vendors: Never Start From Zero Again

    Need a new contractor for something that doesn’t fit an existing category? Every vendor that’s registered on Basementgrid, across any estate, can be searched and asked for a quote directly through the platform instead of starting from a WhatsApp recommendation and hoping. We’ve written more about how the vendor side of Basementgrid works if you want the full picture.

    No Ghost Maintenance: Every Job, Traceable End to End

    Tie all seven together and the pattern is the same process, repeated: a designated council member acting as building manager creates the work order, assigns it, and verifies the work with proof uploaded by the vendor — all from a phone, no separate system per vendor type, and no reliance on anyone remembering to check a list. Once a WO is issued, its details are locked — scope, amount, vendor, can’t be quietly edited after the fact by either side, so there’s no room for a dispute over what was actually agreed.

    Basementgrid Work Order Workflow

    And it closes the loop all the way to payment. Residents can submit a work request in the app; the BM approves it and issues it to a vendor. Once the vendor finishes and uploads proof, the BM verifies it, and the invoice generates a PayNow QR matched exactly to the work order amount and the vendor’s UEN. Council members scan and pay — no manual reconciliation, no guessing whether an invoice matches what was actually approved. If something stalls, the activity log shows exactly where, so nobody’s left wondering if it’s the BM, the vendor, or the council holding things up.

    Still need someone to actually be the BM? That’s fair — not every council has a volunteer with the time. Book a demo with us and we’ll put you in touch with a Managing Agent who already runs on Basementgrid, so you get the system without needing to find the person yourself.

    Prefer to set it up yourself first? Get started here.

    Next up: the other 30% — bookkeeping, AGMs, minutes, and compliance paperwork — and how a self-managed council handles that without an MA either.

  • Running Your Own Building’s Maintenance Without Losing Your Mind

    Running Your Own Building’s Maintenance Without Losing Your Mind

    If you own a landed home or a shophouse, you don’t have an MCST or a managing agent handling maintenance for you. You are the managing agent. Every leaking pipe, every aircon servicing, every contractor who shows up at your gate — you’re the one coordinating it, remembering it, and paying for it.

    Most owners end up doing this through a mix of WhatsApp chats, paper receipts, and memory. It works, until it doesn’t — usually right when you need to remember something from two years ago and can’t.

    Here’s how Basementgrid helps, even without a council or an MA in the picture.

    Verified Contractor App Singapore: Know Who’s Actually in Your Building

    Verified Contractor

    Anyone can call themselves a contractor. Basementgrid only lets UEN-verified vendors take on jobs, so before someone’s doing electrical work or roof repairs on your property, there’s a real registered company behind them, not just a phone number a neighbour passed along.

    Every job also gets logged against that vendor. If the same “handyman” keeps quoting differently each time, or a company’s work keeps failing, you’ll actually be able to see that pattern instead of relying on your own memory of who did what.

    Shophouse Maintenance Tracking: Stop Paying for Work That Quietly Didn’t Happen

    This is the part most self-managing owners get burned by eventually. You pay a vendor for a “routine service” or a repair, and there’s no real way to confirm the work was done properly — or at all — beyond taking their word for it. We’ve written before about how ghost maintenance and falsified invoicing quietly drain maintenance budgets, and it’s just as easy to fall victim to without a council watching over the books.

    With Basementgrid, every job is tied to a work order and a sign-off, so there’s a record that matches the invoice to the actual work. It’s a lot harder for a vendor to bill you for a job that was rushed, skipped, or never fully completed when there’s a paper trail expected on both ends.

    Property Maintenance History Record: Build the Repair-or-Replace Case for Yourself

    Property Maintenance History Record

    This is the one that pays off years later. When your water heater fails, or your roof starts leaking, or your aircon compressor needs replacing — should you repair it again or finally replace it? That decision is so much easier when you can actually see how many times it’s been serviced, by whom, and how much you’ve already sunk into keeping it alive.

    Instead of digging through old texts and hoping you kept the invoice, your property’s full maintenance history lives in one place, tied to the property itself, not to your phone or your memory.

    DIY Building Maintenance Software: Why This Matters More for You Than a Condo Owner

    A condo owner has a council and an MA between them and the mess. You don’t. If you don’t build the system yourself, nobody’s going to build it for you — and the cost of not having one shows up later, as an asset you replaced too early, a vendor who overcharged you three times before you noticed, or a repair history you can’t produce when you’re selling the place.

    Basementgrid isn’t asking you to run a big operation. It’s just making sure that when you’re the one handling maintenance, you’re not doing it from memory.

    If you want to see how it’d work for your property, book a 15-minute demo and we’ll walk through it.

  • Why a 20-Unit Condo Doesn’t Need a Managing Agent

    Why a 20-Unit Condo Doesn’t Need a Managing Agent

    If you’re on the council of a small estate, you’ve probably had this thought at least once: “What exactly are we paying our MA $1,000+ a month for?”

    For a 200-unit condo with a swimming pool, gym, function room and a full-time on-site staff, the answer is obvious. For a 20-unit walk-up or boutique development, it’s a lot less clear. Let’s break down what an MA actually does, and whether a small estate really needs to pay for all of it.

    What Does a Managing Agent Actually Do?

    Strip away the sales pitch and an MA’s job splits roughly into two buckets:

    • 70% maintenance coordination — logging faults, chasing vendors, tracking preventive maintenance, following up on compliance deadlines.
    • 30% admin work — taking minutes, chairing or coordinating AGMs, keeping the books, and filing annual compliance paperwork.

    Neither of these requires an MA specifically. They require a system. Here’s how a 20-unit MCST can cover both without one.

    Running a Self-Managed MCST: The 30% Admin Work

    Outsourced Bookkeeping for a Small MCST

    This is the easiest one to outsource. A 20-unit estate doesn’t generate many transactions a month, so you don’t need a dedicated accountant, let alone an MA’s back office. Services like Osome will handle monthly bookkeeping and year-end financial statements for as little as $200 a month, scaled to your transaction volume. That’s a fraction of what you’re paying an MA to do the same thing, often less efficiently.

    AI-Generated Minutes for MCST Meetings

    Record the meeting with a transcription tool like myminutes.ai, then feed the transcript into an AI tool like Claude to turn it into a formal set of minutes. What used to take an MA staff member hours of manual note-taking and formatting now takes a fraction of the time, and the output is arguably more consistent.

    Running an AGM Without a Managing Agent

    A 20-unit AGM doesn’t need the formality of a 200-unit one. It can run as a round-table meeting chaired by the council Chairman. Use an AI tool to draft the agenda and resolutions in advance, and record and transcribe the meeting the same way as above. Disagreements can be worked out in the room rather than managed through a rigid, MA-scripted process.

    That said, don’t skip the guardrails entirely. For a start, it’s worth engaging a professional on a one-off basis to check that your AGM process and resolutions are legally sound — the same way you’d bring in a lawyer to catch legal blind spots rather than run every decision through one.

    Automating the 70%: Maintenance Coordination for a Small MCST

    This is the bulk of the job, and it’s also the part software is best suited to replace. This is where Basementgrid comes in. Worth a quick clarification here: Basementgrid isn’t a community app like iCondo, and it isn’t trying to be one — it’s built specifically for the maintenance and vendor side of running an estate, not for residents to book facilities or read announcements.

    Basementgrid automates the full maintenance lifecycle: tracking preventive maintenance schedules, logging faults as they’re reported, converting them into work orders, and following up on compliance reminders so nothing falls through the cracks.

    Vendor Payments and PayNow QR for MCST

    Vendor Payment on Basementgrid App

    Payments are handled too. Vendors submit invoices directly on the platform, and each approved invoice auto-generates a PayNow QR code with the correct amount and the vendor’s UEN already attached. One signatory — usually the treasurer or secretary — can double up as maker and approver, creating the payment in their bank app and approving it, while another signatory acts as the second approver. This satisfies most MCSTs’ requirement for double approval on bank transactions, without needing extra headcount. A monthly transaction report is generated automatically for audit purposes.

    The Building Manager Role Without a Managing Agent

    On the ground, the council member acting as “building manager” only has three things to do on Basementgrid: convert a work request into a work order, assign it to a vendor, and review the completed work. Vendors are required to submit GPS-verified job completion photos, so there’s proof of work on file without anyone having to chase it down.

    Finding someone for this role isn’t as hard as it sounds. Many estates have retirees on the council with time on their hands and a genuine stake in how well the place is run. Compare that to an MA staff member managing a portfolio of a dozen estates, who mostly shows up when something’s already gone wrong. Who’s going to put more care into the job: someone who lives there and treats it like their own building, or someone juggling it as one account among many?

    Is a Managing Agent Worth It for a Small MCST?

    If your estate is paying an MA $1,000 or more a month, add up what you’d spend replacing them piece by piece: outsourced bookkeeping, an AI transcription and minutes workflow, an occasional legal check-in, and Basementgrid for maintenance and payments. For most 20-unit estates, that adds up to meaningfully less than an MA retainer, and it’s hard to argue the level of service goes down.

    What would you rather spend the difference on? A monthly gathering for the whole estate probably does more for a 20-unit community than another line item in an MA contract.

    If that math makes sense to you, get started with Basementgrid and see what running your own maintenance actually looks like.

  • A Glass Curtain, Two Court Orders, and Five Years: What MCSTs Should Actually Learn From Sea Esta

    A Glass Curtain, Two Court Orders, and Five Years: What MCSTs Should Actually Learn From Sea Esta

    Five years. Two court orders. $17,000 in costs. All over one glass curtain on a balcony.

    That’s the shape of a recent case involving Sea Esta, a condo on Pasir Ris Link, where the management corporation spent years trying to get a homeowner to remove a balcony installation that was never approved. If you haven’t read the full writeup on Stacked Homes, the short version is this: an owner installed a glass curtain without sign-off, a tribunal ordered it removed and gave the owner a path to reapply, the owner missed the deadline and kept submitting incomplete applications, the MCST kept rejecting them, and the whole thing eventually needed a District Court judgment and a fresh injunction before the removal could actually happen.

    We read this one closely, because it’s exactly the kind of situation Basementgrid was built around. Not because the MCST did anything wrong. They didn’t. The court agreed the curtain was unauthorised from day one, and the MCST had the law on its side the entire way through. What the case actually shows is something quieter and more common: even when an MCST is completely in the right, a renovation approval that isn’t tracked as a live, owned process can drift for years before anyone is forced to act on it.

    The approval process existed. Nobody was tracking it.

    Here’s the part that’s easy to miss in a case built around legal provisions and court orders. The 2021 tribunal ruling didn’t just tell the owners to remove the curtain. It gave them a process: submit a renovation application within two weeks, and the MCST would respond within two weeks after that.

    That’s a form-and-approval workflow. Most estates have some version of it, whether it’s a PDF the owner emails in, a physical form dropped off at the management office, or a request buried in a WhatsApp thread. The problem in this case wasn’t that the process didn’t exist. It’s that once the application was late, incomplete, and rejected, there was no system forcing anyone to close the loop. The owners kept submitting partial applications. The MCST kept rejecting them for the same reasons. Months passed, then years, and by the time the matter got to court, both sides were arguing over what had or hadn’t been submitted, and when.

    None of that ambiguity should have been possible. A renovation request that’s approved, rejected, or sitting incomplete is exactly the kind of thing that should be visible at a glance, with a clear record of who submitted what, what was missing, and how long it’s been sitting there. Instead, it took a letter from lawyers, dated months after the original deadline, to spell out in writing what had actually been missing from the applications all along.

    Approval without follow-through isn’t approval

    The other detail worth sitting with: even after the District Court enforced the removal in 2023, nothing happened. The MCST sent reminder after reminder. No further applications came in. It wasn’t until the MCST tried to send its own people in to do the work directly, over a year later, that things escalated to an injunction.

    A court order is not a work order. Somewhere between “the owner must comply” and “the glass curtain is actually gone,” someone has to be responsible for following up, someone has to be assigned to inspect or execute the fix, and someone has to formally close it out. When that ownership isn’t built into the process, “the MCST is handling it” can quietly mean nobody specific is.

    This is the gap Basementgrid closes

    This is the exact reason we built Basementgrid around a form-to-work-order flow rather than just a form.

    Renovation Approval Flow on Basementgrid

    The way it works: an owner planning a renovation fills out a digital renovation application, similar in spirit to what you’d fill out on a community app like iCondo, but the difference is what happens after it’s submitted. The building manager reviews it and, if it’s approved, converts it directly into a work order inside the same system. That work order gets assigned to a specific person, whether that’s the BM themselves, a coworker, or a security guard doing a site check, and it stays open, visible, and attributed to that person until it’s marked complete.

    Nothing sits in limbo. If an application is incomplete, that’s logged against the submission, not lost in an email thread six months later. If a renovation needs a follow-up inspection, that’s a work order with an owner and a due date, not a mental note. And when the job is actually done, whoever was assigned has to close it out, which means there’s a timestamped record of who signed off and when, not just a form that was “approved” with no trace of what happened next.

    Sea Esta’s MCST didn’t lose because their process was wrong. They lost years because their process had no built-in accountability once things went off track. A council changes every year or two. A managing agent can be swapped out entirely. If the record of who approved what, who was supposed to follow up, and who actually closed it lives in someone’s inbox, that history walks out the door with them.

    This is really what we mean when we say “fix the process, not the people.” The Taylors weren’t going to comply just because the MCST asked nicely, and no amount of reminder emails changed that. What actually needed fixing wasn’t anyone’s attitude. It was the absence of a system that made the next step, and who owned it, obvious from the start.

    Basementgrid is built for MCSTs, building managers, and MAs who want renovation approvals, defect tracking, and vendor work orders on one system, with a full audit trail that survives council and MA turnover. See how it works →

  • The MA Changes. The App Doesn’t.

    The MA Changes. The App Doesn’t.

    Every MCST in Singapore has been through this at some point. The council isn’t happy with the current Managing Agent, so they switch. New MA comes in, new team, new habits — and somewhere in that handover, three years of work order history, defect records, and “who approved what” disappears into someone’s old email inbox.

    Then six months later, the same complaints resurface. Not because the new MA is worse. Because nothing was ever actually systemized in the first place.

    Why Strata Management Software Beats WhatsApp, Email, and iCondo for MA Handovers

    Singapore strata management already has no shortage of tools. WhatsApp for the quick stuff. Email for the “official” stuff. iCondo or a booking portal for facility bookings and announcements. Google Drive for whatever documents someone remembered to upload.

    The problem isn’t a lack of tools. It’s that none of them are built around the actual work. WhatsApp doesn’t know what “approved” means. Email doesn’t track whether a vendor showed up. A booking app has nothing to do with a leaking pipe on Level 12.

    Basementgrid isn’t trying to be a nicer version of any of those. It’s built around one idea: whichever MA is managing the estate, the process stays the same, because the process is baked into the app — not into any one person’s head.

    That’s the difference between a communication tool and an operating system. You can switch MAs. You can’t switch out of the workflow.

    Work Order Tracking Software Solves the “He Said, She Said” Problem in Estate Management

    Ask any council member what actually eats their time and goodwill, and it’s rarely the big-ticket items. It’s the small, recurring disputes:

    • “We approved that repair weeks ago, why hasn’t it started?”
    • “The MA says the vendor was informed. The vendor says they never got the job.”
    • “Who signed off on this quotation, and at what amount?”

    None of these are hard problems technically. They’re hard because the “record” of what happened lives in scattered chat threads, forwarded emails, and people’s memories — all of which are selectively remembered, conveniently misplaced, or simply gone when the MA changes.

    Basementgrid treats every work order as a running checklist with a status, an owner, and a timestamp. Raised, authorized, in progress, completed, paid — each step is logged against a person and a time, not a recollection. When something stalls, you don’t need to ask around. You look at the record and you can see exactly where the delay sits, and whose desk it’s sitting on.

    That’s not about assigning blame. It’s about removing the ambiguity that makes blame the default conversation in the first place.

    Trust But Verify: Council Approval Workflow Software for MCST Funds and Vendor Accountability

    Here’s the uncomfortable truth about strata management: it isn’t a mom-and-pop shop where one person makes every call and wears every consequence. It’s a business relationship involving the MCST’s funds, multiple vendors, a rotating council of volunteers, and an MA that may or may not be the same one in five years.

    In that setup, “we trust our MA” and “we have a system that verifies what our MA does” are not in conflict — they’re the same thing, done properly. A good MA benefits from a system that clearly shows their work is on track. A council benefits from not having to take anyone’s word for it. And when an MA transition happens, the estate’s operational history doesn’t leave the building with them.

    That’s the responsibility ambiguity we built Basementgrid to close. Not by adding more oversight meetings or more WhatsApp groups, but by making the approval trail, the status of every job, and the accountability for every stage something anyone with access can check — anytime, without having to ask. It’s worth remembering that under the BMSMA framework, the council remains legally responsible for the estate even when it delegates day-to-day duties to an MA — which is exactly why the paper trail can’t be allowed to depend on whichever MA happens to be holding it at the time.

    Fix the process, not the people.

  • Why Defects Liability Period Tracking Matters: Lessons from a 10-Year Condo Dispute

    Why Defects Liability Period Tracking Matters: Lessons from a 10-Year Condo Dispute

    Canberra Residences got its TOP in June 2013. Thirteen blocks, 320 units, the usual condo amenities. Residents started finding problems almost immediately: floor tiles popping up, a kitchen cabinet collapsing off the wall above a stove, sagging cabinetry. Normal enough for a new build, and exactly the window the Defects Liability Period exists for — which is why defects liability period tracking, done properly from day one, matters far more than most councils realize.

    It’s 2026. The MCST is now suing the main contractor over an alleged breach of a settlement agreement that was signed in September 2020, itself the outcome of an earlier lawsuit filed back in 2019. The contractor says the repainting was done by January 2023. The MCST’s statement of claim, filed in 2025, says paintwork is still defective and incomplete, along with rusting steel fixtures and shattered balcony glass. The contractor’s defense on some of it: fair wear and tear, poor maintenance by the MCST, maybe damage by third parties.

    So somewhere between “resident’s cabinet fell off the wall in 2013” and “we’re back in court in 2025,” thirteen years happened. Two lawsuits. One settlement agreement that apparently didn’t settle anything. And a genuinely unanswerable question hanging over the whole thing: which of these items are actually still defects, and which have quietly become wear and tear because nobody closed them out when they should have?

    That’s the part that should worry every council out there, not the lawsuit itself.

    Contractor Delay Tactics Cut Both Ways

    Contractors dragging their feet on defects isn’t news. Cashflow’s tight, defect rectification is unglamorous, and if you can stretch it out long enough, some claims age out or get muddied by time. That’s a known playbook, and it’s exactly why the article, and lawyers who write about construction disputes, keep flagging “delay tactics” as a real strategy, not paranoia.

    But a decade of delay creates cover on both sides. A wall crack reported in 2013 as a defect is unambiguous. The same crack, unaddressed and reported again in 2023 alongside years of normal weathering, is now genuinely disputable. Was it always a defect that never got fixed, or did it start as minor settlement cracking and become a maintenance issue somewhere along the way? Nobody can answer that anymore, because nobody photographed it, timestamped it, or tracked its status.

    That ambiguity doesn’t just help the contractor. It also tempts the other side. An MA working under MCST instruction, staring down a mountain of building issues and years of frustration, has every incentive to fold “should have been maintained” items into the defects claim, especially once things go legal and it becomes an all-or-nothing negotiation. The contractor calls it opportunistic. The MCST calls it long-overdue accountability. Both arguments have some truth to them, and the reason neither side can prove their version cleanly is the same: ten years of undocumented back-and-forth.

    This is what happens whenever defects tracking is allowed to lapse. It’s not just that repairs get delayed. It’s that the entire category collapses. Defect vs. wear-and-tear stops being a factual question and becomes a legal one, decided by whoever has better documentation, or failing that, whoever can afford to outlast the other in court.

    Why MCST Defect Tracking Breaks Down Without a System

    Realistically, nobody sat down in 2013 and decided to let this run for a decade. It happened the way these things always happen:

    • A defect gets reported informally, maybe a WhatsApp message to the MA or a call to the building manager.
    • It gets “handled,” sort of, but there’s no structured record of when it was reported, what was promised, or when it was actually closed.
    • Council turnover happens. Volunteers rotate out every year or two. Institutional memory about which defects are open and which are resolved walks out the door with them.
    • The MA changes, which happens more often than anyone likes to admit in this industry, and the new MA inherits a filing cabinet, not a system.
    • By the time anyone tries to reconstruct the defects history for a legal claim, they’re relying on emails, old minutes, and residents’ memories of what fell off which wall in which year.

    None of this is any single party’s fault. It’s what happens by default when defect tracking lives in inboxes and meeting minutes instead of in a system built for it.

    How Defects Liability Period Tracking Software Prevents This

    Building Managers Essential Tools

    This is the exact failure mode Basementgrid’s defect tracking module exists for, so it’s worth being specific rather than just saying “digitalize it.”

    Every defect gets a permanent, timestamped record from day one. Reported date, photos, description, assigned vendor, and every status update logged against it. Not a WhatsApp thread that gets deleted when someone changes phones.

    The DLP clock is visible, not assumed. Council and MA can see at a glance which defects were reported inside the Defects Liability Period and which weren’t, so “was this ever actually a defect claim” stops being a debate reconstructed years later from memory.

    Defects don’t get closed by silence. A defect stays open until someone actively marks it resolved, with evidence attached. No more items quietly falling off the list because nobody chased them for two years.

    The record survives MA and council turnover. Because the data belongs to the MCST’s workspace, not to whichever MA happens to be managing it that year, a new MA or a new council inherits the full history on day one, not a stack of paper and secondhand accounts.

    Defect vs. wear-and-tear becomes a documented fact, not a courtroom argument. If a crack was reported and photographed in 2013 and never closed, there’s no ambiguity about whether it’s old damage or ongoing deterioration ten years later. The timeline speaks for itself.

    None of this stops a contractor from dragging its feet, and it wouldn’t have stopped this particular dispute from ending up in court. What it does is take away the fog that makes ten-year delays survivable for whoever’s slow-walking a claim, and it takes away the temptation on the other side to pad a claim once things get adversarial. A clean, contemporaneous record is bad for stalling and bad for overreach in equal measure. That’s the point.

    Fix the process, not the people. Set it up once, and let the process manage the people.

  • Managing Agent Corruption in Singapore: Why MCSTs Need a Documented Quotation Approval Process

    Managing Agent Corruption in Singapore: Why MCSTs Need a Documented Quotation Approval Process

    Last week CPIB charged a Senior Project Manager at EM Services, the managing agent for Holland-Bukit Panjang, Sembawang and Sengkang Town Councils, with corruption. It’s the latest managing agent corruption case in Singapore’s strata sector, and the pattern is a familiar one: he allegedly took S$220,000 in bribes from the directors of three engineering and construction firms over almost three years, in exchange for steering contracts their way. Part of the money reportedly went toward a Mercedes-Benz. Three vendor directors were charged alongside him.

    Town councils aren’t MCSTs, but the mechanics are identical to what happens in private estates. A person who controls or influences vendor selection and quotation approval, sitting between council volunteers and the contractors bidding for work, quietly gets paid by the vendor to make sure they win.

    No Process Stops Corruption. A Paper Trail Prosecutes It.

    Here’s my honest take: no system stops someone determined to take a bribe. If a managing agent or a signatory wants to be corrupt, a piece of software isn’t the thing standing between them and the money. But that’s not really what a process is for. It’s there to create a paper trail. Who approved this quotation, at what price, against what benchmark, with what proof of work. When CPIB or an internal audit comes asking questions later, that record is what makes a case prosecutable in the first place. Without it, you’re relying entirely on someone’s word.

    Why MCST Vendor Kickbacks Are So Easy to Pull Off

    Maintenance and repair work in Singapore’s strata sector doesn’t differentiate much on quality. Most vendors can competently patch a leak, service a lift, or repaint a corridor. What actually decides who gets the job is price and relationship. That’s a structural weakness, not a moral failing on anyone’s part, and it’s exactly the kind of weakness that’s easy to exploit when there’s no vendor quotation benchmark to check a bid against.

    Managing Agent Fund Mismanagement: The Fee Squeeze Behind MA Kickbacks

    This also explains why kickbacks happen on the MA side specifically. Managing agent fees in Singapore are competitive, arguably too competitive for the scope of work expected. An MA that quotes low to win more clients has to make up that shortfall somewhere. Vendor kickbacks are one of the easiest ways to do it, and the MCST paying an inflated invoice never sees the difference between “market rate” and “market rate plus commission” unless someone is checking.

    Council Member Legal Liability: Why MCSTs Miss the Warning Signs

    MCST councils are volunteers. They’re not accountants, they’re not procurement professionals, and most of them took the role because nobody else would. Financial mismanagement, on its own, doesn’t really worry a volunteer council the way it should. What they do care about, consistently, is not being personally liable. Council member legal liability under the BMSMA is the one thing that gets a council’s attention every time.

    That’s actually the opening. If you frame a quotation approval process not as “extra admin work” but as “the thing that protects you personally if this ever gets investigated,” council members listen differently. A haphazard approval process, where invoices get paid without proof of work or a benchmark comparison, isn’t just bad practice. It’s the exact gap that lets an MA push through an inflated quotation without anyone asking a second question.

    How a Quotation Approval Process Becomes a Barrier Against MA Corruption

    This is where a system like Basementgrid earns its place, not as a fraud-prevention silver bullet, but as friction. Every quotation logged against a benchmark. Every approval tied to a named signatory. Every payment matched to proof of work, photos, timestamps, GPS-fenced attendance. None of that stops a bad actor from trying. What it does is remove the plausible deniability of “I didn’t know” and replace it with a record that says exactly who signed off on what, and when.

    That’s an additional barrier for an MA or a signatory to think through before taking a bribe. Not because the software catches them in the act, but because the record it leaves behind is what turns a suspicion into a case. When there’s no quotation approval process, everything is he-said-she-said. When there’s one, there’s a timeline CPIB can actually work with.

    The Real Fix for Managing Agent Corruption in Singapore

    MCST councils don’t need to become forensic auditors. They need a system that makes “we didn’t have visibility” stop being an excuse, for the MA and for themselves.

    Fix the process, not the people.

  • Digitalization of MCST Management: How Basementgrid’s 5 Roles Help

    Digitalization of MCST Management: How Basementgrid’s 5 Roles Help

    We looked at over 100 MCSTs in Singapore, and one thing kept showing up: the way a maintenance platform defines its roles decides whether the platform actually gets used. Most CMMS tools get this wrong for strata settings, and the gap shows up as unclosed work orders, unpaid vendors, and eventually a return to pen and paper.

    Here’s what we found, and how we built Basementgrid’s role structure around it.

    Why Digitalization of MCST Management Needs More Than a Typical CMMS

    In a normal maintenance department, or a company whose business is maintenance, the role structure is simple. An admin has full access to work orders and assets. He creates a work order and assigns it to a teammate, who has limited access. The teammate does the fix, or calls in a contractor, records proof of work, and closes the case.

    Budget approval sits outside the CMMS entirely. It happens in accounting software, where a director signs off once the amount crosses a threshold. Anything under that threshold gets done first, the vendor invoices after, and the manager submits it to accounting for payment.

    The CMMS itself just tracks asset failure history. An internal technician records completion and closes the case.

    This works because there’s always an internal technician in the loop. That assumption breaks down completely in a strata setting.

    Ghost Maintenance: The Barrier to Digitalization of MCST Management

    About half of Singapore’s MCSTs have fewer than 50 units. That means one managing agent, often juggling several other estates at the same time, running the whole show. There’s no budget to hire a technician to accompany every contractor and log the work.

    That’s how ghost maintenance happens: work gets done, but nobody records it in a system the MCST can actually trust.

    It gets worse when the CMMS itself is the obstacle. A contractor already juggling different CMMS tools across multiple estates isn’t going to climb a steep learning curve for one client. Work orders stay open, or never get logged at all. Eventually the MCST gives up on the software and the building manager, especially one trained the old-school way, goes back to pen and paper.

    Handing the vendor a “limited user” role and expecting diligent record-keeping doesn’t solve this. It just moves the failure point.

    More people are involved in an MCST repair than in a typical in-house maintenance job: admin, council, vendor manager, technician, accountant. More people means more places for a step to get skipped. Without a system that automates the handoffs between them, things fall through the cracks, and when they do, the blame lands on the building manager, whether or not the failure was actually his.

    Basementgrid’s 5 Roles: The Framework for Digitalization of MCST Management

    Digitalization of MCST Management

    Basementgrid’s role structure starts from a different assumption: every role has exactly one job to do at each stage of the maintenance cycle, and the process itself enforces compliance. No role in Basementgrid is ever asked to do more than two primary actions across the whole process. Simple, clear, and easy to follow, even for a first-time user.

    1. Admin (usually the building manager) Creates the work order and tracks its status. Can extend the role to an in-house technician if the MCST has one, or keep it limited to himself. No work order issued means no vendor gets paid, which is what keeps every job logged, especially the ones tied to payment.

    2. Approver (usually council members) Gets notified once a work order crosses the amount threshold and votes for or against it. For a closer look at how threshold-based approval works, see our guide on the MCST maintenance approval process.

    3. Vendor Manager Receives the approved work order and assigns a Vendor Technician to it.

    4. Vendor Technician Travels to site, clocks in on arrival, and completes the job, including GPS-verified photos and any custom form fields required for that job type.

    5. Admin verifies, Vendor Manager invoices, Approver reconciles Admin checks and verifies the completed work. Vendor Manager submits the invoice to the MCST for payment. Once payment is made offline, the Approver (usually an accountant) logs the payment and closes the loop.

    RolePrimary Action
    AdminIssues the work order, verifies completed work
    Approver (Council)Approve or reject above-threshold work
    Vendor ManagerAssigns technician, submits invoice
    Vendor TechnicianClocks in, completes the job with proof of work
    Approver (Accountant)Logs payment

    Why a Longer Process Delivers Real Digitalization of MCST Management

    This process has more steps than a typical CMMS. That’s deliberate. Every role is accountable for one action, and every action is designed to be simple enough that if you know how to use WhatsApp, you can use Basementgrid.

    The result: work that needs doing gets logged, work that’s completed gets verified with proof, and payment gets reconciled against actual work done. No ghost maintenance, no vendor chasing payment nobody agreed to, no manager stuck re-explaining a CMMS to a contractor who’s already juggling three others.

    That’s the difference between a maintenance tool built for internal teams and one built for how MCSTs actually operate.

    For a full breakdown of how each role works inside the platform, see our help center guide: Understanding Roles: Administrator, Collaborator, and Requester.