Wedding checklist
18-Month Wedding Checklist
Use the long runway to compare venues and high-priority vendors without manufacturing urgency.
Read the guide →Practical wedding planning library
Every guide is built around a distinct planning decision, working method, example, failure pattern, and verification boundary. The library contains 28 guides owned by this domain.
Wedding checklist
Use the long runway to compare venues and high-priority vendors without manufacturing urgency.
Read the guide →Wedding checklist
A 12-month plan works best when the first quarter secures the venue and scarce vendors, the middle months build guest and design systems, and the final quarter shifts to reconciliation.
Read the guide →Wedding checklist
Nine months is enough for a full plan when decisions are made in dependency order and shopping or inspiration does not delay booking.
Read the guide →Wedding checklist
A six-month wedding plan must prioritize availability, legal and venue requirements, guest travel, and contract deadlines over traditional planning sequence.
Read the guide →Wedding checklist
A three-month checklist is a critical-path plan: secure the legal, venue, vendor, guest, payment, and timeline essentials, then cut anything that does not protect the event.
Read the guide →Wedding checklist
One month out, planning should become verification and handoff rather than continued concept development.
Read the guide →Wedding checklist
The wedding-week checklist should protect the final version, confirm handoffs, and prevent new ideas from displacing required operations.
Read the guide →Wedding checklist
Destination planning adds travel, lodging, local vendor, documentation, shipping, and guest-communication dependencies to the normal wedding plan.
Read the guide →Wedding checklist
A backyard wedding is a temporary event site and needs infrastructure planning beyond decor.
Read the guide →Wedding checklist
A micro-wedding reduces guest volume, not the need for clear ceremony, hospitality, payment, and handoff decisions.
Read the guide →Wedding checklist
A courthouse wedding checklist should begin with jurisdiction-specific appointment, license, witness, identification, security, and photography rules.
Read the guide →Wedding checklist
Vendor booking is complete only when scope, price, payment schedule, deliverables, access, cancellation terms, and a responsible contact are recorded.
Read the guide →Wedding checklist
Final payments require a reconciliation against signed agreements and approved changes, not a blind transfer of the invoice total.
Read the guide →Wedding checklist
An emergency plan should identify likely disruptions, decision authority, contacts, supplies, and the threshold for calling a professional or emergency service.
Read the guide →Wedding checklist
The rehearsal dinner should be planned as a separate hosted event with its own guest list, budget, timing, dietary needs, speeches, and transportation.
Read the guide →Wedding checklist
The wedding is not operationally closed until rentals, borrowed items, attire, gifts, vendor balances, gratuities, documents, and personal property are reconciled.
Read the guide →Wedding checklist
A wedding planning binder is useful only when it separates current decisions from inspiration and gives every contract, payment, guest, and handoff record a clear home.
Read the guide →Wedding checklist
A wedding vendor list should show each category, candidate or selected vendor, contact, status, scope, contract, payment dates, insurance or access requirements, and final handoff owner.
Read the guide →Wedding checklist
A wedding planning timeline is a dependency order rather than a calendar, because each locked decision is what makes the next one answerable.
Read the guide →Wedding checklist
A bridal shower is somebody else's hosted event, so the checklist has to settle decision rights and who is paying before it settles anything about the party itself.
Read the guide →Wedding checklist
A wedding emergency kit should be packed by failure mode rather than by product category, and split into two bags because the getting-ready room and the venue need different things.
Read the guide →Wedding checklist
A day-of coordinator can only run what has been handed over, so the checklist is really a handover packet plus a written statement of what they are authorised to decide alone.
Read the guide →Wedding checklist
A rehearsal dinner timeline should be anchored to the moment the ceremony rehearsal actually ends, because that is the variable everything else inherits.
Read the guide →Wedding checklist
A venue is a set of constraints before it is a look, and capacity, access, curfew, vendor rules, and the weather fallback decide more about the day than the photographs do.
Read the guide →Wedding checklist
Accessibility is a design input rather than a late accommodation, because routes, seating, sightlines, sound, and dietary needs all constrain decisions that lock early in planning.
Read the guide →Wedding checklist
An elopement removes guests and production but not legal requirements, because the licence, the officiant's authority, and the witness rules still decide whether the marriage is valid.
Read the guide →Wedding checklist
A rain plan is only real when the trigger, the backup space, the decision-maker, and the decision deadline have all been settled before the day itself.
Read the guide →Wedding checklist
Attire is governed by lead times that are set by other people, because the order window, the alteration schedule, and the final fitting each depend on a supplier's calendar rather than yours.
Read the guide →Use the working tool
These guides explain the decisions. Wedding Checklist PDF provides the editable files, checks, and handoff structure needed to carry them out.
Review Wedding Checklist PDF — $9