Tracking time spent on travel enquiries
A practical system to track time spent on travel enquiries—plus a filled example log, spreadsheet template, and a Nowah prompt to structure research sessions.

Track enquiry time by logging every touchpoint in small, consistent time blocks—then totaling it per enquiry and marking the outcome (active/booked/lost/on hold). Use Nowah for itinerary development and flight/hotel research, and record that work alongside calls, checks and revisions in your own log. This gives your process review an observable starting point.
What counts as “enquiry time” (define it once)
Before you track anything, define what you will count so your data stays consistent week to week.
Include the Nowah research session and the review it requires in your records. The itinerary preparation cost guide helps define task boundaries.
Include (typical enquiry work):
- Reading and triaging the request (email/DM/form submission)
- Clarifying questions and client calls
- Trip research and itinerary drafting
- Flight search and comparison (one-way/round-trip/multi-city)
- Hotel search and option shortlisting
- Revising the proposed plan after client feedback
- Preparing booking notes and double-checking traveller details before payment approval
Optional (choose and stick to it):
- Admin tasks directly tied to the enquiry (e.g., creating a file, adding notes to your internal tracker)
- Supplier calls or hold checks (where applicable)
Exclude (to keep the metric clean):
- General marketing, social posting, networking
- Training and supplier webinars
- Broad destination learning not tied to a live enquiry
The goal isn’t perfection; it’s comparability. If you count the same categories each time, your totals become meaningful.
The core challenge: enquiry work is fragmented
Enquiry work rarely happens in one uninterrupted block. You might do:
- 4 minutes to skim a request
- 11 minutes to reply with clarifying questions
- 27 minutes of research between calls
- 18 minutes later that evening to refine routing
If you only track “deep work sessions,” you will undercount. If you try to track every 30-second micro-task, you’ll quit after two days.
A workable system must:
- Capture small blocks without friction.
- Still produce a total per enquiry.
- Record a simple outcome (active/booked/lost/on hold) so the time has context.
Choose one of three tracking methods (and don’t mix them mid-week)
All three methods below can work. Pick the one you can sustain.
Method | How it works | Strength | Risk to watch |
|---|---|---|---|
Timer-based | Start/stop a timer whenever you switch enquiries; assign the time entry to that enquiry. | Most accurate for focused blocks. | Easy to forget stops/starts during interruptions. |
End-of-day log (recommended to start) | At day-end, list each active enquiry and record minutes spent in rounded blocks (e.g., nearest 5). | Low friction; captures “in-between” time. | Estimates can drift unless you use a rounding rule. |
Hybrid | Timer for sessions of at least 15 minutes; end-of-day estimates for quick touches. | Balances accuracy and practicality. | Requires discipline to avoid double-counting. |
Try end-of-day estimates if timers interrupt your work, then compare the entries with your calendar to assess whether the method captures your actual workload.
Your minimal tracking fields (keep it lean)
You only need a few fields to make the log actionable:
- Enquiry ID (use an opaque code instead of unnecessary personal information)
- Enquiry type (e.g., “custom Europe,” “cruise,” “FIT beach,” “flight-only”)
- Date opened / date closed
- Time entries (minutes) as a comma-separated list
- Total time (sum)
- Outcome (active/booked/lost/on hold)
Give the Nowah work a concrete output label, such as hotel-area comparison. The hotel neighbourhood guide helps distinguish that task from general destination browsing.
That’s it. Everything else (budget, destination, lead source) is optional and can be added later if it supports your decisions.
Worked hypothetical example: a 12-day Italy + Switzerland enquiry (170 minutes)
Below is a fully worked example using fictional clients (“Andersons”). The point is not the destination; it’s the structure of the tracking.
For the fictional enquiry, record the Nowah route research separately from proposal presentation. The multi-city proposal method helps identify each stage of the work.
Scenario (hypothetical):
- Two adults
- 12 days, Italy + Switzerland
- Multi-stop routing
- Client wants an itinerary outline plus flight and hotel options
Time log (10 segments):
Date/time (example) | Activity | Minutes |
|---|---|---|
Mon 10:00 | Read enquiry + quick feasibility check (dates, routing, constraints) | 5 |
Mon 11:00 | Initial flight search (multi-city) and note viable time windows | 40 |
Mon 15:00 | Clarification call + notes (call 12, notes 3) | 15 |
Tue 09:00 | Draft day-by-day structure + travel days outline (using Nowah) | 30 |
Tue 10:30 | Refine pacing: reorder stops; add buffer time; align check-in/out logic | 20 |
Tue 14:00 | Hotel search: shortlist options by area, rating, and refundable terms where available | 25 |
Wed 08:00 | Compile proposal in your agency’s usual client-facing document format | 20 |
Wed 08:30 | Send proposal email + record next-step questions | 5 |
Thu 10:00 | Client requests two changes; read and clarify by email | 5 |
Thu 10:15 | Revise plan + refresh pricing/availability checks before presenting update | 5 |
Total tracked time: 170 minutes (2 hours 50 minutes)
Status at this checkpoint: Active; revised proposal sent. The 170 minutes cover enquiry work so far, not a completed booking or its later support. Continue logging if the file progresses.
How to use this later: once you have multiple logs, you can compare time spent by enquiry type and time spent by outcome. Compare like-for-like stages and scope. An active file’s 170 minutes should not be treated as its final delivery effort. Keep the measured sample size visible before drawing conclusions about a trip category.
The copyable spreadsheet template (with a filled example row)
Paste this into a spreadsheet (Google Sheets/Excel) or adapt it to whatever system you already use. The format is deliberately simple.
Client label | Enquiry type | Date opened | Date closed | Time entries (minutes) | Total minutes | Outcome | Notes (optional) |
|---|---|---|---|---|---|---|---|
ENQ-041 (hypothetical) | Custom Europe (12 local days) | Day 1 | Open | 5, 40, 15, 30, 20, 25, 20, 5, 5, 5 | 170 | Active | Revised proposal; booking work not yet logged |
Rules that make this template work in real life:
- Rounding rule: use actual minutes or a consistent estimate. Repeatedly rounding every short touch upward can inflate the total; combine brief touches and avoid counting the same work twice.
- One enquiry = one row: all time entries for that enquiry stay in one place.
- Log today’s minutes today: end-of-day is fine, but don’t wait until Friday.
- Outcome required: even “lost” or “no response” is an outcome—otherwise you can’t interpret the totals.
If you want one extra column, add Stage (New / Researching / Proposal sent / Revision / Booking). That helps you see where time clusters without changing what you’re measuring.
Making tracking easier by structuring research sessions with Nowah
Nowah is a conversational travel planning and booking product on web, iOS, and Android. It supports conversational trip research, editable day itineraries with map/timeline views, flight search (one-way, round-trip, multi-city), hotel search and booking, and travel eSIM purchasing (see /features for the current capability list). You still track time in your own log, but Nowah can help you bundle research into clearer sessions—which makes your time entries more natural (“30 minutes: itinerary framework in Nowah” instead of five scattered micro-entries across tabs).
Copyable Nowah planning prompt (structured, verification-friendly)
Use a prompt like this to produce a working framework you can then verify and refine.
Prompt (copy/paste):
“You are assisting with a travel enquiry. Build an editable 12-day itinerary framework for two adults traveling Italy + Switzerland.
Constraints:
- For this conceptual exercise use 12 local days and 11 hotel nights across five stops (2/2/3/2/2 nights). Test whether the travel burden fits moderate pacing; offer fewer bases if needed. Ask for real dates and places before claiming journey times.
- Keep pacing moderate: no more than 2 major planned items per day.
- For each stop, specify: suggested base neighbourhood/area to stay (not a specific hotel), check-in/check-out logic, and a morning/afternoon/evening structure.
- Add a shortlist workflow for accommodations: run a hotel search per stop and list 3–5 options from search results that match filters (4-star, central, refundable if possible, target under €300/night), with the key differentiators to compare.
- Add a flight search plan: propose 2–3 multi-city routing patterns and what to compare (departure times, total duration, number of connections).
- Flag any items that require schedule/seasonality verification (rail, ferries, local transport, attraction days/hours) without asserting exact operating times.
Output:
1) Day-by-day outline
2) Accommodation shortlists by stop
3) Flight routing comparison checklist
4) A ‘verification to-do list’ for the adviser.”
Review the concepts before pricing the itinerary. Match room quantities, actual dates, inclusions and conditions to the agreed brief, and keep unresolved requirements visible.
What you, the adviser, should check after Nowah generates the draft
Nowah can accelerate the structuring of an itinerary and consolidate flight/hotel searches, but you remain responsible for validating what you present.
Use this quick review rubric (copyable):
- Routing sanity: Are travel days placed where they reduce backtracking? Are there too many one-night stays?
- Time realism: Do travel segments leave enough time for check-in/check-out and transfers?
- Search filters: Did you apply the agreed parameters (rating/area/terms/budget) consistently across stops?
- Availability and terms: Re-check that the shortlisted flight and hotel options are actually available at the time you’re ready to propose and that supplier terms match what your client expects.
- Verification list completeness: Does it flag schedule/seasonality checks without stating specifics as facts?
Start with one week of consistent entries
If you do nothing else, implement the spreadsheet template above and track one week of enquiries using consistent rounding and outcomes. Review the entries for fragmented work and missing stages before drawing conclusions from a small sample.
For the research and itinerary-structuring portion, Nowah can help you consolidate work into clearer sessions—conversational trip research, editable day itineraries with map/timeline views, flight search (including multi-city), and hotel search/booking are built into the product (see /features). Use the copyable prompt, review the output with the rubric, and log the minutes you spend.
Get started with Nowah here: Open Nowah




