When a tenant calls to dispute a charge, the property manager who has to open three systems, scroll through email threads, and call the maintenance team for context before they can respond is not just slow. They are working from an incomplete picture, and the tenant knows it. The conversation that should take two minutes takes twenty, and it ends with either a concession that wasn't warranted or a frustrated tenant who was actually right.

This is the operational cost of fragmented tenant data. It is not a technology problem in the sense that the data doesn't exist. The payment history is in the accounting system. The maintenance requests are in the work order system. The notice history is in a shared inbox or a folder on someone's desktop. The lease documents are in a separate file. The communication log, to the extent one exists, is distributed across the email accounts of whoever has handled the tenancy over its lifetime. The data exists. It just doesn't exist in one place, in a form that can be retrieved and interpreted in the time it takes to keep a tenant on the phone.

The property management teams that handle tenant interactions most effectively are not those with the most experienced staff. They are the ones who have built a complete, structured tenant record that gives whoever is handling the interaction full context before they say a word. Payment history, arrears status, open maintenance requests, prior notices, lease terms, renewal status, and a log of every significant communication: all visible from a single view, in a format that tells a coherent story about the tenancy rather than a set of disconnected data points from separate systems.

That is what a Tenant 360 view is. Not a dashboard for its own sake, but a structured data architecture that connects every dimension of the tenant relationship into a single, queryable record. This guide covers what belongs in a Tenant 360 view, how to structure each data layer, how to maintain data quality across the full portfolio, and how to use the combined record to make better decisions on delinquency, renewals, and risk.

Why Fragmented Tenant Data Is an Operational and Financial Risk

Fragmented tenant data creates risk in three areas that property management teams often underestimate until the cost becomes visible.

Dispute Resolution Risk

A tenant who disputes a charge, a notice, or a maintenance outcome has usually been building their case for longer than the property manager realises. When the property manager cannot quickly produce a complete, accurate record of the tenancy, the dispute shifts in the tenant's favour not because the tenant is right but because the landlord cannot demonstrate they are right. An incomplete communication log, a maintenance history that doesn't show the response time or resolution, or a payment record that doesn't clearly identify how partial payments were allocated: any of these gaps creates ambiguity that a determined tenant will exploit.

The cost is not always a concession. Sometimes it is the time spent reconstructing the record from multiple systems before a response can even be prepared. At portfolio scale, across dozens or hundreds of active disputes at any given time, that reconstruction time is a material operational cost that a properly structured Tenant 360 view eliminates.

Delinquency Management Risk

Effective delinquency management depends on being able to see the full payment history quickly and accurately. A tenant who is three days late for the first time in two years of on-time payments is a different situation from a tenant who is three days late for the fourth time in six months. The appropriate response is different in each case. Without a complete payment history visible at a glance, the property manager applies a uniform response to both situations, either over-escalating a reliable tenant or under-escalating a pattern delinquent.

For how a complete tenant payment record connects to the delinquency escalation process and why the history behind the current balance determines which stage of escalation is appropriate, see how to build a rent delinquency workflow with automated escalation, notices, and arrears tracking.

Renewal and Retention Risk

Lease renewal decisions are typically made with incomplete information about the tenant's actual track record. The leasing team knows the current rent level and the lease expiry date. They may not have easy access to the full maintenance cost history for the unit (which affects the true net yield of that tenancy), the payment behaviour record (which affects the risk profile of renewing versus re-letting), or the communication history (which reveals whether the tenant relationship is strong or strained). Without that full picture, renewal decisions are made on gut feel and current occupancy pressure rather than on a complete analysis of the tenancy's value and risk.

IREM's research on tenant retention and portfolio performance consistently identifies complete tenant data as a foundational requirement for effective retention strategy, noting that property managers who can identify renewal risk early, based on payment patterns, maintenance frequency, and engagement signals, significantly outperform those who manage renewals reactively on expiry dates alone.

What a True Tenant 360 View Contains: The Four Data Layers

A Tenant 360 view is not a single record. It is an architecture of four connected data layers, each of which tells a different part of the tenancy story. The layers must be complete independently and connected to each other to produce the full picture.

• Layer 1: The Financial Record captures every charge, every payment, every adjustment, and every outstanding balance associated with the tenancy. It is the economic history of the relationship.

• Layer 2: The Communication Record captures every notice, every message, every call log, and every formal correspondence associated with the tenancy. It is the documented history of every significant interaction.

• Layer 3: The Operational Record captures every maintenance request, every inspection, every service event, and every asset-related interaction associated with the unit and tenancy. It is the physical history of the tenancy's impact on the property.

• Layer 4: Relationship Intelligence is the analytical layer that sits above the other three, drawing signals from the financial, communication, and operational records to produce a risk profile and a retention indicator for the tenancy. It is the interpretation layer that turns data into decisions.

Layer 1: Building the Financial Record: Payments, Charges, and Arrears History

The financial record is the most operationally critical layer of the Tenant 360 view. It must contain not just the current balance but the complete chronological history of every financial event in the tenancy.

What the Financial Record Must Contain

The financial record for each tenant must include the following fields, structured as a chronological ledger rather than a static balance:

• Charge history: Every charge posted to the tenant's account, including: base rent charges (monthly, with the charge date and the period it covers), late fees (with the date applied, the calculation basis, and the overdue balance the fee was applied to), service charges (utilities, parking, storage, and any other recurring charges specified in the lease), one-time charges (move-in fees, administrative fees, damage charges), CAM reconciliation adjustments (for commercial tenancies), and rent escalation adjustments (date effective, old rent, new rent, escalation basis).

• Payment history: Every payment received, including: the payment date, the payment amount, the payment method, the allocation of the payment across outstanding charge types (base rent first, then fees, or in accordance with the allocation policy), and the resulting balance after allocation. Partial payments must be recorded with the allocation detail, not as a single transaction against a balance.

• Adjustment history: Every credit, waiver, or adjustment applied to the account, including: the date, the amount, the reason, and the approver. Adjustments without this detail cannot be audited and create unexplained variances in the AR reconciliation.

• Arrears aging: The current outstanding balance broken down by aging bucket (0 to 7 days, 8 to 14 days, 15 to 30 days, 31 to 60 days, 60 days plus), by charge type (rent versus fees), and by the current escalation stage in the delinquency workflow. This is not a separate report: it is a live view within the financial record that updates as payments are received and days accumulate.

• Security deposit record: The security deposit amount held, the date collected, the account it is held in, any deductions applied during the tenancy with supporting documentation, and the return status at move-out.

The Payment Allocation Order

One of the most common sources of financial record ambiguity in property management is unclear payment allocation. When a tenant pays $1,800 against a balance of $2,100 (comprising $2,000 rent and $100 late fee), how is the $1,800 allocated? If it is applied to rent first, the tenant has $200 of rent outstanding plus the full $100 fee. If it is applied to fees first, the tenant has $300 of rent outstanding and the fee is cleared. The allocation order affects the aging bucket, the escalation stage, and the balance reported to the tenant.

The allocation order must be defined in the lease, configured in the system, and visible in the financial record. Every payment entry must show not just the amount received but the line-by-line allocation across the outstanding charges it was applied to.

For how payment allocation connects to the rent collection automation process and how automated systems handle partial payment allocation without manual intervention, see how to automate rent collection: from invoice generation to payment reconciliation.

Layer 2: Building the Communication Record: Notices, Responses, and Interaction Logs

The communication record is the layer that most property management operations handle worst. Payment data lives in the accounting system. Maintenance data lives in the work order system. But communication data is scattered across email inboxes, phone call notes, front-desk logs, and whatever documentation the previous property manager chose to keep before they left.

What the Communication Record Must Contain

The communication record must capture every significant interaction between the property management team and the tenant, structured by type and date:

• Automated system communications: Every notice, reminder, and alert generated by the property management system, including: pre-due rent reminders, late fee application notices, formal demand notices, lease renewal alerts, maintenance update notifications, and any other automated outbound communication. Each entry must include the date and time sent, the delivery channel, the delivery status (delivered, opened, bounced), and the full text of the communication as delivered.

• Inbound tenant communications: Every message, request, or complaint received from the tenant, including: the date and channel of receipt, a summary of the content, the name of the team member who received it, and the response or action taken with a date. Inbound communications that are not logged create gaps in the timeline that become critical if the tenancy later produces a dispute.

• Outbound property manager communications: Every call, email, or written communication initiated by the property management team outside of automated system workflows, including: the date, the channel, the team member who initiated it, the purpose, a summary of the outcome, and any follow-up action committed to.

• Formal legal notices: Every notice with legal standing, including: the notice type, the date issued, the delivery method, proof of delivery, and the response or outcome. Formal notices must be stored in their original form, not as template references, because the legally relevant document is what the tenant actually received.

• Meeting and visit records: Any in-person interaction, property inspection where the tenant was present, or formal meeting, including: the date, the participants, the topics discussed, any commitments made by either party, and any documents exchanged.

The Communication Timeline View

The most useful format for the communication record within the Tenant 360 view is a chronological timeline that interleaves all communication types in date order. A property manager reviewing the tenant record should be able to read the timeline from top to bottom and understand the complete narrative of the tenancy relationship without switching between views. A payment dispute in October makes more sense when the timeline shows a maintenance complaint in August, a formal response in September, and a rent reduction request in October that was declined: the financial dispute is in context, and the property manager can respond appropriately.

For how RIOO's tenant portal supports both sides of the communication record, giving tenants a documented channel for all interactions while simultaneously building the property manager's communication log with every message, notice, and alert automatically recorded against the tenant's profile, see the product page for the full capability detail on centralised tenant communication and interaction history.

Layer 3: Building the Operational Record: Maintenance History, Inspections, and Service Requests

The operational record is the layer that connects the tenant's experience of the property to the property's physical condition and cost profile. It is essential for renewal decisions, deposit deduction documentation, and vendor management, and it is the layer most frequently missing from tenant records built around financial and leasing data.

What the Operational Record Must Contain

• Maintenance request history: Every service request raised by the tenant, including: the date raised, the category (plumbing, electrical, HVAC, structural, cosmetic, other), the priority classification, the date assigned, the vendor or maintenance team member assigned, the date completed, the resolution description, the cost incurred, and the tenant satisfaction status. Maintenance requests that are closed without a resolution description or cost record are operationally useless for any downstream purpose.

• Inspection records: Every formal inspection of the unit, including: the inspection type (move-in, periodic, move-out), the date, the inspector, the condition assessment for each inspected element, photographic documentation, any deficiencies noted with their classification (tenant-caused, normal wear and tear, pre-existing), and the follow-up action required.

• Recurring maintenance and planned works: Any planned maintenance that affected the unit during the tenancy, including: the work type, the date completed, the cost, and whether it required tenant access or vacancy. This data is essential for distinguishing between tenant-caused deterioration and management-driven works when assessing deposit deductions at move-out.

• Utility and asset records: Any utility readings, asset registrations, or infrastructure events associated with the unit during the tenancy period.

The Maintenance History Classification Table

Every maintenance request in the tenant record must carry its category and priority classification from the moment it is raised. A request log that shows dates and statuses but not categories cannot support cost analysis, vendor performance review, or deposit deduction documentation.

Layer 4: Relationship Intelligence: Using Tenant Data to Predict Risk and Drive Retention

The first three layers of the Tenant 360 view are records: structured, historical, factual. Layer 4 is the analytical layer that reads those records and produces signals about where the tenancy is heading. It is the layer that converts a data archive into a decision-support tool.

The Tenant Risk Score

A tenant risk score is a composite indicator built from signals across the financial, communication, and operational records. It is not a credit score and it is not a replacement for human judgment: it is a structured way of surfacing patterns in the data that a property manager reviewing a single account might miss when managing a large portfolio.

The core signals for a tenant risk score fall into three categories:

• Payment behaviour signals: Number of late payments in the last 12 months, average days late when payment is late, trend in payment timing (improving, stable, deteriorating), any periods of partial payment, current arrears status, and number of late fee waivers requested.

• Maintenance signals: Total maintenance requests in the last 12 months compared to portfolio average for the unit type, proportion of requests classified as tenant-caused versus normal wear, open requests that have been unresolved for longer than the target resolution time, and any requests that escalated to formal dispute.

• Communication signals: Average response time to property manager outreach, number of formal complaints raised, tone trend in written communications (neutral, positive, escalating), and response rate to automated communications (payment reminders opened versus ignored).

The Tenant Risk Scoring Framework

A tenant with low-risk indicators across all four categories is a strong renewal candidate. A tenant with high-risk indicators in payment behaviour and communication responsiveness is a renewal decision that requires financial analysis of the cost of re-letting versus the risk of renewing.

The Retention Trigger Reference

Retention triggers are data signals in the Tenant 360 view that indicate a tenant may not renew, giving the property management team a window to intervene before the decision is made.

• Financial retention triggers: A tenant who has never been late in the first year of tenancy but has been late twice in the last three months may be experiencing financial stress. The appropriate response is proactive contact to understand the situation, not escalation. A tenant who requests a payment plan for the first time after a strong payment history is signalling a temporary problem, not a pattern default.

• Operational retention triggers: A tenant who raises three maintenance requests in a single month after an 18-month period with minimal requests is signalling dissatisfaction with the property condition. If the requests are not resolved quickly, the probability of non-renewal increases significantly. A tenant who submits a formal complaint about maintenance response time is signalling that the operational relationship is under strain.

• Communication retention triggers: A tenant who stops responding to routine communications, or whose communication tone shifts from neutral to negative across multiple interactions, is disengaging from the landlord relationship. Disengaged tenants do not renew. Proactive contact at the first sign of disengagement, before the formal renewal period, recovers a significant proportion of at-risk renewals.

For how the data signals in the Tenant 360 view should inform the lease renewal outreach timeline and the terms offered to different risk and retention profiles, see how to automate lease renewals: alerts, workflows, and escalation.

How to Structure the Tenant 360 View for Multi-Tenancy and Multi-Property Portfolios

The Single Profile Across Multiple Units

A tenant who holds leases on two units in the same portfolio, or who has a current tenancy and a prior tenancy in the portfolio, should have a single tenant profile that aggregates all records across all leases. Creating separate profiles per lease loses the relationship history: the payment behaviour from a prior tenancy is relevant context for a current renewal decision. The communication history from one property may be relevant to a dispute at another.

The single profile architecture requires a tenant identifier that is independent of the lease or unit. Every lease, every charge, every payment, every maintenance request, and every communication is associated with both the tenant identifier and the property or unit identifier, so the record can be filtered by tenancy (to see all records for a specific lease) or by tenant (to see all records across all associations).

Commercial Tenants in a Mixed Portfolio

Commercial tenants typically have more complex financial records than residential tenants: rent escalation clauses, CAM charges, percentage rent calculations, and multi-party structures where the lease counterparty is a corporate entity rather than an individual. The Tenant 360 view for commercial tenants must extend the financial record layer to include: the full charge schedule under the lease (not just base rent), the CAM reconciliation history, any percentage rent calculations and the underlying sales data, and the contact hierarchy within the tenant organisation (accounts payable contact, facilities contact, lease decision-maker).

NAA's guidance on tenant data management best practices for residential portfolios identifies the single-profile, multi-tenancy architecture as the gold standard for tenant record management, noting that portfolios that maintain separate records per lease consistently underperform on retention metrics because they lose the longitudinal view of the tenant relationship that drives effective renewal and risk management.

For how RIOO's unified customer view consolidates leasing history, payment records, maintenance requests, and communication logs into a single centralised tenant profile across all units and properties, giving property managers complete context for every interaction without switching between systems, see the product page for the full capability detail on comprehensive tenant profiles and multi-property data consolidation.

Data Quality: The Records That Break the 360 View When They Are Missing or Wrong

A Tenant 360 view is only as useful as the data it contains. The most common data quality failures in property management tenant records fall into five categories.

1. Maintenance requests closed without resolution detail. A maintenance log that shows requests opened and closed but no description of what was done, what it cost, or whether the tenant confirmed the resolution is operationally useless for deposit deduction documentation, vendor performance review, or renewal cost analysis. Every closure must include a resolution description, an actual cost, and a confirmation of whether the issue was tenant-caused.

2. Payments recorded as lump sums without allocation detail. A payment entry that shows "$1,800 received on [date]" without showing how it was allocated across outstanding charges tells the property manager what was received but not what remains outstanding or how the balance was affected. Every payment must be recorded with line-by-line allocation.

3. Communications logged by some team members but not others. A communication log that reflects the working habits of individual team members rather than a mandatory recording requirement will always have gaps. The gap is typically in informal communications: a phone call where the tenant mentioned a maintenance issue, an email response that committed to a repair timeline, a conversation at the front desk about a payment plan. These informal communications are often the ones that matter most in a dispute. Logging must be mandatory, not discretionary.

4. Inspection records without photographic documentation. A written inspection report that notes "minor cosmetic wear to bedroom wall" is ambiguous without a photograph. At move-out, if the tenant disputes a deposit deduction for wall damage, the written record from a prior inspection supports neither the tenant nor the landlord definitively. Photographic documentation with date stamps is the only inspection record that resolves deposit disputes clearly.

5. Lease data not updated when terms change. Mid-tenancy changes to lease terms, rent levels, or permitted uses that are agreed and documented but not updated in the tenant profile create a mismatch between the legal agreement and the system record. Charges calculated from an out-of-date rent figure, or renewal options assessed against superseded lease terms, produce errors that take significant time to unwind.

For how the accuracy of the tenant financial record connects to the rent roll reconciliation process and why a Tenant 360 view that contains inaccurate financial data undermines the reconciliation at month-end, see how to conduct a month-end rent roll reconciliation.

How the Tenant 360 View Connects to Delinquency Management and Lease Decisions

Delinquency Decisions

The Tenant 360 view transforms delinquency management from a case-by-case response to a context-informed process. When a tenant is late, the property manager with a complete Tenant 360 view can immediately see: how many times this tenant has been late in the last 12 months, what the pattern of lateness looks like (first of the month versus end of grace period, partial payments versus no payment), whether there is an open maintenance dispute that the tenant may be using as informal leverage, and what the communication history shows about how prior lateness was resolved.

That context determines the response. A first-time late payment from a tenant with a two-year on-time history and an open maintenance complaint warrants a personal call before a formal notice. A fourth late payment in six months from a tenant with no maintenance complaints and a history of ignoring courtesy notices warrants immediate formal escalation. The Tenant 360 view makes both situations visible in the time it takes to open the record.

Lease Renewal Decisions

Lease renewal decisions in most property management operations are driven by one variable: whether the unit will be vacant and how quickly it can be re-let. The Tenant 360 view adds the variables that determine whether the renewal is actually desirable: the total maintenance cost incurred during the tenancy (net of normal wear), the payment reliability record, the communication quality, and the tenant's expressed intentions based on the communication record.

A tenant who has paid reliably, raised minimal maintenance issues, and engaged positively in communications represents a lower-cost occupancy than a new tenant at the same rent level. Re-letting costs (vacancy period, marketing, screening, move-in administration, and initial maintenance) typically represent one to two months of rent equivalent. A well-structured renewal offer made to a high-value tenant three months before expiry, informed by the full Tenant 360 record, recovers that equivalent value in the tenancies that are worth keeping.

Deloitte Insights' research on customer data strategy in asset-intensive industries identifies the ability to act on longitudinal customer data at the point of a renewal or retention decision as one of the most significant operational differentiators between high-performing and average-performing portfolios, noting that the gap is not in data availability but in whether the data is structured and accessible at the moment the decision needs to be made.

Frequently Asked Questions 

Q1. What is a Tenant 360 view in property management and why does it matter?
A Tenant 360 view is a single, consolidated record of every dimension of a tenant's relationship with the property management organisation: the complete financial history (every charge, every payment, every adjustment, every outstanding balance), the full communication log (every notice, every call, every message, every formal correspondence), and the complete operational record (every maintenance request, every inspection, every service event). It matters because property management decisions about delinquency, renewal, and dispute resolution are only as good as the information they are made on. A property manager with incomplete tenant data makes slower decisions, makes more concessions they didn't need to make, and misses retention opportunities that a complete picture would have surfaced. At portfolio scale, those costs compound across every tenant interaction every month.

Q2. What data belongs in the financial layer of a Tenant 360 view?
The financial layer must contain the complete charge history (base rent, late fees, service charges, one-time charges, and adjustments, each with the date, amount, basis, and approver where applicable), the complete payment history (every payment with the date, amount, method, and line-by-line allocation across outstanding charges), the arrears aging view (current balance broken down by aging bucket and charge type), the security deposit record, and the current escalation stage for any delinquent balance. It must be structured as a chronological ledger rather than a static balance, so that anyone reviewing the record can trace every financial event in sequence and understand exactly how the current balance was reached.

Q3. How should communication records be structured within the Tenant 360 view?
Communication records should be structured as a chronological timeline that interleaves all communication types in date order: automated system notices, inbound tenant messages, outbound property manager communications, formal legal notices, and in-person interaction summaries. Every entry must include the date, the channel, the direction (inbound or outbound), the team member involved, a summary of the content, and the outcome or follow-up action. Formal notices must be stored in their original delivered form, not as template references. The timeline format is the most operationally useful because it shows the narrative of the relationship rather than isolated data points, making it possible to understand context immediately when handling a dispute or a renewal conversation.

Q4. How do you handle a tenant who has multiple leases across different properties in the same portfolio?
A tenant with multiple leases or a history of prior tenancies in the portfolio should have a single unified profile with a tenant identifier that is independent of any specific lease or unit. Each lease, charge, payment, maintenance request, and communication is associated with both the tenant identifier and the specific property or unit, so the record can be filtered by tenancy (to review the history of a specific lease) or by tenant (to review the full relationship history across all associations). Separate profiles per lease lose the longitudinal relationship context that is most valuable for renewal decisions and risk assessment.

Q5. What are the most important data quality standards for a Tenant 360 view?
The five non-negotiable data quality standards are: every maintenance request closed with a resolution description, actual cost, and tenant confirmation; every payment recorded with line-by-line allocation across outstanding charges rather than as a lump sum; all communications logged as mandatory practice rather than at individual discretion; all inspections documented with date-stamped photographic evidence alongside written condition assessments; and lease data updated in the system within 48 hours of any agreed mid-tenancy change. Any of these standards consistently not met creates gaps in the Tenant 360 view that will surface at the worst possible moment, typically during a dispute, a deposit deduction challenge, or an audit.

Q6. How should maintenance history be used in a lease renewal decision?
The maintenance history layer of the Tenant 360 view reveals three things relevant to a renewal decision. First, the total maintenance cost incurred during the tenancy, broken down by tenant-caused and management-responsible categories, which reveals the true net yield of the tenancy after the cost of occupancy. Second, the maintenance frequency trend: a tenant whose request volume has increased significantly in the last six months of a tenancy is either experiencing dissatisfaction with the property condition or developing higher maintenance usage habits, both of which are relevant to a renewal offer. Third, the presence of any unresolved maintenance issues at the time the renewal decision is being made: a tenant who is being asked to renew while an outstanding maintenance issue remains open is a retention risk, and the renewal conversation must address the operational issue before the financial terms.

Q7. What is a tenant risk score and how should it be used?
A tenant risk score is a composite indicator that aggregates signals from the financial, communication, and operational layers of the Tenant 360 view to produce a structured assessment of the tenancy's current risk profile. It draws on payment behaviour (frequency and severity of late payments, current arrears status), maintenance signals (request frequency, proportion of tenant-caused requests, open unresolved requests), and communication signals (responsiveness, complaint frequency, tone trend). It is used to prioritise portfolio-level attention: a large portfolio cannot give equal attention to every tenant every month, and a risk score that flags the tenancies most likely to produce a delinquency event, a dispute, or a non-renewal in the next 60 to 90 days allows the property management team to direct proactive effort where it is most needed. It is a triage tool, not a replacement for the human judgment that a complete Tenant 360 view supports.

Q8. How does the Tenant 360 view reduce the time spent on dispute resolution?
Dispute resolution in property management is slow because the property manager typically has to reconstruct the relevant record from multiple systems before they can respond. The charge history is in the accounting system. The notice history is in the email archive. The maintenance outcome the tenant is referencing is in the work order system. Each reconstruction step takes time, introduces the possibility of missing something, and gives a determined tenant the advantage of having prepared their case before the call. A Tenant 360 view that contains all of this information in a single chronological record eliminates the reconstruction step entirely. The property manager who opens a tenant record and can immediately see the complete financial, communication, and operational history is responding from full context, not from a partially assembled picture. Disputes that would have taken multiple conversations and internal investigations are resolved in the first call, and the resolution is based on the actual record rather than on whoever can remember the most.

The Tenant 360 view is not a feature request. It is an operational standard that reflects the complexity of the landlord-tenant relationship. Every tenancy generates data across financial, communication, and operational dimensions simultaneously. The organisations that consolidate that data into a single, structured, accessible record make better decisions, faster, across every interaction. The organisations that leave the data fragmented across systems pay the cost in dispute resolution time, delinquency management inefficiency, and renewal decisions made without the information that would have changed the outcome. Building the Tenant 360 view is a one-time structural investment that produces a compounding operational return across every tenancy in the portfolio, for every month those tenancies run.