wowprompt

Courier delivery performance analysis by partner and region

Compares courier partners on on-time delivery, delay length, failed attempts and return-to-origin rates, broken down by region or pin code band, and says which partner should take which lanes. Use it when delivery complaints rise, before festive volumes, or when a courier contract is up for renewal.

A scorecard table of couriers by region with on-time rate, average delay, failed attempts and RTO rate, a lane allocation table and a list of issues to raise with each partner
The output this prompt produced, unedited.

The prompt

Fill in these first

  • Shipment data: [paste as order ID, courier, origin, destination city or pin code, ship date, promised date, delivered date, attempts, final status]
  • Regions or bands to group by: [e.g. metro, tier 2, tier 3 and rural, or states]
  • Promise you make to customers: [e.g. 3 to 5 days for metros, 7 days elsewhere]
  • Payment mix, if known: [share of cash on delivery orders]
  • Cost per shipment by courier, if known: [rates]
  • Period: [dates]

Task

Score each courier in each region and recommend how to split shipments between them.

Measures

  1. On-time rate: delivered on or before the promised date, as a share of delivered orders.
  2. Average and 90th percentile delay in days for late orders.
  3. First-attempt delivery rate and average attempts.
  4. Return-to-origin rate, split by cash on delivery and prepaid where the data allows.
  5. Cost per delivered order, if rates are given.

Output format

  1. | Courier | Region | Shipments | On-time % | Avg delay | 90th pct delay | First attempt % | RTO % | Cost per delivered order |
  2. The three biggest problems in one line each, with the numbers behind them.
  3. | Region | Recommended courier | Backup courier | Reason |
  4. Questions to raise with each courier, backed by specific lanes and figures.

Rules

  • Do not rank a courier on fewer than 30 shipments in a region; mark it "too few to judge".
  • Count orders with no delivered date as open, not on time.
  • Separate courier delays from late dispatch on our side when ship dates show the parcel left late.
  • Do not invent costs or service levels that are not in the inputs.
courier performance analysisdelivery delay analysislogistics analyticsrto rateshipping partner comparisonlast mile delivery

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity