Dhanteras gift dispatch checklist from confirmed orders
An order-by-order dispatch and pickup checklist that makes missing confirmations visible. Paste this prompt into ChatGPT, Gemini, Claude or Grok, change the parts in brackets to suit you, and generate.
- Written for
- ChatGPT, Gemini, Claude, Grok
- Occasion
- Dhanteras · 6 Nov
- Status
- Tested 9 Oct 2026 in Grok, 9 Oct 2026 (one run; model id not exposed)
- Test settings
- The page's exact default prompt was run once in Grok on 9 Oct 2026. The default details already written on the page were the input. They are illustrative, not a record of a real event. ChatGPT and Gemini were not used. The first result was kept.
- Variability
- A different set of details, or another run, will change the wording. This is the first result for the defaults on this page.
Prompt
Create an order-by-order dispatch checklist from my supplied records. Include item verification, packaging requirement as supplied, address confirmation, promised deadline or ?, dispatch owner and tracking status. Flag conflicting or absent details. Do not invent courier cut-offs, packaging certifications or on-time guarantees. Keep customer addresses out of any public-facing summary. My details: Order A: two bowls, box requested, recipient address not confirmed, dispatch target provided by customer: Thursday. Order B: one tray, pickup, slot not confirmed. Use only supplied facts; fictional default details are examples, not a real event. Ask for essential missing input or mark unknowns rather than inventing people, prices, dates, permissions or commitments. Regional and family practices can differ; do not present one practice as a universal rule. Return a private table with one row per order: supplied item/quantity | packaging | fulfilment mode | target date as supplied | confirmation needed | responsible person or ? | current status. Keep pickup orders out of courier dispatch tasks. A customer target is not a seller commitment; keep those fields separate. An unanchored weekday needs an exact date before scheduling, and an unconfirmed address/slot blocks the relevant step. End with blockers in dependency order; no order becomes dispatched merely because the checklist exists.
Customise
Paste the real details. Leave out anything you do not want repeated.
Fields start with illustrative values; replace them with your own facts. The prompt updates as you type. Copy prompt copies your version.
Example output
Actual tested output. The notes used for this result are an example, not a real event. This box is not copied. Replace the notes above with your own before you paste the prompt.
No order is dispatched or collected because this checklist exists. A customer target is not a seller commitment. Courier cut-offs, packaging certifications, and on-time guarantees are not supplied and are not added. Addresses are not written in a public summary. This table is private. Responsible person: unknown for both orders. Private table Order | Supplied item/quantity | Packaging | Fulfilment mode | Target date as supplied | Confirmation needed | Responsible person or ? | Current status A | Two bowls | Box requested by the customer. Seller agreement to that packaging is not stated. | Dispatch is implied by a dispatch target, but the address is missing, so dispatch cannot start. | Thursday, as a customer target only. Weekday is not an exact date. Seller deadline: ? | Recipient address. Which calendar date "Thursday" means. Whether the seller agrees to the box. Who dispatches. | ? | Not dispatched. Blocked. B | One tray | Not supplied | Pickup. Not a courier job. | Slot not confirmed. Target date: ? | Pickup slot. Packaging, if any. Who hands the tray over. | ? | Not picked up. Blocked. Not in the courier task list. Blockers, in dependency order 1. Order A: confirm the recipient address. Dispatch stays blocked without it. 2. Order A: replace "Thursday" with an exact date before anyone schedules it. The customer's Thursday is not a seller promise. 3. Order A: confirm whether the requested box is accepted packaging. 4. Order A: name the dispatch owner. Until then the owner is ?. 5. Order B: confirm the pickup slot. Do not create a courier task for this order. 6. Order B: name the person who will hand over the tray. 7. Only after the matching blockers clear can an order move to "ready". None is dispatched or collected now. Public-facing summary, if one is required Two orders are open. One is waiting on address and date confirmation. One is a pickup waiting on a slot. No customer address is included.
How to use it
- Open ChatGPT, Gemini, Grok or Claude.
- Paste the prompt and replace the [BRACKETS] with your details.
- Review names, facts and the requested format; follow up with corrections or missing details.
How to use this prompt
- Fill Customise with your real details. Do not let the tool guess a missing fact. Write the missing information clearly if you need to.
- Press Copy prompt and paste it into the AI app named above. This page copies the prompt. The answer is created in the external app.
- Check names, facts, numbers, language and the format you asked for. If something is wrong or incomplete, ask for a correction.
Good to know
- Verify addresses, dates and fulfilment commitments privately. A checklist does not dispatch an order or guarantee delivery; keep customer details out of public summaries. Run once in Grok on 9 Oct 2026 using the illustrative defaults on this page. Check the draft against your own facts before you use it.
- Check facts before you rely on the answer.
