A request is something to act on, a reason is something to discuss

Think about what the other person actually needs from you. A server needs an instruction they can write on a ticket. A host needs to know whether the meal they planned will work for everyone. A friend across the table needs nothing at all.

When you offer a reason anyway, you quietly change what the exchange is about. It stops being about food and becomes about you. Most people respond to that with genuine warmth, and warmth at a dinner table usually arrives in the form of questions, advice, and a story about someone else's health. You end up managing the conversation you were trying to avoid.

No one has run a study on dinner table conversation, and no one is likely to. What follows is practical craft, not a research finding. The value is in having the words ready before you need them, because the moment the server is standing there with a notepad is a bad time to compose a sentence.

Lines that work with a server

Restaurant staff take modified orders constantly. The American Heart Association's advice for eating out is simply to ask: its dining out page tells readers to ask the server or even the chef about ingredients, preparation methods, or substitutions, and notes that most chefs want to please the people they are cooking for. The FDA's sodium page suggests asking for a meal prepared without table salt and for sauces and salad dressings to be served on the side.

These are the lines that do the job without telling anyone anything about you:

1. 1 "Could the kitchen make that without added salt?"
2. 2 "Sauce on the side for me, please."
3. 3 "I'd rather have it plain, if that's possible."
4. 4 "I'm watching the salt, so what would you suggest?"
5. 5 "Could you skip the bread for the table?"
6. 6 "Do you have written nutrition information?"

Timing matters more than wording. Say it when you order, not after the plate arrives. A kitchen can leave salt out of a dish it has not cooked yet, and almost nothing can be undone afterward.

That last line is worth knowing about. Under federal menu labeling rules in effect since May 7, 2018, restaurant chains with 20 or more locations must post calories on the menu and must be able to provide written nutrition information on request, including sodium. Asking for it is an ordinary counter question that discloses nothing. Independent restaurants are not covered and usually have no numbers, so preparation questions are the tool there instead. A separate article in this series covers how to use those numbers once you have them, and another covers how to ask about preparation in more detail.

Ordering through an app or over the phone removes the social part of this entirely. There is no one to read your face, so the special instructions box is just a place for text. Keep what you type short and specific, because long notes get skimmed in a busy kitchen. "No added salt, sauce on the side" will be read. A paragraph about your eating habits probably will not. The American Heart Association's takeout guidance makes the same basic point in a different way: ask staff how something is made, and ask for dressings and sauces on the side so you control how much goes on.

Requests like these are common because restaurant food carries a lot of sodium. In a study of chain restaurants in New York City between 2015 and 2017, 40.6 percent of items at full service restaurants contained 2,300 milligrams of sodium or more, roughly a full day's worth of sodium in one dish, compared with 7.2 percent of quick service items. The average full service item held about 2,160 mg. You are not making an unusual request. You are making one of the most reasonable requests in the building.

What to tell a host, and when to say it

A host is the one audience where a little more information actually makes your evening easier. Someone planning a meal has to shop, cook, and time everything. One sentence sent two days ahead can spare both of you a negotiation at the table.

The sentence works best when it does two things: names what you would like, and releases the host from doing anything special.

1. 1 "I'm keeping the salt down these days, so please don't do anything different for me. Whatever vegetables you're making will be great."
2. 2 "Could you leave the dressing off my salad? Everything else sounds perfect."
3. 3 "I'm easy. If there's something plain on the table, I'm happy."

Notice that none of these mentions a condition, a health care professional, or a medicine. "I'm keeping the salt down" is a preference as far as the listener knows, and it is all the information a host needs to cook well for you.

Say it privately, by text or a phone call, before the shopping happens. The same words spoken at the table land differently. Everyone hears them, the cooking is already finished, and a host who has worked all afternoon may feel judged in front of guests. That is how a small preference turns into a scene nobody wanted.

If you would rather not say even that much, bring something. Arriving with a dish you enjoy means there is always one thing on the table you know the contents of, and nobody has to accommodate anyone. A separate article in this series covers that approach.

When someone keeps asking why

Some people will not let it go. The move is to repeat, not escalate. Give the same answer, in the same friendly tone, up to twice. Then ask them something about themselves, which almost always works because most people would rather talk about their own week than your salad.

1. 1 "Nothing dramatic. I just like it this way."
2. 2 "I'm good, thanks. How was the drive up?"
3. 3 "I'd rather hear about your trip than talk about food all night."

Do not argue about whether your preference is justified. The instant you defend it, you have agreed that it needs defending. It does not. People skip cilantro, olives, and spicy food without producing evidence, and nobody demands a rationale from them.

A harder version of this comes when someone else announces it for you. A spouse, a sibling, or a well meaning friend says across the table, "He's not supposed to have salt." You can let it pass, or you can close it gently with "I'm all set, thanks," and turn back to the conversation. If it bothers you, say so later and privately. Correcting the person in the moment usually enlarges the very topic you wanted to shrink.

Then there is the cook who takes it personally, often a relative who has been making the same dish for 30 years. Praise something specific, take a small portion, and mean both. "Your green beans are the best thing on this table" repairs more than any explanation of why you took less of the ham.

Do not borrow the word allergy

There is a tempting shortcut here, and it is worth naming so you can skip it. Saying "I'm allergic" gets attention from a kitchen in a way that "I'd prefer" sometimes does not.

Leave it alone, for three reasons. It is not true, and you would be putting a falsehood on a ticket that other people rely on. Many kitchens run a separate routine when an allergy comes in: fresh gloves, a clean pan, a manager checking the order. That effort exists for people who could end up in an emergency room, and spreading it across preferences makes it less reliable for them. The claim also tends not to work, because kitchens know that an allergy to salt is not a thing.

"Plain, please, no added salt" gets you the same plate with none of that. And if you do have a true food allergy, say it clearly, say it early, and name the food, because that is exactly when you want the kitchen taking you seriously.

When saying more is the easier choice

Privacy is a tool, not a rule. Sometimes the efficient move is to say more, on purpose, to the right person.

1. 1 A host who is building an entire meal around a small group. One sentence in advance, as above.
2. 2 Someone you eat with often. A partner, a close friend, or the coworker who books every team lunch. One conversation saves 50 small negotiations, and it means someone else is quietly picking restaurants with options.
3. 3 A situation where an ingredient genuinely matters. If your care team has asked you to be careful with a specific food or ingredient, the kitchen needs the name of that ingredient. It never needs the reason. "Does the sauce have soy in it?" is a complete question.
4. 4 Travel or a long stay in someone else's home, where the same small request otherwise has to be made at every meal.

Work meals are their own category. When someone circulates a group order form or a catering menu, you can simply pick the option you want, the way everyone else does, and say nothing. If the choices are all heavy on sodium, a quiet message to whoever is organizing works better than a comment in the group thread: "Could you add a plain grilled option to the order? Happy to pay the difference." Colleagues are the audience that needs the least information about you and is often given the most.

What these have in common is that the other person can actually use the information. That is the test. If knowing changes what someone does for you, telling them may be worth it. If it only gives them something to think about, it is optional.

Your health information is yours, and sharing goes one way

People often assume that health information is protected everywhere. It is not. The federal privacy rule under HIPAA, the Health Insurance Portability and Accountability Act, applies to three kinds of organizations: health plans, health care clearinghouses, and most health care practices, meaning doctors, clinics, dentists, nursing homes, and pharmacies, plus the businesses that handle health information on their behalf. The U.S. Department of Health and Human Services is explicit that an organization outside those categories does not have to follow the HIPAA rules.

A restaurant is not one of those organizations. Neither is a dinner table, a book club, or a group chat. Whatever you say at a meal travels wherever the listener takes it, and there is no mechanism for taking it back.

That is not a reason to be secretive. Plenty of people find it a relief to say out loud what they are doing and why, and support from the people you eat with is worth having. It is a reason to treat each telling as a decision you are making, rather than something you owe anyone who asks. Choosing not to explain yourself over appetizers is not rudeness. It is a preference about your own information, which is the one preference nobody gets to overrule.

Three lines worth having ready

Memorize these, adjust the wording so it sounds like you, and use them without ceremony.

1. 1 For a server, at the moment you order: "Sauce on the side, please, and no added salt if the kitchen can manage it."
2. 2 For a host, in a text two days ahead: "Looking forward to it. Please don't do anything special for me. I'll be happy with whatever vegetables are out."
3. 3 For anyone who asks why: "I just like it better this way."

Say it once, in a normal voice, and go back to whatever you were talking about. The request takes four seconds. The explanation, if you give one, can take the rest of dinner.