How much history do I need?
One full year of bookings with the date each one was made is enough to start. Two years is better, because one odd year (a big event, a closed road) won't skew the curve as much.
Articles
A simple pickup forecast for car hire: on-the-books, last year's booking curve and a utilisation check, with formulas and a template you can copy.
By the DayRunner team ·
Use a pickup forecast. Take the bookings already on the books for each future week, then divide by the share of final bookings you usually have at that point, based on last year's booking curve. That gives a forecast of hire days per week, which you turn into utilisation and compare with your fleet.
It takes one export from your booking system and three formulas. Here's how.
That's it. No special software. A spreadsheet handles a fleet of a few hundred cars fine.
If last year you had 55% of a week's final hire days booked 30 days out, and this year you have 140 hire days booked 30 days out, the week will probably finish near 140 ÷ 0.55 = 255 hire days.
The 55% comes from your booking curve: how bookings build up over the booking window before pick-up.
For each booking, split it into the days the car is out. A 5-day hire is 5 hire days, spread across the weeks it touches.
For each week last year, work out the share of its final hire days that were booked 90, 60, 30, 14 and 7 days before the week started.
Average those shares by season (peak, shoulder, low), so one odd week doesn't drive it.
For each future week: hire days on the books ÷ the curve share at today's distance out.
Forecast hire days ÷ (cars × 7). Compare with the target for that week.
When each week finishes, compare forecast with actual and log the error.
These numbers are hypothetical. Say you run 40 compacts and SUVs from Christchurch, and it's early November.
Last year's curve for the shoulder season looks like this:
| Days before the week | Share of final hire days already booked |
|---|---|
| 90 | 20% |
| 60 | 34% |
| 30 | 55% |
| 14 | 76% |
| 7 | 88% |
Now your forecast for three weeks:
| Week starting | Days out | Hire days on books | Curve share | Forecast hire days | Capacity (40 × 7) | Forecast utilisation |
|---|---|---|---|---|---|---|
| 8 Dec | 30 | 140 | 55% | 255 | 280 | 91% |
| 15 Dec | 37 | 112 | 50% | 224 | 280 | 80% |
| 22 Dec | 44 | 150 | 45% | 333 | 280 | 119% |
The week of 22 Dec forecasts at 119%. You can't hire out more cars than you have, so that week will sell out early. That's your signal to raise rates now, add a minimum rental length, or bring cars in from another depot.
The week of 15 Dec forecasts at 80%. It's fine but not full. Hold your rates and watch it again next week.
Days out of 37 and 44 sit between the 30 and 60 points in the curve. Interpolate a straight line between them, as above, or add more points to your curve.
Your forecast tells you how full you'll be. The market tells you what others are charging for the same days. You need both.
In the Rate Pulse sweep of 7 Nov 2026, the typical economy car at Christchurch was NZ$160 a day, but by pick-up day it ran from $118 to $203. The three dearest pick-up days were 12 to 14 Nov, in the middle of NZ Cup and Show Week and the Canterbury Anniversary Day holiday on 13 Nov. If your forecast and the market both point up for the same dates, you can raise rates with more confidence. If your forecast is high and the market is flat, you may just have sold too cheap, too early.
One row per week per car type. The formulas use spreadsheet column letters for this layout.
| A Week start | B Car type | C Cars | D Days out | E On the books | F Curve share | G Forecast | H Utilisation | I Actual | J Error % |
|---|---|---|---|---|---|---|---|---|---|
| 8 Dec | Compact | 25 | 30 | 90 | 55% | =E2/F2 | =G2/(C2*7) | =ABS(I2-G2)/I2 |
=E2/F2=G2/(C2*7)=ABS(I2-G2)/I2A curve from last year assumes this year books the same way. It won't, exactly.
Flag these weeks in a notes column and adjust by hand. That's still better than ignoring them.
The method works well for a single depot with a handful of car types. It gets heavy when you have several depots, one-way hires, or more than about ten car types, because the curve per type gets thin.
That's when it's worth automating the export and the maths, so the forecast refreshes every morning without anyone touching it. It's work we do as part of revenue management, alongside the market rates from Rate Pulse. Read the demand forecasting term for the wider picture.
One full year of bookings with the date each one was made is enough to start. Two years is better, because one odd year (a big event, a closed road) won't skew the curve as much.
Ninety days covers most car hire bookings and is far enough to change rates and fleet moves. Further out, the forecast is mostly last year plus your gut.
Measure it with MAPE each week. Get it trending down before you lean on it for big rate moves. See forecast accuracy (MAPE).
No. Rate Pulse shows market rates for the next 14 days, ratings and dates to watch. Forecasting your own demand needs your booking data. That's part of our consulting.
Forecasting, rate management and booking-system integration, scoped to how you run.