> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Travel and venue test plan

> QA checks for the mobile ride card with Uber and Lyft, traveler details, the gig venue panel, the venue map with key spots, sharing a venue, and the gig Changes list. Lists the travel and venue work that is API only and not yet testable by hand.

This plan covers recent travel and venue work on the gig. Some of it is API only, with no screen yet. Those parts are listed under [API only](#api-only-agents-test-these) so testers do not look for them. Read the [QA testing guide](https://docs.soundchecklive.io/qa.md) before you start.

## At a glance

| Area | Platforms | Build |
| - | - | - |
| Ride card with Uber and Lyft (ENG-2298) | Mobile, web link | Over the air |
| Rides saved for offline use (ENG-2308) | Mobile | Over the air |
| Traveler details on your profile (ENG-1769) | Mobile | Over the air |
| Admins edit a member's traveler details (ENG-1795) | Mobile | Over the air |
| Venue panel and Directions (ENG-1611) | Mobile | Over the air |
| Share venue address and parking (ENG-1733) | Mobile | Over the air |
| Venue map with key spots (ENG-2287) | Mobile | Over the air |
| Crew notes and files on key spots (ENG-2288, ENG-2289) | Mobile and web | Over the air |
| Grouped Changes list (ENG-2297) | Mobile | Over the air |
| Crew add their own flights and rides (ENG-2291) | API only | Not applicable |
| Boarding passes and confirmations (ENG-2292) | API only | Not applicable |
| Read a travel confirmation into draft bookings (ENG-2293) | API only | Not applicable |

None of these features has a feature flag. [What's ready](https://docs.soundchecklive.io/qa/scope.md) shows where each area is deployed and whether TestFlight has it. An area that is only on dev needs a development or Revyl build.

## Before you start

* **A gig with a venue that has a full street address.** Uber and Lyft need an address the app can find on a map.
* **A ride on the gig** with a pickup and drop-off address, and your crew account as a rider. Managers add rides on web, in the gig's travel section. Choose the rideshare kind for the **Get a ride** checks.
* **Key spots on the venue.** On web, open **Venues →** the venue **→ Key spots**, add a spot with a name and kind, tap **Drop pin**, and click the map. Add at least two.
* **Two accounts:** a crew member and an owner or admin.

## In scope

### Ride card (mobile)

| ID | Role and surface | Steps | Expected |
| - | - | - | - |
| TV-01 | Crew, mobile | Open the gig's Details, then **Know before you go**. | A **Transportation** card follows Flights. Each ride shows its kind and provider, such as "Rideshare / taxi · Uber", **Pickup** and **Drop-off** with times or "Time TBD", and "You're on this ride". |
| TV-02 | Crew, mobile | Look for cost, payer, or booking code on the ride. | None of them show. |
| TV-03 | Manager, mobile | Open the gig's **Logistics**, and **Staffing → Travel**. | The same card, with an **Edit on web** link in its header. |
| TV-04 | Crew, mobile | Tap a pickup or drop-off address. | A sheet offers **Open in Maps** (iOS only), **Open in Google Maps**, **Ride with Uber**, **Ride with Lyft**, **Copy address**, and **Cancel**. |
| TV-05 | Crew, mobile | On a rideshare ride with a drop-off, tap **Get a ride**. | A **Get a ride** sheet with Uber, Lyft, and copy address only. |
| TV-06 | Crew, mobile | Use a ride whose drop-off cannot be found on a map. | The sheet offers maps and says "Uber and Lyft need a map location, and this address couldn't be found on the map." |
| TV-07 | Crew, mobile | Open the venue card's **Directions**. | Uber and Lyft also show there. A key spot's **Directions** does not offer them. |
| TV-08 | Manager, web | Open the gig's transport list. | Rideshare rows show **Get a ride: Uber · Lyft** links once the drop-off is found on the map. |
| TV-09 | Crew, mobile | Open a gig with no rides. | No **Transportation** card. |

### Traveler details (mobile)

| ID | Role and surface | Steps | Expected |
| - | - | - | - |
| TV-10 | Any user, mobile | Open **You → Profile → Edit profile → Crew profile → Location & travel**. Fill in **Legal name**, **Date of birth**, and **Preferred airport** under **Traveler details**. Tap **Save location and travel**. | The values save and show on reopen. Your profile name does not change. |
| TV-11 | Any user, mobile | Use **Clear date of birth**, then save. | The date of birth stays empty after reopening. |
| TV-12 | Any user, mobile | Change a field, then leave without saving. | "Discard location and travel changes?" |
| TV-13 | Any user, web | Open your profile's Location & Travel on web. | It shows the same values saved on mobile, and the reverse. |
| TV-14 | Owner or admin, mobile | Open **You → Organization Admin → Members**. Tap the plane icon on a member. | **Traveler details** opens with "Used to book travel for" the member. **Save traveler details** shows "Traveler details saved." |
| TV-15 | Owner or admin, web | Open that member on web. | Only the field you changed is different. |
| TV-16 | Crew, coordinator, or finance, mobile | Open **Members**. | No plane icon. Opening the screen by link says "Only owners and admins can edit traveler details." |
| TV-17 | Owner or admin, mobile | Look at your own row and at pending invitations. | No plane icon on either. |

### Venue panel, Directions, and sharing (mobile)

| ID | Role and surface | Steps | Expected |
| - | - | - | - |
| TV-18 | Crew, mobile | Open **Details → Venue & load-in**. Managers open the **Venue** tab. | The venue name and address show once each, with **Directions** and **Copy address**. **Copy address** shows "Address copied". |
| TV-19 | Crew, mobile | Tap **Directions**. | A sheet with **Open in Maps**, **Open in Google Maps**, **Copy address**, and **Cancel**. |
| TV-20 | Crew, mobile | Look at **Load-in & access** on a gig with an access code and a show-specific change. | The access code comes first with a copy button. Changed items show **Changed for this show**. |
| TV-21 | Crew, mobile | **Add note** in show notes, then delete it. | The note saves. Delete asks **Delete note?** first. |
| TV-22 | Crew, mobile | Tap the share icon on the venue card. | The share sheet gets the venue name, address, a parking line, and a Google Maps link. With no parking set, the parking line is left out. |
| TV-23 | Owner, mobile | Open a gig with no venue. | "No venue yet" with **Add venue**. No share icon. |

### Venue map (mobile)

| ID | Role and surface | Steps | Expected |
| - | - | - | - |
| TV-24 | Crew, mobile | Open the venue panel on a gig whose venue has pinned key spots. | A **Key spots** card with a map preview and an **Expand** pill. |
| TV-25 | Crew, mobile | Tap the preview. | **Venue map** opens full screen. Numbered pins match the numbered list. |
| TV-26 | Crew, mobile | Tap a pin. | A sheet with the spot's name, kind, notes, photos, and **Directions**. |
| TV-27 | Crew, mobile | Use **Show list**, **Show map**, and **Recenter map**. | The view switches between list and map, and recenter fits all pins. |
| TV-28 | Crew, mobile | Turn on airplane mode, then open the map. | "The map needs a connection. Here are the key spots as a list." |
| TV-29 | Crew, mobile | Open a venue with key spots but no pins. | No map preview. |
| TV-30 | Manager, mobile | Look for a way to add or move a pin. | None. Pins are edited on web only. |

### Crew notes on key spots (mobile and web)

A crew note belongs to the venue's key spot, not to one gig. It shows on every gig at that venue and on the venue page.

| ID | Role and surface | Steps | Expected |
| - | - | - | - |
| TV-45 | Crew, mobile | In the **Key spots** list on the gig's venue, or in a pin's sheet on the venue map, tap **Add note**. Type a note and post it. | The note shows at once with "Added by" your name, the gig, and its date. |
| TV-46 | Crew, mobile | Tap **Add photo or file**. Add a photo from the camera, one from the library, and a PDF. | Each one attaches. A PDF shows as a file tile with its name. Tapping a file opens it. |
| TV-47 | Crew, mobile | Try to attach a video, a file over 25 MB, and more than 10 files in one pick. | "Videos can’t be added to a spot. Add a photo or a PDF." The large file is named as over 25 MB. Past 10 files: "A note can hold up to 10 files." The add buttons turn off at 10. |
| TV-48 | Crew, mobile | Post a note with airplane mode on. | The note stays with its text and files and offers **Retry**. It posts after you reconnect and retry. |
| TV-49 | Crew, web | On the gig's **Venue** tab, pick a key spot on the map or in the side list. | A **Crew notes ·** spot name panel shows under the map. The side list shows "· N notes" on the spot. |
| TV-50 | Crew, web and mobile | Add a note on one gig, then open another gig at the same venue as a second crew member. | The note shows there, marked with the gig it came from. The second crew member cannot edit or delete it. |
| TV-51 | Author, web and mobile | Edit, then delete, your own note. | Both work. Delete asks first. |
| TV-52 | Manager, web | Open **Venues →** the venue **→ Key spots**. | Each spot lists the crew notes from the org's gigs there. A manager can edit or delete any note. |
| TV-53 | Crew, web and mobile | Open the sample gig or an archived gig. | No way to add a note. |

### Changes list (mobile)

The **Changes** section shows on the gig for everyone except org owners and admins, who see **Recent activity** instead. Test it as crew or a coordinator.

| ID | Role and surface | Steps | Expected |
| - | - | - | - |
| TV-31 | Crew, mobile | Open the gig once. Then have an owner change the call time on web five times within an hour. Reopen the gig. | **Changes** opens by itself with "N new". The five edits fold into one row, "… · 5 times", with a time range and a **New** badge. |
| TV-32 | Crew, mobile | Tap the folded row. | It lists each change. Tapping again hides them. |
| TV-33 | Crew, mobile | Open a gig with more than three change rows. | Three rows, then **Show N more**, then **Show fewer**. |
| TV-34 | Crew, mobile | Close the section, leave, and reopen the gig. | It stays closed until something new arrives. |
| TV-35 | Owner, mobile | Open **Recent activity**. | Rows read as sentences, such as "Guest Count changed from 100 to 120", never as code or IDs. |

## API only: agents test these

These checks go straight to the API. Crew flights, rides, boarding passes, and reading a confirmation have no screen yet, so testers skip them. Key spot notes have screens now (TV-45 to TV-53), and TV-39 checks the same rules at the API. Agents run these with `npm run api` against a local stack. See the [agent runbook](https://docs.soundchecklive.io/qa/agent-runbook.md).

| ID | Feature | What to check |
| - | - | - |
| TV-36 | Crew add their own flights (`v1EventsMyFlightsCreate`, `Update`, `Delete`) | As `member.multi`, add a flight. The same flight number on the same local day updates it. Editing a manager's flight or another person's returns 403 "You can only change flights you added". A caller not on the gig gets 404. |
| TV-37 | Crew add their own rides (`v1EventsMyRidesCreate`, `Update`, `Delete`) | A ride with service `UBER` saves as a rideshare. Another crew member's added ride is hidden from crew. Crew never see cost or payer, but the adder still sees their own confirmation code. |
| TV-38 | Boarding passes and confirmations (`v1EventsBookingsDocumentsUploadsCreate`, then the signed upload, then `…UploadsCompleteCreate`) | PDF, JPEG, PNG, HEIC, or `.pkpass` up to 20 MB. Crew upload only to their own booking row. A personal file is visible only to its owner and managers. Files never appear in the gig's documents. |
| TV-39 | Crew notes and files on key spots (`v1EventsVenueSpotsAnnotationsCreate`) | A note added on one gig shows on another gig at the same venue, marked with the gig it came from. Crew cannot edit someone else's note (403). Sample and archived gigs refuse notes (403). |
| TV-54 | Read a travel confirmation (`POST /api/v1/events/{event_id}/travel/parse/uploads`, the signed upload, then `POST /api/v1/events/{event_id}/travel/parse`) | A PDF, JPEG, PNG, or `.pkpass` returns draft flights, stays, and rides, and writes nothing. Crew drafts never name another traveler. HEIC is refused. Another person cannot read your staged file. |

## Out of scope

Do not file these as bugs. They are not built yet.

* Adding or uploading your own flights and rides in the mobile app (ENG-2294).
* A **My travel** screen on mobile (ENG-2295) and crew travel editing on web (ENG-2296).
* A mobile screen that reads a travel confirmation (ENG-2323). The API is in TV-54.
* Seeing boarding passes or confirmations on any screen.
* Editing key spot pins on mobile.

## Known limitations

* **Uber and Lyft need an address the app can find on a map.** The seeded demo venue has none, so Uber and Lyft are correctly missing there.
* **On Android, the app looks up an address only when location access is already on.** It never asks for location for this.
* **The fallback alert** that shows when another sheet is open labels the copy button **Copy Address**.
* **"New" in Changes needs a previous visit on the same device.** On a first visit, nothing is new.
* **The map loads its code from the internet.** Offline, it always falls back to the list.

## Needs a real device

| ID | Check | Expected |
| - | - | - |
| TV-40 | iPhone with Uber and Lyft installed: **Ride with Uber** and **Ride with Lyft**. | Each app opens with the drop-off filled in. |
| TV-41 | Call the driver from the ride card. | The phone dials. |
| TV-42 | Turn on hide sensitive info, then open the ride card. | The driver and the pickup instructions and notes are hidden. |
| TV-43 | Share the venue to Messages, and on Android through the share sheet. | The message holds the address, parking, and map link. |
| TV-44 | Android, venue map. | The map renders in the Android web view. |
| TV-55 | Open a gig with a ride while online. Turn on airplane mode, force-quit the app, and reopen the gig. | The ride card still shows pickup and drop-off, times, the driver, and pickup instructions. Needs a build with ENG-2308. |

## For agents

* **Personas** for `npm run api` on a local stack: `owner.busy`, `admin.busy`, `coord.busy`, and crew `member.multi` or `member.invites`.
* **Path parameters** are snake case on travel routes (`event_id`, `flight_id`, `ride_id`, `booking_kind`, `booking_id`) and camel case on venue spot routes (`eventId`, `spotId`).
* **The signed upload** for TV-38 is a separate `curl -X PUT` with the headers the create call returns. `npm run api` sends JSON only.
* **Hybrid check for the ride card:** create a ride as `member.multi` with service `UBER` and a drop-off, then run TV-01 to TV-05 on a simulator as that member.
* **Existing tests:** `e2e/tests/transports/my-flights-and-rides.test.ts` and `booking-documents.test.ts`.
* **Analytics** (PostHog, mobile key spot notes): `venue_spot_note_added`, `venue_spot_file_added`, `venue_spot_note_add_failed`, `venue_spot_note_updated`, and `venue_spot_note_deleted`. They carry no note text, file names, or spot names.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.