Conferences and offsites expose a gap in Ramp Travel when multiple employees attend the same event.
Current challenge:
Each traveler creates a separate trip often named differently. From an admin and accounting perspective, this fragments visibility, complicates reconciliation, and makes event-level budgeting unnecessarily manual.
Proposed Improvement
Introduce an Event-based trip model:
- A single master Event/Conference trip owned by a team lead or admin
- Team members join the event instead of creating standalone trips
- Arrival and departure dates are auto-derived from bookings (earliest arrival, latest departure)
- Structured event fields:
- Event name
- Start/end dates
- Location
- Trip type dropdown:
- Conference / Event
- Company offsite
- Customer visit
- General travel
Destination should be inferred automatically from booking data.
Why This Matters
This unlocks clean, consistent:
- Event-level spend visibility
- Faster reconciliation
- Accurate year-over-year budgeting by conference or offsite
- Less manual cleanup caused by inconsistent trip naming
Before vs. After
Before:
- 6 employees attend the same conference
- 6 separate trips with different names
- Finance must manually piece together total spend
After:
- 1 Event: “2026 Finance and Accounting Technology Expo”
- 6 travelers attached to the same event
- One consolidated view of total travel spend, dates, and location
This would significantly improve Ramp Travel for teams managing real-world, multi-person travel at scale.