Remaining building switches under their module rows

Gatekeeper part 4: five more per-building switches staff could only flip with a script now show under the Maintenance and Leasing rows. Captured on the Fairhaven Residential (TEST) company on the stage data source.

14 Oct 2026 · branch gk/more-building-switches · captured against propflow-stage · at 671cbeb498f+local

Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.

1 · Under Leasing: the three new-lease switches

Under Leasing, after the listing switch: preparing next steps on approval, drafting the lease, and sending leases for signature. Each says how many buildings have it on; each building keeps its own value.

Asserted in the captured DOM — Prepare next steps when an application is approved · Draft the lease when an application is approved · Send leases for signature. All three labels are on screen under the Leasing row.

Under Leasing: the three new-lease switches
Sections 2–2

2 · Under Maintenance: call-backs and the older turnover switch

Under Maintenance, below the company switch for turnover work: calling residents back with an answer, and the older per-building turnover switch, labelled as older because it is planned to be replaced.

Asserted in the captured DOM — Call residents back with an answer · Turnover sends (older switch). Both labels are on screen under the Maintenance row.

Under Maintenance: call-backs and the older turnover switch
PropFlow Docs