The Leasing Calendar — showings you can actually verify
Every showing your team books, who is doing it, and how it really went — with a server-side clock, a mandatory recap and the viewer's own feedback.
The problem it solves
Owners ask how many times their unit has been shown, and the honest answer used to be “whatever the agent wrote down”. The Leasing Calendar sits beside the Master Calendar and records every showing — but the parts that could be faked are the parts the system owns, not the agent.
The clock is not the agent's to set
Check-in and completion times are stamped server-side when the button is tapped. They cannot be typed in or backdated. That gives you punctuality (booked vs arrived) and time on site (arrived vs left) for free, and neither figure can be edited afterwards.
The viewer is real before the showing, not after
The viewer's contact details are required before the showing and freeze at check-in — a contact added afterwards proves nothing. Later edits are allowed, but they are appended to a change log shown on the record.
The recap gate
A showing only reaches completed through a structured recap. An agent sitting on a recap more than 12 hours old cannot book new work until it is filed. Filing the recap emails and texts the owner — every statement recipient, including owner contacts.
Ask the viewer
The viewer is asked how it went, by email and text, on a no-login link that names the agent, the address and the time — so a viewer who never met that agent will say so. Their words are attached to the record when they arrive. Feedback arriving from the agent's own device is flagged for you to look at, never blocked: a real viewer may well be handed the agent's phone.
Two front doors, one book
Showings booked by tenants from a public EzyRent listing flow onto the same calendar. Approving a listing request promotes it into a full showing — assigned agent, server clock, mandatory recap — carrying the viewer's details and their pre-screen answers across as agent notes. Pending requests show as their own read-only layer so inbound demand is visible before anyone actions it, and they are never counted twice. Cancellations, no-shows and reschedules mirror across, so an agent is never sent to a property the viewer already called off.
The booking policy
Book showings through the listing so the pre-screen is always captured; point email, phone and Facebook enquiries at the listing. A hand-booked showing requires a written reason and is flagged on the record — deliberately not blocked, because blocking would just push people to stop recording showings at all, and a flagged exception you can count beats an invisible one.
What you get out of it
Per-property and per-unit “shown N times” counters — including for EzyRent listings — plus a 1-hour heads-up to the agent and an automatic feedback request 20 minutes after they leave.