Nobody can tell you in advance whether booking early will pay off on your route, but you can find out for yourself with a small log. Note the fare you see each day for one route and date, write down the fare you finally pay, and compare. A dozen entries will not prove a rule, but they show you what your own search behaviour costs or saves.
What should the log record?
- Date you looked.
- Days left before departure.
- Fare shown for the same flight or the same timing band.
- Source: the airline's own page or one comparison site, but keep it the same each time.
- A note on anything unusual, such as a festival weekend, a sale banner or a few seats left.
Check the same route, the same date and the same number of passengers each time, otherwise you are comparing different things.
A made-up 12-day log
Suppose you will fly on 30 January and you check one flight every day for 12 days. These fares are hypothetical.
| Days before departure | Fare seen in ₹ |
|---|---|
| 29 | 5,200 |
| 28 | 5,200 |
| 27 | 5,050 |
| 26 | 4,900 |
| 25 | 4,900 |
| 24 | 5,150 |
| 23 | 5,400 |
| 22 | 5,400 |
| 21 | 5,650 |
| 20 | 5,900 |
| 19 | 5,900 |
| 18 | 6,150 |
What does the log tell me?
In your sheet, put fares in B2:B13 and use =MIN(B2:B13), =MAX(B2:B13) and =AVERAGE(B2:B13). Here the lowest fare is ₹4,900, the highest is ₹6,150 and the average is ₹5,400. The twelve fares add up to ₹64,800, and 64,800 divided by 12 is 5,400.
Say you booked on day 25 at ₹4,900. You paid ₹500 less than the average fare seen, and ₹1,250 less than the highest. You kept logging after booking so you can see what would have happened if you had waited. In this invented example, the fares rose after day 25, so booking was a good call. In real life, a different route can behave differently.
How do I compare what I paid with the average?
- Paid minus average: =D2-AVERAGE(B2:B13), where D2 holds the fare paid.
- Paid minus lowest: =D2-MIN(B2:B13), which shows how far you were from the best fare you saw.
- Days before departure when you booked, to compare with the next trip.
Why one route is not enough
Fares on a busy route around a festival week behave very differently from a quiet midweek flight. Keep a log for each trip, and add a notes column for the reason: Diwali week, school holidays, a long weekend. After three or four trips, you start to see your own pattern and which trips are worth booking early.
What if the fare drops after I book?
That can happen. Whether you can change or cancel at a lower cost depends on the airline's terms for your fare, so check them before deciding.
Keeping your own record
When the booking charge appears on your card or UPI statement, check the amount against the fare you logged. If you import the statement into SpendixAI, you review the rows first and can keep each flight under a travel category. The fare log itself stays in your sheet, because it holds fares you saw, not money you paid.
How many entries are enough?
For one route, a dozen is a fair start. If you fly the same sector every month, a long sheet gives you something to look at. If you fly twice a year, use fewer lines but keep the notes column rich, since the reason for a fare, such as a festival week or a school holiday, matters more than another day of data.
Before the next trip
- Pick the route and date and start the log early.
- Record the fare every day, from the same source.
- Set your own limit: the fare at which you will just book.
- After booking, keep logging for a week and compare.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


