Describe the situation without evaluation
“The last three times we made plans they were cancelled the same day.” Facts only. No adjectives about their character.
Most failed requests were never actually made. They were hinted, tested, or delivered as an accusation and then withdrawn.
Only one of these gives the other person something they can act on.
The need is implied and left for them to detect. If they miss it, the missing becomes evidence they do not care.
The need arrives inside a complaint. They respond to the complaint, so the need goes unaddressed and you both end up somewhere else.
You construct a situation to see whether they will pass. Passing rarely reassures for long, and failing is treated as confirmation.
Stated plainly, addressed to them, specific enough to act on, and survivable if the answer is no.
A sequence you can draft in advance. Written first, said second — the drafting is where most of the work happens.
“The last three times we made plans they were cancelled the same day.” Facts only. No adjectives about their character.
“I end up not knowing whether to hold the time.” Own it as your experience rather than their crime.
“Could you tell me by the morning if it’s not going to work?” Vague asks cannot be met, and unmet vague asks feel like refusal.
“That would mean I can plan the day either way.” This gives them a reason that is not obligation.
Before you ask. If no would be catastrophic, the request will come out as pressure regardless of your wording.
Same need, delivered in a form the other person can act on.
“Could you let me know by the morning if plans change?”
Instead of: “You always cancel on me.”
“I’d like to talk about last night. Is now okay, or is there a better time?”
Instead of: “We need to talk.”
“I can’t take that on this week. I could do it next Thursday.”
Instead of: saying yes and resenting it
“I need about an hour on my own, then I’ll come find you.”
Instead of: leaving the room without explanation
“When you go quiet I assume the worst. Can you tell me you’re just tired?”
Instead of: asking “are you angry with me?” six times
“That’s a no from me, and I’m not upset with you.”
Instead of: apologising for the boundary until it dissolves
Several things get mistaken for assertiveness and produce the opposite result.
Saying whatever you feel, immediately, at full volume
Saying what you need, deliberately, at a chosen time
Getting the outcome you asked for
Making the ask clearly — the outcome is not yours to control
Never backing down
Being able to hear no without it becoming a referendum on the relationship
Explaining until they agree
Stating once, clearly, and tolerating the silence afterwards
Assertiveness is usually taught as a communication skill, which understates the difficulty. For people living with borderline personality disorder, the obstacle is rarely not knowing the words. It is that a no can register as abandonment rather than as a scheduling problem, and a request made while braced for abandonment tends to arrive as pressure however carefully it is phrased.
This is why deciding your response to a refusal before you ask matters more than the wording. If no is unsurvivable, the other person will feel it — the ask carries an unspoken second clause, and they will respond to the second clause. If no is survivable, the same words land completely differently.
Hinting and testing both persist because they seem safer. A hint that is missed can be reframed as never having been a request; a test that is failed produces information without requiring exposure. Both avoid the vulnerability of an explicit ask, and both reliably produce the outcome they were meant to prevent.
The guide treats assertiveness as part of interpersonal effectiveness rather than as confidence-building. The relevant question is not whether you feel brave enough to ask, but whether the request is specific, addressed to someone who can grant it, and made in a form that permits a real answer.
A request only becomes an ask when no is an available answer.