How to Request a Recipe From a Friend (Without the Awkward Text Loop)

By Mel Schembri · Published 2026-05-11 · Recipe Sharing

You loved what they made. You want the recipe. Here is the polite way to ask, and a better way to handle it next time with GetLadle's recipe request feature.

You went to dinner. They made something that made you close your eyes for a second. On the way home, you texted them: "that chicken was incredible, can I have the recipe?"

Three days later: nothing. Two weeks later: nothing. A month later, you run into them at the supermarket and they say "oh my god sorry I forgot, I'll send it over." Six months later, you still do not have the recipe.

This is a guide to the polite way to ask for a recipe, why the current system fails, and the one feature that actually fixes it.

Why most recipe requests die

The request-recipe-by-text loop has four steps:

1. You text them.
2. They see the message.
3. They need to find the recipe (which might be in their head, on a scrap of paper, in an old text to someone else, or bookmarked somewhere).
4. They need to transcribe or locate it and send it to you.

Step 3 is the bottleneck. Most home cooks do not have their recipes in one place. The lamb thing from Sunday was half made up, half from a Jamie Oliver cookbook, with quantities they eyeballed. Translating it into a format another person can cook from is work. Work they were not planning to do that evening.

So it sits in their messages. Forever.

The polite way to ask (when you must ask by text)

If you are stuck with the text-and-hope method, a few rules help:

Be specific about what you want. "That chicken" is vague. "The crispy roast chicken with the lemon and rosemary" gives them a hook.

Give them an easy out. "If it is a family recipe you want to keep in the family, I completely understand." This saves them from the awkward position of having to say no.

Ask at the right moment. Do not ask while they are hosting. Wait until the next day. They are more likely to actually write something useful if they are not also clearing plates.

Follow up once, gently. One reminder, about a week later, something like "no rush, just flagging this in case the message got buried."

Accept a messy version. "Rough quantities, I'll figure out the rest" makes it much easier for them to send something.

Reciprocate. If you ever make something you were asked about, send it first. Karma in kitchens.

The better way

All of the above is workarounds. The actual fix is a system where requesting a recipe is a one-tap action and fulfilling the request is a structured form rather than a transcription job.

GetLadle has a recipe request feature built into Circles. Here is how it works:

From your side: You are in a Circle with the friend who made the chicken. Tap their profile, tap "Request recipe," type "that crispy lemon roast chicken from Sunday." Send.

From their side: They get a notification. They open the app. There is a form waiting with your request at the top. They fill in the ingredients and method, tap save. The recipe goes into the Circle cookbook. You see it immediately.

The whole thing takes them maybe four minutes. There is no transcription, no guessing what format you want it in, no chasing. If they genuinely do not have time right now, the request sits there as a to-do until they do.

The reason this works: a structured form is much easier to fill in than writing a message from scratch. It prompts for ingredients, method, servings. All they have to do is fill in the blanks.

When the recipe request feature matters most

Three situations where this pays for itself fast:

1. Family recipes. Your aunt makes a specific pie. You love it. Every Christmas you mean to get the recipe. Every Christmas you forget. A recipe request in the family Circle creates a gentle, persistent prompt until she fills it in. Zero chasing, zero awkwardness.

2. Recurring host groups. Your supper club meets monthly. Someone brings a showstopper. You want the recipe so you can rotate it into your own life. Instead of texting them the next day, you request it in the Circle. The recipe goes into the shared cookbook the whole group can see.

3. Friends who do not write things down. Some of the best home cooks just cook. They do not have recipes written down. A structured form is much less intimidating than "write me a recipe", they fill it in between other things.

What GetLadle does not do

The app does not force your friend to share. It just makes it easy if they want to. Some recipes are genuinely private, an heirloom, a market-stall recipe, a family thing, and respecting that is part of the etiquette. You can always send a request, and they can always choose not to fill it in. No shame either way.

It also does not let strangers request recipes from you. Recipe requests only go between Circle members, people you have explicitly invited. Nobody outside your Circles can ask you anything.

How to start

If there is a recipe you have been meaning to ask for for months, this is your excuse.

1. Download GetLadle.
2. Create a Circle for your family or closest friend group.
3. Invite them.
4. Once they join, tap the person whose recipe you want. Request it.
5. The recipe turns up in your cookbook when they fill it in. Often within a day.

The free Apprentice tier covers this fully, one Circle, recipe requests included, no payment details needed. You can do the entire thing in 10 minutes.

Worst case: nothing happens and you are no worse off. Best case: you finally have the roast chicken recipe.

Related reading

• Best app to share recipes with friends and family
• Private recipe sharing: what it means and why it matters
• How to save recipes from friends without losing them

Try GetLadle free. Recipe requests, Circles, shared cookbooks. No credit card. Start at getladle.com.