Every other Thanksgiving document depends on the menu. The shopping list needs the menu. The cook-ahead plan needs the menu. Guests who offer to bring a dish need the menu before you can name the dish. So the menu goes on paper first, on one sheet, and everything else follows from it. This page has that sheet plus the three documents it feeds: a shopping list grouped by store section, a cook-ahead timeline for day 3, day 1, and the day of, and a potluck table for the dishes you are not cooking. The first course is filled in as an example. Print it tonight; the full 15-page Thanksgiving Hosting Pack is linked at the bottom.
How to use this page: fill the menu first, in pencil. Write each dish once, with a serves count so the quantities on the shopping list have something to multiply. Circle the source on every line: cook, potluck, or buy. Anything circled potluck moves to the table at the bottom, with a guest's name next to it. Then the shopping list only contains what you circled cook or buy, and the timeline tells you which day each cook dish happens. Works the same for a small family dinner or a 20-person friendsgiving.
Four courses, six lines each. Twenty-four slots covers most tables with room to spare, and if a course runs short, leaving lines blank is fine. The Main course below is filled in as an example: three dishes with a serves count and a source circled, three lines left for yours. Nobody needs to see your handwriting on the other three courses; they are write-in for a reason.
One line per dish. Write a serves count. Circle one source: cook / potluck / buy.
example course — main
sides
dessert
drinks & extras
The example course shows the three sources in use: the turkey gets cooked, the gravy rides the same oven schedule, and the rolls are a buy because Thursday is crowded enough. A dish with no serves count is a dish that comes back from the store the wrong size, so write the number even when it feels obvious.
Fifteen rows, split the way a store is split: produce, dairy and eggs, pantry and baking, frozen and bread, drinks. The grouping is the point. A flat list of fifteen things means four laps around the same aisles; a list in store order means one pass, top to bottom. Copy each line from the menu sheet above and add the quantity from the serves count. If a section has nothing in it, cross out the header and skip it.
In store order. Copy dishes from the menu sheet. Quantity from the serves count.
| Produce | ||
| 1 | qty ______ | |
| 2 | qty ______ | |
| 3 | qty ______ | |
| Dairy & eggs | ||
| 4 | qty ______ | |
| 5 | qty ______ | |
| 6 | qty ______ | |
| Pantry & baking | ||
| 7 | qty ______ | |
| 8 | qty ______ | |
| 9 | qty ______ | |
| 10 | qty ______ | |
| Frozen & bread | ||
| 11 | qty ______ | |
| 12 | qty ______ | |
| Drinks & other | ||
| 13 | qty ______ | |
| 14 | qty ______ | |
| 15 | qty ______ | |
Fifteen rows is a real list, not a dare. If your menu needs a sixteenth item, it goes on the back of the receipt, not in a margin. The sections assume one big store; if you shop two stores, draw a line where the second store starts and keep the same order inside each half.
Three columns, three write-in lines each. The printed hints under each day are the mechanics that apply to almost any menu: thaw check and pantry shop on day 3, make-ahead dishes and fridge clearance on day 1, oven schedule and stovetop order on the day itself. Write your actual dishes from the menu sheet on the blank lines under each hint. No recipes live on this sheet on purpose; which dish goes on which day is a logistics decision, and it depends on your oven, not on a formula.
Write your dishes on the blank lines. One dish per line, with the time it starts.
Day 3
thaw check · pantry shop · borrow what's missing
Day 1
make-ahead dishes · clear fridge space · set the table
Day of
oven schedule · stovetop order · chill the drinks
The day-of column is where dinners are won. Working backward from your dinner hour, give every cook dish from the menu a start time and put the longest oven occupant first. If two dishes need the same temperature band, they share the oven; if they don't, one of them was always a day-1 dish and the timeline just told you so.
For most tables, some dishes are not yours. This table keeps those dishes in the same document as the menu, which is what makes a friendsgiving survivable: when someone asks "what should I bring," you open this table, find an empty row, and name a specific dish. The first row is an example. "A little something" is not a dish; write the dish, then the note about how it arrives.
One row per guest and dish. Name the dish yourself. Note = how it arrives (warmer, cold, reheated).
| Guest | Dish | Note |
|---|---|---|
| ex Dana | mashed potatoes, serves 10 | bringing own warmer |
Eight rows is about the ceiling where assigning dishes beats cooking them yourself. Past that, split the courses among two or three point people instead of eight separate text threads. A dish that arrives without a note is usually fine; a dish that needs oven time at 4:30 with no warning is not, so make the note column earn its keep.
This page owns the food. The free Thanksgiving hosting checklist owns everything around the food: the 18-item prep plan, the guest and RSVP table, and the hour-by-hour cooking timeline for the day itself. The two pages connect at two points. First, the guest count from the RSVP table is what makes every serves count on the menu sheet real. Second, every dish you circle potluck here appears in that page's guest table as a bring-a-dish ask, so nobody gets asked twice. Run this page first; the checklist assumes the menu already exists.
Print-at-home, write-in pages, no app. Comes as A4 and US Letter PDFs and prints fine in grayscale.
Full Thanksgiving Hosting Pack, 15 pages →one-time · A4 + US Letter · instant download · personal use, print copies for your own household