Printable guide
Housing community handover — checklist
The minimum set of data, documents, balances, cases and access records needed for a controlled community handover.
A useful handover record identifies what was transferred, what is missing and who must resolve each omission. A signature under “the documentation was handed over” does not establish the number of files, the reconciliation status or the next inspection date. A firm taking over administration needs an inventory it can use to begin work and later verify responsibility for unfinished matters.
This guide concerns Polish owners’ associations, known as wspólnoty mieszkaniowe. The form below is an editorial handover template, not an official statutory form. Adapt its financial and operational fields to the contract, management arrangement and actual scope of service. Names, amounts and dates used in examples are fictional. The English terminology explains a Polish process and should not be read as guidance on another country’s property law.
Software for managing a Polish housing community
Distinguish the statutory record from a service handover
Article 29(1b) of Poland’s Ownership of Premises Act requires the board or manager identified in that provision to prepare a record of taking over the property and its technical documentation on the association’s behalf. The provision also covers keeping technical documentation and maintaining the owner and share register [1]. It does not supply one form for every financial and operational aspect of changing an administration firm.
Establish what the particular exercise covers: property and technical documentation, a contractual change of administrator or a broader transfer of duties. Do not assume that every administration firm is a manager entrusted with management under Article 18(1). Read the relevant documents to establish representation and responsibility. A service provider’s job title does not determine its legal position.
The package can consist of a main record and several annexes. Record the parties’ authority and scope in the main document; put detailed inventories in annexes. This confirms the handover without repeating every owner’s personal data and every financial entry in a broadly circulated main document.
Agree a reference date and authorised people
Choose the date to which balances, contracts and open cases relate. Keep it separate from the signing date and the new firm’s service commencement date. Documents may arrive earlier and payments later. Without a reference date, two valid figures can appear to contradict one another.
Check the authority of the people signing and receiving information. Record their role and the document authorising representation or the activity. An employee’s presence at the meeting is insufficient. Establish who may accept differences and who may close an omission. If a matter is disputed, retain each party’s position separately rather than writing a shared conclusion that neither has accepted.
Send the expected annex list before the meeting. That allows originals, exports and statements to be prepared instead of discovering gaps while signing. Give the receiving firm time to check the material. Receiving a storage device and accepting the data’s correctness can occur on different dates; state that distinction explicitly.
Main handover form
Copy the following fields into your document and replace the brackets. Mark an inapplicable field with the reason. A blank field forces the next employee to guess whether information is missing or the category does not apply. Identify the annex versions so that later additions cannot be confused with the original package.
| Field | Information to enter |
|---|---|
| Document identifier | [HANDOVER/year/number], version [number] |
| Association and property | [name, address, association identifier; additional identifiers where needed] |
| Scope | [property/technical documentation/administration services/other defined scope] |
| Basis | [contract, resolution or other relevant document, date and scope] |
| Transferring party | [organisation, person, role and authority] |
| Receiving party | [organisation, person, role and authority] |
| Dates | state at [date and time]; delivery [date]; services begin [date] |
| Annexes | [identifiers A–G, versions, page or file counts] |
| Receipt outcome | [received; received with reservations; named item not provided] |
| Gaps | [issue number, responsible person, deadline and closure evidence] |
| Subsequent events | [method for transferring payments, invoices and correspondence after the reference date] |
| Signatures and reservations | [authorised signatures; separate statements where necessary] |
For example, balances can be stated at 30 September, documents delivered on 2 October and services started on 5 October. Payments received between these dates need an agreed transition event list. Merely naming the dates does not automatically add those events to the receiving firm’s records.
Annex A: technical documentation and building access
Separate construction documentation, as-built documentation, the building log, inspection records and other material relevant to the property. For each item give the title, covered period, format, volume or file count, location and check result. “Technical binder” is too vague for a later employee to identify the material reliably.
Do not declare completeness without stating what was checked. You can record that two volumes were received, listed items were checked for presence and substantive review is scheduled by a named date. If something is missing, identify it as missing. “Probably held by the contractor” does not establish that the receiving administrator has usable access to it.
Keep a separate inventory for keys, remotes and technical access. Record the identifier, quantity, purpose and recipient. Do not put active passwords in a widely circulated handover record. Transfer access through an approved channel, test it and then change or revoke the previous team’s permissions at the agreed time. The handover should leave usable access with identified people.
Annexes B and C: registers and financial records
Transfer the current unit, owner and share register with a reference date and sources needed to investigate differences. Joint ownership and ownership changes should be identifiable where relevant to administration. Limit personal information to the handover’s purpose. Personal identifiers should not be copied merely because the previous workbook included them.
Prepare financial statements by association, account and relevant type of settlement. Identify unit balances, receivables, overpayments, supplier liabilities and unresolved items. Explain the sign convention: a positive balance can mean different things in different systems. Include the supporting report or document for each control total and state the covered date.
For example, a schedule may list 48 units, PLN 12,400.00 in receivables and PLN 3,100.00 in overpayments. The receiving firm should verify allocation to units as well as the totals. A PLN 200 overstatement for one unit and equal understatement for another leaves a correct total and two incorrect individual positions.
The bank account balance is not the same measure as the owners’ balance schedule. Do not force the amounts to agree with a manual adjustment. Differences may relate to invoices, incoming payments, funds or the timing of entries. A reconciliation must explain the relationship between the records, rather than just produce a final number.
Annexes D and E: contracts, deadlines and open matters
The contract inventory should identify the parties, subject, term, notice deadline and location of the signed contract and amendments. Add deposits, guarantees and agreed actions requiring attention. Do not copy the whole contract into a table. Include enough information for the next administrator to locate it and act before the relevant deadline.
Give each open case an identifier, short description, last action date, current status and next action. Name the responsible person and deadline. “Roof warranty claim in progress” is insufficient. “Notice sent to contractor on 18 September; response expected by 9 October; attachment D/07” provides a basis for continued work.
Separate urgent matters from those that can wait for normal review. An active incident, procedural deadline or expiring contract requires clear identification and direct handover to the responsible person. The record does not replace responding to a hazard. It preserves evidence that the matter reached a named recipient with a stated action.
Annex F: files, export and data protection
Describe the digital package with a folder or file list, formats, document counts and delivery method. Record the export version and whether it includes history, configuration and attachments. Open sample files at the recipient’s end. An unreadable storage device does not provide an operationally useful documentation handover.
Agree the channel, authorised recipients and handling of information after services end. Determine parties’ roles from their actual activities. Where data processing on behalf of another party occurs, establish the appropriate arrangements; UODO has identified missing contracts and inadequate processor verification in an association case [2]. Signing a handover document does not resolve those responsibilities on its own.
An owner’s inspection rights do not require placing all personal information in a widely distributed main record. Keep detailed schedules under appropriate access control. When disclosing a specific document, assess the purpose and scope. An export for a successor service provider and information sent to every owner are different processing activities.
Annex G: omissions and final acceptance
The issue register should contain at least an identifier, description, operational significance, responsible person, deadline and closure evidence. For example: “G/03 — lift maintenance amendment missing; transferring party obtains it by 9 October; closed when the signed scan is filed.” “We will send it later” needs a name and date to become a usable commitment.
At acceptance, distinguish items merely received from items verified. If a balance remains disputed, preserve the competing positions and evidence. Acknowledging receipt of a file should not be described as confirming the correctness of all settlements. Wording should match the checks actually completed and any remaining limitations.
After gaps are resolved, prepare an addition referencing the main record. Do not silently replace a signed document with a revised version. A firm receiving multiple associations should use a consistent identification and filing method so that colleagues can locate the package during absence or staff changes. Run a short operational check: an employee who did not attend the handover should find two specified contracts, identify the next action deadline and open the supporting document for a selected balance. Check the outcome against the inventory and record any difficulties. If a document can only be found through the previous administrator’s memory, improve the index or instruction. This check does not establish completeness of the whole archive or correctness of every settlement. It shows whether a colleague covering the work can use the package for the identified tasks. Keep that distinct check result with the handover record.
You can assess WM Administrator as a place to maintain the received association’s records, documents and cases. Check the program’s scope, export capabilities and implementation arrangements. Preparing the record and checking its annexes remain the work of authorised people, regardless of the software selected.
A checklist for day-to-day work
- current register of units and owners
- ownership shares and ownership change history
- balances, charges and funds
- bank statements and unreconciled payments
- contracts, resolutions and powers of attorney
- open cases, deadlines and responsible people
- access permissions, roles and MFA rules
- data copies and the full export procedure