At a glance
- The situation
- A growing agency runs every booking, cost and margin from one shared spreadsheet that the whole team edits.
- What goes wrong
- A mistyped cell silently changes a trip total, customer-service staff can see supplier rates and margins, dashboards rot, and finance works out by hand which supplier to pay today.
- What changes
- The platform imports the sheet, hides cost and margin fields by role, keeps KPI dashboards live and turns supplier payments into a queue with due dates and reminders.
An illustrative scenario: a growing agency runs its bookings, costs and margins from one shared spreadsheet, where a mistyped cell changes a total and every agent can see supplier rates. With Sheets import, field-level roles, live dashboards and a supplier payables queue, the agency keeps the familiarity of the sheet and loses the risk.
The scenario
Picture an agency that started with two people and a spreadsheet and now has a dozen. The sheet has grown with them: one row per booking, columns for customer, supplier, cost, selling price, margin, payment status and notes, plus tabs for each month and a pivot-table dashboard the owner built one weekend.
The owner's biggest fear is a fat-finger error. Last month a cost was typed into the wrong row and a trip showed a healthy margin until the supplier invoice arrived. Nobody could tell who had changed the cell or when. The cells are unlocked because locking them breaks the workflow for everyone else.
The second fear is visibility. Customer-service staff open the same sheet to answer a client, and in doing so they see the supplier's net rate and the agency's margin on every booking. Hiding those columns would mean maintaining a second copy of the sheet, which someone would have to keep in sync.
Then there is the daily grind: the pivot dashboard breaks whenever a column moves, and each morning the finance assistant filters the sheet to work out which suppliers are due for payment today — rebuilding the same filter every day because saved views collide with other people's.
Why it is hard to fix
A sheet does not know what a booking is
It cannot validate that a cost belongs to a supplier, keep a per-field audit trail or stop two people overwriting each other.
Permissions are all or nothing
Hiding columns for one role means copies, and copies drift apart.
Dashboards are rebuilt by hand
Pivot tables and filters depend on a layout that changes as the business grows.
Switching feels like stopping the business
The sheet works today; the fear is losing history or momentum during a migration.
What changes with the platform
The Innovate Solution platform starts by importing the existing booking records from Excel or Google Sheets, with the columns mapped to platform fields, so history comes across and totals can be checked against the sheet before the switch.
From then on, each booking is a structured record: supplier costs are tied to suppliers, changes are logged, and field-level role permissions decide who sees cost, margin and supplier rates. Customer-service staff work the same booking without ever seeing the margin column.
Live KPI dashboards replace the pivot table — booking status, margin, receivables and payables update as bookings are made — and the supplier payables queue lists what is due, by date, assigned to a person, with reminders. The ledger side runs in travoBooks, so month-end comes from the platform rather than from a tab.
How it works, step by step
-
Map the sheet
The team agrees which spreadsheet columns correspond to which booking fields and freezes the sheet's structure.
-
Import history
Existing bookings are imported from Excel or Google Sheets and totals are checked against the sheet.
-
Set roles
Field-level permissions are defined: who sees cost, margin and supplier rates, who can edit them.
-
Run in parallel
New bookings go into the platform while the sheet becomes read-only for reference.
-
Switch the daily routine
Finance works the supplier payables queue each morning; managers read the live dashboards instead of the pivot.
-
Close a period from the platform
Once a month has been closed in travoBooks from platform data, the sheet is retired.
Before and after
| Before | With the platform |
|---|---|
| A mistyped cell changes a trip total and nobody knows who did it | Costs belong to suppliers, and every change is logged |
| Everyone sees cost, margin and supplier rates | Each role sees only the fields it needs on the same booking |
| The pivot dashboard breaks when a column moves | KPI dashboards update live from booking data |
| Finance filters the sheet each morning to find who to pay | A payables queue lists what is due, by date, with reminders |
| History lives in monthly tabs | History is imported and searchable on the platform |
What it does not do
- Import brings across the data the sheet holds; it cannot add information that was never recorded.
- Roles enforce what people may see; deciding who should see what remains a management decision.
- It does not replace accounting judgement; it feeds the ledger with accurate booking data.
Questions about this scenario
What was the owner most worried about in this scenario, and how is it addressed?
Fat-finger errors and staff seeing margins. On the platform, costs are structured fields tied to suppliers with a change log, and field-level permissions hide margin and supplier rates from roles that do not need them.
Did the agency lose its booking history?
No. The existing records were imported from the spreadsheet first, and totals were checked against the sheet before new bookings moved over.
How did the daily "who do we pay today?" task change?
It became a payables queue: amounts due by date, assigned to a person, with reminders — instead of a filter rebuilt each morning.
What happened to the owner's pivot-table dashboard?
It was replaced by live KPI dashboards that draw directly from booking data, so there is nothing to rebuild when the business changes shape.
Related
About this page. This is an illustrative scenario: the business is hypothetical and the story is drawn from problems that travellers and travel agents describe in public forum discussions. It contains no customer names and no performance figures. The problem itself is explained on Replace spreadsheets in a travel agency; for measured results from named customers, see the case studies.
Recognise this situation? We will walk through it on the platform with your own bookings. The full explanation of the problem — causes, approach and limits — is on Replace spreadsheets in a travel agency.
