Handing over a property-management case: a record the next person can act on

Source → Verification → Decision → Evidence

A property manager goes on leave while a repair case remains open. The next person finds an email thread, a contractor's message and a note that says “waiting for approval.” The note does not identify who must approve what, whether the resident received an update or when the contractor last attended. The replacement manager starts reconstructing the case instead of moving it forward. The delay comes from missing relationships and ownership, even though the documents are available.

Choose one type of case, such as a routine maintenance request, for the first handover project. The deliverable is a checked case packet with a current next action, authorised owner, evidence and unresolved issues. AI can help prepare the chronology and identify missing fields. It should not decide legal responsibility, approve expenditure or disclose resident information independently. This guide describes Brillnet's operating recommendations and keeps jurisdiction-specific duties separate.

Identify the property and the authority to act

A case needs a stable identifier and the correct property, building or unit context. Similar street names and reused apartment numbers can produce convincing but wrong matches. Preserve the source identifiers and confirm the relationship before combining records. A new filename is not a reliable case identity.

Record which organisation manages the property and under what relationship it acts. A Polish housing community, cooperative, landlord and property portfolio can have different governance and contractual arrangements. Do not translate one organisation's approval route into a universal rule for another jurisdiction or legal form.

The receiving manager needs to know the authority relevant to the next action. That can involve an existing contract, a delegated spending limit or a designated decision maker. Link to the approved source of that authority. The assistant should show a missing authorisation as an open issue instead of inferring it from the previous manager's job title.

Reconstruct events from confirmed records

Arrange the case by actual events: receipt of the request, assessment, instruction to a contractor, visit, report, decision and communication. Keep the source and date with each event. An email discussing a possible visit should not appear as proof that the visit happened.

Separate event time from record time. Someone can enter a note two days after a visit. The receiving manager should see both dates where they matter. If the source only provides the message date, label the event date as unknown rather than creating a precise timestamp from context.

A contractor's “done” message needs interpretation within its source. It might describe attendance, temporary containment or full repair. The packet should preserve the wording and ask the owner to confirm the result. Replacing it with a generic “case completed” status can close work that still requires inspection or communication.

Give every open case a next action

“Waiting” is not a sufficient instruction for the receiving manager. Record the awaited decision or document, its owner, the last confirmed contact and the follow-up date set under the organisation's process. A deadline needs a source or an explicit operating decision, not an assistant's invented urgency.

The next action should be concrete: obtain the contractor's dated report, ask the authorised owner to decide on the estimate or confirm that the resident received the scheduling information. State which record will show completion. This reduces the need for another person to read the entire thread before acting.

Where the case depends on an external party, retain the dependency separately from internal ownership. A contractor can owe a report while the manager remains responsible for following up. Passing an email to the contractor does not transfer every management duty or establish that the matter has been resolved.

Build a packet that answers the receiving manager's questions

Use the existing case system as the authoritative record if it can support these fields. A separate handover spreadsheet can be useful temporarily, but it needs an owner and a reconciliation route. Otherwise, the case system and the handover sheet soon show different next actions.

This is a recommended operating structure. It does not establish legal deadlines, spending authority or an identical record requirement for every property-management business.

Keep urgent incidents on the approved response route

An ordinary handover queue must not become the only route for a potentially urgent hazard. Staff need the organisation's approved incident and emergency instructions, with the responsible contact and escalation method. The assistant should recognise an unresolved urgency assessment and direct the case to the authorised person rather than generating its own safety decision.

The actual response depends on the event, property, contract and applicable law. A leak, electrical report or access problem can require different treatment. This guide does not provide technical repair or emergency instructions. Connect the handover record to the organisation's established response process and preserve the actions taken there.

Test a case received shortly before the manager's leave. The receiving person must know whether the incident route has already been activated and who currently owns it. A neat chronology that hides an outstanding escalation is not a usable handover.

Review resident information before sharing the packet

Case files can contain contact details, complaints, financial information, photographs and information about health or personal circumstances. The receiving manager needs the data required for the role, while a contractor may need a smaller set. A complete internal packet should not automatically become an external attachment.

The GDPR requires assessment of purpose, legal basis, roles, access, processor arrangements and security for the actual processing. Articles 5, 6, 28 and 32 are relevant to this design. Determine the controller and processor relationship from the circumstances and contracts; the term “property manager” alone does not settle every allocation. [1]

UODO's published housing-community enforcement case provides a Polish example of data-protection responsibilities in that setting. It is not a universal role-allocation rule for every management arrangement or country. Use it as context for checking your own documented responsibilities. [2]

Verify the recipient and content of every outgoing update

Before sending a case update, confirm the intended recipient, relationship to the property and information needed for that message. A resident, owner, board member and contractor can have different access needs. A familiar email address in an old thread does not automatically authorise receiving the current full packet.

An assistant can draft a concise update from approved facts. The responsible person should check that the draft does not promise a completion date, approve a cost or attribute fault without authority and evidence. Keep operational communication separate from promotional additions. Electronic-communications rules, including the national implementation of Directive 2002/58/EC, need their own assessment for marketing. [3]

Record the sent version and delivery outcome where the communication system supports it. A prepared draft is not a sent message, and a provider's accepted request does not always establish final delivery. An uncertain result should stay visible so staff do not resend automatically and create conflicting updates.

Test a fictional case with an incomplete contractor report

Consider a fictional repair case in which a contractor attended on Tuesday, sent an invoice on Wednesday and promised a written report later. The outgoing manager's note says “repair handled.” The receiving manager needs to know whether the invoice concerns a completed repair, an inspection or temporary work.

A useful handover packet links the attendance message, invoice and unresolved report. It records the next action as obtaining and reviewing the report under the authorised process. It does not label the case closed because a document named “invoice” exists. The example illustrates evidence design and does not determine when payment is legally due.

Add a second version of the example with a corrected property identifier. The system should preserve the correction and prevent the old relationship from remaining in the receiving manager's action list. This checks the integrity of the handover, not merely whether the assistant can summarise a long email.

Control changes while the handover is in progress

A case can change between preparing and accepting the packet. Record the preparation time and review the latest authoritative state at acceptance. A new contractor visit or owner decision may alter the next action. Do not freeze the case solely because a handover PDF has already been generated.

Assign a receiving owner explicitly and record acceptance according to the organisation's method. Silence should not stand in for a documented transfer if your process requires confirmation. Until the transfer is completed, the organisation needs a clear responsible person for follow-up.

Keep corrections as dated changes with a reason. Replacing the old next-action note without history can make it impossible to explain a delay or misunderstanding later. Retain the evidence required by the organisation's purpose and applicable obligations, with appropriate access and retention. [1]

Measure whether the receiving person can act

Evaluate the packet using historical cases with known outcomes. Ask a manager who did not prepare it to identify the next action, authority and evidence. Record questions that required contacting the outgoing person. A successful handover should reduce reconstruction work while retaining the information needed to make the next decision.

Track missing owners, unsupported closure states, wrong property relationships and inappropriate information sharing separately. Measure review and correction time as well as drafting time. A short automated summary can consume more work if staff must repeatedly verify every date and relationship.

Use a hypothetical sample of ten cases only as an illustration of a pilot design, not a benchmark. Include at least a case with missing evidence, a changed identifier, an urgent escalation and an external recipient with limited access. Report the actual sample and limitations before extending the workflow.

Select software after the handover rules are clear

WM Administrator's public description covers property-management companies and housing communities, including units and owners, charges, funds, documents, resolutions, cases, deadlines, roles and export. Selected accounting, OCR, voting and purchasing capabilities have their own module and configuration context. Confirm the current scope for the intended process. [4]

An integration should connect the reviewed packet to the existing case record and enforce the receiving person's access. It should not independently approve expenditure, send unrestricted resident information or decide contractual responsibility. If document-based staff learning is considered through CrewShift or Zmianowo, confirm its early-access scope and keep a completion record within what was actually assessed.

Bring one anonymised case, its current next action and the authority route to an implementation discussion. The first deliverable should let the receiving manager continue the case without reconstructing its history from scattered messages. That provides a concrete basis for further automation and a clear owner for the remaining work.

Have the receiving manager verify one open case

A fictional case packet records that a contractor attended and that the matter awaits an owner's decision. The receiving manager can read the chronology but cannot identify the decision required. An estimate and an invoice appear in the folder, with no clear link to the proposed next action. The acceptance test should ask whether the packet enables the next authorised step, not merely whether it contains all available files.

Ask the receiving person to state what is awaiting a decision and which source explains it. The answer might concern an estimate, inspection result or further instruction under the actual management arrangement. If the packet does not establish that relationship, retain an unresolved issue and contact the responsible owner. The assistant should not infer approval of expenditure from an invoice or from a brief note saying that the contractor handled the matter.

Check the source of authority for the proposed action. A staff role in the case system can provide access to the record without granting every spending or contractual power. Link the relevant delegation, contract or decision route according to the organisation's process. The receiving manager should know where the authority comes from and which question must be escalated.

Next, verify the latest state in the authoritative system. The contractor may have submitted a report after the handover draft was prepared. Preserve the draft's timing and update the next action using the confirmed new information. A completed PDF should not prevent the case record from reflecting later events. Record the receiving owner's acceptance by the method the organisation uses.

Consider the outgoing communication separately. The resident, property owner and contractor can need different information about the same event. An internal case packet should not automatically become an external attachment. Staff verify the recipient, the purpose and the exact approved content before sending an update. Keep any uncertain delivery outcome visible for follow-up.

The exercise measures whether a person who did not prepare the packet can act without reconstructing the history from memory. Include review time and unresolved questions in the result. Brillnet recommends this test for a bounded handover pilot. It does not determine legal responsibility, create a universal response deadline or authorise payment. Those decisions still follow the actual contract, property context and applicable obligations.

Sources

The sources support the identified legal facts, guidance and public product scope. Workflows, fictional examples and evaluation measures are Brillnet's operating recommendations. Source review: 2026-10-04.

1. European Parliament and Council — GDPR: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02016R0679-20160504
2. UODO — housing-community case of 22 March 2023, Polish jurisdiction: https://www.uodo.gov.pl/pl/138/2656
3. European Parliament and Council — Directive 2002/58/EC, Article 13; assess applicable national implementation: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02002L0058-20091219
4. WM Administrator — public product scope, modules and limitations: https://wm-admin.pl/
5. CrewShift / Zmianowo — training, tests and the meaning of a completion record: https://crewshift-app.com/en