To make a polite request in English, state the action clearly, match your wording to the burden, give one useful piece of context, and leave room for a real yes or no. A reliable default is: “Could you [action] by [time]? [Brief reason]. If that won’t work, please let me know.”
Sometimes politeness eats the request.
“I was just wondering if maybe, possibly, when you have a moment, you might perhaps be able to help me with something…”
The listener is now trapped in a fog bank. What do you want? How much work is it? When do you need it? Can they say no?
To ask politely, you do not need the longest request phrase. A good request makes the action easy to understand, shows that you have noticed the cost to the other person, and lands cleanly whether the answer is yes, no, or “not like that.”
1. Label
Name the exact action, object, amount, or deadline. Do not make the listener excavate the request.
2. Observe
Estimate the load: time, effort, money, inconvenience, risk, notice, repetition, and hierarchy.
3. Add
Give one useful limit or reason: by when, for how long, why it matters, or what alternative would help.
4. Deal
Handle the answer properly: confirm yes, clarify conditions, accept no, or follow up once without pressure.
Request vs command vs favor
A request asks another person to provide something or perform an action. Cambridge’s grammar reference uses the same broad distinction: we can ask for a thing, or ask someone to do something.1
But grammar alone does not tell you whether the listener has a real choice. “Could you submit this by five?” looks like a question. From a manager, it may function as an instruction. From a colleague asking for help, it may be a genuine request.
| Example | Main act | Can “no” genuinely stand? | What the speaker should do |
|---|---|---|---|
| “Can I borrow your charger for ten minutes?” | Request | Yes | Make the action and return time clear. |
| “Please wear eye protection inside the lab.” | Rule or safety instruction | No | State the requirement honestly instead of manufacturing fake choice. |
| “Could you cover my Saturday shift?” | Favor | Yes—and the burden is substantial | Acknowledge the inconvenience and accept refusal. |
| “You could charge your phone at reception.” | Advice or suggestion | The listener chooses their own action | Keep it within the listener-benefit boundary. |
| “Could you replace this charger? It stopped working on the first day.” | Complaint plus request for a fix | The exact remedy may be negotiable | Name the problem, evidence, and requested solution. |
The refusal test
Before choosing a request phrase, ask yourself:
If this person says no, am I prepared to accept it without punishment, guilt, or repeated pressure?
If yes, make a request. If no because the action is genuinely required, give a clear instruction and explain the role, rule, deadline, or safety reason. A command in a cardigan is still a command.
What makes a favor different?
A favor is a request that is especially discretionary and usually benefits the requester: lend me your charger, collect my parcel, switch shifts, watch my child, introduce me to someone. All favors are requests, but not every request is a favor. Asking a server for the bill is a normal service request; asking the server to charge your personal phone behind the counter is a favor because it adds an unusual burden.
Choose directness by burden
The best question is not “Which phrase is the politest?” It is “How heavy is this request here?”
Run the Request Load Test. Estimate:
- Time: ten seconds, ten minutes, or half a day?
- Effort: pass an object, review a document, or reorganise a schedule?
- Cost and risk: does the listener spend money, use authority, share access, or accept responsibility?
- Notice: is this planned, short notice, or an emergency?
- Frequency: is this the first request or the fifth “tiny favor” this week?
- Relationship and power: friend, stranger, customer, colleague, manager, employee, or service worker?
Research on workplace request emails supports this contextual view: in the studied scenarios, the degree of imposition could outweigh hierarchical rank, and directness changed dynamically with rights, obligations, and the situation.7 The study concerns workplace emails, not every spoken exchange, but its central warning transfers well: rank is not the only dial.
| Load | Typical situation | Useful shape | Example |
|---|---|---|---|
| Low | Small, expected, quick, easy to reverse | Clear and fairly direct | “Can you pass me the charger?” |
| Moderate | Several minutes, some inconvenience, or a boundary issue | Request + limit or reason | “Could you keep the music down after ten? The sound carries into the bedroom.” |
| High | Major time, schedule change, money, risk, authority, or short notice | Acknowledge load + specific request + reason + real off-ramp | “I know this is short notice. Would you be able to move the deadline to Friday? We receive the final test results on Thursday. If Friday is not workable, I understand.” |
| Required | Rule, duty, safety, or non-negotiable operational need | Direct instruction + reason + support | “The client names must be removed before this file is shared. Please send me the revised copy by three, and tell me now if you need help.” |
Direct does not automatically mean rude
For a familiar, low-load action, “Pass me the charger, please” may be completely natural. A cross-cultural study of requests in selected English- and Persian-language television series found frequent direct strategies in both datasets, especially in everyday interactions involving small tasks. The authors explicitly caution that directness and politeness do not move in perfect parallel.8
That does not prove that one form is universally safe, and scripted television is not a complete map of real life. It does prove why country stereotypes are a terrible phrasebook. Culture, community, age, personality, urgency, role, tone, and the immediate activity all matter. Learn to read the load in front of you.
Indirect does not automatically mean polite
Compare:
“I was wondering if you might possibly be able to work all weekend, with no extra pay, and send it Sunday night?”
The grammar is soft. The load is a piano. Indirectness has not made it float.
Urgency can also justify directness. “Move away from the door now—the alarm is sounding” is more useful than wrapping a safety instruction in six layers of uncertainty. Politeness includes helping people understand what is happening.
Can, could, would, and indirect forms
Can, could, and would are tools, not a fixed staircase from rude to royal. Official teaching references often present could you and would you as polite request forms, with can you more informal.2 Cambridge likewise describes could as generally more polite than can in requests and would as a more indirect alternative to will.34
Useful guidance, yes. Guaranteed social effect, no. Your tone, timing, role, request load, and willingness to hear no still do most of the heavy lifting.
| Form | Useful for | Example | Watch out for |
|---|---|---|---|
| Can you + base verb? | Familiar or low-load requests; checking practical ability | “Can you hold the door?” | It may be too abrupt for a heavy or upward request without context. |
| Could you + base verb? | A flexible neutral-polite default | “Could you send the revised table by three?” | Could does not make an unreasonable request reasonable. |
| Would you + base verb? | Willingness; a somewhat more formal or deliberate request | “Would you review the final paragraph?” | It can still function as an instruction when hierarchy removes choice. |
| Would you be able to + base verb? | Feasibility, availability, or a meaningful burden | “Would you be able to cover the first hour?” | Do not use it to pretend the burden is small; acknowledge short notice or inconvenience. |
| Would you mind + -ing? | Indirect requests, often about behaviour or a modest action | “Would you mind lowering your voice?” | Use the -ing form, not to. One-word yes/no replies can be confusing. |
| Do you think you could + base verb? | Checking possibility without assuming it | “Do you think you could finish by Thursday?” | Still state the real deadline and impact. |
| Would it be possible to + base verb? | Formal, institutional, or service situations | “Would it be possible to change the appointment?” | The passive shape can hide who needs to act. Clarify when necessary. |
| I was wondering if you could + base verb. | A careful opening for a substantial or upward request | “I was wondering if you could approve a one-day extension.” | Do not add three more softeners until the action disappears. |
| Could I / May I + base verb? | Asking permission for your own action | “Could I use this socket?” / “May I come in?” | May asks permission; do not say “May you send it?” to request another person’s action. |
Cambridge’s request guide also distinguishes urgent, highly direct I need requests from ordinary polite forms and notes that I want can sound impolite as a request.1 “I need the fire extinguisher” is useful in an emergency. “I want you to stay late” is not improved workplace communication; it is desire announced as destiny.
Four situations at three levels
| Situation | Direct | Neutral | More formal or burden-aware | Natural reply |
|---|---|---|---|---|
| Charger | “Can I use your charger?” | “Could I borrow your charger for ten minutes? Mine is dead.” | “Would it be possible for me to use a charger for ten minutes?” | “Sure, but I need it back before the meeting.” / “Sorry, I’m using it.” |
| Deadline | “Can we move the deadline to Friday?” | “Could we move the deadline to Friday? The test results arrive Thursday.” | “Would it be possible to extend the deadline to Friday? We are waiting for the final test results.” | “Friday works.” / “I can give you until Thursday noon, not Friday.” |
| Neighbor | “Can you turn the music down after ten?” | “Could you keep the music down after ten? The sound carries into the bedroom.” | “Would you mind keeping the music down after ten? My child’s room is beside this wall.” | “Of course—we’ll lower it.” / “We have guests tonight, but we can move the speaker.” |
| Service help | “Can you check this charge?” | “Could you check this charge, please? I think it may have been added twice.” | “Would you be able to review this charge? It appears twice on the receipt.” | “Certainly—I’ll check it now.” / “I can’t remove it here, but I can call a supervisor.” |
“Would you mind?” without the yes/no headache
The grammar asks whether the person objects:
“Would you mind closing the window?”
Technically, “No, not at all” means “I do not mind,” so the person agrees. Cambridge gives not at all as a polite response to this pattern.6 In real conversation, avoid turning a simple request into a logic exam. Reply with the action:
- Accept: “Of course—I’ll close it.”
- Refuse: “Sorry, I’d rather leave it open. The room is very warm.”
- Offer an alternative: “I can close it halfway.”
Please is useful, not magical
Cambridge notes that please usually supports politeness but can make a request stronger depending on position and stress; front-position Please… can sound more like an order.5
| Version | Possible effect |
|---|---|
| “Could you check this, please?” | A conventional polite request. |
| “Could you please check this?” | May add emphasis, impatience, or urgency depending on stress and context. |
| “Please check this now.” | Clear and potentially firm; may function as an instruction. |
| “Please, please check this.” | A plea or repeated pursuit, not simply “extra polite.” |
Fast grammar repair
| Awkward form | Repair | Why |
|---|---|---|
| “Could you to send it?” | “Could you send it?” | Use the base verb after a modal. |
| “Would you mind to close the door?” | “Would you mind closing the door?” | Use mind + -ing. |
| “Would you can help me?” | “Would you be able to help me?” or “Could you help me?” | Do not stack two modal verbs. |
| “Can you borrow me your charger?” | “Can you lend me your charger?” / “Can I borrow your charger?” | The owner lends; the receiver borrows. |
| “May you send me the receipt?” | “Could you send me the receipt?” | May I…? asks permission for your action; it is not the normal request form for another person’s action. |
Add context without overexplaining
Context helps the listener judge the request. A biography does not.
Use the One-Breath Context Rule:
Action + useful limit + one reason + off-ramp when needed
“Could you send the revised table by three? I need it for the client call. If today is too tight, tell me what time is realistic.”
The listener now knows what to do, when, why, and how to answer honestly. No archaeological dig required.
| Situation | Too little | Useful context | Too much or pressuring |
|---|---|---|---|
| Charger | “Can I have that?” | “Could I borrow your charger for ten minutes? I’ll return it before your call.” | “My battery is dead because the train was late and then the cable broke and honestly today has been…” |
| Deadline | “I need more time.” | “Could I submit on Friday instead of Wednesday? The final dataset arrives Thursday morning.” | “I know this is terrible and I feel awful and I promise I’m normally responsible and everyone has been asking me for things…” |
| Neighbor | “You’re too loud.” | “Could you lower the music after ten? The bass comes through the bedroom wall.” | “People in this building have no respect and I knew this would happen the moment…” |
| Service help | “Fix this.” | “Could you check this charge? The same item appears twice on the receipt.” | “I have been a customer for years, and after everything I have bought here, I cannot believe…” |
In the cross-cultural request study, a short reason—called a grounder (a supporting reason)—was one of the external modification devices examined.8 Reasons can reduce uncertainty, but they should explain the request, not prosecute the listener.
Name the real burden
Do not use just to shrink work that is not small:
Burden eraser
“Could you just rewrite the presentation tonight?”
Just does not quietly delete four hours from the clock.
Burden recogniser
“I know this is a large, last-minute change. Would you be able to revise the opening tonight? If not, I’ll adjust the client agenda.”
The speaker names the load, narrows the action, and offers a consequence they will own.
Avoid apology fog and guilt hooks
One sincere acknowledgement can help: “Sorry for the short notice” or “I know this interrupts your evening.” Five apologies before the request make the listener manage your feelings before they can evaluate the task.
Also avoid fake off-ramps:
“No pressure at all, but this would really save me, and I don’t know what I’ll do if you say no.”
That is pressure wearing a “no pressure” badge.
Requests at work and in services
At work, the key question is not “How formal should I sound?” It is “What are our rights, responsibilities, deadlines, and alternatives?” In services, the key question is “What exact action can this person reasonably take?”
At work: separate optional help from required work
| Context | Request or instruction | Useful wording | Clean reply |
|---|---|---|---|
| Peer asks for quick help | Genuine request | “Could you check these two figures before the call? It should take about five minutes.” | “Yes, send them over.” / “I can check them after two, not before the call.” |
| Employee asks manager for extension | Upward request with meaningful consequence | “Would it be possible to move the deadline to Friday? The supplier data arrives Thursday. I can send the completed analysis Friday morning.” | “Friday is fine.” / “No, the client meeting is Thursday; send the current analysis and flag the missing data.” |
| Manager asks for optional coverage | Favor; power makes refusal harder | “Would anyone be willing to cover the first hour on Saturday? It is optional, and time off will be arranged next week.” | “I can cover it.” / “I’m not available this weekend.” |
| Manager assigns required work | Instruction | “Please send the signed contract by noon; finance cannot release the payment without it. Tell me by ten if that deadline is at risk.” | “Understood.” / “Noon is at risk because legal has not approved clause four; I need your escalation.” |
A manager can say could and still create an obligation. An employee may hear career consequences even when the sentence ends with a question mark. When the task is required, clarity is kinder than fake optionality. When it is truly optional, state that and behave accordingly when someone declines.
In services: request the action, not a personality transplant
Service requests work best when you give the staff member something actionable:
Check
“Could you check whether this item was charged twice?”
Change
“Would it be possible to move the appointment to Thursday afternoon?”
Explain
“Could you explain what this fee covers?”
Escalate
“If you cannot authorise the refund, could I speak with the person who can review it?”
Notice what is missing: “You people always…,” “This is ridiculous,” and a ten-minute theory about the employee’s character. The person may not control the policy. Ask for the next useful action.
When the central act is reporting a failure and seeking repair, move into How to Complain Politely in English. For a complete sequence at reception—from check-in requests to room problems and alternatives—the scenario owner is English Conversation at a Hotel. This page stays with the general request mechanics.
Formality is not word inflation
Inflated
“I would be exceedingly grateful if you might possibly facilitate the provision of a replacement receipt.”
Professional
“Would you be able to send me a replacement receipt, please?”
The second sentence sounds like a person. Keep the larger system of formal and informal choices with Formal vs Informal Spoken English: How to Choose the Right Register; here, choose only enough formality to fit the relationship and load.
Follow up and accept no
A request is not complete when you finish speaking. It is complete when you handle the response.
| Answer | Requester’s next move | Example |
|---|---|---|
| Yes | Confirm the important limit, thank them, stop. | “Great, thank you. I’ll collect the charger in ten minutes.” |
| Conditional yes | Repeat the condition so both people share the same agreement. | “Thursday noon works. I’ll send the draft then, not Friday.” |
| No | Acknowledge it. Ask for one alternative only when appropriate, then stop. | “Understood. Thanks for letting me know. Is there another person I should ask, or should I leave it there?” |
| Needs time | Agree on when the person will answer. | “Of course. Could you let me know by noon tomorrow? I need to confirm the schedule after that.” |
| Unclear | Clarify the commitment rather than guessing. | “Just to confirm: can you send the full file today, or only the first section?” |
Accept no without making the listener defend it
A useful refusal response can be tiny:
- “No problem—thanks anyway.”
- “Understood. I’ll make another plan.”
- “That makes sense. Thanks for being clear.”
- “Okay. Would a smaller version work, or should I leave it there?”
The final version contains one alternative and an exit. It does not begin a hostage negotiation.
Follow up once with new information
“Just following up” is not wrong, but it often forces the listener to reconstruct the entire request. A useful follow-up repeats the action, the decision point, and the consequence:
“Could you confirm by noon whether Friday works for the revised deadline? If I do not hear back, I’ll keep the original Wednesday date.”
Follow-up pressure rises with frequency. One clear reminder may help. Four messages containing “gentle reminder” are no longer gentle; they are a small percussion section.
Practice the Two-Answer Rule
Do not practise only the perfect yes. For every request, speak the requester’s line, a yes reply, and a no or conditional reply. Then complete the conversation without irritation.
Charger: ask, hear yes, hear no
Say your version before revealing the model. You need a charger for ten minutes, and the other person may need it soon.
Requester: “Could I borrow your charger for ten minutes? I’ll bring it back before your call.”
Yes: “Sure—please return it by two.”
Requester: “Absolutely. Thank you.”
No: “Sorry, I need it right now.”
Requester: “No problem. I’ll ask at reception.”
Deadline: ask upward and handle a counteroffer
Say your version before revealing the model. The data arrives Thursday, but the current deadline is Wednesday.
Requester: “Would it be possible to move the deadline to Friday? The final data arrives Thursday morning, and I can send the completed analysis Friday.”
Reply: “Friday is too late, but Thursday at four works.”
Requester: “Thursday at four—understood. I’ll send the analysis then and flag anything still provisional.”
Neighbor: make the boundary specific without attacking
Say your version before revealing the model. The music is loud after ten and the bass reaches a bedroom.
Requester: “Could you keep the music down after ten? The bass comes through the bedroom wall.”
Yes: “Sorry—we did not realise. We’ll lower it.”
Requester: “Thanks, I appreciate it.”
Conditional reply: “We have guests tonight, but we can move the speaker and lower the bass.”
Requester: “That would help. Thank you.”
Service help: request a check, then accept an alternative
Say your version before revealing the model. The same item appears twice on a receipt.
Requester: “Could you check this charge, please? The same item appears twice on the receipt.”
Reply: “I can check it, but only a supervisor can remove it.”
Requester: “Thank you. Could you ask the supervisor to review it?”
No reply: follow up without restarting the whole story
Say your version before revealing the model. You asked yesterday for a document needed at noon today.
Follow-up: “Could you send the signed form by eleven? I need to submit the application at noon. If eleven is not possible, please tell me now so I can ask for an extension.”
Reply: “I cannot finish it by eleven, but I can send it at one.”
Requester: “Thanks for telling me. I’ll ask whether one o’clock can be accepted.”
Common awkward patterns
Most awkward requests fail in one of five places: the action is hidden, the load is erased, the choice is fake, the grammar is tangled, or the speaker refuses to accept the answer.
| Awkward pattern | What goes wrong | Better version |
|---|---|---|
| “I want you to send it today.” | Desire is presented as authority; can sound controlling. | “Could you send it today? I need it for tomorrow’s review.” |
| “Could you please possibly just maybe look at this?” | Softener pile; action, scope, and deadline are missing. | “Could you check the totals on page two by three?” |
| “Would you mind to send it?” | Wrong verb pattern. | “Would you mind sending it?” |
| “Can you borrow me your charger?” | Borrow and lend are reversed. | “Can you lend me your charger?” / “Can I borrow your charger?” |
| “I need you to stay late, if that’s okay.” | A requirement and optional ending collide. | Optional: “Would you be able to stay late?” Required: “We need coverage until seven; let’s discuss how to arrange it fairly.” |
| “Please do this ASAP.” | Urgency is unexplained and the deadline is vague. | “Could you send it by two? The courier leaves at two thirty.” |
| “I was wondering if perhaps you might…” | The sentence never reaches an action. | “I was wondering if you could approve a one-day extension.” |
| “No worries if not—but I really need you to say yes.” | Fake off-ramp followed by guilt. | “I know this is short notice. Could you cover the first hour? If not, I’ll ask the wider team.” |
| “Could you do me a small favor?” | Pre-commitment hides the real load. | State it: “Could you drive me to the airport at five tomorrow morning?” |
| “Why haven’t you answered my request?” | Follow-up begins with accusation rather than the decision needed. | “Could you confirm by noon whether you can review it today?” |
The Politeness Fog Detector
Before you send or say the request, check whether the listener can answer these five questions in one hearing:
- What exactly am I being asked to do?
- By when, for how long, or to what limit?
- Why does it matter? Only when that reason is useful.
- How heavy is this for me?
- Can I give a real no, condition, or alternative?
If the listener cannot answer question one, your request is too vague. If you cannot answer question four, you have not noticed the burden. If the honest answer to question five is no, stop pretending it is optional.
Please is not a politeness receipt
A conversation-analysis study of naturally occurring everyday requests found please in only 7 percent of request attempts in its dataset and linked it especially to interactional friction, such as prior unwillingness or interruption of another activity.9 That number is not a universal target, and the study focused largely on informal interactions among people who knew each other. Its useful lesson is narrower: politeness is built through the whole situation, not proven by one magic word.
Role-play the request and both answers. Open the speaking-practice chooser, select the path that best fits your blocker, and create one request scene. Speak as the requester, answer yes, then repeat with a no or condition. Finish both versions cleanly.
The linked page is a general speaking-practice chooser. It does not open this request lesson preloaded, record automatically, or score politeness, burden, hierarchy, or cultural fit. You supply the request scene and use the LOAD method to judge your second attempt.10
The strongest polite request is not the longest one. It is the one the listener can understand, evaluate, and answer without walking into a trap.