P
AI for Event Planner

Claude Project: Build a Recurring Conference Knowledge Base

Claude

For Event Planners

Tools: Claude | Time to build: 1-2 hours | Difficulty: Intermediate-Advanced Prerequisites: Comfortable using Claude for long-form event documents. see Level 3 guide: "Use Claude for Long-Form Event Documents"

What This Builds

A Claude Project loaded with everything about your biggest recurring conference. past event recaps, attendee feedback themes, vendor performance notes, and session format preferences. that you can use to generate documents, draft agendas, write proposals, and process feedback for the same event year after year. Instead of starting from scratch each year, you start from years of accumulated institutional knowledge. Planners who build this for their flagship annual event report cutting planning documentation time by 60-70% in subsequent years.

Prerequisites

  • Comfortable using Claude for event documents (Level 3)
  • Claude account. {{tool:Claude.plan}} subscription ({{tool:Claude.price}}): Sign up
  • At least 1 previous year's event files (proposals, recaps, survey summaries, agenda)
  • 30-60 minutes to compile your knowledge documents

The Concept

A Claude Project is like a shared briefing room. you load it with all the documents once, and every conversation you have inside that project starts with Claude already knowing the full history. Unlike a Custom GPT (which is optimized for producing a specific type of output), a Claude Project is more flexible. it's better suited for the kind of exploratory, multi-document work that event planners do during annual conference planning, where you're asking complex questions like "What feedback have we gotten about session format over the past 3 years?"

Build It Step by Step

Part 1: Compile your conference knowledge base

Create a dedicated folder on your computer: [Conference Name]. Claude Project Files/

Collect these documents:

Document 1: Conference master document Write a single document that captures the institutional knowledge of the event:

Copy and paste this
# [Conference Name] — Master Event Document

## Event Overview
- Conference name and purpose
- Annual date range (typically when)
- Target audience
- Core format (keynotes + breakouts / all-general / workshop-based)
- Key success metrics (attendance goal, satisfaction score target, NPS)

## History
| Year | Headcount | Venue | Budget | Satisfaction | Key Theme |
|------|-----------|-------|--------|--------------|-----------|
| [year] | [X] | [venue] | [$X] | [X/5] | [theme] |

## Preferred Vendors
| Category | Vendor | Contact | Performance Rating | Notes |
|----------|--------|---------|-------------------|-------|
| AV | [company] | [name/email] | [rating] | [notes] |
| Catering | ... | ... | ... | ... |
| Hotel/Venue | ... | ... | ... | ... |

## Content/Programming History
- [Year]: Top-rated sessions: [list]. Lowest-rated: [list]
- [Year]: ...

## Recurring Feedback Themes (from attendee surveys)
Positive: [list of consistent positives across years]
Negative: [list of consistent complaints that haven't been resolved]
Requests: [list of things attendees keep asking for]

## Client/Stakeholder Preferences
- [Stakeholder name/title]: [known preferences and sensitivities]
- Budget approval process: [describe]
- Approval timeline: [how many weeks before event]

Document 2-5: Paste your 2-3 most recent post-event reports and survey analysis summaries as separate text files.

Part 2: Create the Claude Project

  1. In Claude, click Projects in the left sidebar
  2. Click + New Project
  3. Name it: [Conference Name]. Annual Planning
  4. In the project description, write: "Knowledge base for [Conference Name]. contains event history, vendor relationships, attendee feedback patterns, and format preferences across [X] years."

Part 3: Upload your knowledge documents

Inside the project, look for Add content or a paperclip/upload icon. Upload:

  • Your Conference Master Document
  • All post-event recaps
  • Survey analysis summaries
  • Any past proposals you want Claude to reference for style

What you should see: The uploaded documents appear in the project's knowledge section. Claude can now search and reference these in every conversation within this project.

Part 4: Set up your project instructions

In the project settings, add instructions that define how Claude should behave in this context:

Copy and paste this
You are an expert event planning assistant specializing in the [Conference Name] annual conference. You have access to [X] years of event history, vendor performance data, and attendee feedback.

When helping with planning tasks:
1. Reference historical data to provide context ("In 2024, the networking session was the highest-rated component")
2. Flag patterns you notice in the feedback data
3. When recommending vendors, refer to the performance history in the master document
4. Keep institutional memory front-of-mind — don't recommend things that have consistently received negative feedback

For document generation, follow these conventions:
- Proposals: [your standard format]
- Run-of-show: table format with time, activity, AV cue, staff owner
- Survey analysis: themes with representative quotes + actionable recommendations

Part 5: Test with planning tasks

Start a conversation inside the project and test with realistic annual planning questions:

Test 1: "We're starting planning for [Year] [Conference Name]. Based on the feedback from the last 2 years, what are the 3 most important programming improvements we should prioritize?"

Test 2: "Draft the opening paragraph of our [Year] conference proposal for [client]. Reference what was successful last year and what we're doing differently."

Test 3: "Here are this year's survey responses [paste]. Compare the themes to the patterns you see in previous years and identify what's getting better, what's getting worse, and what's new."

Real Example: 4-Year Annual Technology Conference

Setup: Built a Claude Project for a technology company's annual user conference (500 attendees), loaded with: 4 years of post-event reports, a vendor performance document, a master conference history sheet, and the last 3 years of survey summaries.

Input for this year's planning: "We're starting planning for the 2026 conference. Based on our history, what are the biggest risks to watch for, and what's worked so consistently that we should keep it exactly as-is?"

Output:

  • Identified that AV reliability has been the #1 complaint 3 years running. recommended specifying a redundancy requirement in the vendor RFQ
  • Noted that the Tuesday networking dinner has received 4.8+/5 every year. recommended keeping format exactly as-is
  • Flagged that session lengths longer than 45 minutes correlate with engagement drop-off based on survey comments
  • Drafted specific language for the AV RFQ addressing the historical reliability issues

Time saved: This kind of historical synthesis would have taken 2-3 hours of manual document review. Claude produced it in 2 minutes from the uploaded history.

What to Do When It Breaks

  • Claude doesn't reference uploaded documents → Ask explicitly: "Based on the post-event reports I uploaded, what were the main feedback themes in 2024?". direct reference to uploaded documents improves retrieval accuracy
  • Answers feel generic despite uploaded knowledge → Your master document may be too vague. Add specific examples and data points: "2024 survey showed 73% of attendees rated networking opportunities as their primary reason for attending" is more useful than "networking is important"
  • Project runs out of context in long sessions → Start a new conversation within the project (the uploaded knowledge persists). the project knowledge is always available regardless of conversation length

Variations

  • Simpler version: Use a single long conversation with all context pasted in. works for one session but doesn't persist across days
  • Extended version: Add a budget history document with actual vs. budgeted line items from past years. Claude can spot budget patterns and flag categories where you've consistently overspent

What to Do Next

  • This week: Build the master document for your biggest recurring event and create the project
  • This month: After your next event, add the recap and survey analysis to the project. make this a ritual after every event
  • Advanced: Share the project with your co-planners on this account so everyone is working from the same accumulated knowledge base

Advanced guide for event planner professionals. Claude Projects require a paid Claude subscription.