> ## Documentation Index
> Fetch the complete documentation index at: https://hack-club-pin-docs-urls.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Adding your travel details
The Travel step tells organizers when you arrive and when you leave, so they can plan pickups and make sure nobody is stranded. You fill it in during onboarding, and — unlike everything else — you can **keep editing it after you submit**, right up to the event.
## What we ask for
* **Visa status** — whether you need a visa to attend, if your event asks.
* **Getting there (arriving)** — how you'll arrive in the event city.
* **Getting home (departing)** — how you'll leave.
For each direction, pick your mode of travel: **plane, train, bus, car, or other**.
## Flying? A few extra fields
If you pick **plane**, each flight needs:
* the **flight code** (like UA1234 — it's on your booking confirmation),
* the **departure and arrival airports** (start typing and pick from the suggestions),
* the **departure and arrival times**.
Attend checks the flight code against real flight data, so double-check it matches your booking exactly.
**Booked but don't have flights yet?** That's fine — you can come back. Enter what you know now and update it later from your event page.
## Updating travel after you've submitted
1. Go to your **Dashboard** and open your event.
2. Find the **Travel** section and click **Edit**.
3. Make your changes and save.
If organizers are missing your travel info, you might get a friendly reminder email — the link in it takes you straight to this page.
## Flying alone as an unaccompanied minor?
If your airline registers you as an unaccompanied minor (UM), there's a specific flow for that — see [Flying as an unaccompanied minor](/participants/05-unaccompanied-minors).