There is a moment most managers recognize: someone on the team raises something important right before a meeting starts. You are already mentally in the next room. You nod, or half-answer, or say "let's talk about this later", and later never quite arrives.

If it happens once, it is a coincidence. If it happens regularly, with the same person, around the same kinds of requests, it is something else.

It is a pattern. And patterns are not neutral.

What this specific pattern does is structurally remove the possibility of a real response. The request arrives in a window where engagement is impossible. The manager cannot say no thoughtfully, cannot ask questions, cannot push back, cannot even fully process what was asked. The timing creates a kind of conversational fait accompli: the request has been made, the manager has been placed in a position where any reaction other than vague acknowledgment feels disproportionate, and by the time there is space to think, the moment has passed.

Whether this is intentional is almost beside the point. What matters is that it works. Requests made in these windows tend to get a yes, or at least not a no. And that outcome, repeated enough times, reinforces the behavior.

For the manager, the effect is accumulation. Mild irritation after the first time. Frustration after the fifth. A creeping doubt about the relationship itself, is this person being strategic? Are they avoiding real conversation? The irritation is not irrational. It is information. Something is not working in how communication moves in this relationship.

The pattern is the message, and ignoring it is also a message.

If a manager continues to receive requests in this format and continues to respond to them anyway, even positively, they are communicating, without words, that this is an acceptable way to operate. The implicit norm gets set. And once a norm is set through repetition, changing it requires much more than it would have taken to set it differently from the start.

This is where the manager's responsibility lands. Not in the individual request, whether to approve the day off, or respond to the information shared, but in the pattern itself. The conversation that needs to happen is not about the content of any specific request. It is about the form: what it means to communicate in a relationship where both parties actually have room to respond.
That conversation does not need to be heavy. It does not need to be a formal feedback session. It needs to happen close to the moment, the next day, ideally, while the example is still concrete, and it needs to name what is happening without dramatizing it. Something in the direction of: I notice that certain things tend to come up right before I am unavailable. I want us to find a better way to have those conversations, because I would like to actually have them.

What is being asked for is not compliance with a rule. It is a different kind of relationship. One where a request can be made when there is time to hear the answer. Where disagreement is possible. Where the outcome is not pre-empted by the timing.

If that kind of communication feels risky to a team member, if catching someone right before a meeting is a way of minimizing exposure to a real response, that is worth understanding. The pattern might be pointing at something in the relationship the manager has not yet seen clearly.
But you cannot start to understand any of that if you do not name what you are observing.