Orzella and Claude: settling a family recipe you can cook again

Three versions of Gran's apricot cake, one smudged card and your own pencil notes. Claude can help you see where they disagree. Orzella keeps the version your family agrees on.

On this page

The short answer

Use Claude to line up the versions and flag where they don't match. Leave the unclear parts unresolved until someone who knows the recipe confirms them. Then save the settled recipe in Orzella with your notes, where it's easy to find and cook. Claude can keep reference material in a project, so this isn't about which tool can hold text. Each one is better at a different part of the job.

Claude: Projects

Where Claude earns its place

Family recipes rarely arrive in one tidy copy. There might be a photo of the handwritten card, a typed version a cousin emailed years ago, and your own changes scribbled in the margin. You can attach supported images and documents to Claude and ask it to compare them.

Claude: uploading files

One catch: if the card photo is pasted inside a Word document, Claude reads the document's text, not the embedded picture. Attach the image itself as a separate file. Accurate handwriting reading isn't guaranteed either, so treat Claude's reading of the card as a draft.

Claude: uploading files

If the project will take several sessions, keep the typed recipe and confirmed transcription as references in a Claude Project. Attach the original card image to the comparison chat when you need Claude to examine it. An instruction such as ‘mark unclear quantities rather than guessing’ can help keep the task focused. Add the reconciled version you want to retain to project knowledge on purpose.

Claude: Projects

A prompt that keeps the gaps visible

I've attached three versions of my grandmother's apricot cake: a photo of her handwritten card, a typed copy my cousin emailed, and my own notes. List every ingredient and step and show what each version says. Mark anything you can't read clearly as unreadable and anything that disagrees as a conflict. Don't guess quantities, temperatures or times, and don't add steps that aren't written in any version. Finish with a short list of questions I should ask my family.

The answer won't be the recipe yet. It's a map of what you know and what you don't. Maybe the flour amount on the card is smudged, or the typed copy gives a different oven temperature. Those become questions, not guesses.

Settle it with people, not probability

  1. Ask whoever made it most often. One phone call can settle what three documents can't.
  2. If nobody remembers a missing detail, keep it marked as uncertain. Record any version you develop yourself as your adaptation rather than the confirmed original.
  3. Write out the agreed version in full, keeping a note of anything that's still a best guess.

Give the agreed version a proper home

Paste the agreed text into Orzella, or save it from a readable photo of a clean copy. Review the resulting draft against what your family agreed, correct it and tap Save recipe. Keep the original card somewhere safe, too.

Your notes are what make the recipe yours. For example: The card says a cup of flour; Mum says heaped. Or: We use less sugar than the typed copy. Put the recipe in a Family collection. When you bake, the cooking view keeps the steps in front of you, with named timers for Cake and Apricots. Doubling for a party scales the supported ingredient quantities, but not the baking time or temperature, so record what worked in a note.

You can also export the recipes you choose with their sources and notes kept together. It's a copy of the recipes you choose, not a backup of the whole app or a shared live cookbook.

A recipe that outlasts the card

Claude helps you work out what the recipe really says. Orzella keeps the answer, along with every heaped cup and family correction, ready for the next birthday. The card can stay in the drawer, and the cake can stay on the table.

Get Orzella

Saving new recipes requires paid access. Recipes you've already saved stay available on this device.

Sources & references