Leasing Funnel

Every stage is a count of distinct prospects with that dated event, so the funnel is monotone and every move-in in the window traces to a prospect and the lease it produced. 0 activity-register events in the window.

Why prospects did not rent

0 lost in the window

0 of 0 (0.0%) are unresponsive. 0 applications were denied.

Campaign lead volume

prospects per tracking number · top eight

Bars are prospects created in the window; the small figure is rentals from that campaign. Campaigns are tracking numbers (or a reply address) per source.

Lead sources

leads and rentals

Source	Leads	Rentals	Lead → lease

Leads by weekday

prospects created

Traffic skews Tuesday to Thursday and is near zero on Sundays, as the source reports show.

Lead quality

0 invalid leads · 0.0% of raw inbound

Dismissed leads by reason. Raw inbound = prospects created + invalid leads.

Agent workload

prospects assigned in the window · followups due to date

Agent	Prospects	Appointments	Shows	Rentals	Followups	Completed	Missed

System agents (Property Website, ILS, Not Assigned) hold leads nobody has picked up. Highlighted row is the agent carrying the most missed followups.

Conversion by unit type

leads to rentals

Unit type	Leads	Shows	Rentals	Lead → lease

Pipeline definitions

Guest cards are prospects by created date. Appointments, shows, applications and executions are distinct prospects with that dated event in the window. Approvals, lease executions and move-ins are prospect status: every approved applicant in this data has a signed lease, so executions equal approvals, and an approval can predate the window while its move-in falls inside it. Missed followups are due before the as-of date and not completed.

Conversion here is executions over guest cards in the same window, a reporting ratio, not a longitudinal lead-to-lease probability.

Prospect ledger

most recent 30

Prospect	Created	Source	Agent	Interest	Last event	Status	Lost reason

Definitions & report reconciliation

Unlike aggregate Yardi exports, every row here carries a prospect id, so the pipeline is a matched cohort: guest cards ≥ appointments ≥ shows ≥ applications ≥ approvals ≥ move-ins holds for every property, and the verify script asserts it. Rentals by Source, Property Performance and Team Performance by Agent are all views over the same prospect and event rows, so their counts agree.

Invalid leads are dismissed inbound contacts (duplicate, hang-up, vendor) and are not prospects. Campaign counts are prospects per tracking number; a prospect belongs to exactly one campaign.