Digitalization & Systems
Media Discontinuities in Leasing: How to Identify Isolated Solutions

Problem: The same tenant is created in the property management system, in the applicant spreadsheet, and in the email client, and the next time there is a handover, no one knows which status is current. Cause: At the handoffs between applications, nothing connects the data—only a person transferring it manually. Thesis: It is not the number of systems that is the problem, but the number of handoffs carried out manually. The property management system remains; the process connects.
What are media discontinuities in leasing, and what are not?
In many property management operations, several applications are used for leasing: the property management system with master data, an inbox for correspondence, a spreadsheet for applicants, a calendar for viewings. This in itself is not a problem. Each of these applications serves its purpose, and an operation using multiple systems is not inherently worse organized than one with a single system.
The landscape becomes problematic elsewhere: individual applications turn into isolated solutions when nothing connects them. This happens when switching from one application to the next. A handoff is the moment when a process moves from one system to another. The self-disclosure arrives by email and is typed into the spreadsheet. The tenant already exists in the property management system and is created again for leasing. The viewing appointment is in the calendar, its outcome in a note. Each of these handoffs is small. Together, they are the reason why a process depends on individuals: only those who keep it in their heads know what the current status is.
Therefore, this article does not ask how many applications you have. It asks how many handoffs between them are performed manually.
A clarification beforehand: the property management system should not be replaced. It remains the foundation for master data, contracts, and accounting. EverReal is not an ERP and does not replace one; it complements it. Why an ERP reaches its limits during operational leasing steps and what a complementary setup looks like is discussed in the article ERP-System ergänzen. Here, the focus is on the preceding step: identifying where the handoffs lie. An overview of system types and their interaction is provided in the article Systemarten im Überblick; this article is about the transitions, not the selection.
How do you recognize media discontinuities? Five signs
The following signs concern the process, not the people in it. Recognizing them in your own organization does not mean you have a discipline problem, but rather a disconnected handoff.
1. Something is created twice. Properties, units, and tenants already exist in the property management system and are manually entered again for leasing. Creating something twice takes twice the time. And it can result in differing information in two places.
2. Two applications show two different statuses. The applicant is marked as "approved" in the spreadsheet and still "open" in the inbox. Which status applies depends on who checked last.
3. The status is retrieved by asking around. Anyone wanting to know if a lease agreement has already been drafted for an apartment does not open the process, but sends an email or asks a colleague. A process whose status can only be retrieved via individuals has no fixed place.
4. Workarounds live in the team's memory. "The yellow column means they made the shortlist." "If the folder is empty, the disclosure is still missing." Such rules work as long as the people involved know them. They are rarely written down anywhere.
5. Onboarding takes a long time because workflows are explained individually. New colleagues must learn which application is used for what, where specific information resides, and which handoff is handled manually at what point. The knowledge resides inside the heads of established staff.
A single sign is normal. If three or more occur in a process, it is worth examining the handoffs.
Where do handoffs occur in the leasing process?
A leasing process runs from inquiry to the handover of the apartment. Several stages lie in between. At each stage, a switch in application may occur. The table shows typical handoffs and the question that arises in each case. It is a working tool for your own review, not a description of your specific setup.
Handoff | Typical manual work | Assessment question |
|---|---|---|
Inquiry to applicant | Transfer sender, apartment, and preferred date from the email into the applicant spreadsheet | Where is it noted which apartment the inquiry applies to? |
Applicant to viewing | Enter appointment in calendar, update status manually in the spreadsheet | Can everyone see whether the viewing took place? |
Viewing to selection | Pass on impressions from the viewing verbally or in a note | Where is the rationale for the selection documented? |
Selection to screenings | Forward documents by email, store results in the inbox | Where is the screening result stored, and who approved it? |
Screenings to lease agreement | Type data from spreadsheet and property management system into the contract template | Is something being created for a second time here? |
Lease agreement to signature | Send draft by email, match returned documents manually | Which version is the valid one? |
Signature to property management system | Transfer tenant and contract data into the property management system | Who creates the tenant record, and when? |
Contract to apartment handover | Coordinate handover protocol appointment separately, file the report | Is the process completed, and where is that visible? |
Count the answers "I don't know" and "let's ask my colleague" in the last column. Each of them marks a handoff that exists only in someone's head.
What are the costs when something is created twice?
There is no single figure for this, and it would not accurately reflect your organization anyway. However, the costs can be clearly identified, and they arise at the handoffs.
Time. Every manual transfer is working time that does not contribute to any actual leasing step. It does not occur just once, but with every process, at every handoff shown in the table above. Anyone wanting to know whether a specific prospective tenant still needs a response must open several applications and compare their statuses.
Errors. What is typed manually can be mistyped: a phone number with transposed digits, a status change entered in one application but not in the other. Such discrepancies are rarely noticed immediately. They become apparent later, when someone expects a confirmation that does not exist anywhere.
Onboarding and absences. Where the current status can only be found through experience, any absence becomes a risk. The article Personenunabhängigkeit in der Immobilienverwaltung describes why this has nothing to do with reliability. The people who bridge the gaps between applications work reliably. The expensive part is that everything depends on them.
Especially with lean staffing, manual work at transitions is harder to absorb: every transition that someone has to track manually ties up time that is missing elsewhere.
Does the property management system remain, and what changes about the process?
The answer to media discontinuities is rarely another application and never abandoning the property management system. It consists of two things.
The property management system remains. It maintains master data, existing contracts, and accounting. That is its purpose, and it remains untouched.
The leasing process is kept largely in one place. Where an integration to the property management system exists, duplicate entries are eliminated. In EverReal, the process from inquiry to handover is kept largely in one place: inquiry, application, screenings, contract, and handover are not separate silos, but stages of the same process. Tasks can be assigned to a property, a listing, or an applicant, optionally with a due date and priority. Reassigning a task is done manually; the newly assigned person is notified. Every user can see all company tasks by clearing the filter for the assigned person. The assignee and due date of a task are thus visible to everyone in the company.
Integrations ensure that data already available somewhere does not need to be created a second time. EverReal connects to several property management systems: systems connected via Aareon Connect, Aareon PowerHaus (via CSV import), iX-Haus, Wowiport, and casavi; the integration with DOMUS is currently being piloted with initial customers. Portals are connected via OpenImmo, ImmoScout24 via API. In addition, Getmomo handles rental deposit accounts. A notice of termination received in the property management system is displayed in EverReal and initiates the leasing process.
Which data flows in which direction varies by system; a sync back after contract signing does not exist for every integration. Two examples of this difference: in Wowiport, tenant and contract data flow back after finalization; in iX-Haus, only applicant data flows back, and that return flow is triggered manually.
Getmomo as an example of a partner. For rental deposits, there is an integration with Getmomo. Those who create their lease agreements in EverReal and have their own contract with Getmomo request the deposit account directly within the lease agreement. A dialog box shows beforehand which data will be sent to Getmomo. Getmomo creates the account, and the IBAN is pulled directly from Getmomo into the lease agreement instead of being typed manually. The integration applies to lease agreements with up to two private tenants and for properties in Germany, and it is activated upon request; pricing and terms are shared during the consultation. You can view payment receipts in Getmomo, not in EverReal. The details can be found on the Getmomo integration page.
DOMUS as an example of a property management system. The integration with DOMUS is currently being piloted with initial customers. Learn more on the DOMUS integration page.
These examples demonstrate the same principle: data that already exists somewhere should not have to be created manually again. Whether an integration exists for your property management system and how comprehensive it is, is a question you should ask every vendor. An answer without boundaries—meaning without specifying what is not transferred—is not a complete answer.
How do you proceed? A handoff inventory in five steps
Before deciding on applications, it is worth taking stock of your handoffs.
Choose a real process. Pick a leasing case that was completed recently, ideally an ordinary one. An everyday example reveals more than an idealized workflow.
Trace the path. Go through the workflow stage by stage with the person who handled the process: Where did the inquiry arrive? Where was the applicant recorded? Where were the documents stored? Where was the contract created? Note down every application and every transition.
Highlight every handoff that was handled manually. Typing data, forwarding, updating records, following up: these are the key spots. Note whether data was created a second time in the process.
Identify the point with the most follow-up questions. This is usually where you find the handoff where the current status cannot be read clearly. Ask who could step in if someone were absent, and whether that person could find the answer without asking around.
Select three handoffs. Do not take on more than that. Decide for each handoff: Can it be replaced by an integration, by a dedicated place for the status, or by a written rule? A fillable framework for the workflow from inquiry to handover is provided in the workbook The Stand-in Test: Process Map for Your Leasing Operations.
Which questions help with assessment?
The following questions are meant without judgment. They serve to describe the current state of your process before you change it. Answer them for a concrete case.
How often are the same tenant or the same apartment created in different applications?
Is there a single place where the current status of a process can be seen from inquiry to handover?
Can you state for each stage who is responsible and by when it should be completed?
Where is the result of each pre-lease verification stored, and who approved it?
How many handoffs rely on manual typing, forwarding, or record updates?
Which team rules are not written down anywhere?
How long does it take until a new colleague can continue an ongoing process without having to ask questions?
Which data exists in the property management system and is recorded a second time for leasing?
Regarding questions 2 through 4, here is how EverReal addresses them: The process from inquiry to signed contract—and upon request, through to handover—is managed largely in one place. Tasks can optionally include assignees, due dates, and priorities. Starting with the Pro edition, the company defines which of up to four verifications must be completed, and the contract can only be drafted or sent once the specified verifications are finished. All of these settings are disabled by default; the company decides which ones to enable. A task is reassigned manually; the newly assigned person is notified.
Evaluate every provider against these same questions. A solution that clearly states its limits is more reliable than one that glosses over them.
Conclusion
Media discontinuities are not a sign of backwardness, nor are they a question of how many applications you use. They are the expected result of many reasonable individual decisions between which nobody planned the handoffs. They become visible through what is created twice, where two differing statuses coexist, and who needs to be consulted to find out the current status.
The answer is not a system replacement. The property management system remains, and the leasing process is managed largely in one place and connected to it wherever an integration exists. How such a process is structured is described in the cornerstone article on geführten Workflows in der Immobilienverwaltung. The broader context is outlined in the article Ganzheitliches Immobilienmanagement.
Anyone wishing to map their own handoffs next will find a framework for this in the workbook: The Stand-in Test: Process Map for Your Leasing Operations
If you would like to review your handoffs together with us: book a consultation.
We do not provide legal advice. Specific legal questions are best resolved by property managers in consultation with a specialized attorney or their industry association (VDIV, IVD).
Sources
EverReal product documentation on process, tasks, and verifications, as of October 2026.
EverReal product documentation on systems and integrations, as of October 16, 2026.
EverReal product status on the Getmomo integration, as of October 2026.
FAQ
What are media discontinuities in leasing?
Media discontinuities in leasing occur when multiple applications are used for a leasing process and data is manually re-entered or reconciled at the transitions between them. The problem is not the number of applications, but the missing connection at the transitions. This leads to isolated solutions: the same tenant exists in two places, and nobody knows which status is current.
How do I know that my software landscape is becoming a problem?
Typical signs include data being entered manually a second time, inconsistent statuses between spreadsheets and the property management system, emails sent merely to determine the current status, unwritten team shortcuts, and lengthy onboarding periods for new colleagues. The critical factor is how often information must be re-entered when switching between applications.
Do I have to replace my ERP if I want to improve handoffs?
No. The property management system remains the foundation for master data, contracts, and accounting. The key is ensuring that the leasing process is connected to the property management system and that data does not have to be created manually a second time. EverReal is not an ERP and does not replace one; it complements it.
Which integrations are available today?
EverReal connects to several property management systems: systems connected via Aareon Connect, Aareon PowerHaus (via CSV import), iX-Haus, Wowiport, and casavi. The integration with DOMUS is currently being piloted with initial customers. Portals are connected via OpenImmo, ImmoScout24 via API, and Getmomo is available for rental deposit accounts. Which data flows in which direction varies by system; a sync back after contract signing does not exist for every integration. We will clarify what applies to your property management system during a consultation.
Is a leasing solution enough to eliminate media discontinuities?
That depends on where the status of a process resides. A solution eliminates media discontinuities only where inquiry, application, contract, and handover are managed largely in one place and an integration is present. Test during a demo using a real process to identify where data would still need to be transferred manually.
More articles

Legal & Compliance
Energy performance certificate during viewings: when landlords must present it and how the process ensures compliance
The landlord must present the energy performance certificate at the viewing at the latest (Section 80 GModG, formerly GEG). Here are five occasions when it must be available.

Rental Process
Guided workflows in property management: what a guided process achieves
Guided workflows in property management: what they achieve, how to recognize them, and how to get started with a process. Includes self-assessment.

Processes & Organization
Scaling the Leasing Process: Where It Breaks Down After 200 Units
Between 200 and 2,000 units, the leasing process breaks at the transitions between steps, not at the tasks themselves. Identify four failure points, run a stress test.

Rental Process
Approval process in leasing: Setting up approvals before the lease agreement
Leasing Approval Process: Typical checks before signing a lease, who approves what, and how to track approvals directly within the file rather than your inbox.
Renting and selling. Reimagined.
Get started