I need an executable logistics plan for [PROJECT OR EVENT], taking place at [LOCATION AND DATES]. The goal and success criteria are [GOAL AND SUCCESS CRITERIA]. Available people, suppliers, vehicles, inventory, or systems are [RESOURCES AND OWNERS]. Constraints and known risks are [CONSTRAINTS AND RISKS]. Ask up to 3 clarifying questions only if a required input is missing. Otherwise produce a plan that a coordinator can run without translating vague advice into tasks. Output these sections: 1. Assumptions and scope: state what is included, excluded, and unconfirmed.
2. A workback schedule from final delivery or closeout to launch, with task, accountable owner, due date or relative deadline, dependency, and proof of completion. Use RACI only when multiple roles genuinely share a decision. 3. An operations-day run sheet ordered by time, including arrival windows, loading or receiving, setup, checkpoints, communications, handoffs, and closeout. 4. A materials and movement plan: item, quantity, source, destination, transport method, custodian, and return or disposal action. 5. A risk register covering likelihood, impact, early warning, prevention, contingency, decision owner, and the last responsible time to act. Include realistic cases such as late delivery, weather or access restriction, absence, damaged goods, capacity shortfall, and communication failure where relevant. 6. A concise escalation protocol: which channel to use, who can approve changes, and what facts to report. Do not invent permits, vendor commitments, inventory, capacity, costs, or legal requirements. Before answering, check that every critical task has one accountable owner and that no task is scheduled before its dependencies can be complete.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROJECT OR EVENT] | Name the work to be planned and state its main deliverable. | Move 180 attendee welcome kits from our office to a one-day customer conference. |
| [LOCATION AND DATES] | Provide all relevant places, dates, operating hours, and time zones. | Warehouse in Newark to The Westin Jersey City; event is Thursday, October 15, 8 a.m.–5 p.m. ET. |
| [GOAL AND SUCCESS CRITERIA] | State what must happen and the measurable conditions for success. | Every checked-in attendee receives one complete kit by 10 a.m.; leftover kits return to the warehouse Friday. |
| [RESOURCES AND OWNERS] | List people, vendors, equipment, transport, stock, budgets, and the person responsible for each. | Maya owns event operations; Luis owns warehouse count; 200 kits, one rented cargo van, hotel loading dock booked 6–7 a.m. |
| [CONSTRAINTS AND RISKS] | List deadlines, access limits, dependencies, compliance needs, and known risks. | No storage in the lobby, freight elevator required after 7 a.m., rain possible, two kit items arrive Tuesday. |
How to use
- Paste the prompt with dates, locations, named owners, and resource counts from the actual job.
- Check the workback schedule for missing approvals, lead times, and tasks with no single owner.
- Share the run sheet with each owner and confirm their arrival window and proof-of-completion method.
- Follow up with: “Convert the operations-day run sheet into a Slack-ready update schedule with exact messages.”
Variations
Vendor coordination
Use this when several suppliers must deliver into one operation.
Create a vendor coordination plan for [PROJECT], involving [VENDOR LIST] at [LOCATION AND DATE]. Deliverables, receiving rules, and contacts are [DELIVERY DETAILS]. Produce a vendor matrix with delivery window, loading instructions, receiving owner, required paperwork, acceptance check, payment or signoff trigger, and backup contact. Add a timeline of confirmation messages from now through delivery. Flag conflicts in arrival times, dock capacity, insurance, permits, or unclear ownership. Do not invent vendor terms or contact details.
Route and delivery plan
Use this for multi-stop movement of people, stock, or equipment.
Plan a route and delivery schedule for [ITEMS OR PASSENGERS] across [STOPS AND TIME WINDOWS], starting from [ORIGIN]. Vehicles, drivers, capacity limits, and loading requirements are [AVAILABLE RESOURCES]. Output an ordered route table with departure and arrival buffers, load assignment, driver owner, proof of delivery, fuel or charging assumptions, and contingency for delay or vehicle failure. Identify any route that cannot meet its window using the supplied facts. Do not assume travel times or legal driving limits not provided; label them for confirmation.
Launch readiness review
Use this before a rollout to find gaps before the point of no return.
Run a logistics readiness review for [LAUNCH OR EVENT] on [DATE], using these current plans: [CURRENT PLAN]. Stakeholders and hard requirements are [STAKEHOLDERS AND REQUIREMENTS]. Produce a red-amber-green checklist grouped by people, materials, location, technology, communications, and contingency. For every amber or red item, state the missing evidence, accountable owner, decision deadline, and recovery action. Finish with a go or no-go recommendation based only on supplied evidence, not optimism.
Tips
- Use a workback schedule, not only a forward timeline, because vendor lead times and approvals must be complete before dependent tasks can start.
- Name one accountable owner per task even when several people contribute; shared accountability often leaves handoffs unattended.
- Build buffers around receiving, loading, security, and elevators rather than only transit time; those handoffs frequently cause the actual delay.
- Set a decision deadline for each contingency, such as when to dispatch a backup vehicle, so the team does not wait until recovery is impossible.
FAQ
What is the difference between a logistics plan and a project plan?
A project plan covers the broad work. A logistics plan specifies how people, materials, locations, timing, movement, and handoffs work in practice.
Can AI estimate travel times or capacity?
It can help structure assumptions, but verify route times, venue restrictions, vehicle capacity, and staffing with current sources before committing.
How detailed should an operations-day run sheet be?
Detailed enough that each handoff has a time, owner, location, and confirmation method. Avoid tasks such as “handle registration” without those details.