What's booked in placement, and where does each booking stand?
FIT (tailormade), GIT and series
Share of bookingsShare of hotel room nights
By product
Bookings by status · click a product to show only it
By month of service
Placement statuses
How is every branch doing, and which ones need help this week?
Still open this week
Every branch
Sorted by what's still open this week · click a column to sort, a branch to open it
Choose a branch
Pick one with the branch filter at the top, or start with one of the busiest:
Next 14 days
Services per day, by status
By product
Services dated in the period
Cities served
Services in the period
To act on
Choose a branch
Pick one with the branch filter at the top, or start with one of the busiest:
Notice the branch gets
Median days from handover to the service, by month of service
Load ahead
Who does the work
XOs not issued
How much do our branches earn on the work they handle, and from which vendors?
By branch
Services dated in the period · highest margin first · click a column to sort
Branch margin by month
Month of service, a year back to three months ahead
Transport: own fleet vs outside vendors
Share of vendor spendShare of branch margin
Show as a table
By product
Branch margin per product · margin % of vendor spend
Show as a table
Vendors
How do branches make money, and how does this dashboard count it?
The short version
Every ground service a branch handles (a transfer, a jeep safari, a guide day) has one cost, split in two:
what the vendor gets and what the branch keeps. The branch's share is its profit on that service.
When a service goes through a branch, the system issues two exchange orders (XOs) at the same moment: one to the
branch (for example TCI-Agra) and one to the vendor (for example Travel Bureau - Agra).
Both XOs point at the same cost. The branch doesn't bill a second, bigger amount; its share is recorded on the cost itself and paid
to it separately. On every service paid so far, the amount paid to the branch equals the recorded branch share exactly.
Own offices and associate offices
Own offices are our branches, named "TCI-‹city›" in the XO system (TCI-New Delhi, TCI-Agra, TCI-Jaipur…).
They earn the branch share.
Associate offices are outside agencies that cover smaller places for us (Ranthambhore Nature Tour, Travel Bureau
Khajuraho, Route49 Adventures…). They're paid like vendors and earn no branch share.
"TCI-Agra" is therefore the Agra branch, not a transport company.
Where branches earn, and where they don't
Activities, transport and guides carry a branch share. Typical rates are 10–50% of the vendor's share,
and they're set vendor by vendor: some vendors carry one on nearly every service, most never do.
Meet & greet and monuments never carry one; the branch delivers them at cost.
Hotels, flights, trains and meals never go through a branch.
Fewer than one in five ground services carry a branch share (about a third of activities, transport and guides).
A branch with little profit isn't necessarily doing badly: it may mostly handle work that carries none.
Our own fleet
Some transport is done with our own vehicles. In the XO system those show up as vendors named "TCI Fleet - Varanasi",
"TCI-Delhi", "TCI Goa Fleet", "TCI-Jaipur Fleet" and so on. Every other transport vendor is an outside operator.
Vendors called "… INDIRECT SUPPLIER" (for example TCI-SHIMLA INDIRECT SUPPLIER) are treated as outside operators.
Not counted yet: what our own fleet costs to run (fuel, drivers, upkeep) is in SAP, not in the XO system.
The own-fleet margin shown here is the branch share only, not the fleet's full profit.
How the numbers are counted
One cost per service. When a service is rebooked, the XO system keeps the old cost records. The dashboard uses
the one for the current booking (exactly one for 99.7% of services).
Period = the date of the service, from 1 Oct 2025. Cancelled and declined services are left out.
Rupees only. Branch shares only exist in INR; the few services costed in USD, EUR or JPY are left out.
Paid vs not yet paid. "Paid" is what has actually gone to the branch. "Not yet paid" is recorded but not
paid: usually services still ahead, or past ones whose payment hasn't been made.
FIT (tailormade), GIT and Series come from placement's own classification of the file, as on every other page.
The data is refreshed every night from the XO system and placement.
Still to confirm with the business
Is the own-fleet list right: every vendor named "TCI Fleet…" or "TCI-‹city›", and nothing else?
Why does New Delhi, the busiest branch, earn almost no branch share? Is it run as head office?
Can we get own-fleet running costs from SAP, so own-fleet profit can be shown in full?
About 24,000 branch XOs have no office name: which branch do they belong to?
Some branch shares were paid on a cost record from before the service was rebooked, as well as on the current one
(Varanasi, last 12 months: 125 services, ₹1.15 lakh). Were those paid twice? This dashboard counts only the current booking.
How many bookings are travelling each day, with how many travellers, and how many hotel stays begin?
Each day: bookings on tour · travellers · hotel check-ins
MonTueWedThuFriSatSun
What do we have to chase, and with whom?
Who is completing files properly, and how fast are bookings placed?
Time to request, by product
From the file reaching placement to the request or handover
Request to confirmation
Median, where a confirmation is logged
Busiest handlers
Most bookings · click a bar
Lowest completion
Every handler
Which files starting soon aren't ready to operate?
Files
By month of service
Bookings, confirmed and not yet confirmed, from Oct 2025 to six months ahead
Choose a supplier
Use the picker at the top, or start with one of the busiest in this period:
Coming up
By month of service
Confirmed and not yet confirmed
Who books it
Bookings in the period
What's booked
Bookings in the period
Where
Bookings in the period, by city
Where do our guests stay, and how do they move between cities?
Guest flow
Most travelled legs
Latest files
Bookings
The journey
The booking
Booked cost by product
Net rates booked in placement, this file only
Incidents
Supplier payments
Main file and extensions
One booking: the same first 13 characters of the code
Where do we make our margin, and where do we lose it?
What's on the books for the coming months, in placement and in upcoming queries?
By month of travel
Forecast: not shown yet. It will appear here once the forecast is provided.
Picked up each week
Sent to placement, any travel date
By market, next six months
How many guests do we look after, from which markets, and when do they arrive?
FIT (tailormade), GIT and series
Averages are per tour type · click one to show only it
Arrivals by week
Guests arriving; weeks ahead hold what's booked so far
Where they arrive
City of the first service
By market
Guests arriving in the period
How far ahead does each market book, and when do they travel?
How far ahead
Booking curve
Share of a month's trips already confirmed, by days before travel.
When each market travels
Guests by month of travel, as a share of the market's own total
By market
Files sent to placement, trip starting in the period
How much do we depend on a few customers, and who is drifting away?
How concentrated revenue is
Customers ranked by revenue
Reliance on one customer
Share of each market's revenue from its biggest customer
Are the biggest customers still asking?
Queries created per month · top 15 by revenue in the period
What goes wrong on trips, how serious is it, and with which suppliers?
What went wrong
Incidents by kind of problem: click one to show only it
By month
Incidents by the month they happened, by how serious
How serious
The worst any report on it says
Whose lapse
Who caused it, as the report reads
What was done
Incidents where each step was taken
By supplier
The hotel, transporter, guide or venue on the service: most incidents first
Incidents
Newest first, in the reporter's own words
What do we lose to changes and cancellations, and with whom?
Re-sent after placement
New versions sent to placement after the first, per file
Hotel cancellations by notice
Room nights, by days before check-in
Cancelled services
By product, services dated in the period
By customer
Most rework and cancellations first
Top 10 by queries
Queries created in the period
Top 5 by revenue
Booked in the period, ex-tax
Top 5 by conversion
Quarter on quarter
Top 5 growing
Top 5 declining
Asks a lot, books little
Each dot is a customer
Demand ahead
By travel month · next 12 months
Every query travelling in each month, whenever it was created. Quiet queries are left out.
Queries created in the period · revenue booked in the period
Scoreboard
Each step credited to whoever held the query then
▲▼ marks values far from the team median (half or 1.5× and beyond). Click a name for their view.
Who creates queries
Queries created in this period, and how they turned out
Open queue
Top customers
Quoted or placed by them in this period
Backlog
Not urgent · worth a clean-up
Travart has no "lost" status yet, so abandoned queries stay open and collect here.
Changes compare with the previous period at the same age: those queries are counted as they stood one period ago, so recent queries aren't penalised for having had less time.
From query to placement
Queries created in this period
How far each query has got so far. Percentages are of queries created.
Where these queries are now
Recent queries are still moving, so conversion for the latest days rises over time.
Queries created and sent to placement
By date created
Time between steps
Median and slowest 10%
By query type
By source market
Top customers
By queries created
Account
Name
Email
Appearance
Change password
Data source
Source
Cache
Results are cached for up to an hour
Refresh
Reloaded from Travart and placement every night at 23:00 IST