My first Friendsgiving, I did the thing everyone does: told fourteen people "just bring whatever!" and then cooked an entire Thanksgiving dinner myself as insurance, because "whatever" is not a menu. The result: $412 in receipts (I still have them — turkey, sides, three pies, wine, plus the panic-bought backup rolls), two days of cooking, and a table where four people brought chips. One friend brought a single avocado. Not guacamole. An avocado.
The avocado radicalized me. Every Friendsgiving since has run on what my group now calls the Assignments Method, my host receipt now runs about $126, and — this is the part I didn't expect — people have more fun, because a potluck with structure is a shared project instead of a logistics gamble. Here's the whole system.
Why "bring whatever" fails every time
"Bring whatever" isn't generous; it's an information vacuum, and information vacuums fill with chips. Guests can't see the menu forming, so everyone defaults to the safest, most portable option. Meanwhile the host, who also can't see the menu forming, over-cooks as a hedge. You end up with both too much food and the wrong food — five desserts, no vegetables, and a host who paid for a full dinner anyway. The fix isn't assigning specific dishes like a tyrant ("Jessica: the Silver Palate green beans, page 141"). It's assigning categories.
The Assignments Method, start to finish
Step 1: The host owns the turkey, the gravy, and the house. Non-negotiable. The turkey is the one dish that can't travel, the gravy needs the turkey, and centralizing the scariest item removes 80% of the group's anxiety. Everything else is assignable.
Step 2: Build the category board. For 12–14 people, the menu is: 2 starches, 3 vegetable sides, 1 stuffing, 1 cranberry item, 2 desserts, bread, 1 appetizer (exactly one — it's holding people until dinner, not competing with it), drinks, and ice. That's 12 assignable slots. Post it where the group lives — the group chat, a shared note — with names attached to categories: "Priya: a starch," "Marcus: a vegetable side." People pick their category, they choose the actual dish, and ownership does the quality control: someone who chose "starch" and picked their grandmother's mac and cheese shows up motivated. Nobody has ever shown up motivated about an assigned recipe.
Step 3: One rule — no orphan dishes. Anything brought outside a category slot is welcome but goes out with dessert, not dinner. This single rule ended the chip flood. Chips at dessert hour are hilarious and therefore fine.
Step 4: The logistics footer. The board ends with three lines that save the day: "Oven space: taken 1–5 p.m., bring sides that serve at room temp or in a slow cooker." "Serving utensils: bring your own, tape your name on it." "Cold storage: my fridge is full of turkey; coolers on the porch." Oven collisions, not cooking failures, are the #1 potluck disaster, and they're solved entirely in the invitation.
The board, verbatim
People keep asking me for the actual text, so here's last year's board, names changed, copy-paste-able into any group chat:
FRIENDSGIVING NOV 21, 6 PM — THE BOARD. I've got: turkey, gravy, mashed potatoes, the house. Claim a category, cook whatever you love inside it. 🦃 Starch #2: Priya. Veg side 1: Marcus. Veg side 2: Dana. Veg side 3: OPEN. Stuffing: Jules. Cranberry situation: Sam. Dessert 1: Amara. Dessert 2: OPEN. Bread: Theo. One appetizer (just one, it's a bridge not a destination): Nic. Drinks: Rosa. Ice + seltzer: Dev. — Oven is occupied 1–5 pm, so bring sides room-temp or slow-cooker-ready. Bring your own serving spoon, tape your name on it. Fridge is full of bird; coolers on the porch. Off-board dishes welcome and will be served at dessert, chip people, you know who you are.
Notice what the board does in four sentences of logistics: it kills the oven collision, the utensil shortage, and the fridge crisis before anyone commits to anything. And the two OPEN slots aren't failures — an almost-full board fills faster than an empty one. Post it two weeks out and watch.
The host's receipt
Host Costs — Friendsgiving for 13
- 14 lb turkey @ ~$1.60/lb (frozen, store brand)$22.40
- Butter, herbs, aromatics, brine salt$9.75
- Gravy (stock + drippings + flour)$6.50
- Backup starch: 5 lb potatoes, cream, butter$11.25
- Bread I said I wouldn't buy but always do$6.00
- Wine, 3 bottles + sparkling cider x2$34.00
- Seltzer, ice (10 lb x2)$11.50
- Candles + one flower bunch (the whole "decor")$8.25
- Foil pans, to-go containers for leftovers$9.00
- Coffee + half-and-half for dessert hour$7.50
- Total$126.15
August 2026 prices; November turkey promos frequently beat $1.60/lb — grocery loss-leader turkeys hit $0.49–0.99/lb with a minimum spend. The $400 version of this receipt is what happens without the board.
Per guest, that's under $10 to host the whole holiday. Guests spend $15–25 each on their category, which is exactly what they'd spend attending anything, except here it buys their grandmother's mac and cheese a moment.
The timeline (the sane version)
- Two weeks out: post the category board. Categories fill within 48 hours because they're finite and visible — mild scarcity is the entire psychology of this system.
- Weekend before: buy the frozen turkey. A 14-pounder needs about three full days thawing in the fridge (roughly 24 hours per 4–5 pounds), and that math is not a suggestion — the counter-thaw shortcut parks the bird for hours in the USDA's 40–140°F bacterial danger zone. Thursday's turkey enters the fridge Monday.
- Day before: dry-brine the bird, set the table, clear the fridge shelf, stage the coolers, confirm the board one last time in the chat ("we are GO on all 12 slots").
- Day of, T-minus 5 hours: turkey in. Potatoes at T-minus 2. Everything else arrives cooked, per the board.
- Dinner + one hour: leftover triage. Perishables have a two-hour countertop window before the USDA says toss, so the to-go containers on the receipt aren't a nicety — they're how the group's $250 of collective food ends up in twelve fridges instead of one trash bag. Refrigerated leftovers are good for 3–4 days after that, per FSIS leftover guidance. Quantities-wise, potluck portions follow the same per-guest math as everything else — the cheat sheet applies, with the "polite ceiling" adjustment: groups finish N−1 portions of every shared dish.
Answers to the objections (there are always objections)
"Isn't assigning categories bossy?" The opposite, weirdly. "Bring whatever" outsources a planning problem to every guest individually; the board solves it once, publicly. In my group the board now fills competitively — the mac and cheese slot has a waitlist. Structure reads as care, not control, as long as people choose their own dish inside the category.
"What about the friend who can't cook?" The board has non-cooking slots on purpose: drinks, ice, bread, the appetizer (a cheese board is assembly, not cooking). The avocado friend has owned "ice + seltzer" for five years now and executes flawlessly.
"What if someone flakes?" That's what the host's backup starch is for — one flake-proof buffer dish, not a whole shadow dinner. One. The $412 disaster was me building a shadow dinner. If two people flake, dinner has eleven dishes instead of twelve and no one ever knows.
"Does this scale down?" At six people or fewer, skip the board and cook — a small Friendsgiving is just a dinner party wearing a seasonal outfit, and the host-cooks model is cheaper than coordination at that size. The board earns its keep from about eight people up.
The deeper thing the Assignments Method fixed wasn't money, though $275 saved per year is real money. It fixed the shape of the day. Hosting a holiday alone in a hot kitchen while your friends have fun in the other room is a strange kind of lonely, and no one who's done it forgets it. The board puts the host back at the table — which, it turns out, is the thing guests actually came for.