2026-10-18 · Monthly Plan

How Should a Shanghai Company Build a Monthly Vehicle Plan? Demand Consolidation, Forecasting and Reserved Capacity

In most companies corporate vehicles are requested by whoever remembers, and administration spends the day between taking orders and hunting for cars, paying a premium in busy weeks. What is missing is a single sheet: roughly how many vehicles next month, when, for how many days, which parts are fixed and which are only possible. Companies that plan monthly discover two things. Predictable use accounts for well over half of the total and genuinely unforeseen demand for less than a third, and if the predictable part is locked early the pressure from the rest halves. A monthly plan does not turn administration into a control tower; it replaces guesswork with arithmetic: group by type, forecast by rhythm, reserve by priority. The framework below is general, while the ratios, lead times and approval route need to fit your own business cycle.

1. What the Plan Buys

Q1: What does a monthly plan actually buy?

Three things. Cost stability: vehicles booked ahead run at the agreed rate, while short-notice sourcing is priced at whatever the market offers that day, and the gap widens in peak weeks; more usefully, knowing which week is tight allows itineraries to move rather than the cost to be absorbed. Supply certainty: fleets tighten in busy periods, and a company that declared its demand early gets the right vehicle and a familiar driver, while a late request takes whatever is left. Internal coordination: departments work to one deadline on one sheet, so conflicts surface before the day rather than at eight in the morning when two bookings collide. The cost of not planning is equally concrete. Administration spends its time mediating, business units treat transport as a matter of luck, and the year-end review cannot explain why spend was high. Two hours a month buys a month of certainty.

2. Grouping and Forecasting Demand

Q2: How should demand be grouped?

Four groups, because their certainty differs completely. Fixed demand: the employee shuttle and any long-term full-vehicle arrangement for executives, daily and on set routes, locked monthly. Cyclical demand: pickups for the weekly meeting, client visits on fixed dates, travel around the monthly close, which can be scheduled by week. Project demand: exhibitions, annual conferences, audits, office moves, training cohorts, dated but concentrated into a few days, raised as projects and scheduled separately. Ad-hoc demand: an unexpected client visit, emergency repairs, a sudden trip, unpredictable but governable through rules on notice, approval and access to standby capacity. The consolidation sheet needs six columns only: department, purpose, date and time window, headcount and luggage, origin and destination, grade. Separating the four groups usually reveals that the chaos was four different kinds of demand competing on one list.

Q3: How should demand be forecast without guessing?

Layer three sources. History: trip counts and vehicle-days over the past three to six months, distributed by week, show the base load and the range of variation, and a maintained ledger shows which weeks are consistently tight. Business rhythm: month-end close, quarter-end push, exhibition season, recruitment season, annual audit, and the weeks around public holidays are predictable peaks that belong on a calendar rather than in an average. Known events: confirmed client visits, commissioning, relocation and training go straight in. Layer them into a range rather than a number, for example 120 to 140 vehicle-days next month with the third week tightest. The upper bound drives reservation, the lower bound drives base scheduling. The forecast does not need to be right to the vehicle; it needs to answer which week is tight and how tight, and that is enough to change decisions.

3. Full-Vehicle Work and Reserved Capacity

Q4: When is a full-vehicle arrangement better than per-trip booking?

Three questions decide it. Will the day involve several stops? Multi-stop itineraries booked per trip accumulate waiting and empty running, while a full-vehicle arrangement is transparent. Does the vehicle need to stand by? For conferences, exhibitions and multi-day hosting, a vehicle present matters more than a vehicle on call, and there the arrangement is the only workable form. How continuous is the corporate transport work? Three days or more, the same people, the same district, rewards a driver who knows the route and the passengers. Conversely, a single return journey of predictable length with no waiting is usually cheaper per trip. One caution: a full-vehicle arrangement is not automatically better because it covers a whole day; if the vehicle is used for two hours, per-trip is right. The monthly plan should list the two separately, with full-vehicle work locked monthly and settled by day, and per-trip work consolidated weekly and ordered as needed. The cost structure and the boundaries of responsibility both become clearer.

Q5: How much capacity should be reserved?

Reserve in two dimensions. Quantity: take the upper end of the forecast, subtract what is already committed, and hold part of the gap as standby, for example ten to fifteen per cent of the expected peak, a ratio that three months will calibrate better than any estimate. Time: peak vehicles and drivers need locking early, ordinary periods three days ahead, and exhibition season, the days before public holidays and month-end close one to two weeks ahead. Reservation also needs a release mechanism: capacity still unused two or three days before should be handed back, otherwise the provider charges for the hold or stops offering it next time. Finally, reservation is not administration working alone; agree the reservation window and release rule with the provider, put it in the contract appendix, and both sides work to the same timetable.

4. Closing the Loop with Execution

Q6: How do the plan and day-to-day execution stay connected?

Four habits. Roll weekly: the monthly plan sets the frame, and fifteen minutes every Monday updates additions, cancellations and date changes, so the plan does not end up in a drawer. Record deviations: note a line of reason for each ad-hoc vehicle, cancellation or grade change, and after a month the pattern shows whether the unpredictability is inherent or simply late requests. Review monthly against three numbers: plan accuracy, the share of ad-hoc demand, and the utilisation of reserved capacity. Low accuracy with a low ad-hoc share means the forecasting method needs work; a high ad-hoc share means the request rules need tightening. And feed the conclusions back into the next plan, deciding what can be fixed, which peaks to lock earlier and which ratios to adjust. After three cycles the plan stops being a sheet and becomes a mechanism that corrects itself.