For trustees

You were elected to run the scheme. Not to answer for it alone.

Trustees are volunteers who carry personal liability for a body corporate most of them didn’t ask to run. The exposure isn’t abstract: it’s money authorised without your name properly on the file, a decision nobody can prove was taken correctly, a certificate that lapsed while everyone assumed somebody else was watching it, or a scheme’s whole history disappearing the day the managing agent does. Nexorah is built against exactly those four, and the important parts are enforced in the database, not written down as a policy.

The fears, in order
  • 01

    Liable for what you didn’t know about

    Every item in the queue carries its evidence before it carries a button — where it came from, the rule that applies, who may approve it, what happens next. You’re never asked to approve a number; you approve a case you’ve actually seen.

  • 02

    The money going somewhere it shouldn’t

    An ordinary payment needs one trustee’s signature. Above the threshold your own resolution sets, it needs two, and one of the two has to be the treasurer. That’s a row in the database, not a policy on a page nobody re-reads.

  • 03

    Unable to prove a decision was properly taken

    Every act — and every attempt that was refused — is written to the record with who did it and when. “We definitely discussed that” stops being two trustees’ competing memory of a meeting.

  • 04

    Losing the scheme’s history when the agent changes

    Minutes, ledgers, the arrears book, every certificate, every audit line — they belong to the scheme, not to whoever happens to be managing it this year. Export all of it, any day, in full.


The decision queue

Nothing reaches you without its working shown alongside it.

A contract renewal, a payment, an arrangement with an owner behind on their levy, a bank asking for records — every open item carries the same four lines before it carries an action. You’re never asked to take it on faith.

Time-boundRaised by Nexorah · open 9 days

Generator service contract expires in 42 days

The previous renewal required three written quotations before award. I can prepare the request, send it to the three contractors used in 2023, and put the comparison in front of you for approval.

Where this came from
Generator contract cl. 9 · invoices 2023–26
Rule that applies
Resolution 2023/07 — 3 quotes above R25 000
Who may approve
Any two trustees · treasurer must be one
What happens next
RFQ closes 17 Aug · comparison returns here
Prepare the RFQSee the 2023 awardDefer to the meetingWritten to the record either way
Also waiting
Sorted by consequence, not by who shouted
  • Unit 45 · arrangement over two months
    R12 450 · credit policy allows up to three months · treasurer must be one of the two approvers
    Approve
  • Standard Bank · read-only access, 30 days
    Financials and arrears summary only · bond assessment, unit 5 · expires on its own
    Grant
The signing mandate

One signature moves an ordinary payment. Two move a large one — and one has to be the treasurer.

It isn’t a rule everyone is trusted to remember. A signature is a row in the ledger, unique to that trustee and that payment, so the same person physically cannot sign twice — and a payment releases the moment the mandate is actually satisfied, counted, not asserted.

Waiting on a signature
  • Kruger Electrical — gate motor replacement
    R6 850
    4.2 Repairs & maintenance one signature required
    ✓ SignedReleased — mandate met
  • Hollard — insurance premium, August instalment
    R18 400
    4.3 Insurance two signatures, one must be the treasurer
    ✓ SignedWaiting on the treasurer — not yet released

Sign a payment twice and the second attempt is refused, not quietly ignored — and whether a signer was the treasurer is fixed the moment they sign, not looked up again later, so a change of board can’t rewrite a payment’s mandate after the fact.

The audit trail

Every act is written down. So is every refusal.

The record isn’t only what the trustees did — it’s what was attempted and stopped, too. A payment signed twice by the same trustee, a second signature offered by someone who isn’t the treasurer when the mandate calls for one: both are refused at the database, and both are still a line in the trail, attributed.

  • 3 Aug, 14:12payment.signedTreasurerHollard — insurance premium, R18 400
  • 3 Aug, 11:40payment.sign.refusedTrustee“The remaining signature must be the treasurer’s.”
  • 2 Aug, 16:05decision.resolvedTrusteesUnit 45 — arrangement approved
  • 1 Aug, 11:20grant.createdTrusteeStandard Bank — financials summary, 30 days
  • 30 Jul, 09:15payment.sign.refusedTrustee“You have signed this one — the second signature must be someone else’s.”

Nothing here needed a trustee to remember to look. It was already written by the time anyone asked.


The statutory calendar

The clock runs whether or not the agent does. Sorted by date, never by importance.

A lift certificate that lapses isn’t a matter of opinion, and it’s the trustees who carry it personally — not the managing agent, and not the caretaker who mentioned it once in passing.

  • Fire equipment annual service
    City of Cape Town Fire & Rescue · Lapsed 27 Jul 2026 — not yet booked
    04 Sept 2026
    Not booked
  • Lift certificate of compliance
    Department of Employment and Labour
    08 Sept 2026
    Not booked
  • CSOS levy return and payment
    Community Schemes Ombud Service
    23 Sept 2026
    Not booked
  • Insurance renewal
    Hollard
    17 Oct 2026
    Not booked
  • Annual general meeting
    STSMA s.6(1)
    17 Jun 2027
    Not booked

The demo scheme runs this same calendar, live, at /demo/governance. Book an item there and it moves out of the list, same as it would for yours.

See the mandate hold. Don’t just take our word for it.

The queue, the mandate and the audit trail above are exactly what’s running at the live demo — a simulated 100-unit Cape Town scheme with three years of ledger behind it. Sign a payment. Try to sign it twice. Watch the refusal land in the trail.

No account needed — it runs on a simulated scheme with its whole history.