How do I track which vendors I've worked with before?

Track vendor history wedding planner records can prove: connect past weddings, dated notes, and contacts so your next vendor recommendation has context.

How do I track which vendors I've worked with before?

Track vendors you have worked with by keeping a master vendor record connected to a separate history of completed weddings, with dated notes about each collaboration. Record the actual contact, event responsibilities, what happened, and whether you would recommend that vendor again; a saved phone number alone does not establish a working relationship.

TL;DR

  • Track vendor history: wedding planner records need completed events, dated observations, and current contacts.

  • Separate vendors you have worked with from referrals and contacts you have not hired.

  • Keep internal assessments separate from client-facing recommendations and shared timelines.

  • Rundown combines wedding planner CRM, budgets, timelines, client portals, and vendor coordination; evaluate history retrieval before committing.

How do I track which vendors I've worked with before?

Build a vendor directory with event-level history, then update it during your wedding closeout. Use this sequence for your 2026 records:

  1. Contact record: Create a master entry for the business and identify the people you actually worked with.

  2. Event history: Record the wedding date, venue, service provided, and your role in the collaboration.

  3. Debrief notes: Add factual observations about communication, delivery, handoffs, and follow-through.

  4. Relationship status: Distinguish direct experience from introductions and untested referrals.

  5. Next event: Check the history before recommending the vendor or assigning responsibilities again.

You can follow this structure in a spreadsheet or in planning software. The essential requirement is the same: find the vendor, see the relevant weddings, and understand the evidence behind your recommendation without searching old inboxes.

Why this matters

At 10–30 weddings per year, you need a record that survives the gap between one wedding season and the next. Remembering a business name is not the same as remembering which coordinator handled the booking, how the load-in worked, or who resolved a timeline change.

Rundown brings CRM, client portals, timelines, budgets, and vendor coordination into one wedding planning system. For vendor history, the practical test is whether your chosen setup lets you retrieve past collaboration details alongside the work you are planning now.

Your directory should explain why you trust a vendor, not just confirm that you know them. That distinction matters when you are preparing a proposal, briefing an assistant, or recommending someone for a wedding with different requirements.

Build vendor records you can actually use

Keep business details separate from wedding details

Use 2 record types: a vendor record and an event record. The vendor record describes the business; the event record describes a particular collaboration. This is a recommended structure, not a claim about how any specific platform stores information.

Keep current contact details in the vendor record. Put the wedding date, venue, assigned team, service scope, and observations in the event history. Otherwise, a phone-number update can sit beside an old complaint with no clear indication of which wedding it concerns.

Vendor record

  • What belongs here: Business name, service category, current contacts, relationship status

  • What does not belong here: An undated summary of every wedding

Event record

  • What belongs here: Wedding date, venue, actual team, responsibilities, debrief

  • What does not belong here: Assumptions about future availability

For your 2026 directory, use consistent business names rather than creating separate entries for every spelling variation. Preserve former names or alternate spellings in a note so you can still recognize older records.

Record the people behind the business

The company you book and the person who delivers the service are different pieces of information. Record the booking contact separately from the lead who attended the wedding.

That distinction makes your next inquiry more precise. You can ask whether the same lead is available rather than treating every team member's work as interchangeable. Keep the wording factual: identify who handled which responsibility instead of assigning a company-wide judgment to an individual interaction.

Capture the context of the collaboration

Write enough context to explain whether the experience applies to another wedding. A vendor's role, the venue requirements, and the agreed scope all belong beside your assessment.

Useful fields include:

  • Service scope: What the vendor was responsible for delivering.

  • Venue context: Access arrangements, setup restrictions, or other relevant requirements.

  • Actual team: Who attended and who served as your main contact.

  • Timeline handoffs: What information each party needed and when.

  • Outcome and follow-up: What happened and what remained unresolved.

Avoid copying an entire inbox into the record. Summarize the operational point and retain a reference to the supporting correspondence in your existing filing system.

Use a repeatable closeout process

Vendor history becomes useful when updating it is part of finishing a wedding, rather than a separate project you keep postponing. Follow the same sequence after each completed event.

Contact record

Check the business name, service category, and current contacts first. Search for an existing entry before adding another one.

If the business already exists, add the new collaboration to its history. Do not overwrite the previous wedding's notes with the latest experience; you need both to understand what changed.

Event history

Attach or reference the completed wedding using a consistent identifier and date. Include the venue and the service delivered so another planner can understand the record without reconstructing the whole event.

Keep referrals distinct from completed work. Receiving a brochure, attending a networking event, or exchanging emails does not establish that you have coordinated a wedding together.

Debrief notes

Record the agreed expectation, the observed outcome, and any follow-up. This gives your future self something more useful than a general impression.

For example, replace a vague label such as difficult communication with a description of the specific unanswered request and how it affected your work. If the vendor resolved the issue, include that resolution rather than leaving the record frozen at the point of frustration.

Relationship status

Use 3 relationship statuses: worked together, referred, and not yet worked together. These describe the source of your knowledge, not a quality ranking.

Keep your recommendation decision separate. A vendor can be someone you have worked with but would recommend only for a particular scope, venue, or team arrangement. That nuance belongs in a dated note.

Next event

Before recommending the vendor again, review the relevant history and confirm current details directly. Past collaboration does not establish present availability, staffing, or suitability for a different brief.

Carry forward actionable requirements, not the entire debrief. Your new timeline needs the agreed handoff; it does not need a private assessment of the previous wedding.


Vendor history process from contact record through review for the next event

Review past collaboration before making the next recommendation.

Should I use a spreadsheet or wedding planning software?

Choose the setup you will maintain and can search during a real planning decision. A spreadsheet gives you direct control over your fields; connected planning software places vendor coordination alongside other event work. Neither replaces a clear note-taking process.

Spreadsheet directory

  • Best for: A solo planner building a structured history

  • Practical advantage: You define the columns and review the records directly

  • Limitation to plan for: You must maintain event references and prevent duplicate entries yourself

Connected planning system

  • Best for: A planner managing vendor coordination alongside CRM, budgets, and timelines

  • Practical advantage: Related planning work sits within the same system

  • Limitation to plan for: You must verify history retrieval, record structure, and access controls before adopting it

Do not choose from a feature label alone. During your 2026 evaluation, use a realistic vendor example and ask to see how the system handles repeat collaborations, changed contacts, and internal notes.

Rundown is best for professional wedding planners who want CRM, budgets, timelines, and vendor coordination in one connected system. Its stated scope covers those planning functions; confirm the specific vendor-history workflow before moving your existing records.

The same discipline applies when comparing Rundown with Aisle Planner or another platform. Test the workflow you need rather than assuming that a vendor directory includes every kind of historical record.

Start with Rundown's free plan

Explore CRM, budgets, timelines, and vendor coordination against your own planning workflow.

Start free plan

Why vendor-history detail varies

The right record contains enough evidence for your next decision without becoming a second event archive. Adjust the depth to the work you actually coordinated.

  • Your service scope: Full planning and wedding-day coordination give you different visibility into inquiries, proposals, and pre-event communication.

  • The vendor's responsibilities: Record the handoffs and deliverables relevant to that service rather than forcing every vendor into identical notes.

  • The people involved: A different lead or team changes the context of your previous experience.

  • The venue requirements: Access, setup, and scheduling constraints help explain what happened.

  • The intended reader: Internal assessments and client-facing recommendations need different levels of detail and access.

Review your 2026 fields against these factors. Remove anything you never use, and add a field only when it supports a recurring planning decision.

How do I keep vendor notes factual and private?

Separate observations from interpretations, and keep internal assessments out of shared client materials. Write each note as though another planner will need to act on it without asking you for the backstory.

A useful entry identifies the expectation, the outcome, the source, and the resolution. Avoid speculation about motives, personal comments, or statements you cannot substantiate. If you did not witness something directly, identify where the information came from rather than presenting it as your own observation.

Before putting sensitive notes into any platform, check who can view them, whether they appear in shared documents, and what happens when you export or duplicate an event. A client portal and an internal debrief serve different purposes; do not assume their contents stay separate without checking.

What should I do with old vendor emails and spreadsheets?

Start with vendors relevant to your active work and preserve the original records while you organize them. You do not need to rewrite every past email to create a useful directory.

Deduplicate business names, confirm current contacts, and add dated event references. Mark uncertain history as unverified rather than filling gaps from memory. An honest blank is more useful than an invented conclusion.

For your 2026 cleanup, distinguish a completed collaboration from an inquiry that never became a booking. Only mark worked together when you can identify the event and your involvement.

When should I update a vendor's recommendation status?

Update the recommendation when new direct experience or verified information changes the basis for it. Keep the earlier event notes so the change has context.

Do not turn a single unexplained issue into a permanent label. Record the specific concern, any resolution, and what you need to confirm before recommending the vendor again. Equally, do not erase a documented concern just because a later inquiry went smoothly.

FAQ

What's the best way to remember which wedding vendors I've worked with?

Keep a master vendor directory with a dated history of completed weddings. Record the actual team, service scope, observations, and recommendation context rather than relying on a contact list.

Can I track vendor history in a spreadsheet?

Yes, a spreadsheet can hold vendor details and event history. Keep current business information separate from wedding-specific notes, and use consistent references to connect them.

Should I mark a referred vendor as someone I've worked with?

No, a referral is not direct working experience. Use separate relationship statuses so your recommendation accurately reflects what you know.

What should I write after working with a vendor?

Record the agreed responsibilities, observed outcome, people involved, and unresolved follow-up. Include the wedding date and enough context to explain your assessment.

Can I share my vendor history with couples?

Share relevant recommendations, not your entire internal history. Check document and portal visibility before adding private assessments to any shared workspace.

Does a past booking mean a vendor is available again?

No, past collaboration does not confirm availability for another wedding. Contact the vendor to confirm the date, scope, and actual team before making commitments.

Should I replace old vendor notes after another wedding?

No, add a new dated event entry rather than replacing the previous one. Preserve both experiences and update your current recommendation with the relevant context.

One last thing

A vendor you know is not automatically a vendor you have worked with. Make that distinction visible before you add ratings, tags, or a preferred-vendor label.

The next time a couple asks for a recommendation, your record should tell you which wedding supports it, who delivered the work, and what you need to confirm now. That is the difference between keeping contacts and keeping useful vendor history.

Related guides

Keep reading

Newsletter

Planning ideas and product updates for wedding and event studios.

© 2026 rundown · Lawless Ventures LLC

Newsletter

Planning ideas and product updates for wedding and event studios.

© 2026 rundown · Lawless Ventures LLC

Newsletter

Planning ideas and product updates for wedding and event studios.

© 2026 rundown · Lawless Ventures LLC