When they ask for a favour

Stage 3 · A year and beyond · Article 91 · Wave 3

---

The Co-Parent asks for something that isn't in the agreement. To swap a weekend. To pick up the children early. To cover an evening that was supposed to be yours. To lend something. To watch the pet. To attend something. The request is reasonable. It's also a category of interaction that didn't exist for the cooler version of the channel you've built. And how you respond shapes whether favours become part of the new normal or stay rare.

This article covers what favour-asking actually means in Stage 3, the four types of requests and how to evaluate them, when to say yes, when to say no, how to do either cleanly, and what to do when the favours become asymmetric.

What favour-asking actually means in Stage 3

In the marriage, favours weren't really favours. The two of you were running shared logistics with shared responsibility. Asking the other person to handle something wasn't a favour; it was task distribution.

Post-separation, that changes. Each of you runs your own logistics. The other person handling something isn't task distribution anymore; it's discretionary help. The same request that used to be routine now requires explicit asking and explicit deciding.

Three things this shift means.

1. The asking carries weight it didn't used to. The Co-Parent asking for help has had to choose to ask. The choice isn't trivial, the cooler channel makes asking slightly uncomfortable. When they ask, they're crossing a small threshold.

2. The answer carries weight too. Your yes or no isn't routine the way it was in the marriage. It's a small statement about the relationship the two of you are building post-separation. The statement doesn't have to be huge, but it isn't nothing.

3. The pattern of asking and answering becomes part of the channel. Across years, the favour pattern shapes whether the channel is functional, generous, transactional, or grudging. The individual decisions are small; the cumulative pattern matters.

The shift is real. It doesn't mean every favour has to be analysed deeply. It does mean the favour-channel deserves some thought.

The four types of requests

Not all favour-requests are the same. Four common types, each with different evaluation.

Type 1: Genuinely mutual

Something that benefits both of you. Can we swap weekends, works better for both our schedules. The favour is in form only; the actual benefit is shared.

How to evaluate: usually say yes. These are the easiest. They're the kind of cooperative logistics that healthy co-parenting includes. Saying no to mutual benefit is usually about the channel's emotional weight, not the request itself.

Type 2: Their need, low cost to you

Something they need that's not a big deal for you to provide. Can you take the children Friday evening, my work has run over. Yes if you're available and willing; no if you're not.

How to evaluate: yes is the easy answer when you actually can. The check: would you do this for a colleague or family member? If yes, do it for the Co-Parent unless there's a specific reason not to.

Type 3: Their need, real cost to you

Something they need that costs you something significant. Time you'd planned for yourself. A weekend you'd been looking forward to. Effort that's substantial.

How to evaluate: depends on the specific situation. Some of these you do (the Co-Parent's mother is in hospital and they need to fly out). Some you don't (they want a weekend off and you'd been planning a needed quiet weekend yourself).

There's no universal answer. The principle: yours is yours. You're not obligated to give it up. Sometimes you choose to. Sometimes you don't. Both are legitimate.

Type 4: Something that should be covered by the agreement

A request for help that's actually the Co-Parent asking you to do their job. They've forgotten something they should have remembered. They're not available when they're supposed to be. They want you to fill a gap that exists because they didn't fulfil their side.

How to evaluate: case by case, but with awareness that consistent yes-answers to Type 4 requests undermine the agreement. Sometimes the right answer is yes (it's a one-off, the children's needs matter, doing it once is fine). Sometimes the right answer is no (the pattern has become a way of shifting their responsibilities to you).

The distinction matters. Type 4 isn't really favour-asking; it's agreement-erosion via favour-framing. Treat it as the second when the pattern suggests it is.

When to say yes

Five conditions where yes is usually the right answer.

Condition 1: It benefits the children

A swap that gives the children more good time with one parent. A pickup that lets the children attend an event they care about. A schedule shift that aligns with the children's needs.

These are easy yeses. The children's wellbeing is the standard most worth honouring, even when the channel is otherwise cooler.

Condition 2: The Co-Parent has a genuine difficult moment

Illness, family emergency, work crisis, something they couldn't have planned around. Saying yes when they're in a genuinely difficult moment is what reasonable people do for each other, separated or not.

Condition 3: You're available and willing

The basic functional yes. You can do it, it doesn't cost you something significant, the request isn't a pattern of unfairness. The yes builds the channel's functional capacity.

Condition 4: The reciprocity feels possible

A yes you'd be comfortable asking them to match if the situation were reversed. The reciprocity test is: would I feel okay asking them for the same thing? If yes, your saying yes is balanced.

Condition 5: You want to

Sometimes you just want to. The favour will produce a small good outcome, the children will benefit, the Co-Parent will appreciate it, you can. There doesn't need to be a more elaborate reason than that.

When to say no

Five conditions where no is usually the right answer.

Condition 1: It would override something you've genuinely planned

If you've made plans for the time the Co-Parent is asking about, the plans aren't automatically lower priority. You don't owe the Co-Parent your discretionary time.

The plans don't have to be elaborate. I have plans is a complete answer. You don't need to specify or justify.

Condition 2: It's a Type 4 in a pattern

A one-off Type 4 is sometimes worth doing. A repeated Type 4 is the Co-Parent shifting their work to you. Saying no breaks the pattern and is appropriate.

Condition 3: You can't reasonably do it

You're not available. You're sick. You're working. The reasonable practical reasons for no. State briefly, don't justify extensively.

Condition 4: The pattern of favours is already asymmetric

If you've been saying yes for months and they haven't been reciprocating, the channel is becoming one-sided. A no is sometimes needed to recalibrate. The recalibration isn't punishment; it's just rebalancing.

Condition 5: You don't want to

Sometimes you just don't want to. You're tired. You'd rather not. There's no specific reason but the answer in you is no. The honest no is usually better than a yes that costs you more than the favour is worth.

How to do either cleanly

Yes and no both deserve clean execution. Five principles.

1. Respond within a reasonable window

Don't take days. Don't ignore the message. A response within 24 hours is appropriate for most requests.

The waiting often produces more stress for both parties than the answer itself would. Get back to them.

2. Be brief

A yes is yes, that works. A no is I can't do that one. Neither needs elaboration.

Brevity isn't coldness. It's appropriate to the channel's temperature. Extended explanations re-warm the channel beyond what the request requires.

3. Don't justify a no

You don't owe a justification. The reasons are yours. I can't do that one is a complete answer. If they ask why, I have something on is sufficient.

Justifying invites argument. Stating without justification doesn't.

4. Don't accept a yes you don't mean

If you're going to say yes, mean it. A yes you don't mean produces resentment later and erodes the channel.

If you're not sure, ask for time. Let me check and get back to you. Then decide. Then respond.

5. Don't expect gratitude

A yes given is given. If they don't acknowledge it adequately, that's information about them but not a reason to regret the yes. The yes was the right thing for whatever reason it was given.

Expecting gratitude makes the yes transactional. The transactional yes corrodes the channel over time.

When favours become asymmetric

A common pattern. You're saying yes to most of their requests. They're saying no to most of yours, or aren't reciprocating in kind. The favour pattern has become one-sided.

Three things to do.

1. Notice the asymmetry

Count if you have to. Over the last six months, how many favours has each of you asked, how many has each of you granted. The numbers usually clarify the picture.

2. Start saying no more often to non-essential requests

Recalibrate gradually. Don't suddenly refuse everything. Just start declining the requests you'd usually say yes to but don't actually want to.

The asymmetric Co-Parent often calibrates without explicit conversation. Your reduced availability adjusts their expectations.

3. Have the conversation if needed

If the asymmetry doesn't shift through behaviour, name it. I've noticed I'm saying yes more often than you are. I want to find a more balanced pattern. Let's both be more deliberate about asking and answering.

The conversation is direct. It's not blame; it's calibration. Most Co-Parents respond reasonably to this conversation when it's framed without hostility.

If the conversation doesn't produce change, the channel may have a more fundamental imbalance. Article 86 on asymmetric situations covers this in more depth.

When you're the one asking

The article so far has assumed you're the one being asked. You'll also be the one asking sometimes. Four principles.

1. Ask when you actually need to

The grey-rock channel can produce reluctance to ask for anything. The reluctance protects the channel's coolness but can mean you go without help that would be reasonable to request.

Ask when you actually need help. The asking is appropriate.

2. Make the request small and specific

Could you take the children Friday evening so I can attend X? The specific request is easier to evaluate than a vague one.

If they say no, accept it without pressure. The vague follow-up could you maybe figure out a way is unhelpful; the specific no problem, I'll figure something else out is what works.

3. Reciprocate when you can

If they've said yes to recent requests, find opportunities to reciprocate when the situation comes up naturally. The reciprocity doesn't have to match exactly; it just has to register.

The pattern of reciprocity is what keeps the favour channel functional.

4. Don't make the asking emotional content

Don't apologise excessively. Don't explain at length. Don't preface with caveats. Just ask. The clean ask is what fits the channel.

Quick reference

Three things favour-asking means in Stage 3:

1. The asking carries weight (they've chosen to ask).
2. The answer carries weight (it's a small statement about the channel).
3. The pattern becomes part of the channel.

Four types of requests:

1. Genuinely mutual (usually yes).
2. Their need, low cost (yes if available).
3. Their need, real cost (depends; yours is yours).
4. Should be covered by agreement (case by case, watch for pattern).

Five conditions where yes is usually right:

• It benefits the children.
• They have a genuine difficult moment.
• You're available and willing.
• The reciprocity feels possible.
• You want to.

Five conditions where no is usually right:

• It overrides something you've planned.
• It's a Type 4 in a pattern.
• You can't reasonably do it.
• The pattern is already asymmetric.
• You don't want to.

Five principles for execution:

1. Respond within 24 hours.
2. Be brief.
3. Don't justify a no.
4. Don't accept a yes you don't mean.
5. Don't expect gratitude.

When favours become asymmetric:

• Notice the pattern (count if you have to).
• Start saying no more often to non-essential requests.
• Have the conversation if needed.

When you're the one asking:

• Ask when you actually need to.
• Make the request small and specific.
• Reciprocate when you can.
• Don't make the asking emotional content.

Favours are how cooperative channels stay cooperative. Done well, they don't re-warm the channel; they just keep it functional. Done badly, they become either resentments or obligations. The discipline is keeping them what they are.