Wedding Vendor Research in Notion

Create one wedding-vendor database

Use one Notion database for every category. Separate florist, photographer and venue pages make overall progress harder to compare. Name the database something clear such as Wedding vendors, and let each row represent one business—not one photo, email or social post.

Include:

Vendor name and category
Website and location
Contact person and details
Status
Quote received and quote file or link
Why we saved this vendor
Questions
Next action

Useful statuses are researching, contacted, meeting booked, shortlisted, declined and booked. Keep the set small enough that every state remains distinct. This is a decision record, not another browser bookmark graveyard.

Record why each vendor made the list

Complete the “why” field when you create the row. Write a specific sentence:

Photographs indoor receptions without making the room look cold.
Uses loose arrangements with pale flowers and little greenery.
Venue has covered outdoor space in case of rain.
Cake designs are simple and use the colors already in our plan.

Avoid nice, love this and good option. If you and your partner differ, keep both reactions: You like the documentary photographs; partner thinks the editing is too dark. That is decision context you will not want to reconstruct later.

This addresses the hard drive fallacy: preserving a link is not the same as preserving why it mattered.

Bring Instagram and Pinterest discoveries into Notion

Keep Instagram and Pinterest as discovery tools; use Notion for candidates that enter the decision process.

For an Instagram discovery, create the vendor row, find the business website, paste the original post link and note the exact image or detail that caught your attention. A screenshot needs its account name or source.

For Pinterest, add a vendor only when the pin leads to a real business you might contact. Keep purely visual inspiration with design references. This prevents the tracker from becoming another inspiration collection—the same collecting pattern behind unused Pinterest saves.

Keep quotes and conversations on the vendor page

Open each database row as a Notion page. Add the quote—or the email link—and record what it includes, what needs clarification and when you must respond. Never copy a price from memory.

After a call, add a dated note containing only what the vendor explained, including availability, cancellation terms and deliverables. Put uncertainty in the questions field instead of guessing.

Make the next action concrete:

Ask about availability.
Compare package details.
Review portfolio with partner.
Decline by email.
Confirm meeting time.

Use views for current decisions

Create a Shortlist view for shortlisted vendors, a Follow-up view for contacted vendors with unfinished actions, and category views for florists, venues, photographers and other services.

Hide booked and declined vendors from active views, but do not delete them. Their quotes, conversations and reasons remain useful if a booking changes. Review active candidates before collecting more. If you already have several viable photographers, decide what is missing before saving another. The same principle helps when wedding Pinterest research stops helping.

Triage an existing research mess

If research is spread across Chrome, Instagram, Pinterest and email, do not import everything. Start with vendors you can still imagine contacting.

For each serious candidate, find the official site, preserve the useful original save, explain why they remain in consideration, attach matching quotes and replies, and add a next action. Archive duplicates and candidates you can no longer explain. A large list is not valuable merely because it took months to collect.

For cross-source recall, dEssence can save links, images and files with context. Notion remains stronger for a structured table, shared editing and visible decision stages.

Keep personal details elsewhere

Guest dietary needs, travel questions and small promises do not belong in the vendor database, but they still need a reliable home. Record each request with enough context to act on it. See tracking small wedding details.

The database is working when every active vendor has a reason, a status and a next action—and the shortlist explains earlier decisions without reopening months of tabs.