How to choose housing community management software: test one real process, not a feature list

Start with the tasks that consume your team’s time

For one working week, record tasks that require manual copying, searching for attachments or comparing several versions of a file. Add their frequency, working time and the consequence of an error. “We do many settlements” tells a supplier very little. “Two employees spend four hours reconciling payments and preparing a statement for the board” gives you an operational baseline.

For a firm administering several buildings, a repeatable process matters more than a single attractive screen. Check whether your team can apply consistent working rules while keeping each association’s records separate. Also distinguish data problems from software problems. A missing resolution setting a charge rate or an unreconciled opening balance remains a problem after changing systems.

Select five representative tasks: an ownership change, monthly charges, a correction, a maintenance case and a document request. Define the starting information, expected result and approving person for each task. You can then compare suppliers on the same work instead of following the order of their presentations. Prepare a scorecard recording the outcome, time, manual steps and corrections. Also identify who ran the test: the presenter or an employee of your firm. If success required a support intervention, record the help provided. Do not award a full score for an outcome that the future user cannot repeat independently. Use the same scorecard with every supplier you compare.

Separate the core records from optional modules

Your shortlist might require association records, units, owners, charges, documents, case handling and data export. Confirm the exact scope in each offer. The owner record should let you understand which period the information describes. The current contact person is not necessarily the person associated with a liability recorded several months earlier.

Accounting, KSeF handling, OCR and voting may be separate modules. Ask which capabilities are included in the proposed plan, which require configuration and which are still planned. A roadmap promise should not receive the same score as a function demonstrated successfully. Ask for the module name and the commercial conditions in writing.

Use four statuses for each requirement: tested and working; available through an additional paid module; requires work outside the system; not confirmed. Add a reference to the evidence, such as an export file, an instruction or the test result. This matrix is more useful than dozens of unqualified “yes” answers.

Build a demonstration with measurable results

Prepare a fictional association with twelve units, a jointly owned unit, a garage and an ownership change during a month. Add two charge rates, a correction and three payments: an identifiable payment, a payment with an ambiguous reference and an amount exceeding the current charge. Write the expected result for each task before the demonstration.

Ask the supplier to calculate charges, identify the basis for the rate and produce information for an owner. Then change one input and examine the correction. Ask what happens to the previous document and whether an employee can explain why the record changed. A successful presentation is the first stage. The next stage is repeating the task with a future user operating the software.

You do not need confidential production data for this comparison. Invented names, addresses and account numbers reduce unnecessary disclosure. If a later pilot needs real data, first agree the purpose, limited scope, user permissions and processing arrangements. Do not upload a full production archive simply because it would make a demonstration more convenient.

Test how several employees work together

Create separate accounts for a building administrator, a payment reconciliation employee and a colleague who only helps with documents. Check whether the document user can change a rate or download information from an association outside their assignment. Test a denied action as well as an allowed action. Hiding a button in the interface is insufficient evidence of an effective access restriction.

Remove a test employee’s permissions and check what happens. Can the account still enter the system? Does the history of earlier actions remain understandable? Establish who may grant roles and what record the system keeps of that decision. Small firms rely on cover during holidays and absences, so transferring cases and access deserves a specific test. Test two employees working on the same case. Change its status in the first account and open it in the second. Check whether the second employee sees the current position and can accidentally overwrite an earlier decision. Record the result together with the working rule your team will follow.

Login protection should reflect the account’s importance. The NCSC recommends additional protection for important online accounts, including two-step verification when passwords are used [3]. Check the available methods, account recovery and the process following loss of a phone. These are purchasing criteria; they do not imply that every product provides every method mentioned.

Check document retrieval and owner inspection

Article 29(3) of Poland’s Ownership of Premises Act gives each unit owner a right to inspect the board’s activities [1]. Your system should help prepare documents for a specific request. A document repository does not itself decide who may receive each attachment or which personal information requires restricted disclosure.

Test retrieval by association, period and case. Open the document, check legibility and inspect the relationship between the attachment and its record. Prepare a package for an authorised recipient. Assess whether an employee can limit the package without copying the entire archive onto a personal computer.

Agree how document versions and approvals are managed. After a correction, employees should be able to identify the current file and locate the earlier version. Organisational rules remain necessary even if software provides a change history. The application cannot independently decide whether an uploaded resolution was adopted correctly.

Ask for evidence about data and security

Request the data processing description, storage locations, subcontractor information and incident reporting process. Determine the roles of the association, administration firm and supplier from their actual activities. Where one party processes data on another’s behalf, appropriate contractual arrangements are necessary. The Polish supervisory authority has identified failures in these arrangements in an owners’ association case [2].

Ask questions that can be answered with a document: how supplier staff access is restricted; how backups are made; who requests recovery; when recovery was tested; and how to report a problem outside normal office hours. “Secure cloud” is a label. An instruction, defined responsibilities and a test result give you something to evaluate.

Keep data export separate from a complete system backup. An export of unit records may omit attachments, change history or configuration. Specify each required scope separately in the offer and exit arrangements. Check whether information needed for continued administration remains readable without an active licence from the previous supplier.

Calculate a full year and the cost of leaving

Put subscription fees, modules, import, training, employee time, support and termination exports in one comparison sheet. Mark unknown prices as “to be confirmed”. An unknown cost is not zero. Separate one-off and recurring amounts and compare offers on the same tax basis, with the same number of associations, units and employees.

For an internal calculation, if implementation requires two employees to work ten hours each, the labour cost is twenty hours multiplied by your chosen internal hourly rate. This is a planning assumption, not a market benchmark. Estimate savings from tasks measured during the pilot and include review time and correction of errors. Do not treat every automated step as time saved without checking the resulting workload. Include the period when old and new processes run in parallel, data preparation before import and access to archives after termination. Compare the same horizon: the complete first year and a later year of ordinary operations. One-off implementation can change the first comparison, so keep both calculations visible.

Check limits on units, employee accounts, document storage and operations. Ask how an additional association is billed and which services require a separate order. A low entry price may change after adding a module necessary for your work. Select a scope that supports the full working year rather than only the easiest demonstration.

Make the decision after a pilot and an export test

Run a limited pilot with a named implementation owner. Set its dates, tasks, acceptance criteria and rollback process. Your proposed criteria might require all balances in the test set to match, correct charge calculations, no unauthorised access between associations and readable exported documents. Adjust the criteria to your workload and risks; they are operational decisions rather than statutory thresholds.

Weight requirements before comparing results. A charge calculation error or inability to retrieve necessary data should block purchase even if the interface receives a high score. For other criteria, compare time spent, corrections needed and user independence. Save the test result with the quotation and written agreements so that the final choice has an identifiable basis.

You can evaluate WM Administrator using the same scenario. Review records, charges, documents, cases and exports, then confirm the availability of any additional modules before deciding. Check the scope of the program for property administration firms and bring your task list to the discussion. A useful demonstration ends with evidence that your team can use.

Red flags

• “export” means only a few PDF reports;
• correction erases the original record;
• several people use one account;
• import publishes ambiguous data;
• an amount cannot be traced back to source and rule;
• data location or subprocessors are unclear;
• pricing cannot be reproduced without an individual quote;
• the product promises compliance without defining responsibility boundaries.

A 30-minute demo

1. 5 min — import a small sample;
2. 5 min — reconstruct one charge;
3. 5 min — correction and history;
4. 5 min — roles, MFA and community isolation;
5. 5 min — export and offboarding;
6. 5 min — price for a specific scenario.

See how WM Administrator covers these areas