Skip to main contentWhat is Activity History?
Activity history provides a complete audit trail of everything that happens to a run or event. Every action—whether taken by a team member, a guide, or automatically by the system—is recorded and displayed in chronological order.
This lets you see exactly what happened, when it happened, and who made the change. Activity history is essential for understanding the lifecycle of a booking, troubleshooting issues, and maintaining accountability across your team.
What Actions Are Tracked
Activity history captures a comprehensive range of operations across all aspects of runs and events.
Run Operations
The system tracks all changes to the run itself:
- Run created: When a new run is added to the system
- Run updated: Changes to run details like dates, times, locations, or other attributes
- Run deleted: When a run is removed
- Status changed: Transitions between states like draft, confirmed, completed, or cancelled
- Run merged: When multiple runs are combined into one
- Run split: When a single run is divided into separate runs
Booking Operations
Every booking action is recorded:
- Booking created: When a new booking is added to a run
- Booking deleted: When a booking is removed
- Booking attached: When an existing booking is linked to this run
- Booking detached: When a booking is unlinked from this run
Guide Assignments
All guide-related activities are tracked:
- Assignment created: When a guide is initially assigned to a run
- Assignment deleted: When a guide assignment is removed
- Status changes: When assignment status changes (invited, accepted, declined, etc.)
- Responses: When a guide responds to an invitation or request
- Withdrawals: When a guide withdraws from an assignment
Tickets and Documents
Document management actions appear in the history:
- Ticket uploaded: When a new ticket or document is attached
- Ticket removed: When a ticket or document is deleted
Passenger Changes
Any modifications to passenger information on the run are recorded, including additions, removals, and updates to passenger details.
Notes
Changes to run notes are tracked, showing when notes are added, edited, or removed.
All communication is logged:
- Comments: Every comment and reply appears in the activity history timeline
- Emails sent: When the system sends emails related to the run
- App invitations accepted: When a guide accepts an invitation to join the platform
Third-Party Integrations
Activity history tracks synchronization with external systems:
- Third-party syncs: When data is synced to or from integrated platforms
- Calendar events: When events are created or updated in connected calendars
Who Made the Change
Every activity entry identifies who or what caused the action. This takes two forms:
User Actions: When a person makes a change, the activity history shows which user performed the action. This can be an agency team member or a guide. You’ll see their name associated with the entry.
System Actions: Some actions happen automatically—like third-party syncs, automated status changes, or scheduled operations. These entries appear without a user name, indicating the system performed the action on its own.
This distinction helps you understand whether something happened because someone actively made a change or because an automated process triggered it.
How Activity History Is Displayed
Activity history appears as a chronological timeline, with the most recent actions at the top. Each entry shows:
- What happened: A clear description of the action
- When it happened: The timestamp of the action
- Who did it: The user’s name, or an indication that it was a system action
- Related details: Additional context specific to the action type
Comments appear inline within this timeline, giving you a unified view of both actions and discussions. This combined view makes it easy to understand the full context of what happened—you can see a comment discussing a problem right next to the actions taken to fix it.
Filtering Activity History
When working with runs that have extensive history, you can filter the timeline to focus on specific types of actions. This helps you quickly find what you’re looking for without scrolling through everything.
Filtering options let you show or hide different categories of activities, making it easier to focus on booking changes, guide assignments, or communication separately.
What’s Not Tracked
Activity history focuses on meaningful changes to runs and events. It intentionally doesn’t record:
- Viewing actions: Simply looking at a run doesn’t create a history entry
- Failed actions: Actions that were attempted but didn’t complete successfully
- Draft changes: Partial edits that aren’t saved
- Search and filter operations: Navigation and exploration activities
This keeps the activity history focused on actual changes to the run, making it more useful as an audit trail.
How History Connects to Runs and Events
Each activity entry is linked to specific runs and events. This means:
- Activity history for a run shows everything that happened to that specific run
- If a run is part of an event (a multi-day tour or series), you can see both run-specific and event-level activities
- When runs are merged or split, the history preserves connections so you can trace the lineage
This linking ensures that no matter how runs are organized or reorganized, you maintain a complete record of what happened. 
