Most regional operators know their total trips per day but not the shape of their hour-by-hour demand curve. That curve — with three or four identifiable peak windows and clear valleys in between in operations handling 150 to 600 daily trips — is the most direct map of when the platform needs drivers and when it can run with lower coverage without degrading the passenger experience. The difference between a day with 280 completed trips and 4-minute wait times and one with the same volume and 12-minute waits is rarely the number of registered drivers: it is how many were active during the hours when demand arrived in clusters. Managing supply distribution by hour of the week — not just by day — is the highest-impact intervention for reducing wait times while simultaneously improving driver income per session hour.

This article is for the operator with 20 to 80 active weekly drivers who wants to understand how to read their hourly demand curve, what shape it takes in typical regional markets, what the difference is between managing drivers by total count versus by time slot, how to communicate demand peaks to activate latent supply without relying on surge pricing as a first resort, and how to use the agent to detect the coverage gaps responsible for the week's longest wait times. Demand does not distribute uniformly across the day: it has peaks and valleys, and that structure is stable enough to anticipate and respond to with planning rather than reaction.

The hourly demand curve: the metric that daily totals hide

The daily trip total is the most visible metric in the dashboard but also the least actionable from a supply management perspective. Knowing that Tuesday had 180 trips says nothing about when they arrived: if they came uniformly across 16 active hours, the operation can handle them with 12 drivers in parallel. If 40% of those trips arrived between 7:00 and 9:30 a.m., the operation needed more drivers in that block and had excess capacity the rest of the day — drivers connected and waiting on requests that weren't coming. The hourly demand distribution — trips per 30 or 60-minute slot — is the metric that makes that concentration visible and actionable.

In cities of 150,000 to 600,000 residents with operations 3 to 24 months old, hourly distribution is rarely uniform. In most regional markets, 35 to 45% of daily trips concentrate in four two-hour blocks. That means an operator who aligns availability with those blocks achieves lower wait times and higher driver income per session hour than one who spreads coverage uniformly across all active hours. Demand asymmetry is not a problem to mitigate: it is an efficiency lever that only works when it is made visible.

How to read your hourly distribution with available data

The agent query to build the hourly curve: 'For the last 21 business days, show me completed trips by one-hour slot from 5:00 a.m. to midnight. Separate weekdays from weekends. For each slot, also show the count of unique active drivers in that hour.' That query yields two curves: the demand curve (trips per hour) and the supply curve (active drivers per hour). The gap between them in each slot is the map of where the system is out of balance and where the week's highest wait times originate.

The first reading of that curve for most operators reveals three conditions per slot. The first: high demand and sufficient supply — the system works, wait times are low. The second: high demand and insufficient supply — the critical point where wait times climb, passengers cancel, and the active driver has their best income-per-hour of the day because the request-to-available-driver ratio is at its highest. The third: low demand and excess supply — drivers waiting on requests that arrive more slowly than their capacity, producing low income and an unproductive session experience. Mapping those three conditions across every hour of the week is the foundation of any availability plan.

The four typical peak windows in regional cities

In cities of 150,000 to 600,000 residents with established mobility operations, Monday-to-Friday demand concentrates in four identifiable windows with distinct operational characteristics. Their exact start and end times vary by city profile and local habits, but the shape — with predictable morning, midday, evening, and a differentiated weekend pattern — holds across most regional markets in Mexico and Central America.

The hourly coverage gap: how to calculate it and what it reveals

The hourly coverage gap is measured by comparing two numbers in each slot: the average occupancy rate — completed trips divided by active drivers in that hour — and the median wait time of requests in that same block. A slot with a high occupancy rate and median wait time above 7 minutes signals supply saturation: more demand than active supply can handle without delay. A slot with low occupancy and 2 to 3-minute wait times signals supply excess: drivers available and waiting on requests that arrive more slowly than their collective capacity. Both conditions carry operational cost, but the first — saturation — produces the visible damage: cancellations and passengers who switch to a competitor.

The hourly gap has predictive value in operations with six or more weeks of data: the same slots that show a deficit this week showed one last week. That means interventions in those slots have predictable outcomes. Increasing availability in the 7:00 to 9:00 a.m. block by 20% can drop median wait time from 11 minutes to 5, improving the completion rate and the experience of the frequent passenger who uses that slot for their daily commute. The driver who shifts to that block also increases their income per hour because the request-to-driver ratio is more favorable than in the excess-supply slots, where the wait between trips is longer.

How to communicate high-demand windows to activate latent supply

A driver who knows that Tuesday between 7:00 and 9:00 a.m. will have a request spike in the northern zone has a concrete signal to plan their session around. One who receives that information as a notification the night before is more likely to connect in that block than one with no advance information. The difference is not about financial incentive — it is about information: a driver who doesn't know when work is concentrated cannot plan their availability optimally, and the operator cannot attribute low peak-hour coverage to lack of motivation when the real problem is lack of signal.

Communicating high-demand windows takes three effective forms in regional operations. The first is the weekly advance summary: at the start of the week, a list of the three or four highest-expected-demand slots with the predominant origin zone and estimated income per active driver. The second is the pre-peak notification: a message 30 to 45 minutes before the window opens with the request forecast and estimated hourly income. The third is the post-peak close: a brief summary showing how many trips were completed, average income per active driver, and how many drivers were available — information each driver can compare against their own session to understand whether they were present during the most productive block of the week.

How the agent maps the distribution and detects coverage gaps

The weekly diagnostic query: 'For the last 14 business days, show me the time slot with the highest median wait time. Does it coincide with the highest request volume slot? How many unique drivers were active in that slot compared to the highest-availability slot of the day? Give me the driver count difference between the most-demanded slot and the peak-supply slot.' That query directly identifies whether the problem is distributional — peak demand and peak availability don't coincide — which is the most common and most actionable scenario, solvable without changing total driver count or fare structure.

To automate driver communication: 'Every Sunday before 8:00 p.m., generate a summary of the three highest-demand expected slots for the coming week based on the last four weeks of history. Include the predominant origin zone for each slot and average income per active driver during those hours over the last 14 days. Send that summary via WhatsApp to drivers who completed more than 20 trips the previous week.' That flow converts the hourly distribution into planning information for the most active drivers — the ones most likely to respond to concrete signals about when and where the platform needs them — without the operator having to draft and send that summary manually each week.

The hourly demand distribution is the most concrete map of when the operation needs supply and when it can run with less coverage without affecting the passenger experience. An operator who knows that distribution — who knows that Tuesday between 7:00 and 9:00 a.m. needs 18 active drivers and that between 10:00 a.m. and noon the operation runs well with 9 — has a supply management tool that no general 'more active drivers' target can replicate. Hourly specificity turns fleet availability from a vague variable into a plan that drivers can understand, anticipate, and execute out of self-interest.

Moving from 'we have X registered drivers and expect them to be there when needed' to 'we know when they're needed and communicate that map in advance' requires two things: reading the hourly curve once to understand the pattern, and sharing that pattern with drivers as planning information rather than as rules. A driver who understands when work is concentrated makes better session decisions out of self-interest. An operator who provides that information before it is needed — rather than reacting with surge pricing once the peak has already arrived — reduces wait times during critical slots with the same driver count, without raising operating costs or management complexity.