Skip to main content
RateHighwayVibeLab
My LabGet Started
Menu
Modules/Module detail
In Development
Fleet & Operations
Intermediate

Fleet Pressure Calendar

See where demand is pressing against available fleet, across the whole rental period rather than a single day.

Version
0.1 draft
Maintainer
RH-maintained
Sample data
Sample data planned
Support status
To be defined
Licence status
To be defined

Inputs

What data is required?

  • Fleet count by location and vehicle class, by day
  • Reservations with pickup date, return date, location and vehicle class
  • Planned fleet movements, maintenance and out-of-service days where you have them

Outputs

What does it calculate, display or help you decide?

  • A calendar grid showing committed fleet against available fleet for every day and class
  • The days where pressure crosses a threshold you set
  • The assumptions used, shown next to the result rather than hidden in the code

Build prompt

Select the prompt below and paste it into your AI-assisted editor as a starting point, then change the field names so they match your own export.

Build a calendar view of fleet pressure for a car rental operation. Inputs are two CSVs: fleet with location, vehicle_class, date, units_available; and reservations with reservation_id, location, vehicle_class, pickup_datetime, return_datetime. A reservation occupies a unit on every day from pickup to the day before return, not only on the pickup day. For each location, vehicle class and day, calculate units committed, units available and pressure as committed divided by available. Draw a month grid where each cell shows the date and the pressure value, and let me set the threshold at which a cell is highlighted. Let me filter by location and vehicle class. Show the total number of reservations included and excluded, and list every excluded reservation with its reason. State every assumption on screen, including how same-day returns and cross-location returns are treated.

Sample data

Use synthetic fleet and reservation data. Reservation records can contain personal information, so a learning prototype should never hold real customer detail.

Setup

  1. Start with one location and one vehicle class for a single month.
  2. Confirm by hand that a three day rental occupies three days, not one.
  3. Add the pressure threshold control.
  4. Add location and class filters.
  5. Add planned maintenance and out-of-service days once the base grid is correct.

Dependencies

  • A CSV parser and a date library that handles time zones honestly
  • A grid or table you can style
  • No connection to RateHighway services is required for the first version

Tests

  • Enter a single five day reservation and confirm five days show one unit committed.
  • Enter a reservation that returns the same day and confirm the treatment matches the assumption you stated.
  • Reduce available units for one day and confirm pressure rises only for that day.
  • Enter a reservation that spans a month boundary and confirm both months show it.
  • Confirm excluded reservations are listed rather than dropped.
Operating complication

The part that catches people out

Availability across the full rental period. A vehicle is not free on the pickup day alone. A five day rental removes a unit from the fleet on five consecutive days, and a tool that counts pickups instead of occupied days will understate pressure on exactly the dates you most need to price carefully.

Cross-location returns, planned maintenance and vehicles in transit each change the count again. Decide how you treat them, state it next to the grid, and make it easy to change.

Optional

Optional RME connection

Fleet pressure is one of the signals that informs pricing decisions. Where an operator runs RateMonitor Elite as their pricing foundation, a custom pressure view can sit alongside it as an operational lens. Any supported data connection would need approved interfaces, verified data rights and tenant isolation before it could be used.

Any connection to RateHighway services would require approved interfaces, authorisation, tenant isolation and verified data rights. Nothing about access or availability is approved.

Build it, then check it by hand

Run the prompt, point it at sample data, and verify one row or one date against the source before you trust the whole file.

Open the PlaybookAll modules