know.

CookbookKitchen and tableNo. 24

A community fundraiser cookbookrecipes from eighty families, checked, proofread and ready for the printer

Recipe No. 24Kitchen and table

For
A PTA volunteer compiling the school cookbook that pays for next year’s field trips
You bring
Recipes arriving by web form and email from dozens of families, a printer’s deadline, and a submission form that asks each family to confirm the recipe is theirs
You get
A cookbook of about 140 recipes in seven sections, each credited to its family, with a list of questions for every contributor, a proofreading link per section and clean text for the printer
Time
An evening to set up, half an hour a week checking what your assistant filed, and two weekends of checking before the printer’s deadline
Works in
know.sh on the web · your AI assistant, through MCP
Keep it
Private while you work; share one document by a read-only link when it is ready.

A fundraiser cookbook is an editing job disguised as a bake sale. Eighty families send recipes in eighty formats: “1 T”, “1 tbsp” and “a spoon”; oven temperatures missing from half the casseroles; a lasagne typed into the body of an email with the pan size left out. Someone has to turn that pile into a book, usually one volunteer with a deadline.

This recipe gives the volunteer a library and an assistant to do the filing. Hand the week’s submissions to whichever assistant you use, Claude, ChatGPT or a local model connected to know.sh, and it files each recipe into its section as a numbered finding with the family’s credit in the title, then reads each section for the inconsistencies a printer will not fix for you. You fix up the results in the editor. It lists the questions to send each family, one email per contributor rather than one per problem. When a section is clean, a read-only link goes to the contributors to proofread, and their corrections come back to you by email.

The web form, the contributors’ email addresses and the printer’s order stay where they are now. know.sh holds the recipes, the questions and the record of every correction.

What you will use

Shelf
One shelf, Linden Park cookbook, holding the seven section documents and a short House style document.
Research document
One document per section: Breakfast and brunch, Soups and salads, Mains, Sides, Breads, Desserts, and Kids in the kitchen.
Finding
One finding per recipe, titled with the dish and the family, filed as an Observation; a recipe waiting on an answer is filed as a Question until it arrives.
Your AI assistant
Files each week’s submissions into the right sections, flags duplicates, checks units, temperatures and allergen lines, and drafts one list of questions per family.
The editor
Where you settle duplicates, apply the families’ answers, fix units to the house style and mark the recipes that sold the bake sale as Key.
Proposed notes
Where your assistant is unsure about a single line, such as “1 can” with no size, it can leave a proposed note beside it, with Accept and Dismiss.
Revisions
Every change, yours or the assistant’s, is a revision you can point to when a family asks who changed their recipe.
Public link
A read-only link per section, with a password and an expiry on the proofreading deadline.

Method

  1. 1

    Set the ground rules on the submission form

    Before a single recipe arrives, add three lines to the form and to the email you send families. First: “This recipe is my own or my family’s. If it is adapted from a book, a website or a package, say which.” Second: “Recipes will be credited to your family name, not to children.” Third: list what every recipe needs, which is a title, servings, ingredients with amounts, the oven temperature or cooking time, and the pan size.

    The first line matters most. A fundraiser cookbook is sold, so it cannot reprint another cook’s headnote or method word for word. The note at the end of this recipe says what can be kept and what has to be rewritten.

  2. 2

    Hand each week’s submissions to your assistant

    Once a week, collect that week’s form responses as a spreadsheet and the emailed recipes as text, and give them to the assistant you use. First delete the columns and lines you do not want it to see: email addresses, phone numbers and children’s names. The contact list belongs in the PTA’s own records, not in an AI chat or the cookbook.

    Ask it to file each recipe as a new finding in the right section on the Linden Park cookbook shelf, titled Green chile chicken enchiladas — the Delgado family, in the family’s own wording, typos and all, and to list anything it could not place. The filing becomes the assistant’s job; the checking stays yours.

  3. 3

    Fix up each batch in the editor

    Open each section and read what arrived. Every finding the assistant created shows in Revisions as made by an assistant, so you can see exactly what moved. Press Edit to fix a misfiled recipe, drag findings into the order you want, and change a recipe to a Question while it waits on the family.

    Ask your assistant to flag near-duplicates too. Three families will send Texas sheet cake. Choose one, or run them side by side as Texas sheet cake — the Nguyen family and — the Brooks family; either way, decide before the printer counts pages.

  4. 4

    Settle the house style once

    Decide the style before you start correcting: “tbsp” and “tsp”, °F with no °C, “9 x 13-inch pan”, servings as a number. Write it as a short document called House style, one finding per rule, so your assistant can check every section against it.

    Change the units, not the voice. If Mrs Brooks writes “stir until it looks like wet sand”, that stays. Record each fix in the recipe itself and, when it came from the family, select the line and leave a Note: “Temperature confirmed by email, 14 October.”

  5. 5

    Ask your assistant for a consistency check, section by section

    When a section has most of its recipes, ask your assistant to read it, by name, against House style for the things printers see and volunteers miss: units written three ways, missing oven temperatures, missing pan sizes, “1 can” with no size, servings left blank, and a Contains: line that is missing or disagrees with the ingredients.

    Ask for the result in a new finding at the end of the section, grouped by family, with the line each question is about. That list becomes your email: one message to the Delgados with their three questions, not three messages. Your assistant can also leave a proposed note beside a line it is unsure of; Accept the ones you want to keep as reminders and Dismiss the rest.

  6. 6

    Send a proofreading link per section

    When a section is clean, press Share. Add a password, set the expiry to the proofreading deadline, and copy the link the moment it appears; it is shown only once. Readers see the section’s overview and recipes, never your notes or highlights. If a recipe is still waiting on a family’s permission, leave it out of the link from its own page.

    Send the link and password to that section’s contributors with one instruction: reply by email with corrections. They cannot write in your library, so you make each change yourself. The Share panel’s read count tells you whether anyone opened it before you chase.

  7. 7

    Copy the final text into the printer’s template

    Most fundraiser printers take recipes one at a time, in fixed fields: title, contributor, ingredients, method. Read each finished section and copy the text across, or ask your assistant to read a section back as plain text in the printer’s field order, without changing a word.

    Check the printer’s proof against the library, not memory. When a late correction arrives, the revision history shows what changed since the files went.

Specimen

  1. You

    Using know.sh, check the Mains document on my Linden Park cookbook shelf against the House style document. List every recipe with a missing oven temperature, pan size or Contains line, or units that break the style, grouped by family, and quote the line each problem is on.

  2. Claude

    I read the 22 recipes in Mains. Nine need an answer from the family; the rest only needed units changed, which I have not touched.

    The Delgado family, Green chile chicken enchiladas (4) - “Bake until bubbly”: no temperature or time. - “1 can green chiles”: no can size. - No Contains line. From the ingredients: milk, wheat.

    The Brooks family, Slow-cooker pulled pork (9) - No internal temperature for the pork. The card says “until it falls apart”, which is usually well past 145°F (63°C), but the family should say how they check.

    The Okafor family, Jollof rice with chicken (12) - “Chicken until done”: add 165°F (74°C), measured with a thermometer. - Contains line lists none; the stock cube they name contains soy and may contain wheat. Ask which brand.

    Six more families below. Shall I put the whole list in a finding called “Questions for Mains contributors” at the end of this section?

    From your library

    1. Mains, 4: Green chile chicken enchiladas — the Delgado family
    2. Mains, 9: Slow-cooker pulled pork — the Brooks family
    3. Mains, 12: Jollof rice with chicken — the Okafor family
    4. House style, 2: Temperatures, pans and the Contains line
Claude, connected to know.sh, checking one section against the house style: questions grouped by family, each quoting its line, and nothing changed until you say so.

Linden Park cookbookNo. 6

Dessertsbars, cakes and the bake-sale table

31 findings, 9,840 words, about 42 minutes, filed 29 September, revised 18 October, 4 highlights, shared.

Thirty desserts from twenty-six families, most of them tested at the spring bake sale whether we meant to or not. Recipes are credited to the family that sent them.

Every recipe ends with a Contains: line listing the major allergens in its ingredients. It is a guide to the ingredients, not a promise about anyone’s kitchen.

Findings

  1. 1Texas sheet cake — the Nguyen familyObservation, keyThe one that sold out first. Frost it while the cake is still warm. Contains: milk, eggs, wheat, tree nuts (pecans).
  2. 2Lemon bars — the Brooks familyObservation350°F (175°C), 9 x 13-inch pan. Adapted from a church cookbook of 1988; method rewritten by the family.
  3. 3Tres leches cake — the Delgado familyObservation, 1 notePan size confirmed by email, 14 October. Contains: milk, eggs, wheat.
  4. 4Peanut butter blossoms — the Hart familyObservationContains: peanuts, milk, eggs, wheat. Printed on the page with the other peanut recipes, not beside the plain sugar cookies.
  5. 5Chin chin — the Okafor familyQuestionWaiting on the family: how many cups of flour, and fried at what temperature?
  6. 6Questions for Desserts contributorsQuestion, keyEleven questions for seven families, grouped by family, from the assistant’s check on 16 October.

and 25 more findings

One section as a document: each recipe credited to its family, a Contains line on every page, and the assistant’s question list filed at the end.

Prompts to try

  1. Your assistant, connected to know.sh (Claude, ChatGPT or a local model)

    These are this week’s cookbook submissions. Using know.sh, file every recipe as a new finding in the right section document on my Linden Park cookbook shelf. Keep the family’s wording exactly, title each one “Dish — the ___ family”, file it as an Observation, and list at the end any recipe you could not place or that looks like a duplicate of one already filed.

  2. Your assistant, connected to know.sh (Claude, ChatGPT or a local model)

    Using know.sh, read the document Mains on my Linden Park cookbook shelf against the House style document on the same shelf. Find missing oven temperatures, pan sizes, can sizes and servings, units that break the style, and Contains lines that are missing or disagree with the ingredients (milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, sesame). Put the questions in a new finding, grouped by family, quoting each line. Do not change the recipes.

  3. Your assistant, connected to know.sh (Claude, ChatGPT or a local model)

    Using know.sh, read the Desserts document on the Linden Park cookbook shelf and give me every recipe as plain text in this order: Title, Contributed by, Servings, Ingredients (one per line), Method (numbered), Contains. Do not change any wording. Skip any finding filed as a Question.

Variations

  • For a congregation rather than a school, add a section of the recipes made for funerals and church suppers, and credit the cooks who have made them for years.
  • With Claude Code and the know.sh plugin, make a campaign from the schedule: Submissions close, Sections checked, Proofreading, Files to printer, with each step blocking the next, so the graph shows what the deadline is waiting on.
  • For one family rather than eighty, the family cookbook keeps the stories behind each recipe as well as the recipe.

Where it falls short

  • Families cannot type into the library. Everything comes to you by form or email and goes through your assistant, so the volunteer who owns the library does all the checking and all the correcting.
  • There is no export and no print layout. The printer’s template is filled by copying, section by section, or with your assistant reading the text back to you.
  • Proofreading links are one section each, so seven sections means seven links and seven passwords, or one password you reuse and change when proofreading ends.
  • Connecting an assistant means signing in once, following the support page. Smaller local models call know.sh’s tools less reliably than Claude or ChatGPT, so read what they file; Revisions shows every change.
  • Any assistant can miss an allergen hidden in a brand-name ingredient, such as a stock cube or a spice mix. The Contains lines are a check you make, not one you hand over.

A note on contributors, allergens and what goes in print

Indexed under

Fundraiser cookbooksContributorsHouse styleProofreadingAllergensPrinter’s templateConsistency checks