Build a copy-paste prompt library for my logistics operation. Operation context: [OPERATION DETAILS] Primary flows and constraints: [FLOWS AND CONSTRAINTS] Current systems and data available: [SYSTEMS AND DATA] Main recurring problems: [RECURRING PROBLEMS] People who will use the prompts: [USERS] Create 10 prompts for the highest-value recurring tasks in this operation. Cover a useful mix of: shipment planning, dispatch handoff, carrier or vendor communication, late-shipment triage, inventory or receiving discrepancies, dock scheduling, customer status updates, freight-cost review, capacity planning, and weekly operating reporting. Replace any task that does not fit my operation with a more relevant one.
For each prompt, provide: 1. A clear task name and the operational decision it supports. 2. A copy-ready prompt with square-bracket inputs a user can fill in. 3. The exact output format required, such as a dispatch table, prioritized exception list, email draft, or action plan. 4. One sentence naming the data needed and one sentence naming what the AI must not assume. Make the prompts practical for a busy coordinator: specify time zone, cutoff times, service commitments, ownership, and escalation thresholds where relevant. For shipment triage, require a ranked list by customer impact, promised date, recoverability, and next owner. For cost analysis, distinguish accessorials, fuel, linehaul, and avoidable versus unavoidable variance. Do not invent rates, transit times, inventory, capacity, or delivery status. Before answering, check that every prompt has enough inputs to produce an actionable result and that no prompt delegates a safety, compliance, customs, or hazardous-material decision without directing the user to the responsible qualified person. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [OPERATION DETAILS] | Describe your business, locations, shipping modes, order volume, and customer commitments. | Regional furniture distributor; two warehouses in Ohio and Pennsylvania; 180 LTL and parcel shipments weekly; next-business-day retailer updates. |
| [FLOWS AND CONSTRAINTS] | List the inbound, outbound, returns, or transfer flows plus key deadlines and service constraints. | Inbound container drayage to Columbus, warehouse transfers twice weekly, outbound LTL; orders received by 2 p.m. ship same day; appointment deliveries required. |
| [SYSTEMS AND DATA] | Name the TMS, WMS, ERP, spreadsheets, carrier portals, and data fields your team can access. | NetSuite ERP, Manhattan WMS, MercuryGate TMS, carrier tracking portals, and a weekly freight invoice export. |
| [RECURRING PROBLEMS] | List the logistics issues that consume time or create service failures most often. | Missed delivery appointments, short picks, late carrier scans, unexpected accessorials, and unclear ownership of exceptions. |
| [USERS] | State the roles and experience levels of the people who will use these prompts. | Two dispatch coordinators, a warehouse supervisor, and a logistics manager; all use Excel daily. |
How to use
- Paste the core prompt and replace each bracketed field with details from your lanes, systems, and service commitments.
- Keep the prompts that match your work, then test one against a real but non-sensitive exception or shipment list.
- Check that each output names an owner, deadline, source data, and escalation point before your team relies on it.
- Follow up with: “Turn prompt 4 into a one-screen version for dispatchers and include only fields available in [SYSTEM].”
Variations
Late load triage
Use this when several loads are at risk and dispatch needs a recovery queue.
I need to triage late shipments. Shipment data: [SHIPMENT LIST]. Customer commitments: [SERVICE RULES]. Available recovery options: [RECOVERY OPTIONS]. Create a prioritized exception table with shipment ID, promised delivery date, current status, customer impact, recoverability, recommended next action, owner, and deadline. Rank first by imminent customer-service failure, then by recoverability. Draft only the customer updates that need to be sent today. Do not assume a carrier can expedite or that inventory is available. Flag missing tracking events or promised dates before recommending action.
Freight invoice review
Use this to prepare an audit queue from a carrier invoice export.
Review this freight invoice data: [INVOICE DATA]. Contracted rates or routing guide: [RATE RULES]. Shipment reference data: [SHIPMENT RECORDS]. Identify charges needing review. Output a table with invoice number, shipment ID, charge type, billed amount, expected amount or reason it cannot be calculated, discrepancy, likely cause, supporting evidence needed, and dispute deadline. Separate linehaul, fuel, accessorials, taxes, and duplicate charges. Do not label a charge invalid without comparing it to a stated rule or record. Flag any charge that needs a contract or proof-of-delivery check.
Dock schedule plan
Use this before a busy receiving or shipping day.
Create a dock schedule for [DATE]. Appointments and load details: [APPOINTMENT LIST]. Dock doors, labor, equipment, and operating hours: [RESOURCE CONSTRAINTS]. Priorities: [PRIORITY RULES]. Produce a time-block schedule by dock door, with unload or load sequence, expected duration, assigned lead, staging location, and contingency for late arrivals. Identify conflicts, labor peaks, equipment conflicts, and appointments that need confirmation. Preserve required food, temperature, hazmat, or security separation rules in [COMPLIANCE RULES]. Do not create an appointment outside operating hours or assume a load can be double-stacked.
Tips
- Use shipment IDs, promised delivery dates, latest tracking scans, and carrier contact details together; an exception list without those fields cannot drive recovery.
- Set an explicit escalation threshold, such as a missed delivery appointment or a forecasted delay beyond four hours, so the AI does not bury urgent work in a general summary.
- Keep rate cards and carrier agreements out of public AI tools unless your company has approved the tool and data-handling arrangement.
- Ask for a separate “missing evidence” column in invoice and claims work so suspected errors are not treated as proven disputes.
FAQ
Can AI decide which carrier to use?
It can compare options against rates, service requirements, capacity, and lane rules you provide. A qualified operator should still confirm contractual, safety, customs, and hazmat constraints.
What data should I avoid pasting into a logistics prompt?
Follow your company policy for customer addresses, pricing agreements, personal data, security procedures, and regulated shipment details. Use IDs or redacted examples when possible.
How do I keep logistics prompts useful after conditions change?
Store the prompts with their assumptions, then update cutoff times, carrier rules, locations, and system fields whenever the operating model changes.