Making a clear request
The conversation

Making a clear request: specific, doable, and open to no

Turn a complaint or a wish into one request that names an action and a time, test it against a demand, and plan what to do when the answer is no.

Start here Essentials

This chapter asks for one request: one action, one time, said so that either of you could tell later whether it happened. A position is what you ask for; an interest is why it matters. Your request is your position put as an action, and What you want and why is where the reason behind it lives. Make the request after you have listened, when you know something about what matters to them.

  1. Write what you want them to do, not what you want them to stop. See Make it specific, positive and doable.
  2. Make it specific enough that you would both know if it happened, and add when. The same section covers the time.
  3. Test it against a demand. Ask yourself whether you could hear no. See Request or demand.
  4. Decide what you will say if the answer is no. See Hearing no.

Minimum time: about 20 minutes. Done when: the conversation plan has one request that names an action and a time, and the draft check finds a request in your message.

What a request is Understand

Most disagreements leave one person with a complaint and nothing else. "The sink is always full" tells the other person what you dislike. It does not tell them what to do, and a person who has to guess what you want will often guess wrong or give up. A request closes that gap. It names an action you would like the other person to take.

The handout that Nonviolent Communication's publisher distributes describes a request as a specific action stated in the positive, doable now, measurable, and open to the other person's answer (a handout on the four components of NVC). We use that definition because it is short and easy to test. Convention The same handout contrasts a request with a wish, which tends to be vague, future oriented and non-specific. "I wish you were more considerate" is a wish. "Would you be willing to rinse your dishes before you go to bed this week?" is a request.

A wishA request
"I wish you were more considerate.""Would you knock before you come into my room, starting today?"
"Stop leaving dishes in the sink.""Would you put your dishes in the tub by the sink before bed, for the next two weeks?"
"The job needs to get done.""Could you tell me by Friday which date you can commit to finish?"

Many conversations that "went fine" change nothing because they end in a wish. Both people leave agreeing that things should improve, and neither knows what that means on Monday. A request is how the conversation turns into action.

Your position as an action

A position is what you ask for, and an interest is why it matters to you. A request states the position as a single action. If your interest is a calm start to the morning, your position could be "no dishes in the sink," and your request is the action that gets you there: "wash or soak your dishes before bed." Notice that this request is one of several that would meet the interest. Options and agreements explains how to compare them. For now, make one request, and be open to a better one.

Make it specific, positive and doable

Check a request against four tests.

  1. It names an action. "Be more respectful" is not an action. "Knock before coming into my room" is.
  2. It is stated in the positive. Ask for what you want, not for what to stop. "Stop leaving dishes" leaves a hole where the new behavior should be. "Rinse and stack them before bed" fills it. Positive requests are also easier to say yes to, because they describe a way to succeed.
  3. It is doable now. It fits the other person's real situation. A request for something the person cannot do (finish tile that depends on a worker who quit) invites a no or a promise that will not hold.
  4. It has a time. "By Friday at noon," "starting tonight," "for the next two weeks." A time is what makes the request measurable. Without one, "soon" will mean different things to each of you.

The Gottman Institute adds two small habits: say "please", and say "I appreciate it when you..." (Gottman Institute on the six skills). Neither is a trick. They tell the other person you are asking, not ordering. Preference

"I would like" and not "you should"

APA advises turning demands into "I would like" (APA on controlling anger), and Family Caregiver Alliance suggests "I need..." and not "You should..." for a family meeting (Family Caregiver Alliance on holding a family meeting). "You should wash up before bed" puts you in the position of a judge. "I'd like the sink clear by 8 a.m." states what you want and leaves space for the other person to say how. The draft check lists sentences with "should", "need to" and "have to" aimed at the other person, so you can reread them.

The assertive middle

Two university counseling pages describe a middle between staying silent and pushing. A passive style avoids expressing opinions or needs, and the frustration builds up like a pressure cooker and may end in an outburst. An aggressive style is comfortable stating needs but struggles to see anyone else's. A passive-aggressive style shows anger indirectly, through sarcasm or conveniently forgetting. An assertive style states values and needs and respects the other person's (University of Toledo on communication styles). Union College defines assertiveness as a direct and appropriate expression of your feelings, beliefs and opinions that does not violate anyone else's rights (Union College on assertiveness). A clear request is the assertive middle in one sentence. People use different styles in different situations, so the labels describe habits and not people.

Limits

A clear request makes an answer more likely. It does not create an obligation. Whether someone must do what you ask, such as make a repair, give a refund or finish the work, is set by the lease, the contract, the employer's policy or the law, and not by how you phrase the request. This chapter does not tell you who is in the right. Neighbors, landlords and people you hired says where to look and what to write down. If the person has hurt or threatened you, or you are afraid of how they will respond to a request, see When this manual is the wrong tool.

Request or demand

The difference between a request and a demand is not in the words. It is in what happens when the answer is no. The NVC handout says a demand includes a threat of punishment or the promise of a reward. The Center for Nonviolent Communication offers two questions to check yourself: is my request really a demand in disguise, and am I prepared to hear no, listen, and keep the connection? (CNVC on the purpose of NVC)

Use those questions on your draft. If you notice that you are already planning how to make the person pay for a no, you are making a demand, and the sound of "please" will not change it. If you can picture yourself saying "OK, tell me what would work for you," it is a request.

Some situations contain a legitimate expectation: a contractor agreed to a finish date, or a lease says the landlord repairs a heater. A request in those cases can state the expectation and still be a request: "The contract says September 26. Can you tell me by Friday what date you can commit to?" It asks for information and a commitment. It does not threaten.

Consequences

Some scripts end with a consequence: what will happen if the behavior continues. We leave it out of the default request, for three reasons. The NVC handout defines a demand by its threat or reward. Oklahoma State University's extension sheet keeps the consequence part of an I-message mainly for use with children (Oklahoma State extension on "I" messages). And a consequence added to a first request often reads as an ultimatum.

Our default is this: state a consequence only when it is a real, proportionate next step that you will take, and say it as information, not as a threat. "If we can't agree on a date, I'll ask the attorney general's mediation unit to help" is information about what you will do next. "If you don't fix this, you'll regret it" is a threat. Test it by asking whether you would still say it if the other person asked, calmly, "What would you do?" Preference

When a record matters, a stated next step is fair, because the other side then knows what you are weighing. Getting a third party describes the steps that exist. The comparison below sets this default beside DESC, which includes consequences by design.

Hearing no

A request has to be open to no, or it is a demand. Plan before you ask what you will do when you hear it.

  1. Say it back. "So that doesn't work for you." Do not argue.
  2. Switch to listening. Gordon Training suggests shifting from sending to listening when you meet resistance (Gordon Training on shifting gears). Ask what makes it hard. The reason behind a no is often an interest you did not know about. The CNVC page says the same: look for the need behind it.
  3. Treat a counter-offer as a new option. "I can't do it at midnight, but I can do it at ten" is a yes to a different version. Options and agreements shows how to compare it with yours.
  4. Ask for a time to decide. If the person needs to think, ask when you can talk again, and write the date in the plan.
  5. Write down what you heard. Where a record matters, ask for a deadline in writing and keep a copy. The log section of Neighbors, landlords and people you hired covers this.

If you hear a flat no and the issue matters, you have choices that do not involve winning the conversation: agree to disagree for now, change what you do, or ask for a third party. What you want and why has you write what you will do if you do not agree. That sentence is what makes it safe to ask.

Go deeper

The three kinds of request

The NVC handout names three kinds. A request for clarity checks understanding ("Can you tell me what you heard me say?"). A request for feedback asks for a reaction ("How do you feel about that?"). A request for action asks for a behavior ("Would you be willing to talk about the schedule for ten minutes, now?"). Most of this chapter is about the third. The first two are useful inside the conversation, particularly after a paraphrase.

DESC and the consequences step

DESC (describe, express, specify, consequences) comes from Sharon and Gordon Bower and is reproduced in a Yale handout for managers. Its last step is to state the consequences, both positive and negative, of the behavior continuing or changing (Yale's handout on DESC). A positive consequence might be: "If we can do that, I'll stop texting you about it." The sources disagree on when this belongs. Oklahoma State keeps a consequence mainly for children; the Yale handout includes it for adults at work. We default to leaving it out and add it only when it is a real next step, because the same words can read as an offer or a threat depending on tone and history, and you cannot hear your own tone.

Union College's three-part statement

Union College teaches an empathy statement, then a direct statement of your needs, then an action statement or proposed way to resolve it. Its roommate example ends with "Can we talk about this and try to come up with a solution?" The handout adds that assertiveness does not guarantee that the other person will respond as you hope. That final action statement is a request, so this script fits this chapter as well as the one on openings.

Where the sources do not reach

We found no study that tests whether a request with a time gets more compliance than one without. The advice to add a time rests on the definition of a measurable request and on practitioner convention. Test it Try it with a low-stakes request and see.

See it: Maya and Teresa See it

Fictional example

Maya Torres and Eli Brooks are invented for this manual. After listening, Maya knows Eli would rather wash up when he wakes at around ten, and does not want to be nagged at midnight. She also knows her interest: a clear counter and a calm start before her 7:15 commute.

Maya's first draft request: "I need you to stop leaving your stuff in the sink." The draft check finds "need to" aimed at Eli, no clear action and no time. She rewrites it: "Would you be willing to put your dishes to soak in the tub by the sink before you go to bed, and wash them when you get up, so the sink is clear by 8 a.m.? Could we try that for two weeks, starting tonight?"

That request names the action (soak, then wash), is positive, is doable on Eli's schedule, and has a time (starting tonight, for two weeks). Eli says: "The tub works. But I can't promise 8 a.m. on my late nights. Can it be 10:30?" Maya considers it. 10:30 breaks her morning, but the tub keeps the sink clear. She counters: "The tub by the sink handles my mornings. Wash by 10:30, and if you can't, put it in the dishwasher." They treat Eli's counter as a new option; Options and agreements writes it down.

Known: Maya's interest and Eli's schedule. Assumed: that a tub on the counter is acceptable to both; Maya and Eli each settle that for themselves. Open: whether two weeks is long enough to see a pattern; they check on the date they set.

Teresa Alvarez (fictional, she/her) hired Ray Dunn (fictional, he/him) to remodel her bathroom under a written contract for $18,400, finish date September 26. On October 17 the job is three weeks late, and Ray has added a $640 charge for a tile change Teresa approved by text with no price. Teresa's draft: "You need to fix this now or I'm not paying." The draft check flags "need to" and finds no time. Her rewrite: "I'd like to settle two things. Could you tell me by Friday which date you can commit to finish, and could we look at the $640 charge together before I pay it?" That is two requests, which is more than one issue. She keeps only the first for the call, and holds the charge for the next conversation, as One issue at a time advises. Teresa settles which to raise first; the contract, which says changes must be in writing with a price, settles what she can expect on the charge.

Practice Practice

Minimum: write one request for your own disagreement and run it through the draft check. Time: about 25 minutes. Materials: the conversation plan.

  1. Write what you want in your own words. Do not edit yet.
  2. Turn any "stop" into a "do". What do you want them to do instead?
  3. Add a time. A date, a clock time, or a period such as "for two weeks".
  4. Check it is doable. Could the person do this on their real schedule and with their real resources? If you do not know, make a request for information first.
  5. Run the draft check. It should find a request and a time word. Fix any "should", "need to" or "have to" aimed at them.
  6. Write your answer to no. One sentence, in the plan: "If they say no, I will ask what makes it hard."
Go deeper

Turn two wishes into requests. Write two wishes you have for someone ("I wish he'd be more helpful"). For each, write the specific action, the time and the "doable now" check. Add the exercise to Practice sheets.

Your disagreement Your disagreement

Check your work Check your work

Criteria

  • Does your request name an action, in the positive?
  • Would you both know if it happened? Does it include a time?
  • Is it doable by this person, now?
  • Is it one request, not two or three?
  • Could you hear no? Have you written what you will do then?
  • If you stated a consequence, is it a real, proportionate next step, said as information?

Worked example

Maya's second request passes. It names an action (soak, then wash), is positive, includes "starting tonight, for two weeks", and fits Eli's schedule. She wrote what she would do on no: ask what makes it hard. When Eli countered with 10:30, she treated it as an option and not as a defeat. Teresa's rewrite passes the "one request" test only after she holds the charge back for a second conversation.

Common mistakes

  • Stacking requests. Two requests give the other person an easy way to answer only one.
  • Asking for a state of mind. "Be more considerate" is hard to see. Ask for an action.
  • Burying the request in the story. Say it plainly after the opening.
  • Making the request before listening. You may be asking for something they cannot do, or something a better option would replace.
  • Adding a threat. A consequence tacked on in anger turns a request into a demand.

What is still unresolved

The other person's answer. If it is yes, Options and agreements shows how to write it as who does what by when. If it is a counter-offer, the same chapter compares options. If it is no, and the issue matters, Getting a third party covers what comes after talking. If either of you gets heated, see When it heats up.

Knowledge check and scenario

What turns "I wish you were more helpful" into a request?
A specific action in the positive, doable now, with a time: "Would you be willing to take out the trash on Tuesday and Friday nights this month?" The wish names a quality. The request names a behavior.
How can you tell a request from a demand?
By what happens when the answer is no. If you are prepared to hear no, ask what makes it hard, and keep talking, it is a request. If a threat or a penalty waits behind the no, it is a demand.
Why does this chapter leave out consequences by default?
A consequence tacked on to a first request can read as an ultimatum, one extension source keeps it mainly for children, and the NVC definition of a demand includes a threat. A stated next step is fine when it is real and proportionate.
(Go deeper) What are the three kinds of request in the NVC handout?
Clarity (checking understanding), feedback (asking for a reaction) and action (asking for a behavior).
Teresa (fictional) is on the phone with Ray. She asks, "Can you tell me by Friday which date you can commit to finish?" Ray says, "I can't promise anything, my tile setter quit." What does she say?
This jumps to a consequence before she has learned what is in the way. It turns a request into an ultimatum and ends the conversation.
It restates his obstacle, asks what he needs, and asks for a time to hear back. Teresa has not given up her request, and she keeps the next steps in reserve.
It avoids a fight, but it drops the time. Without one, Teresa has no date to check and nothing to put in a written follow-up.

Checklist

Records your learning only; it is not a qualification.