Act as an operations analyst helping a logistics company improve the specific workflow below. Build recommendations from the actual operating facts I provide. Do not invent shipment volumes, savings, carrier performance, regulatory requirements, delivery promises, warehouse capacity, or system features. Where evidence is incomplete, state what must be measured or confirmed before changing the process. Inputs: [LOGISTICS WORKFLOW AND OBJECTIVE] [OPERATING DATA AND EXCEPTIONS] [NETWORK, SYSTEMS, AND PARTNERS] [OWNERS AND CONSTRAINTS] [SERVICE TARGETS AND TIMEFRAME] First, map the flow from order or inbound trigger through final handoff, proof of completion, and exception resolution. Identify each handoff, cut-off time, scan or data event, carrier or warehouse dependency, decision owner, and customer communication point. Separate normal flow from exceptions such as address problems, stockouts, missed pickups, damage, delivery failures, returns, and claims. Produce: 1. A current-state operating map and a concise statement of the service problem. 2. A diagnosis table ranking likely causes by evidence, operational impact, and confidence. 3. A prioritized improvement plan covering process, data quality, carrier or warehouse management, systems, and customer communications. For each item, state owner, dependency, expected mechanism of improvement, risk, and acceptance test. 4. A 30/60/90-day rollout plan with a contained pilot before broader deployment where appropriate. 5. A daily and weekly control tower scorecard: on-time performance, cycle time, exception rate, backlog aging, scan compliance, cost per shipment or order where relevant, and one quality or safety guardrail. 6. An exception playbook with trigger, owner, response SLA, customer message decision, recovery action, and escalation path. Do not recommend reducing controls that protect safety, customs, regulated goods, or chain of custody without qualified review. Before answering, check that every proposed action has an accountable owner and measurable operational signal, and flag any recommendation based on missing baseline data. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [LOGISTICS WORKFLOW AND OBJECTIVE] | Describe the logistics workflow and the service, cost, speed, or reliability outcome you need to improve. | Improve outbound fulfillment for an online home-goods retailer so orders placed before the 2 p.m. cut-off ship the same day. |
| [OPERATING DATA AND EXCEPTIONS] | Provide volumes, timing, performance measures, exception types, sample incidents, and known trends. | 1,100 orders per weekday; 78% ship same day versus a 92% target; late orders cluster on Mondays; 9% have inventory-location mismatches; carrier pickup is 5:30 p.m. |
| [NETWORK, SYSTEMS, AND PARTNERS] | List warehouses, carriers, suppliers, regions, order systems, transport systems, and external partners involved. | One warehouse in Columbus, Ohio; Shopify, NetSuite, ShipStation; UPS and FedEx; no weekend warehouse shifts. |
| [OWNERS AND CONSTRAINTS] | Name the roles with responsibility and state budget, staffing, contracts, safety, regulatory, and technical constraints. | Warehouse Manager owns labor plan; Inventory Control Lead owns cycle counts; Operations Director approves process changes; carrier contracts renew in six months. |
| [SERVICE TARGETS AND TIMEFRAME] | State the service-level targets, baselines if known, and deadline or planning horizon. | Reach 92% same-day shipment within 90 days without increasing mis-picks above the current 0.6%. |
How to use
- Paste a real workflow and include the cut-off times, scan events, exception codes, and carrier or warehouse dependencies that shape it.
- Ask the people who own warehouse, transport, customer service, and systems data to validate the current-state map.
- Start with a contained pilot and use the scorecard to compare it against a stated baseline.
- Follow up with: “Write the missed-pickup exception playbook for our operation, including ownership, customer communication thresholds, and escalation timing.”
Variations
Carrier scorecard
Use this to manage carrier performance and prepare a business review.
Create a carrier performance scorecard for [CARRIERS] using [SHIPMENT DATA] for [LANES OR REGIONS] over [TIME PERIOD]. Calculate only metrics supported by the data: tender acceptance, pickup compliance, transit performance, on-time delivery, damage or claim rate, tracking event completeness, exception aging, and cost where supplied. Segment results by lane, service level, and shipment type where possible. Flag data-quality limits, define investigation thresholds, and propose an agenda for a carrier review. Do not infer fault from a single metric. Ask up to 3 questions only if required inputs are missing.
Warehouse SOP
Use this to document a repeatable warehouse process.
Write a warehouse SOP for [WORKFLOW] at [FACILITY] using [CURRENT PROCESS AND SYSTEMS]. Include safety prerequisites, roles, equipment, start-of-shift checks, numbered task steps, required scans, label or inventory checks, quality-control sampling, exceptions, escalation, and end-of-shift reconciliation. Specify what proves each step is complete in [SYSTEM OF RECORD]. Do not create safety rules or equipment instructions absent from approved policy; flag them for the warehouse safety owner. Ask up to 3 questions only if required inputs are missing.
Returns improvement
Use this when returns are slow, costly, or poorly communicated.
Develop a returns-process improvement plan for [PRODUCT TYPE] across [RETURN NETWORK] using [RETURN DATA AND POLICIES]. Map the path from return request to customer resolution, receipt, inspection, disposition, inventory update, and refund or replacement. Analyze avoidable return reasons, transit delays, inspection backlog, disposition recovery, and customer communication gaps. Deliver prioritized actions with owner, baseline, target, pilot, and guardrail for fraud, quality, or safety. Do not change refund, regulated-goods, or disposal rules without authorized review. Ask up to 3 questions only if required inputs are missing.
Tips
- Use event timestamps from order creation, release, pick completion, pack completion, manifest, pickup, and delivery to locate delay; one final delivery metric hides the cause.
- Define exceptions with operational codes and ownership, because free-text notes make recurring causes difficult to measure.
- Check scan compliance separately from on-time delivery; missing scans can make a healthy operation look late and obscure actual exceptions.
- Keep a quality guardrail such as mis-picks, damages, or claims beside any throughput target so faster work does not shift cost downstream.
FAQ
Which logistics metrics should come first?
Start with the metric tied to the stated problem, then add cycle time, exception rate, and a quality guardrail. Segment by facility, lane, carrier, or order type before assuming one system-wide cause.
Can AI identify the root cause from delivery data alone?
It can form hypotheses, but delivery data alone rarely shows whether the failure originated in inventory, picking, carrier pickup, transit, or customer address quality. Add event-level timestamps and exception codes.
Should customer service own delivery exceptions?
Customer service should own communication and customer resolution, while the operational team owns recovery actions and systemic fixes. The exception playbook should make both roles explicit.