Handing over a community without losing documents or context

Legal requirements and working controls

This guide concerns housing communities in Poland. Under Article 29(1b) of the Polish Act on Ownership of Premises, the management board or manager entrusted under Article 18(1) must prepare a protocol taking over the property and its technical documentation on the community's behalf. The provision also addresses retaining technical documentation and maintaining the list of owners and their shares. [1]

That provision does not prescribe one template covering every detail of bank reconciliation, data exports, integrations and complaints. The process below adds practical controls for those areas. Match its scope to the contracts, management arrangements and actual property. Where a change affects a management arrangement established under Article 18(1), the particular requirements of Article 18(2a) must be considered. Not every replacement of an administration firm is that type of change. [1]

Check each party's authority first. The recipient should have a documented basis for receiving the records. Sending a new contract to a general mailbox is not sufficient evidence that someone may receive the complete set of owners' personal information.

Agree the cut-off and operational responsibility

Agree the date, time and scope of the reference position. Use one time zone. For example, financial records might cover transactions up to 31 October at 23:59 Polish local time. This is an illustrative agreement between the parties, not a statutory deadline.

Record who handles payments, emergencies, correspondence, invoice collection and register changes before and after the cut-off. If there is a transition period, set its end and the procedure for recording late events. Two teams should not change the same balance simultaneously without an agreed reconciliation mechanism. A late bank transaction needs a defined route rather than an informal phone call.

Name a coordinator on each side and the community's approver. For matters requiring a board decision, specify an escalation channel. Also agree who responds to an emergency on handover day. A technical incident does not wait for the last attachment to be signed, and the contractor needs to know whose instruction they can accept.

Inventory the records before exporting them

List premises, owners, ownership shares, charges, balances, receipts, supplier liabilities, funds, meters, contracts, resolutions, correspondence and open cases. For each collection, record its location, responsible person, reference date and delivery format. Check technical documentation separately. It is not merely an attachment to the accounting spreadsheet.

Include paper originals, keys, storage media, inspection records and information about ongoing proceedings. State whether each item is being transferred completely, partially or through continued access. “Stored in the cloud” does not explain who can reach it the following morning or what happens when the previous firm's subscription ends.

Keep different communities' information separate. Before sending an export from a portfolio system, check its actual scope and recipient. A folder name does not prevent another client's data from entering the package. Record the scope check in the protocol or a supporting attachment. When a collection is missing, list the absence instead of quietly leaving it out.

Reconcile finances against independent evidence

The bank balance, owners' receivables and supplier liabilities describe different parts of the financial position. Do not compare them as if they were one total. Identify the appropriate control evidence for each: bank statement, balance schedule, source-document list and the adopted recording rules.

For receivables, show the cut-off balance, its component entries and how incoming payments were allocated. For liabilities, identify the supplier, invoice, payment deadline, approval status and any dispute. List advances, overpayments, unallocated receipts and charges awaiting correction separately. Combining them into a single unexplained opening balance makes the first complaint difficult to answer.

For the renovation fund, explain income, expenditure and commitments already made. A bank balance alone does not identify funds committed to particular jobs. Include the approved plan and contracts for work already started. The incoming administrator needs to understand decisions taken before their appointment and distinguish an available cash balance from a sum already required for accepted obligations.

Example: a difference that must remain visible

This is a control example. The balance schedule covers 48 premises. A bank statement shows a PLN 1,500 receipt before the cut-off, but the transfer has not been assigned to a premise because its description is ambiguous. The money is in the bank account; it is not yet part of a properly reconciled owner's balance.

In the exception register, record the transaction identifier, amount, date, reason and person responsible for clarification. The incoming team acknowledges receiving information about the unresolved item. It should not certify that every owner's balance is correct while that item remains open.

Agree who contacts the payer and when they supply an update. Once clarified, create a linked allocation entry and retain both the original exception list and the later change. Assigning the payment to an arbitrary premise merely to close the protocol passes the problem to the next administrator and to an owner. A signed document does not make that guess accurate.

Transfer cases and deadlines as well as documents

Each open case needs a description, current state, completed actions, next step, responsible person and deadline. Attach the relevant records. A leak, court proceeding and equipment replacement quote have different priorities. Giving all three the status “in progress” provides very little operational guidance.

Create a near-term deadline list covering inspections, insurance policies, expiring contracts, payments, meetings and dates arising from correspondence. Confirm each date against its source. A calendar entry is a reminder, but it is not always evidence of the underlying deadline. Identify the person who will check completion after the transfer.

For disputed cases, describe established facts and the current stage without personal judgements. Indicate which decisions need the board or a specialist. Do not transfer an unverified employee comment as a proven statement about an owner's debt or responsibility. Preserve the question and supporting documents so the new team can complete the assessment.

Test files and their relationships

The recipient should open the package before confirming completion. Check record counts, dates, encoding, units, number formats and identifiers. Include a field dictionary and relationship descriptions connecting premises, owners, charges and documents. Even a valid CSV can be unusable without those definitions.

Choose a sample containing an ordinary premise, co-ownership, a correction, an overpayment and an open case. Follow a balance back to its components. Open a technical document and confirm readability. A file hash can help establish whether a transmitted copy changed; it does not establish whether the original content is correct.

Retain the original package, check report and mapping into the replacement system. Repeat the reconciliation after import. “Import completed” confirms a technical operation, not correct balances or complete documentation. If a field cannot be mapped without guessing its meaning, record that exception before allowing the new data to become authoritative.

Confirm the property's actual condition

Check the physical position together with the documentation. Record known defects, temporary protections, work in progress and access to technical rooms. Equipment records need identifiers, operating information and the available inspection documents. Mark missing records explicitly. Do not enter “no issues” where nobody performed the relevant check.

Involve people capable of recognising material problems. Where a specialist assessment is necessary, arrange it and record the deadline. A photograph can document a visible condition, but it does not replace an assessment that is required for the equipment. Distinguish acceptance of documents from confirmation that an installation is safe. The difference prevents unverified assurances becoming the incoming team's assumed facts.

Protect the transfer and remove obsolete access

The GDPR requires appropriate safeguards and accountability. The disclosure scope should reflect its purpose and the recipient's role. [2] Use a controlled channel, verify the recipient and limit access duration. Transfer passwords, keys and certificates through a separate protected procedure, not an attachment to the general handover record.

Inventory accounts, roles, bank permissions, mailboxes, integrations and document access. Agree when old permissions end, verify deputies and test new accounts. For KSeF, review the complete permission list. Ministry guidance explains that removing the permission manager does not automatically cancel permissions previously granted to others. [5]

Where the former provider acts as a data processor, close the processing arrangement correctly. Article 28(3)(g) GDPR provides for returning or deleting personal data according to the controller's choice, subject to legal requirements for continued storage. Agree instructions and completion evidence instead of demanding uncontrolled deletion of everything. [2][3]

Close the handover with evidence of continuity

The protocol should identify the parties, authority, cut-off, attachments, check results, differences and responsibility for further work. Distinguish acknowledgement of receipt from confirmation of completeness. Keep reservations visible when the meeting ends. Signing the package is not a reason to remove a genuine unresolved issue.

After takeover, perform the first control cycle: read a balance, prepare a charge, find an invoice, handle a case and check export. Reconcile the results and remaining exceptions. This supplies practical evidence that work can continue.

If information reaches an unauthorised recipient during transfer, initiate the breach assessment. In April 2026, Poland's data protection authority reported a penalty against a community after a settlement disclosure was not notified. An owner's right to inspect management does not authorise indiscriminate disclosure of other owners' data. [4]

View WM Administrator's scope and test a handover process. Use sample data to check whether the next person can reconstruct the position and complete a task without the predecessor's help. That test provides more evidence than a general claim about complete export.