Who touched this booking, what changed and when
The change history of the management software for travel agencies.
Every save is recorded with the name of whoever made it, the date and the detail field by field: what it said before and what it says now. It opens from the card itself, without leaving where you are.
The record builds itself, down at the database
Nobody has to remember to write anything down for it to be there.
It opens from the card, not from another menu
On the menu of a booking, a collection, an invoice, a passenger, an expense, an operator payment or a calendar event you'll find View change history. A window opens with that record's full sequence of saves, and closes without losing the place you were working in.
- Seven entities with their own history
- On each card's menu
- Without leaving the screen
Field by field, with the before and the after
Each save is shown as a table: section, field, previous value and new value, with the old value struck through. It is not a notice that something changed, it is exactly what changed. A save that altered nothing real produces no entry at all.
- Previous and new value
- Grouped by section
- Empty saves don't clutter it
Created, edited or deleted
Each entry carries its action in its own colour, so it reads at a glance whether someone added a section, corrected it or removed it. When a single save did several things at once, they show separately but share the same timestamp, so it is clear it was one operation.
- Created, Edited and Deleted
- One save can hold several actions
- With date, time and user
Inside a booking, section by section
A booking's history does not stop at the header fields: it covers what happened to its flights, accommodation, transfers, insurance, excursions, vehicles, allotments, passengers, groups and collections. Every change is labelled with the section it belongs to.
- Twelve sections within the booking
- Every change with its section
- Including what was deleted
The database records it, not the screen
The record is written by the database itself every time a value changes, not by the application when it remembers to. That means it doesn't depend on anyone using the right screen, and a record's history survives even if the record is later deleted.
- Written on save, always
- Cannot be edited from the app
- Survives the record's deletion
Everyone sees the history of what they can already see
Access to the history mirrors access to the entity: whoever cannot reach expenses or operator payments cannot see their history either. The Passenger role reaches no history at all. And it is all separated per agency, like the rest of the data.
- Inherits the entity's permissions
- The Passenger role is excluded
- Separated per agency
Frequently asked questions
Change history in Tripwise
What we get asked most about traceability.
Every time a change is saved, an entry is kept with who made it, when, which action it was (created, edited or deleted) and the field-by-field detail with the previous and new value. Bookings, collections, invoices, passengers, expenses, operator payments and calendar events each have their own history; inside a booking you also see what happened to each of its sections.
They see the history of what they already have permission to see. That reaches bookings, collections, passengers, invoices and calendar events across the agency, but not expenses or operator payments, because they cannot reach those modules either. The Passenger role sees no history at all.
No. The history is read on screen and has no export: no PDF, no Excel, no CSV and no evidence package to hand over externally. Nor is there a global screen answering what one person did across a whole week: it is consulted record by record, from that record's own card.
No. It is read-only: it exists to understand what happened and who did it, not to reverse it. There is no restore, no rolling back to an earlier version and no comparing two arbitrary versions against each other. Each save is compared against the one immediately before it.
The window shows that record's last fifty saves and says so when there are more. There is no pagination to keep going back and no date filter to jump to a particular moment. Reads are not recorded either: there is a trace of who modified something, not of who looked at it.
Explore the other modules
Your agency's whole back-office, in one place.
Bookings
Passengers, flights, documents and statuses for each booking in one place.
Learn moreFinance & commissions
Commissions and margins calculated for you, with each booking's real result.
Learn moreARCA invoicing
A, B and C invoices and credit/debit notes, built into the booking.
Learn moreAI import
The wholesaler's PDF becomes a loaded booking, ready to review.
Learn moreAir + Land Allotment
The wholesaler's closed package, loaded as one unit with its expiry date in plain sight.
Learn moreTake control of your agency today
Start free in minutes. No card, no installs. Your operation, organized from day one.