Your weekly leasing funnel report shows rising leads and stable signed leases. Before changing advertising spend, check whether the renter who called, submitted a website inquiry, and returned through a listing site became several leads. A usable leasing conversion rate counts defined prospect journeys that reached an outcome within a declared observation window, divided by the eligible journeys that entered it.
A website inquiry, an EliseAI conversation, and a guest card in Yardi can describe the same rental search. Signed leases recorded this week can also belong to inquiries from an earlier week. Reconcile those identities and dates before reading a change in the ratio as a change in leasing performance.
Count a prospect journey before counting conversions
Choose the unit you want to measure. For property-level reporting, use one prospect or declared applicant household pursuing a rental at one property during a defined search episode. Give that journey an identifier and attach its inquiries, tours, applications, and lease evidence. Keep the household rule explicit so roommates applying together do not become several successful journeys for the same lease.
Preserve source prospect IDs and the links used to match records. A stable cross-system ID is stronger evidence than a matching name; an email address or phone number can help identify a candidate match, but shared contact details need review. Leave uncertain matches visible instead of forcing them together to make the totals agree.
Keep property identity separate from prospect identity. A renter can pursue neighboring communities during the same search, so each property can have a journey without the portfolio claiming several distinct renters. A transfer between communities needs a declared attribution rule if you report portfolio conversion. Renewals belong in a separate population because their entry event differs from a new inquiry.
Compare entrants with equal time to reach an outcome
An entry cohort groups journeys by when they first met your lead definition. Define that event, such as the first identifiable rental inquiry, and declare exclusions before calculating the result. Spam and test records can be excluded under recorded rules; a renter who lost interest remains an outcome in the population you were trying to convert.
Choose an observation window based on the rental-search cycle you need to evaluate, then apply the same elapsed time to comparable cohorts. A recent inquiry has had less time to sign than an older inquiry. Mark cohorts still inside their window as incomplete and show their current stage counts without presenting them as finished conversion results.
For each journey, the deadline is its entry timestamp plus the chosen observation window. Count only qualifying outcome events on or before that deadline, using one reporting timezone. Keep an as-of timestamp for the report (a late lease export may change the evidence available at that cutoff). Distinguish an event recorded late from an event that happened after the deadline.
Retain calendar-period activity alongside cohort conversion. Tours completed and leases signed this week help you plan staffing, but dividing this week's signatures by this week's new inquiries combines different populations. Show that activity in a separate view so it does not answer the cohort question by accident.
Define stage events and their denominators
Store dated events rather than relying on a current status field that overwrites the journey. A scheduled tour can become a no-show or a completed visit; an application can be started without being submitted. Use the following formulas as a cohort-based design, with distinct journey counts and the same entry deadline throughout.
| Measure | Formula | Event rule |
|---|---|---|
| Lead-to-tour | Cohort journeys with a completed tour ÷ eligible entry journeys × 100 | Count completed visits by the deadline, not bookings or repeated visits. |
| Tour-to-application | Toured cohort journeys with a later submitted application ÷ toured cohort journeys × 100 | Require the observed tour-to-submission sequence by the same deadline. |
| Application-to-signed-lease | Applicant cohort journeys with a later executed lease ÷ cohort journeys with a submitted application × 100 | Use the declared signature-completion event, not an approval or draft. |
| Lead-to-signed-lease | Cohort journeys with an executed lease ÷ eligible entry journeys × 100 | Include qualifying direct applicants; flag routes that bypass a tour. |
A journey counts once in each stage it reaches, even if the renter visits again or revises an application. Define how agent-led, self-guided, and virtual visits qualify as completed tours. Keep canceled bookings and no-shows as separate events so an apparent tour-conversion change can be checked against the activity that produced it.
Direct applications need their own route flag. If a renter applies without an observed tour, that journey can reach the lead-to-lease outcome but should not enter the tour-to-application numerator. Stage rates will not necessarily multiply to the total lead-to-lease rate when journeys bypass stages, and a missing tour event must remain distinguishable from a confirmed bypass.
Keep the signed event, cancellation event, and occupancy event separate. Gross signed conversion measures whether a lease reached execution. A net result can remove leases canceled by a stated as-of date, while a move-in result requires recorded occupancy; label each result so a signed lease for a future move-in does not become an occupied unit. Broader operating comparisons belong in Property management KPIs: a comparable portfolio scorecard.
Explain channel differences after fixing the journey
Choose the channel attribution rule before ranking sources. First known inquiry source measures where an identifiable journey entered; last recorded source describes a later touchpoint. Preserve the full touchpoint history even when your report assigns one credit, because overwriting the entry source when a renter returns can move a lease between channels without changing the journey.
Use an unknown-source bucket for missing attribution. If you assign one source per journey, source totals should reconcile to the eligible cohort total. Multi-touch reporting can give several channels credit, but its counts cannot be added as though they represent distinct renters. Document the credit rule alongside the result rather than using the same label for incompatible calculations.
Compare channels within matched property and entry-period groups before changing spend. Check unit availability, advertised rent, offered concessions, and desired move-in timing where those records exist. A channel sending renters for unavailable floor plans presents a different question from a channel whose completed tours do not lead to applications. Associations in those records do not establish that a concession caused a conversion change.
Inspect the journey evidence behind the stage with the change: booking and completion events for a tour gap, submission events for an application gap, or signature and cancellation events for a lease gap. Leave a reason unclassified when the source does not record it. A dashboard label should not turn an absent explanation into a judgment about the renter or leasing agent.
How Permute prepares leasing evidence for analysis
Permute is the context layer we sell between business data and the AI tools you use. We can work with supplied leasing exports alongside approved sources such as Excel and HubSpot, reconciling prospect and property records under declared matching rules. Keep the original source IDs and unresolved matches available so a combined journey can be inspected.
We encode agreed entry events, observation windows, and stage definitions as reusable reporting logic. Dashboards and scheduled data outputs can use the same rules, with source evidence and freshness retained. Your prospect records also need defined access; how the data is handled governs which users and agents can inspect the underlying detail.
A leasing operations lead can ask which completed cohorts lost conversion between tours and applications, then inspect the journeys and event evidence behind the answer. We supply that governed context underneath Claude, ChatGPT, and Copilot and to dashboards. Real estate reporting can then draw on the same property identities without changing the leasing denominator.
Build a journey view from your exports
Bring prospect and lease exports into a workspace, then inspect the source IDs and dates behind a combined leasing view.
Leasing execution and housing decisions stay in their workflows
We read the sources used for this analytical workflow; it does not send leasing outreach, schedule tours, or write changes to the property management system. Supplied Yardi or EliseAI exports do not imply native Permute integrations with those systems. Leasing communication and execution remain in the tools you use for those jobs.
We are not a forecasting engine, and a measured conversion rate does not predict a future lease outcome. Applicant screening, housing decisions, and interpretation of missing renter information remain outside this reporting workflow. Matching exceptions require review against available evidence, and a missing source event stays a gap until it can be resolved.
The weekly report needs an interpretable denominator
Leasing conversion measures how a defined group of prospect journeys reaches a declared outcome within its observation window. Reconcile repeat inquiries before deciding that rising lead volume means weaker performance. Separate stage activity, executed leases, cancellations, and occupancy so each result answers the question its label promises. Compare channels after the identities, populations, and elapsed time agree.
Review the definitions behind your leasing report
Bring your current funnel report and source exports. We will examine mismatched populations, missing events, and the evidence needed for a repeatable result.
Questions about measuring leasing conversion
How should I present conversion for a small property?
Show the eligible journey count and outcome count beside the percentage. A small population can change its rate when a single journey reaches the next stage, so avoid ranking properties on the percentage alone. Combine entry periods only under the same definitions and observation window.
When should a returning prospect start a new journey?
Declare a reopening rule before reporting, using the recorded end of the prior search and evidence of a new rental search. A new inquiry channel alone does not establish a new journey. Preserve the relationship to the earlier episode so a changed rule can be checked against the source history.
What if the lead definition changes during the year?
Keep the prior definition and mark when the revised rule takes effect. Recalculate historical cohorts only if the source evidence supports the new definition, and label that series as restated. Otherwise, show the break in comparability instead of connecting the results as one unchanged trend.