Plan Trips and Packing Lists with ChatGPT

Consolidate Travel Preparations in a Single Project

Instead of fragmented searches, create a dedicated conversation thread for each trip. ChatGPT's project feature aggregates related dialogues, uploaded files, and instructions into one workspace.

When queried, it prioritizes project-stored data, eliminating the need to repeatedly explain destination, dates, or group size.

Projects are available across all subscription tiers with no quantity limits. Per OpenAI's help center, project sharing works on Free, Go, Plus and Pro as well as Business, Enterprise and Edu: Free allows 5 files and 5 collaborators per project, Go and Plus 25 files, and Edu, Pro, Business and Enterprise 40 files.

To check packing with family or companions, share the project, or copy the table if they have no account.

Example Input for Booking Consolidation

Uploading flight PDFs, accommodation confirmations, and insurance documents allows ChatGPT to generate itineraries by cross-referencing dates and times. File size limits: 512MB per file, 2 million tokens per document/text. Scanned booking photos must not exceed 20MB per image.

For a January Tokyo trip (5 days, 3 nights), input:

Based on uploaded flight and accommodation documents, create a January Tokyo 5-day, 3-night itinerary table with dates, times, airport transfer durations, and check-in/check-out schedules.

This query includes three conditions: source materials (uploaded files), format (date/time table), and critical elements (airport transfers). Omitting any may lead to inaccurate results as ChatGPT might infer missing details.

Storage limits: 25GB per user and 100GB per organization. When traveling across time zones, always specify the current location's time zone to prevent scheduling errors.

Store Recurring Travel Preferences in Memory

Memory retains frequently repeated contexts across chats, files, and connected apps. Save preferences like "window seats preferred" or "cannot eat spicy food" to avoid re-explaining them in future trips. One-time details like booking numbers should remain in project files to prevent accidental disclosure.

Memory settings are adjustable in personalization options. In shared accounts, disable memory for users who shouldn't retain data. Before deleting memories, verify their irrelevance as removal is irreversible.

Packing List Table Creation Process

Follow this repeatable workflow:

1. Create a new project in the project interface with destination and date in the name.
2. Upload flight, accommodation, and insurance documents, verifying their dates.
3. Record group size, duration, season, and activity focus in project instructions.
4. Request an initial itinerary: "Generate a date/time table based on uploaded bookings."
5. Request a packing list: "Create a table for January Tokyo 5-day, 3-night, 2 adults, sightseeing-focused. Include possession status and purchase necessity columns."
6. Differentiate existing items from needed purchases in the table.
7. Review reservations and packing completion the night before departure.

Sample table output:

If discrepancies arise, re-upload the table and specify problematic rows: "Rows 3 and 5 are accurate; refine the rest based on these." Avoid partial edits as column values may persist.

Upload Risks to Verify

Booking documents may contain personal data like names, reservation numbers, or card details. Avoid uploading original passports; blur sensitive fields if necessary. Company workspaces require verifying data policy compliance and potential manager access.

Delete files after use. Archiving conversations doesn't fully remove data; manually delete sensitive files. Export critical records via data export before account cleanup.

Verify Storage and Deletion Status

Check file list visibility and size post-upload. Confirm file names and sizes appear, and queries reference them. Itinerary errors may indicate upload issues or document inaccuracies.

If mobile upload buttons are missing, try the web version. Missing export emails may indicate 24-hour link expiration; re-request if needed. If a deleted memory or file still shows up in answers, the change is still propagating; check again in a new chat a little later. For unresolved issues, prepare screenshots and timestamps for official support.