Proofsheet
Illustrative visual preview for Wedding or event checklist timelineOutput format

Illustrative visual preview. Copy the text prompt or template below; this image is not its tested output.

Chat & workPlanningFamily

Wedding or event checklist timeline

A month-by-month to day-of checklist for your wedding or event, with owners and a vendor tracker. Paste this prompt into ChatGPT, Gemini, Grok or Claude, change the parts in brackets to suit you, and generate.

Written for
ChatGPT, Gemini, Grok, Claude
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 a planning checklist and timeline for my event.
Event: Wedding with haldi, mehendi, sangeet and reception
Date and place: 8 February 2027, Varanasi
Guests: 350
Helpers I can assign tasks to: Me, my brother Rohan, cousin Priya, event planner

Output:
1. Timeline from today to the event, grouped: 6+ months, 3 months, 1 month, 2 weeks, 1 week, day before, the day, after the event. Adjust if the date is sooner.
2. Each task as a checkbox line: "[ ] Task — owner — due". Assign owners from my helpers list.
3. A vendor tracker table: Vendor type | Name | Contact | Quote | Advance paid | Status (leave blanks for me).
4. A day-of running order with times.
5. An emergency kit list (10 items).

Include the rituals or traditions I mention, and don't assume any I haven't. Offer a WhatsApp-friendly version to share with family.

Ask for the current planning date and exact event date/year before assigning calendar deadlines. Keep named owners as proposed until agreement is supplied. A running order needs confirmed start/end times and activity durations; otherwise ask for them instead of inventing bookings. Use fewer timeline phases if the event is nearer, and never schedule a completed planning phase in the past as a future task.

Customise

For example: Wedding with haldi, mehendi, sangeet and reception.

For example: 18 December, community hall.

For example: 40.

For example: Me, my brother Rohan, cousin Priya, event planner.

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.

Event supplied: a wedding in Varanasi on 8 February 2027, about 350 guests. Rituals named: haldi, mehendi, sangeet and reception. No other ritual is added.

The planning date was not supplied, so calendar deadlines are not assigned. Tell me today's date and I will drop any phase that is already over. I will not turn a finished phase into a future task.

Also unanswered, so not invented:
- Are haldi, mehendi, sangeet and reception all on 8 February 2027, or on other dates?
- What is the start time, end time and duration of each? The running order is not written until you send those.

Owners below are proposed only, until that person agrees: Me, brother Rohan, cousin Priya, event planner.

1. Timeline
Each task is a checkbox line: [ ] Task, owner, due. Owners are proposed until they agree.

2. Tasks by phase
Each due date stays unset until the planning date is confirmed.

6+ months before the event (use this group only if that phase is still ahead)
[ ] Fix which of haldi, mehendi, sangeet and reception fall on 8 February 2027 — Me (proposed) — due: not set
[ ] Hold a Varanasi place that can take about 350 guests — event planner (proposed) — due: not set
[ ] Start the guest list toward 350 — Me (proposed) — due: not set
[ ] Ask Rohan and Priya whether they accept the tasks proposed for them — Me (proposed) — due: not set

3 months
[ ] Decide whether food is served at each named event, then arrange it only if yes — event planner (proposed) — due: not set
[ ] Arrange the mehendi artist — Priya (proposed) — due: not set
[ ] List haldi materials and who brings them — Rohan (proposed) — due: not set
[ ] Plan the sangeet music — Priya (proposed) — due: not set
[ ] Note outfits only for the people you already know must have them — Me (proposed) — due: not set

1 month
[ ] Send invitations only with dates you have confirmed — Me (proposed) — due: not set
[ ] Check the guest list against 350 — Rohan (proposed) — due: not set
[ ] Confirm the food plan if you are serving a meal — event planner (proposed) — due: not set
[ ] Reception look, with no extra ceremony added — event planner (proposed) — due: not set

2 weeks
[ ] Give final numbers to whoever is doing food, if a meal was agreed — event planner (proposed) — due: not set
[ ] Try the sangeet music once — Priya (proposed) — due: not set
[ ] Check haldi materials against the list — Rohan (proposed) — due: not set
[ ] Set the mehendi length only after you confirm the duration — Priya (proposed) — due: not set

1 week
[ ] Confirm arrival times for the vendors you have actually booked — event planner (proposed) — due: not set
[ ] Share a family phone list with Rohan and Priya — Me (proposed) — due: not set
[ ] Pack the emergency kit — Rohan (proposed) — due: not set

Day before
[ ] Confirm how you get into the venue on the event date — event planner (proposed) — due: not set
[ ] Lay out the outfits you have — Me (proposed) — due: not set
[ ] Check haldi and mehendi supplies — Priya (proposed) — due: not set

The day (8 February 2027, times not set)
[ ] Run only the named events whose times you have confirmed — event planner (proposed) — due: times not set
[ ] Guest flow for about 350 — Rohan (proposed) — due: times not set
[ ] Keep the kit where the family can reach it — Priya (proposed) — due: times not set

After the event
[ ] List what was paid and what is still open — Me (proposed) — due: not set
[ ] Complete any return a booked vendor requires — event planner (proposed) — due: not set
[ ] Thank Rohan, Priya and the planner for the tasks they actually did — Me (proposed) — due: not set

3. Vendor tracker
Name, contact, quote, advance and status are blank for you to fill.

| Vendor type | Name | Contact | Quote | Advance paid | Status |
| --- | --- | --- | --- | --- | --- |
| Venue, Varanasi, about 350 guests |  |  |  |  |  |
| Food, only if you serve a meal |  |  |  |  |  |
| Mehendi |  |  |  |  |  |
| Haldi materials |  |  |  |  |  |
| Sangeet music or sound |  |  |  |  |  |
| Reception decor |  |  |  |  |  |

4. Day-of running order
Not scheduled. Send the start, end and duration for haldi, mehendi, sangeet and reception. I will not invent bookings or clock times.

5. Emergency kit (10)
- A basic first-aid kit
- Medicines people in the family already use, in their own packs
- Phone chargers and a charged power bank
- Safety pins
- Needle and thread
- A small soap or stain wipe
- Sanitary pads
- Drinking water
- A written list of family numbers, including the planner
- Cash for small on-site payments (no amount is set here)

WhatsApp version to forward

Wedding, Varanasi, 8 February 2027. About 350 guests. Events named: haldi, mehendi, sangeet, reception. No other ritual is on this list.

Proposed helpers only, not yet agreed: Me, Rohan, Priya, event planner.

Please reply with today's date, which events are on 8 February 2027, and the start, end and length of each. No day plan until then.

Open jobs, dates not set: confirm the four events, venue for about 350, guest list, mehendi, haldi materials, sangeet music, and whether food is served.

How to use it

  1. Open ChatGPT, Gemini, Grok or Claude.
  2. Paste the prompt and replace the [BRACKETS] with your details.
  3. Review names, facts and the requested format; follow up with corrections or missing details.
How to use this prompt
  1. Fill Customise with your real details. Do not let the tool guess a missing fact. Write the missing information clearly if you need to.
  2. 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.
  3. Check names, facts, numbers, language and the format you asked for. If something is wrong or incomplete, ask for a correction.

Full guide: Search, Copy, Save and test labels

Good to know

  • Checklists are generic starting points; add family customs and local vendor lead times yourself. 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.

Try next

Related prompts

Wedding or event checklist timeline
Prompt copied