Dependency on Key Personnel in Rental: What Happens When Your Best Person Is Out?

When a specific person falls ill, no one knows where any process stands anymore. Processes stall, owners ask questions, applicants wait. Not because the team is bad, but because the knowledge resides in the head of a single person.

This is not due to a lack of teamwork. From experience, we know: About 60 to 70% of process knowledge in property management is not documented. It resides in the heads of individual people.

Person-dependency is not an HR risk. It is a system risk.

Those who transfer knowledge into the system make their organization independent of individual absences.

Person-dependency in leasing arises where processes remain implicit. In this article, we explain where the risks lie, and how you can systematically build substitutability.

What does person-dependency mean in leasing?

Person-dependent processes are workflows in which knowledge, decisions, and communication do not reside in the system, but with individuals. It is not about competence, but about the question of whether the process works without a specific person.

Four signs of person-dependency in the leasing process:

• Knowledge is not documented: Workflows, contacts, and decision paths exist only in someone's head.

• Decisions are not traceable: Why an applicant was selected cannot be gathered from the system.

• Communication takes place via personal channels: WhatsApp, direct calls, personal email, without system access for others.

• No onboarding without "asking the person": New employees cannot get started without consulting the knowledge holder.

Why does it fail in practice today?

Person-dependency does not happen intentionally. It is the result of processes that were never documented as a system.

60 to 70% of knowledge is undocumented

From experience, we know: 60 to 70% of process knowledge in property management does not reside in the system. It resides in the heads of individual employees. This is not a failure of individuals. It is a structural deficit.

Decisions are not traceable

Those who select an applicant often do so based on experience and gut feeling. If this person is absent, not only is the decision missing, but also the logic behind it.

Communication bypasses systems

Personal channels are faster than system routes. This is understandable, but it means that information stays with only one person. No colleague has access, and no system saves the context.

No onboarding without knowledge holders

New employees take weeks to become productive, not because the tasks are complex, but because the knowledge is not accessible.

How a lack of controllability plays a role here is explained in our article Why chaos occurs despite workflows.

What it costs: effects and ROI

Risks of high person-dependency

Absence risk: From the practical experience of typical property management companies, we know: One week of unplanned absence of a key person reduces team capacity by 20 to 40%, because processes stall and no one has an overview.

Turnover costs: Employee departures cause significant costs, through recruitment effort, onboarding time, and loss of knowledge. These costs are not systematically recorded in most management companies.

Onboarding time: In the experience of typical management companies, it takes 3 to 6 months to reach full productivity. During this time, the team works with reduced capacity.

Knowledge loss: With industry turnover estimated at 18 to 25% per year (industry estimate), a substantial part of implicit knowledge is lost every year, irretrievably, if it is not documented.

Efficiency gains with reduced person-dependency

Practical experience from typical property management companies:

• Complete substitutability achievable in under one day of training

• Onboarding time significantly reduced when process steps are documented

• Absences no longer cause escalations

• Team stability even during staff turnover

The complete framework is provided in our Guide to optimizing the leasing process.

Practical example

An employee is absent for two weeks. 30 ongoing cases are on her desk. No one knows the processing status, communication with applicants and owners stalls, and escalations pile up.

The problem was not the absence, but the fact that knowledge, statuses, and communication resided exclusively with one person.

After introducing systematic process documentation (status visibility in the system, documented substitution rules, structured handover protocols):

• Complete substitutability in under one day of training

• No process stalls anymore in case of absence

• Onboarding of new employees in days instead of weeks

• Owner communication runs independently of individuals

Document process steps and map them in the system

Make every step in the leasing process explicit. Document not only what is done, but also how decisions are made and what information is required.

• Document every process step with decision logic

• Transfer contacts and communication channels into the system

• Create checklists for recurring steps

Make statuses visible to everyone for every process

Ensure that everyone on the team can see where every process stands at any time. Statuses must live in the system, not in someone's head.

• Introduce status definitions for each process step

• Set up a central dashboard or overview

• Update statuses regularly (mandatory, not optional)

Define, practice, and test substitution rules

Define a substitute person for every process step. Test the substitution deliberately, not just in an emergency.

• Create a substitution matrix for each process step

• Actively test substitutions once a quarter

• Identify and close gaps

60 to 70% of process knowledge resides in the head, not in the system. Person-dependency is not a question of loyalty, but of system maturity.

Those who document today save weeks of onboarding tomorrow and prevent escalations. Substitutability is an operational prerequisite. A digitally documented workflow makes statuses visible to the entire team and is easier to hand over. What this looks like during a tenant turnover is shown by EverReal for property management.

How do you reduce person-dependency in property management?

Through three measures: document process steps and map them in the system, make statuses visible for every process, and define and regularly test substitution rules. The key is to make implicit knowledge explicit.

What does substitutability mean in the leasing process?

Substitutability means that every process step can be taken over by at least one other person, without processes stalling or knowledge being lost. This requires that knowledge resides in the system and statuses are visible.

How do you transfer implicit knowledge into the system?

Through structured documentation: record every process step with decision logic, required information, and communication channels. Create checklists for recurring steps. And define substitution rules that are regularly tested.