01
Scope
Who needs the workflow, what is visible, and what stays out.
Loading this page.
Use case · Move-in and move-out
Run move-in and move-out checklists with QR intake, condition evidence, owner-safe reporting, vendor follow-up, and compliance review boundaries.
Use-case proof path
Move-in and move-out is framed with personas, trigger, preset workflow, proof, related modules, and a screenshot destination when one is available.
Inspect proof Open demoWho needs the workflow, what is visible, and what stays out.
Screenshot, proof card, or demo path that makes the claim inspectable.
What requires human review or source evidence.
Personas
Trigger
Resident or guest occupancy changes, security deposit evidence is needed, or a unit must be made ready.
Preset
Move-in/out checklist preset with room-by-room condition, keys/access, utilities, cleaning, damage notes, QR handoff, and reviewer boundary.
Problem
Resident or guest occupancy changes, security deposit evidence is needed, or a unit must be made ready.
Solution
Move-in/out checklist preset with room-by-room condition, keys/access, utilities, cleaning, damage notes, QR handoff, and reviewer boundary.
Outcome
Run move-in and move-out checklists with QR intake, condition evidence, owner-safe reporting, vendor follow-up, and compliance review boundaries.
Workflow
Start from the scheduled occupancy event or service request.
Run mobile room/area checklist with required photos and notes.
Separate tenant-visible, owner-visible, and operator-review context.
Create follow-up vendor tasks for cleaning, repair, access, or inventory gaps.
Archive the reviewed packet so future disputes and readiness checks have history.
Proof
Related product areas
Product proof
A buyer can see the operating moment become a reviewed, owner-safe next step.
Service preset or owner request opens a synthetic workflow.
A buyer can see the operating moment become a reviewed, owner-safe next step.
Safe sample scenario · illustrative operational state only.
Boundary
Use-case pages describe controlled product workflows, presets, and reviewed proof paths. They do not dispatch vendors, send legal notices, approve payments, change reservations, monitor alarms, or create accounting records without the governed product surface and account entitlements.
Pilot access
The best demo is not a feature checklist. It follows a request from owner intake to manager triage, vendor packet, field evidence, reviewed closeout, and owner-safe reporting.
We respond with the recommended demo route, who should attend, and what production access would require.