Family & health · Spring 2026 · with Delivered A−

Planning a kid's birthday party with Claude

A birthday has a hard date and a long tail of small decisions. I handed the research and structure to Claude and kept the parts that need a parent.

The problem

My kid's birthday happens to land right around the busiest time of the year for my work, and it falls right beside other birthdays and my anniversary. Between school pickups and drop-offs, daily stand-ups during my busiest stretch and everything else, I also needed to plan a birthday party. Here is how I tasked AI to help.

What I wanted was not a list of party ideas. I wanted the boring scaffolding done and the shopping research done: what to do and when, who is coming, what it will cost, what goes in the goodie bags, and what to feed everyone. The question was whether a single detailed prompt, followed by a few focused ones, could produce something specific enough to act on instead of a generic checklist.

How I tasked Claude

I started with one prompt written like a spec instead of a chat. It gave the constraints that actually mattered and named the deliverables:

• Who and what: a birthday party for a young child, outdoors at a city park
• When and where: a specific Saturday in spring, in a specific city
• Three deliverables: a timeline checklist, a guest list with RSVP tracking, and a budget tracker with realistic costs
• Where to put it: saved as files in a named folder, so the planning does not live in a chat window

Then I did two follow-ups that turned out to be the most useful part. I told Claude the areas my kid was interested in, and asked for the top-reviewed party favors for the goodie bag in those areas, plus food options for the party.

Here is the prompt with the specifics swapped for placeholders, so you can reuse it:

I'm planning a birthday party for a [age]-year-old at [an outdoor park / venue]
on [day, date] in [city/area]. [Number] kids and about [number] adults.

Please create three files and save them in [folder name] on my computer:

1. A party checklist organized by timeline (4+ weeks out, 2-3 weeks out,
   1 week out, day before, day of)
2. A guest list template with RSVP tracking (name, contact, RSVP status,
   headcount, dietary restrictions, totals at the top)
3. A budget tracker with realistic local cost estimates

Then research two more things:

- Goodie bag favors. My kid is into [interest 1], [interest 2], [interest 3].
  Find the top-reviewed, age-appropriate favors in those areas, with a price
  range for each.
- Food options for [number] kids and [number] adults at a park, including
  something for common dietary restrictions.

Look up the venue's actual rules (reservations, permits, size limits,
inflatables) and include contact details for anything I need to arrange.

What came back

The checklist was split into five phases: four or more weeks out, two to three weeks, one week, the day before, and the day itself. It covered venue, invitations, theme, food, cake, entertainment, goodie bags, supplies, photos and cleanup. The structure is what made it usable. "4 weeks out" tells you what to do this week instead of at some vague future point.

The guest list was a plain table: name, contact, RSVP status, headcount and dietary restrictions, with totals at the top. Nothing fancy, but it is the table I would have thrown together in a notes app eventually, already built, and it gave me a clean list to carry into whatever RSVP tool I ended up using. I ran the invitations and RSVPs through Partiful.

The budget tracker was itemized by category with rough estimates for a high-cost metro area, for a party of 20 to 30 guests:

It also added a short "staying on budget" section I had not asked for: buy supplies in bulk, and remember that kids at this age are happy with games and free play, so the bounce house is optional rather than required.

That unrequested addition is worth keeping. It reframed the most expensive line on the budget as a choice.

The favors research was the part I found most helpful. Instead of scrolling shopping sites, I gave Claude my kid's interests and asked for the top-reviewed favors that fit them. That meant the goodie bags were built around things this specific kid and their friends would like, with reviews as the filter, instead of the same generic bag of stickers and whistles.

The food options came back as choices to pick from, not one answer, which is what I wanted. I was deciding under time pressure, and picking from a short list is much faster than building one.

Product reviews and prices change, and a list of top-reviewed items is a starting point. Open the listings and read a few recent reviews before you order, especially for anything small kids will handle or eat.

The part that earned its keep: venue rules

Because I named the park and the city, Claude looked up the venue's actual policies instead of writing generic advice. Two findings stood out:

• The picnic areas were first come, first served, with no reservations. So the plan is to arrive early and claim a spot, not to book one online.
• A bounce house, or a group above roughly 25 people, likely needs a special event permit from the city, and the output included the contact details to sort it out.

That is the kind of detail I would otherwise have discovered at 11pm the week before the party. It saved me about twenty minutes of tab-hopping I did not have, and a worse outcome if I had missed it.

Treat this as a head start, not the final word. It came from a web lookup, and park and permit rules change. Before spending money on a bounce house, confirm the policy and the permit threshold with the city directly, using the contact details Claude gave.

What still needed me

• Taste and knowledge of the kid. The checklist suggests a face painter or a bounce house, but it cannot know whether my kid would rather have a craft table or an egg hunt. Theme, friends and cake flavor are mine. The interests I supplied are what made the favors list personal.
• Real prices. The budget is a range, not a quote. I still have to call and ask.
• The guest list is empty by design. The template is the useful part. The names are mine.

Where it ended up

From one prompt and a couple of follow-ups I got a timeline, a guest list, a budget, a goodie bag shortlist, food options and a venue briefing, and each was specific enough to act on the same day. Claude handled the research and structure: the time-consuming part that is not the interesting part. I kept the part that requires knowing my kid.

The pattern is reusable for anything with a fixed date and a lot of small tasks: a trip, a move, a school event. Name the constraints, give it the personal details that make the results specific, ask for the rules to be looked up, and fill in the human parts yourself.

The original files were saved by Claude to a folder, and have since moved along with the chat they came from. The checklist and budget above are my cleaned-up rebuild of that structure, with rough ballpark prices. They are not a record of the exact output, and prices will differ where you live.

This is entry 25 in the AI Collaboration log.