For self-managed housing communities
Housing community management software for finances, documents and decisions with a complete history
Good administration should not depend on one person who “knows where everything is”. The board, owners and people responsible for finance need appropriate access, while significant operations must remain explainable later.
What community software should do before anyone talks about automation
The foundation is not the number of buttons. It is a coherent register and the ability to answer simple questions:
- who owned a unit during a given period;
- what ownership share applied at that time;
- why a particular amount was charged;
- which payments changed the balance;
- which source document created the cost;
- which version of a resolution was voted on;
- who performed or approved a significant operation;
- which cases and deadlines are still open.
If those answers require combining several spreadsheets and mailboxes, the first problem is not a lack of automation. It is the lack of one trustworthy sequence of events.
Finances that can be explained to an owner
A balance alone is not an explanation. It should lead to the operations that created it: charges, payments, corrections and settlements.
A charge should identify at least the period, source cost, input data, allocation rule and result. If a correction is required, the original record should not disappear. The correction needs its own reason, author and date.
The same principle applies to funds. The bank account balance, renovation plan, liabilities and genuinely available funds are different pieces of information. The system should help keep them separate rather than reducing them to one number.
Resolutions and decisions: wording, vote, result and execution
A resolution is a process, not a single PDF. It should be possible to see what wording was voted on, the relevant owner/share state, when votes were cast, how the result was calculated and what action followed.
The result should connect to implementation: a contract, task, purchase, deadline or document. “Resolution adopted” does not finish the work.
Documents and cases remain with the housing community
Community records should not be scattered across a board member’s private drive, an administrator’s mailbox and an unstructured directory.
In practice the organisation needs access to:
- contracts and amendments;
- resolutions and powers of attorney;
- invoices and cost documents;
- inspection and handover reports;
- insurance policies;
- correspondence linked to cases;
- deadlines and responsible people.
The important question is not only whether a document is available today, but whether the complete context can be handed to the next responsible person without rebuilding the archive from scratch.
Roles and approvals instead of a shared account
One shared account seems convenient until something goes wrong. Afterwards it becomes difficult to establish who actually performed an operation.
A better model assigns roles to individual users and records significant actions. Higher-risk operations can require a fresh confirmation or independent second approval where the organisation’s process requires it.
Moving from Excel or a previous administrator
Migration should begin with preview and validation, not unconditional import.
- Collect current files and set a cut-off date.
- Decide which source is authoritative for units, owners, shares and balances.
- Map source columns to system fields.
- Detect duplicates, missing identifiers and inconsistent totals.
- Test with one housing community first.
- Reconcile unit counts, owners and balances against the source.
- Publish only after differences have been understood.