Peak-capacity and seasonal planning

We put the Ramadan, Eid, national day, White Friday and summer peaks on one calendar and plan the capacity each one needs: extra riders and vehicles, the partners called on, the slots restricted, what the customer pays and when each decision is taken.

Each peak ends with a review that updates the next plan.

• A peak calendar with the expected volumes for each peak.
• A surge capacity plan with rider, vehicle and partner numbers by date and hour.
• Pre-agreed surge terms with partners, with prices and reserved volumes.
• A peak-day control plan: who decides what, when to limit slots, when to raise fees.
• A post-peak review that sets cost, revenue and service against the plan.

• Orders served on peak days are set against orders demanded.
• Extra cost per peak order is known before the peak and after it.
• Surge capacity is secured by agreement ahead of the peak.
• On-time delivery on the peak day is read beside a normal day.
• Your board sees the peak volume forecast scored for accuracy after every peak.

Peaks are known and still handled as emergencies. Surge riders are hired at the last moment at high rates, partners are called without agreed terms, service fails on the days that matter most and the extra cost is not tied back to the extra revenue.

• Ramadan evenings or an Eid week overwhelm dispatch every year.
• Surge pay is decided on the day.
• Partners decline calls during the shared peak because no capacity was reserved.
• Promotions drive volume the network cannot serve.
• Nobody can state the cost of last year's peak.

Grocery, restaurant, retail and e-commerce groups, courier and 3PL operators, and boards of delivery businesses whose year turns on a small number of very busy days in the Gulf.

Qasim Abbas spent group finance years in Dubai and Abu Dhabi and years in Doha working with grocery, quick commerce and family groups, where the calendar sets the load. He treats each peak as a capital request with a payback.

We work from last year's peak costs and your dispatch platform's scheduling. See how fees work.

Should we staff for the highest peak?

Staff for the ordinary peaks and buy the rest as surge. Capacity for a handful of days costs the other three hundred and sixty, so the plan balances surge, partner capacity and restricted slots.

Do summer months need a separate plan?

Yes. Heat changes the hours riders can work and the demand pattern through the day, and the shift design takes that into account.

Can we limit service rather than add capacity?

Yes. The plan prices restricting slots, raising fees and pausing remote zones against margin and service, and sets the trigger for each.

Call at least eight weeks before your next major peak. We go through last year's peak with you and mark where the money went.