Claude Project: Your Persistent Event Planning Assistant

What This Builds

Instead of starting every AI conversation from scratch and re-explaining the event details, client preferences, and your agency's style, you build a Claude Project that holds all of this context permanently. Every time you open it, Claude already knows the event inside and out. producing vendor emails, attendee communications, proposals, and reports in minutes instead of hours, and in your voice, not generic AI output.

Prerequisites

• Comfortable using Claude for basic writing tasks (Level 3)
• Claude Pro account ({{tool:Claude.price}}). Projects require a paid subscription
• One major event or recurring client to build the first Project around

The Concept

A Claude Project is like a dedicated project folder that Claude keeps open indefinitely. You load it once with the event brief, client preferences, your agency's style, vendor list, and any relevant documents. Then every conversation within that Project starts with full context. the equivalent of having a highly skilled assistant who read the entire event file before every task.

Without Projects: You re-explain "the event is a 300-person leadership conference in Austin, the client prefers a formal tone, our main venue contact is Sarah at the Fairmont..." every single session.

With Projects: You never re-explain anything. Claude already knows. You just say "write the venue briefing document" and it does it correctly on the first try.

Build It Step by Step

Part 1: Create the Project and define its scope

1. Log in at claude.ai and click Projects in the left sidebar
2. Click + New Project and give it a descriptive name: "Smith & Co. Annual Partner Summit 2025" or "[Client Name]. All Events"
3. Click Project instructions (the pencil/gear icon at the top)
4. Write a system prompt that captures the essentials:

You are an expert event planning assistant for [Your Agency Name].

CLIENT: [Client company name and brief description — 2-3 sentences]
EVENT: [Event name, date, city, headcount, event type]
TONE: [Formal/casual/warm/energetic — describe what "on-brand" means for this client]
BUDGET: [Total budget and any notable constraints]
KEY CONTACTS:
  - Client lead: [name, title, email, preferences]
  - Venue contact: [name, venue, email]
  - Key vendors: [list 3–4 with names]

ALWAYS:
- Use "we" when referring to our agency's role
- Address the client formally as [Mr./Ms./etc.] in correspondence
- Include all event logistics (date, venue, time) in every attendee communication
- Use active voice and keep paragraphs under 4 lines

NEVER:
- Include specific pricing unless asked
- Reference vendors we haven't yet confirmed
- Use exclamation points in formal communications to this client

1. Click Save

Part 2: Upload event documents

1. In your Project, click + Add content or the paperclip icon in the chat
2. Upload the documents you have for this event:

• Event brief or RFP
• Client brand guidelines (PDF or text)
• Approved event budget (summarized version. remove sensitive data)
• Confirmed vendor list with contacts
• Any prior event recap reports (for recurring events)
• Your agency's standard proposal template

For documents you can't upload (e.g., large email threads), create a plain text file called event-context.txt with the key details pasted in, then upload that.

Part 3: Build your starting library of tasks

After uploading documents, test the Project by running these common tasks in sequence. each becomes a reusable template in your conversation history:

Test 1. Vendor outreach email:

Write a venue briefing email to Sarah at the Fairmont covering:
setup requirements (round tables, AV needs, load-in access),
dietary restrictions (14 vegan, 6 gluten-free),
and day-of timeline. Professional tone.

Test 2. Attendee communication:

Write the pre-event logistics email for all 300 attendees.
Include: venue address, parking instructions, registration desk times,
agenda overview, and dress code. Send date: 5 days before the event.

Test 3. Post-event report:

Using the event details in context, write a post-event report template
with sections I'll fill in: attendance, budget performance,
key highlights, what went well, areas to improve, and recommendation for next year.

Review each output. If Claude missed something or got a detail wrong, update the Project instructions to clarify. Run each test again until the output is immediately usable.

Real Example: Annual Partner Summit

Setup: You run an annual 200-person partner summit for a B2B software company every October. You build a Claude Project in January called "TechCo Partner Summit 2025" and upload:

• Last year's run-of-show
• Client brand guide (voice: "executive but approachable")
• Confirmed venue contract summary
• Preferred vendor list for Austin (4 vendors confirmed)
• 2024 post-event report with client feedback

Input (any time in the 9 months before the event):

Write an updated vendor briefing document for the catering team at Apis Restaurant.
They're handling: cocktail reception (120 people, 5pm–6:30pm),
group dinner (200 people, 7pm–9:30pm). Use the dietary data from last year's survey
plus the new restrictions Sarah sent last week [paste her email].

Output: A complete, professional vendor brief that uses the correct brand voice, references all confirmed logistics, includes accurate headcounts and timing, and addresses the caterer correctly, all without re-explaining a single detail.

Time saved: What would have taken 45 minutes of digging through email threads and rewriting from scratch takes 5 minutes.

What to Do When It Breaks

• Claude doesn't have a detail you need → Add it to the Project instructions or upload a document containing it. Don't just add it in the chat, add it to the permanent record.
• Output sounds too generic → Add more specifics to your Project instructions. Paste an example of your actual writing style and instruct Claude to match it.
• Context conflict (old vs. new information) → When event details change, update the Project instructions immediately. Old details in uploaded documents can confuse output. note the change in the instructions: "NOTE: Venue changed from Fairmont to JW Marriott as of March 15."
• Uploaded document not being used → Explicitly reference it: "Using the brand guidelines document I uploaded, write...", this tells Claude which file to prioritize.

Variations

• Simpler version: If you don't want to use Projects, save a master context document as a plain text file and paste the relevant sections at the top of any ChatGPT or Claude conversation. Less powerful but zero setup cost.
• Extended version: Build a separate Project for each major recurring client. Over 2-3 event cycles, the Project accumulates years of client preferences, vendor history, and lessons learned, becoming an irreplaceable knowledge base for your agency.

What to Do Next

• This week: Build one Project for your current largest event. Upload the event brief and run the 3 test tasks above.
• This month: Measure the time you spend on AI writing tasks with the Project vs. without. Most planners report saving 10-15 minutes per writing task.
• Advanced: When an event ends, update the Project with the post-event report and client feedback. The next year's planning starts with a richer knowledge base than any competitor who doesn't have this system.

Advanced guide for event planning professionals. Claude Projects require a paid Claude subscription. These techniques use persistent memory features that may evolve as Claude updates.