How it works

From management sign up to lease

The end-to-end workflow: management owns the platform, the leads, and the prospects. Each step hands off cleanly to the next — and the Showing Engine guards every transition.

  1. 1

    Management sync

    Management synchronizes eligible property and unit information through a PMS adapter. The management company remains the system of record for eligibility.

  2. 2

    Resident Available NOW

    A participating resident controls a simple Available NOW status — the resident decides when their occupied unit can be shown.

  3. 3

    Prospect request

    A prospective tenant requests access to an eligible unit. Private resident contact information is never shared with the prospect.

  4. 4

    Resident accept

    The resident accepts or declines the request. A showing only moves forward when the resident says yes.

  5. 5

    Broker gate (optional)

    When broker participation is required, the optional broker gate assigns or confirms broker involvement before the showing is locked in.

  6. 6

    Confirmed

    The Showing Engine confirms the workflow and locks the unit, preventing conflicting active showings for the same unit.

  7. 7

    Showing

    Check-in opens the showing. The engine tracks it in progress until the tour is complete.

  8. 8

    Completed

    Completion releases the unit lock and enables the prospect's outcome step.

  9. 9

    Apply / Watch / Decline

    After the tour, the prospect selects Apply, Watch, or Decline — closing the loop back to leasing.

Engine states

One authoritative state machine

The Showing Engine moves each workflow through these states — portals and mobile apps request transitions, the engine approves them.

AVAILABLEREQUESTEDRESIDENT_ACCEPTEDBROKER_GATECONFIRMEDIN_PROGRESSCOMPLETEDOUTCOME

Eligibility is enforced up front

A prospect can't request a unit unless it's eligible and the resident's availability is active. Invalid requests are rejected before they start.

Locks prevent conflicts

Confirmation creates a unit lock so no two active showings can claim the same unit; completion releases it.

Retries are safe

Caller idempotency keys make repeated or concurrent requests replay safely instead of double-booking.

Everything is audited

Each material transition records actor, organization, timestamp, and the state change — a complete trail for operations and review.

Follow the full workflow live

The workflow is running in the portal today — sign in to explore the management and Control Center views, or contact us about a pilot.