Guides · owners’ decisions
Online resolution voting: keeping a complete decision record
A practical model for online resolution voting: draft version, eligible voters, voting weights, proof of votes, result and implementation. It does not replace legal assessment of the appropriate procedure.
A resolution is not finished when somebody adds up the votes. A property administration company needs to show which text owners considered, who could vote, how the majority was calculated and how the result reached the owners. When evidence sits in an employee's mailbox, a paper folder and a spreadsheet without a change history, an ordinary question becomes an investigation. This guide concerns housing communities in Poland. It distinguishes the Polish legal requirements from practical controls recommended for administration companies; it is not a guide to voting law in another country.
Software for managing a Polish housing community
Establish the management arrangement before drafting
Check the property's management arrangement, the community's documents and any management entrusted under Article 18 of the Polish Act on Ownership of Premises. The number of premises matters too: Article 19 directs properties with no more than three premises to the relevant rules on co-ownership. Do not automatically copy the procedure used by a larger community into that setting. [1]
Within the management model described in the fourth chapter of the Act, Article 22 distinguishes ordinary management from actions exceeding it. The latter require an owners' resolution approving the action and the relevant authority for the board. Adopting the annual economic plan and setting charges covering common-property management costs are examples listed in the Act. [1] An administration contract should not be treated as evidence that an employee holds every power of the community's board.
As an operational control, open a case record with the decision's subject, the responsible preparer, the basis of authority and the required form. Changes to the management arrangement or transactions involving real property may require a particular form. Check that before collecting votes. A mathematically correct result will not resolve an incorrectly selected procedure.
Issue one identifiable text with its complete attachments
Owners need to understand what a vote will authorise. A refurbishment proposal should describe the work, its funding, the spending limit and the responsibility for selecting a contractor. If an estimate supports the decision, identify its date and version. An attachment stating a different amount from the draft creates a preventable ambiguity. Resolve it before distribution.
Give the draft an identifier covering the community, year and specific matter. Preserve the version supplied for voting. Separate editorial corrections from changes affecting the decision. Changing the amount, scope or delegated authority after some votes have been received requires an assessment of how to proceed. Do not replace the document and present earlier declarations as votes on a text those owners never received.
The supporting explanation can set out the operational problem, the alternatives examined and the costs that remain uncertain. That is recommended working practice, not a universal statutory resolution template. Make the trade-off understandable: delaying repairs may lead to another leak, while approving work commits the community to a defined expenditure. An assertion that a proposal is beneficial gives owners much less information than its scope and assumptions.
Verify ownership, shares and representation
Check the current owners' register and shares before calculating anything. Article 29 requires the board or manager specified there to maintain and update that register. [1] Operationally, record when evidence of an ownership change was received, who entered it and which questions remain unresolved. A message from a new resident does not by itself establish entitlement to vote.
Review any power of attorney for the represented person, its scope, date and the applicable form. A tenant, a family member and an owner have different roles. The person who usually reports faults is not automatically entitled to vote. Joint ownership also needs separate attention. Article 23(2b) addresses written appointment of a representative in the specified one-vote-per-owner situation. [1] Do not compress every jointly owned premise into an assumed rule without checking the particular circumstances.
Mark conflicting shares as an exception requiring explanation before publication of the result. Keep unresolved information in a visible list, with an owner and a next action. A contact-address discrepancy, uncertain ownership and an incorrect voting share are different problems. Treating all three as a generic data-cleaning task makes it harder to decide which evidence is actually needed. Before collection starts, preserve a dated dataset used for calculation. A subsequent contact update should not erase which information was used for the vote. If ownership changes during collection, flag the case and establish its effect on entitlement and any earlier declaration. Do not copy an old meeting list without checking it simply because the previous meeting was recent. Retain the basis for the approach adopted.
Distinguish the statutory voting method from the technical channel
Article 23 provides for resolutions adopted at a meeting, through individual vote collection by the board, or through a combination of both. The general rule is a majority calculated by ownership shares, subject to the exceptions stated in that article. [1] A majority of people present at the meeting is therefore not automatically the majority required for the resolution.
Email and an online portal are technical channels. A voting button does not demonstrate that every requirement applying to a particular decision has been met. Establish how the voter is identified, how their declaration is evidenced, how it relates to the specified draft and how a disputed declaration will be handled. Assess the required form and notification method too. Get the proposed procedure checked before launch if it raises legal uncertainty.
A useful operational register identifies the resolution, owner or representative, share, position, date, channel and source evidence. If the same person submits conflicting declarations, do not choose the convenient one. Flag the conflict, establish which declaration can be considered and retain both records with the explanation. The purpose of a register is to reveal an exception while it can still be resolved.
Make the calculation independently checkable
Consider an illustrative community whose shares total 100%. Votes supporting a draft represent 51%, votes against it represent 12%, and the remaining share has abstained or has not voted. Under ordinary share-based counting, the assessment uses the shares of the whole community, rather than only the participants. This illustration excludes Article 23 exceptions and any relevant particular rules in the community's documents. [1]
Before the result is approved, have another person check the draft against the voting records, the shares, representatives' documents, duplicate entries and the arithmetic. This is an operational recommendation, not a statutory requirement to employ two people. It is particularly useful where a company handles many communities and a staff member may otherwise repeat a copied spreadsheet error across several matters.
Preserve a result report stating the counting method and verification date. If an error is later discovered, record the correction, its reason and its effect on the result. Do not silently overwrite the earlier report. An owner asking why a number changed should receive an explanation supported by records, not a guess about what a former employee probably edited.
Control notifications and implementation separately
Article 23 requires written notification to every owner of a resolution adopted with individually collected votes. Article 25 provides a six-week period for challenging a resolution, calculated as specified there from adoption at a meeting or notification of a resolution adopted through individual collection. [1] Do not assume that the sending timestamp of any electronic message settles all questions about notification or the running of a deadline.
Maintain an operational record of recipients, channels, dates and evidence of communication. Returned letters and incorrect addresses need a defined response. Check whether the electronic notification form satisfies the procedure being used. Keep resolution notices distinct from product advertising, resident surveys and ordinary building-work announcements so that the purpose and evidence remain clear.
Filing a challenge does not automatically suspend implementation; Article 25(2) provides for suspension by the court. [1] Nevertheless, keep the resolution's status separate from the work's status. Identify the responsible person, timetable, procurement documents and any remaining approvals. For refurbishment, add a check before contract signing covering the approved spending limit, scope, date and acceptance document. A quotation exceeding the adopted assumptions requires assessment rather than concealment in another attachment. The board report should show the authority for the action and the actual implementation status, keeping the resolution and order connected. An administrator needs to know whether the adopted decision actually authorises the planned step and whether further conditions remain outstanding.
Test the complete file before the next meeting
Choose one completed resolution and reconstruct its sequence without asking its author for help. Locate the draft, attachments, relevant shares, declarations, result report and notifications. Record the time needed and the missing evidence. This tests the actual documentation process. Check that attachments open on another workstation and that the export includes documents held outside the application. Missing evidence often becomes apparent when someone searches for a power of attorney stored in private email. Include a resolution involving an exception, rather than testing only a straightforward case without corrections. That reveals whether the process supports situations requiring an additional decision. Merely having a software subscription does not show that the company can answer owners' questions.
Set a clear working division afterwards. The administrator prepares the file, an authorised person checks the procedure, an assigned employee handles exceptions and the documentation owner closes the case only when the package is complete. A common verification form can help a company handling multiple properties, while preserving the legal arrangement specific to each community.
When evaluating software, give the supplier that exact scenario. Request a demonstration of a revised draft, disputed declaration, corrected share and complete documentation export. Ask what happens when the employee who prepared the vote leaves the company. View the scope of WM Administrator and check it against your process. Base an implementation decision on the observed result and the community's requirements, including any legal review of the procedure.
Sources and scope
For information only. This is not legal, tax or accounting advice; adapt the procedure to the documents and circumstances of the specific housing community.