Operations guide

Wedding Planner Client Offboarding Checklist After the Wedding

A step-by-step offboarding checklist for wedding planners covering final files, payments, vendor notes, feedback, and archiving.

7 min readReviewed August 20, 2026Juno product & planning team

The short answer

Closing out a wedding properly means finalizing files, settling payments and returns, logging vendor notes, sending a closeout communication, collecting feedback, confirming permissions, archiving records, and running a short team retrospective. A consistent checklist protects your business records and keeps client relationships intact after the event ends.

What files need to be finalized before closing a client file?

Before you mark a wedding closed, every working document needs to reflect what actually happened, not just what was planned. This means updating the final timeline, floor plan, vendor list, and budget to match the day-of reality. A client file with outdated planning drafts is not a closed file.

Treat the finalization step as a reconciliation exercise. Compare your planning documents against your day-of notes and any last-minute changes, then update the master copies so anyone who opens the file later sees accurate history. This matters if a client returns for a vow renewal, refers a friend, or if a vendor dispute surfaces months later and you need to show what was actually agreed to and delivered.

Update the timeline to reflect actual event-day timing and changes
Save the final floor plan and layout as executed, not as drafted
Reconcile the budget against final invoices and last-minute additions
Confirm the vendor contact list matches who actually worked the event
Label all documents as final versions to prevent draft confusion later

How should outstanding payments and returns be tracked and closed out?

Every wedding closeout needs a single owner who confirms all money and physical items have moved in the right direction before the file is marked complete. This includes final client payments, vendor payouts, deposit returns, and any rented or borrowed items. Leaving this loose creates awkward follow-up conversations weeks after the event.

Build a short closeout ledger for each wedding that lists every outstanding item by name, amount or description, and status. Assign one person, usually the lead planner or a designated admin role, to confirm each line before the file closes. This is not a substitute for your accounting system; it is a simple checklist that flags anything unresolved so nothing gets forgotten once the event excitement fades.

Confirm the final client invoice has been paid in full or noted as pending
Verify vendor final payments and any balance-due invoices are settled
Track return of security deposits owed back to the client or venue
Log any borrowed decor, signage, or equipment that needs to be returned
Note who owns each unresolved item and the date it needs to close

What vendor notes should be captured before the file is archived?

Vendor performance notes are only useful if you capture them right after the wedding, while details are fresh, rather than relying on memory during your next booking cycle. Record what worked, what caused friction, and whether you would recommend the vendor again. These notes become a reference for future client matching and vendor relationship decisions.

Keep vendor notes factual and specific rather than general impressions. Note timing issues, communication responsiveness, quality of delivered work, and any problems that required your intervention. This record should live wherever you already track vendor relationships so it is visible the next time that vendor comes up for a different client, not buried in a single wedding's file where no one will find it again.

Record whether each vendor met agreed timing and delivery commitments
Note any communication issues or last-minute changes vendors introduced
Flag vendors you would confidently rebook for a similar client profile
Document any complaints or concerns raised by the client about a vendor
Update your internal vendor reference notes, not just the wedding file

What should the final client communication include?

The closing message to a client should thank them, confirm the engagement has formally ended, and set expectations for any remaining items like final photos or reviews. Keep it warm but clear about what happens next and by when. This message also doubles as your natural opening to request feedback.

Send this communication within a week or two of the wedding, while the experience is still fresh for the client. Avoid leaving it open-ended; state clearly if there is nothing further expected from either side, or specify the one or two items still pending, such as a final album delivery timeline or a pending refund. Ambiguity here is what generates confused follow-up emails later.

Thank the client and acknowledge the engagement is now complete
List any remaining deliverables and their expected delivery timeframe
Invite the client to share feedback or a testimonial if comfortable
State clearly that no further action is needed if that is true
Offer a way to reach you for referrals or future events

How should client feedback and permissions be handled?

Ask for feedback directly and separately from any permission request, since combining the two can make clients hesitant to answer honestly. Feedback should be collected consistently across every wedding, not only when you expect praise. Permissions for photos, testimonials, or portfolio use need explicit, recorded consent, not assumed agreement.

Use the same short feedback request for every client so responses are comparable over time. Keep the questions simple and focused on the planning process itself. Separately, if you want to use wedding photos, quotes, or the couple's names in marketing, ask directly and keep a written record of what they agreed to and any restrictions, such as no last names or no specific vendor tags.

Send a short, consistent feedback request to every client after the wedding
Ask what worked well and what could have gone more smoothly
Request explicit written permission before using photos or quotes publicly
Record any restrictions the client places on how their story is shared
Store permission records separately so they are easy to find later

What does a proper archive and retention process look like?

Archiving means moving the closed file to a clearly labeled inactive status while keeping it accessible in case questions arise later. Decide in advance how long you retain contracts, communications, and financial records, and apply that rule consistently. Do not delete client files immediately after closing; give yourself a defined retention window instead.

Set a retention period that fits your own recordkeeping needs rather than guessing case by case. Many planners keep contracts and financial records for several years and communication logs for a shorter window, but the exact period is a business decision you should make deliberately and document in your own procedures, not something to leave unwritten. Consistency matters more than the specific number you choose.

Mark the client file as archived or inactive in your system
Apply a consistent retention period for contracts and financial records
Keep communication logs accessible for a defined, documented period
Restrict archived files from showing in active client dashboards
Review your retention policy periodically to confirm it still fits

Why does the team need a retrospective after every wedding?

A short retrospective captures lessons while they are still useful, rather than losing them to memory before the next event. Include everyone who touched the wedding, from lead planner to assistants and vendor coordinators. The goal is specific, actionable notes for your standard operating procedures, not a general debrief.

Schedule the retrospective within a week or two of the wedding closing, before details fade. Keep it structured around three questions: what worked, what caused avoidable stress, and what should change in your process going forward. Assign an owner to actually update your procedures or templates based on the discussion, otherwise the retrospective becomes a conversation that changes nothing.

Schedule the retrospective within one to two weeks of the wedding
Include everyone on the team who worked the event directly
Ask what worked well and what created avoidable last-minute stress
Identify one specific process change to test on the next wedding
Assign an owner to update templates or procedures based on findings

Common questions

How soon after the wedding should offboarding be completed?

Most planners aim to close out core steps like payments, vendor notes, and the client thank-you message within two to three weeks. Feedback requests and final archiving can extend slightly beyond that if you are waiting on final deliverables like photos.

Who should own the offboarding checklist on a team?

Assign one clear owner per wedding, usually the lead planner, even if tasks are split across assistants. A single owner prevents steps from being assumed done by someone else and ensures the file actually reaches a fully closed status.

Should offboarding differ for a full-planning client versus a day-of client?

The checklist stays the same in structure, but the depth changes. Day-of clients typically have fewer outstanding vendor payments and files to reconcile, while full-planning clients often require more thorough financial reconciliation and vendor notes.

What should happen if a client is unresponsive to the closeout message?

Send one clear follow-up after a reasonable window, then proceed with archiving based on your own records even without a client reply. Note the lack of response in the file so there is a record of your outreach attempt.

Continue the system

Related planner resources