# Cove and Visitt UI task journeys

> *AI-generated recommendations for discussion. These are not Nick’s recommendations or approved JLL/PRISM guidance.

13 goal-based maps connect all 58 documented UI flow maps. The two reservation journeys have screen-by-screen storyboards. Public video and animation links are indexed separately in [ui-task-videos.json](https://crefieldnotes.com/ui-task-videos.json).

**Evidence rule:** Each numbered stage inside a flow is drawn from public vendor documentation. A transition from one module or flow map to another is a research reconstruction unless an original source explicitly states the handoff. No authenticated customer-account journey was performed. Old training frames do not prove the current layout.

## Contents

- [Cove: Launch a building and invite its tenant team](https://crefieldnotes.com/#cove-building-launch)
- [Cove: Resolve a tenant request and create its charge](https://crefieldnotes.com/#cove-service-to-invoice)
- [Cove: Plan, inspect and close maintenance work](https://crefieldnotes.com/#cove-planned-maintenance)
- [Cove: Reserve a room from the tenant app](https://crefieldnotes.com/#cove-amenity-reservation)
- [Cove: Register arrivals and manage access](https://crefieldnotes.com/#cove-arrival-and-access)
- [Cove: Publish building content and measure response](https://crefieldnotes.com/#cove-tenant-engagement)
- [Cove: Operate compliance, procurement and incident controls](https://crefieldnotes.com/#cove-control-desk)
- [Visitt: Configure a property and onboard a tenant](https://crefieldnotes.com/#visitt-portfolio-launch)
- [Visitt: Turn a tenant issue into completed, billable work](https://crefieldnotes.com/#visitt-service-to-accounting)
- [Visitt: Complete an inspection and correct a missed task](https://crefieldnotes.com/#visitt-inspection-correction)
- [Visitt: Book a room and prepare it for use](https://crefieldnotes.com/#visitt-amenity-reservation)
- [Visitt: Handle a tenant's visitors, packages and building updates](https://crefieldnotes.com/#visitt-tenant-day)
- [Visitt: Manage vendor insurance and operational documents](https://crefieldnotes.com/#visitt-compliance-desk)

<a id="cove-building-launch"></a>
## Cove: Launch a building and invite its tenant team

**Goal:** Make a configured property usable by the right building and tenant roles. **Trigger:** A new site or tenant organization is added. **Outcome:** A tenant can enter the branded app with the correct permissions. **Map type:** connected task map.

1. **Buildings, floors, suites → Property Info → Resources** — Property administrator. Define buildings and spaces → Edit property information → Publish resources → Configure the web address. Handoff: Property record and hierarchy are available for tenant setup. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-property-setup) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-property-setup) · [Primary source](https://support.cove.is/hc/en-us/articles/34283842710676-Buildings-Floors-And-Suites).
2. **Directory → Tenant organizations → Leases** — Property administrator. Create an organization → Associate people and leases → Update tenancy → Offboard the tenant. Handoff: Associate the organization and its people with the site. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-tenant-lifecycle) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-tenant-lifecycle) · [Primary source](https://support.cove.is/hc/en-us/articles/34863785965716-Adding-and-Managing-Tenant-Organizations).
3. **Directory → Add users / bulk upload → Roles** — Property administrator. Create or import users → Select roles → Send invitations → Review access. Handoff: Invite building and tenant users. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-user-onboarding) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-user-onboarding) · [Primary source](https://support.cove.is/hc/en-us/articles/34283855224852-Adding-Users).
4. **Tenant Admin User Manager** — Tenant administrator. Find a person → Update access → Suspend access → Review offboarding. Handoff: Delegate people management to the tenant administrator. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-tenant-user-admin) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-tenant-user-admin) · [Primary source](https://support.cove.is/hc/en-us/articles/40201638777876-Tenant-Admin-User-Manager).
5. **App Screens → Highlights → Spotlights → Quick Actions** — Property administrator. Arrange app screens → Add highlights → Configure spotlights → Set quick actions. Handoff: Publish the actions and content the tenant will see. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-tenant-home) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-tenant-home) · [Primary source](https://support.cove.is/hc/en-us/articles/34283735758228-App-Screens).

**Decision points:** Which role can see each building, space and app action? What happens when a tenant or user is offboarded?

**What to verify in a live demo:** Create a test tenant and user; confirm visibility in the mobile app and dashboard.

**Relevant video / animation evidence:**
- [App Screens and Spotlights Webinar](https://www.loom.com/share/f375cc3aa4df488097d5692b32e74d49) — official embedded video; Video reference; no image sequence captured.
- [Directory Management Webinar](https://www.loom.com/share/1f3bdde0f23e4eb8bac6f7c61d6866dc) — official embedded video; Video reference; no image sequence captured.

<a id="cove-service-to-invoice"></a>
## Cove: Resolve a tenant request and create its charge

**Goal:** Follow a tenant issue from intake through assignment, field execution, charging and review. **Trigger:** A tenant submits a service request. **Outcome:** The work record is completed and the appropriate tenant charge is visible. **Map type:** connected task map.

1. **Tenant app / dashboard → Submit Work Order** — Tenant and property team. Select the request entry point → Enter request details → Attach context → Review the submitted record. Handoff: A request record enters the property team's queue. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-request-intake) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-request-intake) · [Primary source](https://support.cove.is/hc/en-us/articles/34283654757908-Submitting-a-Work-Order).
2. **Work Orders → Assignments & Routing → Work Groups** — Operations manager. Configure routing → Organize work groups → Set escalation rules → Set notifications. Handoff: Rules or a manager assign the responsible team. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-dispatch) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-dispatch) · [Primary source](https://support.cove.is/hc/en-us/articles/36583309699476-Work-Order-Assignments-and-Routing).
3. **Tenant / property-team conversation** — Tenant and property team. Open a conversation → Exchange messages → Review the other role’s conversation view. Handoff: Clarify scope and communicate status where chat is enabled. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-chat) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-chat) · [Primary source](https://support.cove.is/hc/en-us/articles/50430089696788-Chat-Tenants).
4. **Mobile Work Order → Notes, labor, materials → Complete** — Engineer. Open assigned work → Record notes, labor and materials → Add travel where enabled → Resolve missing completion information. Handoff: Engineer records work and satisfies required completion fields. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-field-work) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-field-work) · [Primary source](https://support.cove.is/hc/en-us/articles/51873675144468-Guide-to-Work-Orders-on-Mobile).
5. **Time Cards** — Engineer and property manager. Configure time-card settings → Record time → Review team time cards. Handoff: Time is recorded or reviewed if that module is used. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-time-cards) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-time-cards) · [Primary source](https://support.cove.is/hc/en-us/articles/45991910109460-Time-Cards-Setup-Property-Teams).
6. **Estimates → Billable Charges → Tenant Invoices** — Property team and tenant approver. Configure labor and material rates → Review estimates → Add charges → Create the tenant invoice. Handoff: Property team reviews estimate and creates the tenant invoice. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-chargeback) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-chargeback) · [Primary source](https://support.cove.is/hc/en-us/articles/49287794767124-Adding-Labor-Rates-to-Your-Work-Order-Library).
7. **Reports / Insight Boards** — Property and regional manager. Select the data and metric → Configure filters and grouping → Arrange report cards → Review records or export. Handoff: Manager reviews service and billing metrics. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-analytics) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-analytics) · [Primary source](https://support.cove.is/hc/en-us/articles/52326436838420-Insights-Dashboard).
8. **Activity Log** — Property administrator. Open the activity log → Filter events → Inspect recorded changes. Handoff: Administrator inspects recorded changes. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-audit) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-audit) · [Primary source](https://support.cove.is/hc/en-us/articles/46177424570132-Activity-Log).
9. **CoveAI entry points** — Property team and engineer. Review content-generation entry points → Inspect work-order assistance → Review certificate extraction → Identify assistant release limitations. Handoff: AI assistance may help with writing or extraction; human review remains a separate step. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-ai-surfaces) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-ai-surfaces) · [Primary source](https://support.cove.is/hc/en-us/articles/45516314082068-CoveAI-FAQ).

**Decision points:** Is approval needed before billable work? Can the engineer close without required evidence? Is a tenant invoice the final accounting record?

**What to verify in a live demo:** Submit one billable and one non-billable request; trace record IDs across assignment, completion and invoice.

**Relevant video / animation evidence:**
- [Edit Viewable Columns](https://www.loom.com/share/c60aad4fd1a94a80b0bea1d56daf8942) — official embedded video; Sampled.
- [Reorder Columns](https://www.loom.com/share/0d97ff8bbf99490e8db34f5c6067e4a0) — official embedded video; Sampled.
- [Routing & Assignments Simplified: Ensure work orders, maintenance tasks, and inspections go to the right people and teams.](https://www.loom.com/share/9e36b0866f044f029fba35bbf7ad174c) — official embedded video; Video reference; no image sequence captured.
- [Work Order Billing Webinar](https://www.loom.com/share/d062160e03ab466aaf40e964eba5488b) — official embedded video; Video reference; no image sequence captured.
- [Tenant & Building Engineer View of Work Order Estimates](https://www.loom.com/share/ca950bec11d84740834cb273ee2023ad) — official embedded video; Sampled.
- [Tenant Admin Training: Submitting a Work Order](https://www.canva.com/design/DAGdyyfTphk/KvQ37_0o6QbMUhQ7QOMXOg/watch) — official training clip; Five historical frames sampled; original recording linked.

<a id="cove-planned-maintenance"></a>
## Cove: Plan, inspect and close maintenance work

**Goal:** Set up equipment and recurring tasks, execute on site and inspect performance across buildings. **Trigger:** Equipment or a recurring procedure is created. **Outcome:** Completed work and inspection history can be reviewed at site or network level. **Map type:** connected task map.

1. **Equipment → Associate QR → Scan** — Engineer. Associate a QR code → Scan from the field → Open equipment context. Handoff: The engineer can open equipment context in the field. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-equipment-qr) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-equipment-qr) · [Primary source](https://support.cove.is/hc/en-us/articles/34283774713620-Assigning-QR-Codes-to-Equipment).
2. **Recurring Work Orders → Template / Schedule** — Operations manager. Create a recurring template → Edit its recurrence → Configure when work opens. Handoff: A recurring work item is generated when due. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-recurring-work) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-recurring-work) · [Primary source](https://support.cove.is/hc/en-us/articles/34283774751636-Recurring-Work-Orders).
3. **Maintenance → Equipment → Procedure → Task** — Engineer and operations manager. Create equipment records → Configure procedures and schedules → Assign scheduled work → Complete tasks → Review history. Handoff: Assigned preventive work can be executed and recorded. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-maintenance) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-maintenance) · [Primary source](https://support.cove.is/hc/en-us/articles/34283806326292-Equipment-Libraries).
4. **Inspections → Create → Assign → Complete** — Operations manager and engineer. Create an inspection → Manage assignments → Open the inspection → Record completion. Handoff: Inspection evidence and status are recorded. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-inspections) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-inspections) · [Primary source](https://support.cove.is/hc/en-us/articles/34283690377492-Creating-Inspections).
5. **Network Maintenance → Site switcher** — Regional manager and engineer. Select network scope → Review maintenance → Switch sites on mobile → Review personal and group work. Handoff: Regional staff can review work across sites. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-network-work) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-network-work) · [Primary source](https://support.cove.is/hc/en-us/articles/49406066828180-Maintenance-at-the-Network-Level).
6. **Reports / Insight Boards** — Property and regional manager. Select the data and metric → Configure filters and grouping → Arrange report cards → Review records or export. Handoff: Manager reviews completion and exception patterns. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-analytics) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-analytics) · [Primary source](https://support.cove.is/hc/en-us/articles/52326436838420-Insights-Dashboard).

**Decision points:** Does a failed inspection automatically create corrective work? How are overdue tasks escalated?

**What to verify in a live demo:** Scan equipment at a property; finish a PM and an inspection; trace any corrective record.

**Relevant video / animation evidence:**
- [Equipment QR Codes- Associating QR Codes](https://www.loom.com/share/993e2a2edbbd4c6aa51fa1c80fbec941) — official embedded video; Sampled.
- [Equipment QR Codes- Scanning QR codes](https://www.loom.com/share/d74509f4b3384e10bfd0fca88806707f) — official embedded video; Sampled.
- [Inspections Webinar](https://www.loom.com/share/3596616a375e4050af517ce5e6324852) — official embedded video; Sampled.
- [Edit Viewable Columns](https://www.loom.com/share/c60aad4fd1a94a80b0bea1d56daf8942) — official embedded video; Sampled.
- [Reorder Columns](https://www.loom.com/share/0d97ff8bbf99490e8db34f5c6067e4a0) — official embedded video; Sampled.
- [Best Practices for Success: Maintenance Module Webinar ](https://www.loom.com/share/10db1d7e7d734779bf98a4de3193108a) — official embedded video; Video reference; no image sequence captured.
- [Create Recurring Work Order Templates](https://www.loom.com/share/785294f5f07b42698abfab9ef617a40d) — official embedded video; Sampled.
- [Edit Recurring Work Orders ](https://www.loom.com/share/1a43f37d46ea40bf9a04ad52d50b16e8) — official embedded video; Sampled.

<a id="cove-amenity-reservation"></a>
## Cove: Reserve a room from the tenant app

**Goal:** Configure a reservable space, let a tenant choose a slot, then handle approval and charges. **Trigger:** A tenant needs a conference room or other amenity. **Outcome:** A requested or confirmed reservation is visible to tenant and property team. **Map type:** screen-level example.

1. **Reservation Setup → Amenity Setup → Category / Space / Policies** — Property administrator. Create categories and spaces → Define reservation policies → Set seating options → Configure reservation credits. Handoff: Building team publishes capacity, schedule, rules and optional credits. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-amenity-setup) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-amenity-setup) · [Primary source](https://support.cove.is/hc/en-us/articles/34283827538964-Create-an-Amenity-Space-Category).
2. **Tenant home → Reserve Amenities quick action / Highlight** — Property administrator. Arrange app screens → Add highlights → Configure spotlights → Set quick actions. Handoff: The tenant reaches the booking entry point. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-tenant-home) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-tenant-home) · [Primary source](https://support.cove.is/hc/en-us/articles/34283735758228-App-Screens).
3. **Reserve Amenities → Availability → Space → Reservation Time → Complete Request** — Tenant and property team. Choose a space and time → Review the reservation → Handle approval → Review charges and reminders → View tablet entry points. Handoff: Each selected date becomes an individual reservation record. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-amenity-booking) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-amenity-booking) · [Primary source](https://support.cove.is/hc/en-us/articles/49442451819412-Reserving-Amenities-Tenant-Admins).
4. **Waivers / booking questions** — Property team and tenant. Create the waiver → Configure questions and signatures → Set visibility and notifications → Review responses. Handoff: The tenant supplies required questions or signatures when configured. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-waivers) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-waivers) · [Primary source](https://support.cove.is/hc/en-us/articles/34283693801876-Waivers-Overview).
5. **Requested Reservations → Reservation Details → Approve / Deny** — Tenant and property team. Choose a space and time → Review the reservation → Handle approval → Review charges and reminders → View tablet entry points. Handoff: Property team resolves a request when approval is required. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-amenity-booking) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-amenity-booking) · [Primary source](https://support.cove.is/hc/en-us/articles/49442451819412-Reserving-Amenities-Tenant-Admins).
6. **Amenity Reservations → Billing / Reminders** — Tenant and property team. Choose a space and time → Review the reservation → Handle approval → Review charges and reminders → View tablet entry points. Handoff: Team reviews fees, reminders and any linked work orders. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-amenity-booking) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-amenity-booking) · [Primary source](https://support.cove.is/hc/en-us/articles/49442451819412-Reserving-Amenities-Tenant-Admins).

### Screen-by-screen example

1. **Entry and availability (Tenant)** — Tenant home → Reserve Amenities quick action or Highlight → date, start and duration → available spaces. [UI asset](https://crefieldnotes.com/ui/cove-expanded-df7d3a70a6e4495d.png) · [Source](https://support.cove.is/hc/en-us/articles/49442451819412-Reserving-Amenities-Tenant-Admins). Composite screen 1 shows availability and a room choice; the home-screen entry is documented rather than pictured here.
2. **Space and time (Tenant)** — Open space → review room details and availability → edit date/time; optional multi-date selection. [UI asset](https://crefieldnotes.com/ui/cove-expanded-df7d3a70a6e4495d.png) · [Source](https://support.cove.is/hc/en-us/articles/49442451819412-Reserving-Amenities-Tenant-Admins). Composite screens 2–4 show room details, date editing and multiple dates.
3. **Review and submit (Tenant)** — Review the selected dates, then tap Complete Request (composite screen 5). [UI asset](https://crefieldnotes.com/ui/cove-expanded-df7d3a70a6e4495d.png) · [Source](https://support.cove.is/hc/en-us/articles/49442451819412-Reserving-Amenities-Tenant-Admins). The composite does not show a questionnaire or waiver. Any conditional requirements need their own guide or live demonstration.
4. **Result (Tenant)** — View Requested or Confirmed reservation; each selected date is a separate record. [UI asset](https://crefieldnotes.com/ui/cove-expanded-df7d3a70a6e4495d.png) · [Source](https://support.cove.is/hc/en-us/articles/49442451819412-Reserving-Amenities-Tenant-Admins). Composite screen 6 visibly shows Requested. A Confirmed result and the approval rules require the linked guide or a live demonstration.
5. **Approval branch (Property team)** — Requested Reservations → Reservation Details → approve or deny, with optional reason. [UI asset](https://crefieldnotes.com/ui/cove-expanded-c94096cd6e2c8e7e.gif) · [Source](https://support.cove.is/hc/en-us/articles/34283721439124-Reservation-Approvals). Animated official help-center sequence; current layout may differ.
6. **After booking (Property team)** — Amenity Reservations → open record → review charge, reminder and linked work orders when configured. [UI asset](https://crefieldnotes.com/ui/cove-expanded-e9fefd3faffa0519.png) · [Source](https://support.cove.is/hc/en-us/articles/34283776157204-Amenity-Reservation-Billing). Final payment/accounting posting is not established by the public UI evidence.

**Decision points:** Available slot? Approval required? Fee or credit applies? Edit or cancel after submission?

**What to verify in a live demo:** Show the tenant, approver and billed-booking views on one test reservation; verify time-zone behavior and linked work orders.

**Relevant video / animation evidence:**
- [App Screens and Spotlights Webinar](https://www.loom.com/share/f375cc3aa4df488097d5692b32e74d49) — official embedded video; Video reference; no image sequence captured.
- [Amenity Reservations Webinar- April 30, 2024](https://www.loom.com/share/657549c916cc4980841aad194dc8bf91) — official embedded video; Video reference; no image sequence captured.
- [Tenant Admin Training: Reserving Amenities](https://www.canva.com/design/DAGeQFMtmw4/8PWfo0Qrb3TplSHZvHq-_w/watch) — official training clip; Four historical frames sampled; original recording linked.
- [Reservation approvals animated UI](https://crefieldnotes.com/ui/cove-expanded-c94096cd6e2c8e7e.gif) — official help-center animation; Animated property-team approval sequence; not tenant booking creation.

<a id="cove-arrival-and-access"></a>
## Cove: Register arrivals and manage access

**Goal:** Prepare individual or group guests, handle check-in and connect related access and package tasks. **Trigger:** A tenant expects visitors or a delivery. **Outcome:** The arrival and any package handoff have a visible status. **Map type:** related task branches.

1. **Visitor Management → Register → Check-in** — Tenant administrator and front desk. Configure visitor rules → Register an individual or recurring visit → Check in the visitor → Review a watchlist match. Handoff: Guest is expected and front desk can process arrival. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-visitors) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-visitors) · [Primary source](https://support.cove.is/hc/en-us/articles/34283728982164-Visitor-Management-Setup).
2. **Groups → Bulk Visitor Upload** — Tenant administrator and front desk. Set up a group → Prepare visitor rows → Upload the list → Review imported visitors. Handoff: For events or larger visits, import multiple attendees. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-group-visitors) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-group-visitors) · [Primary source](https://support.cove.is/hc/en-us/articles/34283818099476-Group-Visits).
3. **Mobile Credential Setup → Issue / Revoke** — Tenant and property administrator. Enable the applicable access integration → Add the mobile credential → Review device setup → Revoke a credential. Handoff: Tenant access credential is a separate related path. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-mobile-access) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-mobile-access) · [Primary source](https://support.cove.is/hc/en-us/articles/45785657215508-HID-Bluetooth-Apple-Google).
4. **Packages → Register → Notify → Collect** — Front desk and tenant. Register the package → Associate its recipient → Track notification and collection. Handoff: Delivery reception and pickup run as a parallel front-desk path. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-packages) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-packages) · [Primary source](https://support.cove.is/hc/en-us/articles/50115736550292-Packages).

**Decision points:** Individual or group arrival? Watchlist or access exception? Is credential issuance required for this person?

**What to verify in a live demo:** Register one visitor and one group; show front-desk check-in, notifications and access exception handling.

**Relevant video / animation evidence:**
- [Adding & Formatting Bulk Visitor Upload Data](https://www.loom.com/share/b6977399796d40b380be6c0f6fef1f2b) — official embedded video; Sampled.
- [Exporting Bulk Visitor Upload Data](https://www.loom.com/share/250843837e264552bd696f5b92390fa2) — official embedded video; Sampled.
- [Upload Bulk Visitor Data](https://www.loom.com/share/ab7da30f146e4f05992d8fd64e849752) — official embedded video; Sampled.
- [Tenant Admin Training: Registering Visitors](https://www.canva.com/design/DAGeQEG3Lgg/VlpfGBLGpM8upbGBSqKN7g/watch) — official training clip; Four historical frames sampled; original recording linked.

<a id="cove-tenant-engagement"></a>
## Cove: Publish building content and measure response

**Goal:** Run tenant-facing campaigns, events, building displays and feedback collection. **Trigger:** Property team has an announcement or event to publish. **Outcome:** Tenant sees the content and the team can inspect participation or responses. **Map type:** related task branches.

1. **Events → Create → RSVP → Check-in** — Property team. Create the event → Configure recurrence or RSVP slots → Check in attendees → Gather feedback. Handoff: Publish an event and track attendance. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-events) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-events) · [Primary source](https://support.cove.is/hc/en-us/articles/34283794009492-Creating-Managing-Events).
2. **Email Builder → Recipients → Send → Metrics** — Property team. Select or build an email template → Prepare recipients → Send the announcement → Inspect delivery and engagement metrics. Handoff: Target an announcement and review delivery. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-announcements) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-announcements) · [Primary source](https://support.cove.is/hc/en-us/articles/48812777192212-Email-Templates).
3. **Displays → Layout → Device setup** — Property administrator. Create display content → Configure display layout → Connect and troubleshoot the display device. Handoff: Publish building display content as a separate channel. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-displays) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-displays) · [Primary source](https://support.cove.is/hc/en-us/articles/34283824748948-Displays).
4. **Surveys → Audience → Send → Responses** — Property team. Build the survey → Select the audience → Send it → Review responses. Handoff: Collect feedback from the chosen audience. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-surveys) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-surveys) · [Primary source](https://support.cove.is/hc/en-us/articles/34283715549972-Surveys-Creating-a-Survey).
5. **Reports / Insight Boards** — Property and regional manager. Select the data and metric → Configure filters and grouping → Arrange report cards → Review records or export. Handoff: Review engagement data where available. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-analytics) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-analytics) · [Primary source](https://support.cove.is/hc/en-us/articles/52326436838420-Insights-Dashboard).

**Decision points:** Which tenant segments see the content? Is event attendance linked to survey response?

**What to verify in a live demo:** Publish one test event and announcement, then inspect tenant rendering and response records.

**Relevant video / animation evidence:**
- [Adding Attachments to Email Builder Emails](https://www.loom.com/share/ee2aef62c4854755825289bf5783ac26) — official embedded video; Sampled.
- [{Webinar} Event Planning Made Simple: Leverage Cove’s Events & Reservations for Your Holiday Season ](https://www.loom.com/share/eb6c762a7f3243bb9fd98a6f1d15aa68) — official embedded video; Sampled.
- [Setting Up Displays](https://www.loom.com/share/6c25081291cb4de29b3d63a9f8c4d29d) — official embedded video; Sampled.
- [Edit Viewable Columns](https://www.loom.com/share/c60aad4fd1a94a80b0bea1d56daf8942) — official embedded video; Sampled.
- [Reorder Columns](https://www.loom.com/share/0d97ff8bbf99490e8db34f5c6067e4a0) — official embedded video; Sampled.
- [Cove Kiosk App- Download and Setup](https://www.loom.com/share/53a3088360c8427ab3f175d38ba98870) — official embedded video; Sampled.
- [Event App- Check-In](https://www.loom.com/share/b34185a05a1c4b5aa40adaa25cd78592) — official embedded video; Sampled.
- [Use Coves Email Builder Like a Pro-Webinar](https://www.loom.com/share/9971ee2178bd4c9a9a08834c19cb9b29) — official embedded video; Video reference; no image sequence captured.

<a id="cove-control-desk"></a>
## Cove: Operate compliance, procurement and incident controls

**Goal:** Map related administrator tasks that share oversight but are not proven as one enforced workflow. **Trigger:** A COI, purchase request or incident needs handling. **Outcome:** Each record has an owner, state and review path. **Map type:** related task branches.

1. **COI → Requirements → Extraction Review → Compliance** — Compliance administrator. Configure requirements → Upload and review extraction → Manage coverage versions → Track compliance and notifications. Handoff: Review certificate evidence and exceptions. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-coi) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-coi) · [Primary source](https://support.cove.is/hc/en-us/articles/46139514014868-COI-Setup).
2. **Purchase Orders → Request → Approval → Export** — Property team and approver. Configure purchase orders → Create a request → Review approval behavior → Export or print. Handoff: Create and approve a purchase record. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-purchase-orders) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-purchase-orders) · [Primary source](https://support.cove.is/hc/en-us/articles/34283770552852-Purchase-Order-Setup).
3. **Incidents → Categories → Routing → Report** — Property manager and operations team. Set categories and incident types → Configure routing → Open an incident report → Review response and status. Handoff: Route and review an incident report. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-incidents) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-incidents) · [Primary source](https://support.cove.is/hc/en-us/articles/34283788035604-Incident-Setup).
4. **Activity Log** — Property administrator. Open the activity log → Filter events → Inspect recorded changes. Handoff: Inspect the resulting changes where recorded. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#cove-audit) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=cove-audit) · [Primary source](https://support.cove.is/hc/en-us/articles/46177424570132-Activity-Log).

**Decision points:** Who owns each exception? Do PO, incident and COI records actually link to one another?

**What to verify in a live demo:** Ask for a live exception trace, including permission checks and audit event IDs.

**Relevant video / animation evidence:**
- [Create Purchase Orders](https://www.loom.com/share/357a83154dde49b1b98dc257955befee) — official embedded video; Sampled.
- [Export and Print Purchase Orders](https://www.loom.com/share/eb491a37e4fc44468c98cd9504ec1381) — official embedded video; Sampled.
- [Create Incident Categories](https://www.loom.com/share/21639cb29a944e7c80186299f93995d0) — official embedded video; Sampled.
- [Create Incident Types](https://www.loom.com/share/cd3dae263b814ae085fe00e57067a5db) — official embedded video; Sampled.
- [Route Incident Reports](https://www.loom.com/share/37db0f3707c843fb9fbf2b4b32b13a0a) — official embedded video; Sampled.
- [Open an Incident Report](https://www.loom.com/share/0f444f633a684319aee3f4a368ea5734) — official embedded video; Sampled.

<a id="visitt-portfolio-launch"></a>
## Visitt: Configure a property and onboard a tenant

**Goal:** Create the property structure, access roles and tenant-facing entry point. **Trigger:** A new property or tenant is being launched. **Outcome:** Staff and tenant can enter the right property context. **Map type:** connected task map.

1. **Global Settings → Buildings / Properties** — Global administrator. Open global settings → Manage buildings and properties → Set primary properties → Inspect property structure. Handoff: Define the operating scope. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-portfolio-setup) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-portfolio-setup) · [Primary source](https://help.visitt.io/en/articles/14997267-global-settings-buildings).
2. **Global Categories → Local Categories → Templates** — Property and global administrator. Create global categories → Manage local categories → Create or edit reusable templates. Handoff: Standardize classifications and reusable work. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-categories) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-categories) · [Primary source](https://help.visitt.io/en/articles/15545550-global-categories).
3. **Users → Invite → Property Access → Permissions** — Property and global administrator. Invite a user → Assign property access → Configure permissions → Transfer responsibilities → Deactivate access. Handoff: Grant staff the appropriate scope. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-user-access) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-user-access) · [Primary source](https://help.visitt.io/en/articles/9246330-how-to-add-users-to-your-property).
4. **Tenants → Contacts → Property association** — Property team. Create or edit a tenant → Associate contacts and properties → Archive contacts → Restore access when appropriate. Handoff: Set the tenant directory and contacts. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-tenants) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-tenants) · [Primary source](https://help.visitt.io/en/articles/9394000-manage-your-tenants-in-visitt).
5. **Tenant App Settings → Branding → Pages** — Property administrator. Configure branding and app features → Create pages and links → Arrange tenant content → Review the tenant presentation. Handoff: Publish the tenant-facing property experience. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-tenant-branding) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-tenant-branding) · [Primary source](https://help.visitt.io/en/articles/9242176-managing-your-tenant-app).
6. **Login code → Home → Property switcher** — Tenant. Enter the login code → Review the home screen → Switch property context → Set profile and notification preferences. Handoff: Tenant enters the app and chooses property context. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-tenant-start) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-tenant-start) · [Primary source](https://help.visitt.io/en/articles/16891940-getting-started-with-visitt-a-guide-for-tenants).
7. **Profile → Notifications / Preferences** — Property team member. Log in → Open the profile → Configure personal details and preferences → Review notification and permission controls. Handoff: Staff member tunes personal settings. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-profile) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-profile) · [Primary source](https://help.visitt.io/en/articles/10425978-how-to-log-in-to-your-account).

**Decision points:** What data is inherited globally versus overridden by a property? Can a tenant see only their assigned locations?

**What to verify in a live demo:** Launch a sandbox property, invite one manager and tenant, and verify effective access.

**Relevant video / animation evidence:**
- [My Property](https://www.loom.com/share/31ca03a066fa475e896139e2b8aa07cb) — official embedded video; Sampled.

<a id="visitt-service-to-accounting"></a>
## Visitt: Turn a tenant issue into completed, billable work

**Goal:** Trace intake, work-order ownership, field updates, tenant approval, accounting transfer and reporting. **Trigger:** Tenant submits an issue in Visitt+. **Outcome:** Completed work and eligible charges reach a visible export or sync state. **Map type:** connected task map.

1. **Visitt+ → + → New request → Open / Closed requests** — Tenant. Create a request → Add category, description and attachments → Inspect open and closed requests → Message the property team. Handoff: Request is visible to the tenant and property team. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-tenant-requests) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-tenant-requests) · [Primary source](https://help.visitt.io/en/articles/16297490-visitt-work-orders-create-and-track-requests).
2. **Work Orders → Open → Detail / Acceptance** — Property team. Create a work order → Review and accept it → Manage subscribers → Inspect removal controls. Handoff: Manager accepts and owns the operational ticket. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-work-orders) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-work-orders) · [Primary source](https://help.visitt.io/he/articles/9881125-כיצד-ליצור-קריאת-עבודה-תהליך-חדש-ומשופר).
3. **Work Orders → Automation / Recurring Schedules** — Operations manager. Choose a trigger → Define conditions and actions → Set default assignment → Create recurring work. Handoff: Rules assign people, priority or SLA where configured. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-automation) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-automation) · [Primary source](https://help.visitt.io/en/articles/9000597-how-to-set-work-order-automations).
4. **On-call Schedule → Rotation / Replacement** — Global administrator and on-call engineer. Define properties and rotation → Assign tiers → Request replacement coverage → Review on-call assignment context → Set out-of-office periods. Handoff: Coverage handles after-hours assignment. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-on-call) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-on-call) · [Primary source](https://help.visitt.io/en/articles/14791155-set-up-and-manage-on-call-schedules).
5. **My Work → Request detail → Updates → Complete** — Engineer. Find assigned work → Open request context → Record updates → Complete the work → Review visibility troubleshooting. Handoff: Engineer records work and status. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-field-work) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-field-work) · [Primary source](https://help.visitt.io/he/articles/9842720-ניהול-וביצוע-קריאות-שבר-אנשי-שטח).
6. **Billable Items → Tenant Approval → Sync / Export** — Property manager, tenant approver and accounting. Add billable items → Request tenant approval → Verify completed work → Queue eligible charges for synchronization → Inspect export and synchronization states. Handoff: Manager and accounting review eligible charges and transfer state. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-billing) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-billing) · [Primary source](https://help.visitt.io/en/articles/9357580-billing-management).
7. **Reports → Views → Export** — Property and regional manager. Review status metrics → Inspect operational reports → Define a saved view → Configure sharing and export. Handoff: Portfolio team examines completion and cost patterns. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-reporting) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-reporting) · [Primary source](https://help.visitt.io/en/articles/9352401-status-page-explained).
8. **Work-order AI assistance** — Property team and engineer. Review related-request suggestions → Inspect title and category assistance → Review writing assistance → Inspect certificate analysis. Handoff: Related-request, title, category or writing assistance is reviewed in context. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-ai-surfaces) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-ai-surfaces) · [Primary source](https://help.visitt.io/en/articles/9697354-visitt-ai-capabilities).

**Decision points:** Awaiting acceptance or auto-assigned? On-call coverage needed? Tenant approval required? Did the accounting system acknowledge the export?

**What to verify in a live demo:** Use a billable tenant request and trace IDs from tenant chat through posted accounting entry; public evidence stops at export/sync state.

<a id="visitt-inspection-correction"></a>
## Visitt: Complete an inspection and correct a missed task

**Goal:** Set up assets and a scheduled inspection, verify field presence and deal with exceptions. **Trigger:** A scheduled inspection is due. **Outcome:** A completed or reopened inspection has an auditable reason and any corrective work is tracked. **Map type:** connected task map.

1. **Spaces / Equipment → QR context** — Property manager and engineer. Manage floors and spaces → Add equipment → Record lifecycle fields → Open QR-linked context. Handoff: Define the location and equipment being checked. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-assets) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-assets) · [Primary source](https://help.visitt.io/en/articles/10054955-my-property-floors).
2. **Inspections → Template → Tasks / Locations / QR requirement** — Operations manager. Define the inspection → Add tasks and locations → Set order and schedule → Require a QR scan where appropriate. Handoff: Design the route and verification rules. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-inspection-setup) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-inspection-setup) · [Primary source](https://help.visitt.io/en/articles/8799107-how-to-create-and-edit-inspections).
3. **Open Inspections → Task detail → Complete / Reopen** — Engineer and operations manager. Open scheduled inspections → Record task completion → Inspect closed records → Reopen an eligible missed task; record a late-completion reason when finishing. Handoff: Engineer completes tasks; manager may reopen an eligible missed item. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-inspection-execution) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-inspection-execution) · [Primary source](https://help.visitt.io/en/articles/9097482-how-to-view-and-complete-open-inspections).
4. **Inspection → New Work Order → Finish inspection → Work Orders** — Property team. Create a work order → Review and accept it → Manage subscribers → Inspect removal controls. Handoff: The Visitt inspection guide says a work order started during an inspection is officially created after the inspection is finished. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-work-orders) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-work-orders) · [Primary source](https://help.visitt.io/he/articles/9881125-כיצד-ליצור-קריאת-עבודה-תהליך-חדש-ומשופר).
5. **My Work → Updates → Complete** — Engineer. Find assigned work → Open request context → Record updates → Complete the work → Review visibility troubleshooting. Handoff: Engineer closes any related corrective ticket. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-field-work) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-field-work) · [Primary source](https://help.visitt.io/he/articles/9842720-ניהול-וביצוע-קריאות-שבר-אנשי-שטח).
6. **Reports / Shared Views** — Property and regional manager. Review status metrics → Inspect operational reports → Define a saved view → Configure sharing and export. Handoff: Manager reviews missed and late work. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-reporting) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-reporting) · [Primary source](https://help.visitt.io/en/articles/9352401-status-page-explained).

**Decision points:** QR scan required? What happens when the inspection is missed? Does the corrective work order appear only after Finish inspection?

**What to verify in a live demo:** Run one on-time and one missed inspection; show reopen reason and the corrective work-order linkage after completion.

**Relevant video / animation evidence:**
- [How to view and complete open inspections](https://www.loom.com/share/b6607444367e4f64bb8680afccddd726) — official embedded video; Sampled.
- [How to Edit Inspections](https://www.loom.com/share/773c96cf43ed401f84d2688f2e243935) — official embedded video; Sampled.
- [Visitt - Google Chrome - 13 June 2024](https://www.loom.com/share/bc93fb4144dc46469ab639ddaba6a240) — official embedded video; Sampled.
- [ביצוע משימות שפוספסו ](https://www.loom.com/share/f29fb2e28abd43cd811200ca37d9332e) — official embedded video; Sampled.

<a id="visitt-amenity-reservation"></a>
## Visitt: Book a room and prepare it for use

**Goal:** Configure an amenity, let the tenant book it, and show the manager's approval, work-order and billing paths. **Trigger:** A tenant wants a reservable room or resource. **Outcome:** Tenant sees booking state, property team handles it, and preparation work is completed. **Map type:** screen-level example.

1. **Amenities → Manage Amenities → Rules / Pricing** — Tenant and property team. Review amenity settings → Select the space and time → Submit a booking → Inspect booking details and communication. Handoff: Property manager sets capacity, slots, cost, hours and booking questions. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-amenities) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-amenities) · [Primary source](https://help.visitt.io/en/articles/9414363-visitt-amenities-for-property-managers).
2. **Visitt+ home → + → Book amenity** — Tenant. Enter the login code → Review the home screen → Switch property context → Set profile and notification preferences. Handoff: Tenant opens the creation path. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-tenant-start) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-tenant-start) · [Primary source](https://help.visitt.io/en/articles/16891940-getting-started-with-visitt-a-guide-for-tenants).
3. **Book amenity → Space → Date and time → Notes → Book** — Tenant and property team. Review amenity settings → Select the space and time → Submit a booking → Inspect booking details and communication. Handoff: Booking appears under Amenities with its status. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-amenities) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-amenities) · [Primary source](https://help.visitt.io/en/articles/9414363-visitt-amenities-for-property-managers).
4. **Amenities → Bookings → Approve / Reject / Edit** — Tenant and property team. Review amenity settings → Select the space and time → Submit a booking → Inspect booking details and communication. Handoff: Manager handles the pending request; the animated UI illustrates later booking views. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-amenities) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-amenities) · [Primary source](https://help.visitt.io/en/articles/9414363-visitt-amenities-for-property-managers).
5. **Work Orders → Amenity preparation record** — Property team. Create a work order → Review and accept it → Manage subscribers → Inspect removal controls. Handoff: Official manager guide says a booking creates a work order for preparation. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-work-orders) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-work-orders) · [Primary source](https://help.visitt.io/he/articles/9881125-כיצד-ליצור-קריאת-עבודה-תהליך-חדש-ומשופר).
6. **Billable item / export state** — Property manager, tenant approver and accounting. Add billable items → Request tenant approval → Verify completed work → Queue eligible charges for synchronization → Inspect export and synchronization states. Handoff: Vendor marketing says bookings flow to billing; exact ledger handoff needs a live demonstration. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-billing) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-billing) · [Primary source](https://help.visitt.io/en/articles/9357580-billing-management).

### Screen-by-screen example

1. **Entry (Tenant)** — Visitt+ home → yellow + → Book amenity. [UI asset](https://crefieldnotes.com/ui/visitt-expanded-8b0efc241ad24a3e.png) · [Source](https://help.visitt.io/en/articles/16288920-amenities-visitt). Official help-center screenshot.
2. **Space and form (Tenant)** — Choose a space → review image, capacity and price → select date/time and enter required details → Book. [UI asset](https://crefieldnotes.com/ui/visitt-expanded-76a0ea13c54b9828.png) · [Source](https://help.visitt.io/en/articles/16288920-amenities-visitt). Official help-center screenshot; specific fields vary by property.
3. **Booking status (Tenant)** — Amenities → booking list → open booking; see status and chat with the building team. [UI asset](https://crefieldnotes.com/ui/visitt-expanded-90a36f8b8d969cea.gif) · [Source](https://help.visitt.io/en/articles/16288920-amenities-visitt). Official animated help-center UI shows later booking views, not the creation tap sequence.
4. **Approval branch (Property team)** — Amenities → Bookings → approve, reject, edit or cancel; switch to calendar if needed. [UI asset](https://crefieldnotes.com/ui/visitt-expanded-b3f7806e33940d21.png) · [Source](https://help.visitt.io/en/articles/9414363-visitt-amenities-for-property-managers). Documented manager guide; exact tenant notification handoff should be checked.
5. **Preparation and charge (Property team)** — Open the work order triggered by the booking → complete preparation; inspect billable charge/export state where configured. [UI asset](https://crefieldnotes.com/ui/visitt-expanded-9ee2559d0c0dd870.png) · [Source](https://help.visitt.io/en/articles/9414363-visitt-amenities-for-property-managers). Work-order trigger is documented; complete accounting handoff is vendor claim plus analytical join.

**Decision points:** Is the slot available? Is approval needed? Does a charge appear before or after approval? Who completes the setup work order?

**What to verify in a live demo:** Book a paid room in a sandbox account; follow the same booking ID through approval, preparation work and accounting export.

**Relevant video / animation evidence:**
- [Amenities (Visitt+) animated UI](https://crefieldnotes.com/ui/visitt-expanded-90a36f8b8d969cea.gif) — official help-center animation; Animated booking-management screens; not a full booking-creation video.

<a id="visitt-tenant-day"></a>
## Visitt: Handle a tenant's visitors, packages and building updates

**Goal:** Show parallel tenant-app tasks around a typical on-site day. **Trigger:** A visitor, package or building notice needs handling. **Outcome:** Tenant receives the relevant invite, pickup alert or broadcast. **Map type:** related task branches.

1. **Visitt+ → New visitor → Scheduled visitors** — Tenant and front desk. Create a visitor invitation → Inspect scheduled visitors → Manage arrival records → Review watchlist controls. Handoff: Tenant pre-registers a visitor; front desk manages arrival. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-visitors) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-visitors) · [Primary source](https://help.visitt.io/en/articles/16297178-visitors-overview).
2. **Packages → Record → Notify → Collect** — Front desk and tenant. Record a package → Associate the tenant or contact → Review collection status. Handoff: Front desk records delivery and tenant confirms pickup. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-packages) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-packages) · [Primary source](https://help.visitt.io/en/articles/9448312-managing-packages).
3. **Broadcasts → Audience / Channel → Preview / Send** — Property team. Create the broadcast → Select recipients and channels → Preview and send → Review the tenant message entry point. Handoff: Property team publishes a building update. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-broadcast) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-broadcast) · [Primary source](https://help.visitt.io/en/articles/9383612-how-to-use-visitt-s-broadcast-messaging).
4. **Visitt+ home → Messages / Preferences** — Tenant. Enter the login code → Review the home screen → Switch property context → Set profile and notification preferences. Handoff: Tenant receives content in the chosen property context. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-tenant-start) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-tenant-start) · [Primary source](https://help.visitt.io/en/articles/16891940-getting-started-with-visitt-a-guide-for-tenants).

**Decision points:** Does a watchlist match require manual review? Which channel actually delivered the broadcast?

**What to verify in a live demo:** Demonstrate visitor QR arrival, package e-signature and one targeted broadcast in the same tenant account.

**Relevant video / animation evidence:**
- [Visitors Watchlist](https://www.loom.com/share/d3a8c300cfb34d80b2dd3b4f31054ebc) — official embedded video; Public metadata unavailable.
- [Visitors Watchlist](https://www.loom.com/share/1b30613e44814a54b127822125102690) — official embedded video; Public metadata unavailable.

<a id="visitt-compliance-desk"></a>
## Visitt: Manage vendor insurance and operational documents

**Goal:** Track vendor scope, certificate requirements and document expiry as related compliance tasks. **Trigger:** A vendor is engaged or a certificate nears expiry. **Outcome:** Compliance reviewer sees the current evidence and outstanding exceptions. **Map type:** related task branches.

1. **Vendors → Property links → Verification** — Property and global administrator. Create or find a vendor → Link properties → Upgrade or merge records → Review verification and property-specific compliance. Handoff: Identify the vendor and affected properties. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-vendors) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-vendors) · [Primary source](https://help.visitt.io/en/articles/16579477-manage-global-vendors-across-your-portfolio).
2. **COI → Requirements → Analysis → Exceptions** — Compliance administrator. Configure tracking and requirements → Upload certificate evidence → Review analysis → Configure reminders and exceptions. Handoff: Review tenant or vendor coverage and reminders. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-coi) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-coi) · [Primary source](https://help.visitt.io/en/articles/14456467-set-up-and-validate-tenant-coi-requirements).
3. **Documents → Upload → Context / Expiry** — Property team. Upload a document → Set its context and expiry → Validate its status → Remove a document when appropriate. Handoff: Maintain related operational evidence. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-documents) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-documents) · [Primary source](https://help.visitt.io/en/articles/9491071-documents-in-visitt).
4. **Reports / Shared Views** — Property and regional manager. Review status metrics → Inspect operational reports → Define a saved view → Configure sharing and export. Handoff: Review status across the portfolio. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-reporting) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-reporting) · [Primary source](https://help.visitt.io/en/articles/9352401-status-page-explained).
5. **COI analysis assistance** — Property team and engineer. Review related-request suggestions → Inspect title and category assistance → Review writing assistance → Inspect certificate analysis. Handoff: AI-supported analysis is a claimed control; exception resolution remains to validate. [Flow detail](https://crefieldnotes.com/ui-flow-atlas.html#visitt-ai-surfaces) · [Images](https://crefieldnotes.com/ui-gallery.html?flow=visitt-ai-surfaces) · [Primary source](https://help.visitt.io/en/articles/9697354-visitt-ai-capabilities).

**Decision points:** Which documents are required for each vendor? Can an expired COI block dispatch? Who approves an AI exception?

**What to verify in a live demo:** Create an expiring certificate and show reminders, exception review, access rules and audit history.

## Coverage and limitations

All 58 existing flow maps appear in at least one journey: 33 Cove and 25 Visitt. Related-task branches group distinct jobs; they are not a single product-enforced transaction. The video index includes official embedded recordings and two official help-center animations; some are references only, without captured frames. Missing public footage is a research gap, not a capability gap.