A weekly review should help a small tour operator decide what needs attention before the next departures. It does not need a presentation or a large dashboard. It needs dependable figures, a short explanation of what changed and a few actions that someone can finish.
The challenge is usually definition. A booking made this week may depart next month, and money shown as expected may arrive later still. When those are combined into one success figure, the business can look busy while its next departures or bank balance need attention.
1. Give the review a fixed purpose and time
Choose a regular time when the previous week's records are reasonably complete and someone can still act on the coming week. A thirty-minute meeting is a useful starting target for a small team, not a rule. A solo operator can use the same agenda in a short written note.
Bring together the person responsible for bookings, the person who understands delivery and the person who can explain financial commitments. One person may hold all three roles. Include the guide or dispatcher when a recurring operational problem needs their account.
Prepare a one-page review with a reporting period, preparation time and data sources. Start with urgent exceptions, then review demand, delivery, contribution and cash. Finish with decisions.
Do not let routine reporting postpone a safety issue, an imminent missed pickup or an overdue guest response. Those need action when they arise. The weekly meeting examines whether the underlying process needs to change after the immediate problem has been handled.
2. Define the dates and units behind every number
Separate three views. The sales view describes bookings created during the period. The delivery view describes tours scheduled or operated during it. The cash view describes money received or paid during it. Label each clearly and use the same local reporting boundary from week to week.
Count booking references and participants separately. One group booking can occupy several places. Keep adults, children and other resource-relevant categories clear where those distinctions affect capacity or delivery costs.
Choose how to treat amendments, cancellations and rebookings before comparing totals. A guest moving from Tuesday to Friday should not become two new customers simply because a second record was created. Retain the references needed to explain the change.
Write a brief metric definition beside each figure in your working sheet. “Guests delivered” might mean checked-in participants on completed departures, excluding staff. “New bookings” might mean confirmed booking references first created in the period, with later status tracked separately. Your definitions should fit your operation; consistency makes them useful. Record any definition change so an apparent improvement is not merely a counting change.
3. Start with unresolved commitments
Before discussing growth, inspect commitments that could fail. Look at bookings awaiting a required decision, promised guest updates, missing pickup details, pending changes, unresolved supplier confirmations and refunds that need follow-up. Sort by consequence and deadline, not just age.
For each exception, identify the booking or departure, current state, next action, owner and deadline. “Waiting for driver” is incomplete without a person responsible for contacting the driver and a time to escalate if there is no answer.
Review exceptions carried over from last week. An item repeatedly deferred needs a decision: resolve it, change the plan or obtain the necessary specialist help. Do not mark it complete because someone sent an email.
A useful discussion might be: “Three Friday bookings have no final pickup arrangement. The dispatcher will verify the route today, and the booking owner will send each guest the confirmed details by the agreed time.” That is an action your next review can verify. “Improve communication” is too broad to manage. Keep personal guest information in the appropriate booking record rather than copying it into a widely shared meeting summary.
4. Read demand with the future departures in view
Review new confirmed bookings and participant numbers by product and departure date. Then look ahead over a period that matches your normal planning needs. A business requiring early guide commitments needs a different horizon from one running several daily departures.
Compare the current position with the same point before comparable departures, where you have reliable history. A Saturday with two weeks left to sell should not be judged against another Saturday's final attendance. Note holidays, closed dates, marketing changes and product changes that affect the comparison.
Check what the demand can actually fit. A popular morning departure may have little room left while afternoon capacity remains unsold. Before offering a promotion, establish whether the constrained resource is seats, guides, equipment or pickup transport.
If you use a spreadsheet, Google's pivot table documentation explains grouping and summarising records. A pivot can organise bookings by product and activity date, provided the underlying records and units are correct. It will not detect a duplicated booking or an incorrect status for you. Reconcile a small sample to the original records before trusting a new summary.
5. Compare delivery with the capacity actually offered
Review completed departures, participants carried, late arrivals, operator cancellations and material service problems. Define the available capacity carefully. Physical maximum capacity, places actually offered and places occupied answer different questions.
In a hypothetical example, three completed departures each offered ten places and carried twenty-four guests in total. Occupancy across those departures is 24 divided by 30, or 80%. That does not describe a fourth departure cancelled before operation. Show that cancellation separately so it does not disappear from the review.
Group service problems by cause rather than counting every message as a separate failure. Several guests asking where to meet may reflect one incorrect instruction. Conversely, one complaint can reveal a serious process problem even when the week's overall rating looks positive.
Ask what changed the delivery outcome. Was a delay caused by an inaccurate duration, a supplier issue, a late guest or an impractical pickup route? Record evidence rather than assigning blame from the first account. Choose the correction at the right level: the product design, listing, final message or departure process. Monitor the next comparable departure to see whether that correction worked.
6. Review cancellations without mixing unrelated groups
A cancellation recorded this week may relate to a booking made months ago. Dividing this week's cancellation count by this week's new bookings can produce a misleading rate because the numerator and denominator describe different groups.
For a quick weekly view, show cancellation events and their reasons as counts. For a meaningful rate, define a consistent group, such as bookings for a particular completed departure period, and state when their final status was checked. Keep operator cancellations, guest cancellations, duplicate corrections and genuine booking moves distinguishable.
Look for patterns that suggest an action. Repeated cancellations after guests receive pickup information may point to a problem with the coverage promise. Weather cancellations may require a better decision timetable or product mix, rather than more persuasive sales copy.
Review financial effects separately: amounts refunded, amounts still under review and any relevant supplier costs. Do not assume every cancelled booking has the same treatment. Apply the actual booking conditions, platform process and applicable requirements, obtaining qualified advice where needed. The weekly review identifies work and trends; it does not determine universal refund rights or replace a booking-level decision.
7. Compare product contribution using explicit assumptions
Sales value alone does not show what a tour contributes toward the rest of the business. Review a simple contribution calculation by product or departure using verified selling values, applicable channel costs and direct delivery costs. State whether tax, refunds and shared overhead are included.
Consider a hypothetical completed departure with eight guests paying 70 currency units each. Gross booking value is 560. Assume channel charges of 10% of that value, direct guest costs of 20 each and departure-specific costs of 140. The remaining contribution is 560 minus 56 minus 160 minus 140, or 204 units.
That 204 is not net business profit. It excludes shared overhead, tax and any other costs outside the assumptions. Compare it with what you expected and investigate the difference. A supplier price increase, a discount or a lower-priced participant mix can change the result even when attendance is stable.
Use the tour pricing and contribution guide for a fuller costing method. For wider financial review, Australia's business.gov.au explains the roles of financial statements in its financial health guidance. Its jurisdiction-specific obligations should not be assumed to apply everywhere; use an accountant for your own reporting and tax treatment.
8. Check when the cash will actually move
Look at available bank funds, expected receipts and committed outgoing payments on their actual expected dates. Include supplier deposits, wages, refunds and other obligations relevant to your business. Keep uncertain receipts visibly separate from money already received.
The Australian government's cash flow guide supports maintaining records, monitoring due dates and comparing expected with actual movements. For your weekly review, use that principle to ask whether the next delivery commitments can be funded when they fall due.
A hypothetical business might begin with 1,000 units available, expect 300 of receipts that clear during the week and have 700 of payments due. Its projected closing balance is 600, assuming those timings hold. A further 500 expected the following month cannot fund this week's bill unless another arrangement exists. Test a delayed-receipt scenario before committing more spending.
Tripnatic's operator reporting includes expected payouts. Eligible completed and cleared operator bookings enter monthly bank-transfer payout, so expected values need to be read alongside eligibility and timing. Do not treat them as an instant payment or as cleared cash. Investigate unexplained differences using the actual account information and relevant support process.
9. Review channels with comparable evidence
Choose a small set of channel measures that can change a decision: attributable bookings where known, participants, contribution, cancellations and staff time required. Keep the booking reference as the main way to avoid counting the same sale twice across several reports.
If you operate your own website with a separately configured Google Analytics property, its Traffic acquisition report helps examine where visits come from. Website visits are a different unit from confirmed bookings in your booking records. Do not assume every visitor can be matched to a sale.
Google also explains the distinction between user acquisition and traffic acquisition: the reports answer different questions about first acquisition and visits. Keep the selected report and date range consistent when making comparisons. No native Tripnatic connection to these tools is implied.
Avoid changing a strategy because one small week looks unusually good or bad. Check the actual bookings, the product mix and a longer comparable period. Record an unknown channel as unknown rather than forcing a guess. A review becomes more reliable when uncertainty is visible and future measurement improves gradually.
10. Finish with three decisions the team can verify
End the meeting with a short action record. Each action needs an owner, deadline, reason and completion evidence. Limit the list to what the team can realistically do while delivering the coming week's tours. Carry significant unresolved issues into the appropriate management process instead of hiding them under routine tasks.
A practical action record might contain:
- Verify the Friday pickup route and send corrected instructions by the agreed deadline.
- Check the revised meal cost against the next product contribution calculation.
- Review the morning departure's remaining capacity before approving a promotion.
At the next review, check those outcomes first. If an action did not help, examine why and adjust the plan. Keep a dated note so you can distinguish a recurring issue from a one-off event.
Operators exploring Tripnatic can review the operator partner page. Its reporting views include bookings, cancellations, promotions and expected payouts, alongside product and operational tools. Use the available information with your delivery records and financial records, rather than expecting one screen to answer every question.
The value of the weekly review is the connection between evidence and action. Keep the definitions stable, explain exceptions honestly and leave with decisions that make the next week more manageable.
