The short answer
When a lateral department manager attempts to task your administrative staff directly with an urgent logistical request, you are facing a severe breach of operational boundaries. You must intercept this request immediately before your executive assistant begins processing it. Your primary directive as a frontline manager is to protect the bandwidth, focus, and strategic alignment of your direct reports. Allowing lateral managers to bypass your reporting lines turns your specialized team into a generic concierges service for the entire company.
You must step in and formally redirect the request back to the requesting manager. You cannot allow the urgency of their poor planning to dictate the workload of your staff. If their consultants need international flights by noon, that is a failure of their departmental foresight. It is not an emergency that requires your team to drop their core executive support functions. You will define the boundary, state the intake protocol, and force the peer manager to utilize standard corporate resources.
By executing this interception, you establish yourself as a protective shield for your team. You train the broader organization that administrative support is a finite, highly governed resource tied to specific executive priorities, not an open-access helpdesk. You must hold the line with absolute professional detachment.
Why this question is a trap
The trap relies entirely on the engineered urgency of the request. The peer manager is weaponizing a tight deadline (noon today) to bypass normal bureaucratic friction. They approach your assistant directly because they know assistants are generally conditioned to be helpful, accommodating, and service-oriented. The peer manager is intentionally exploiting this service mentality to offload their own logistical burden onto your headcount.
If you allow your assistant to execute the booking, you instantly establish a toxic precedent. The peer manager learns that your team is available for ad-hoc tasking. Next week, they will return with catering requests, meeting scheduling, and expense reporting. Other lateral managers will observe this dynamic and begin routing their overflow administrative work to your desk. Your team will become hopelessly backlogged, and your core responsibility (supporting your assigned executives) will suffer. When your actual executives complain about degraded service, the peer manager who hijacked your team will not step in to defend you. They will simply take their bookings and leave you to face the consequences.
This interaction is a direct test of your managerial spine. The peer manager is checking to see if you actually control your department or if your staff can be easily poached for free labor. Giving in to avoid a minor conflict today guarantees a systemic failure of your department's operating model tomorrow.
What most people say
Most newly promoted support managers react passively and try to accommodate the request to maintain a friendly office culture. They might say, "We are really busy with the Q3 board prep right now, but I guess we can squeeze this in just this once. Next time, please try to give us a little more notice."
This response is an absolute failure of leadership. By agreeing to do the work "just this once," you completely validate their bypass of your authority. You teach them that your boundaries are fake and that your complaints about being busy do not actually stop you from doing their work. Pleading for more notice in the future sounds like a weak request rather than a firm operational policy. The peer manager will ignore your plea and continue to dump last-minute work on your team because you have proven that complaining is the only resistance you will offer.
What to say instead
"My team is fully dedicated to executive support priorities this morning. All ad-hoc departmental travel must go through the centralized workload queue for review, or your team can book those consultant flights directly through the corporate travel portal right now."
This script shuts down the lateral tasking immediately and permanently. You begin by stating a hard fact regarding your team's current allocation. By saying your team is "fully dedicated to executive support priorities," you raise the status of your team's current work. You make it clear that dropping current tasks to book their flights would mean actively ignoring executive mandates.
You then introduce the structural barrier. By explicitly naming the "centralized workload queue," you remove the personal element from the refusal. It is not that you dislike the peer manager; it is that their request failed to follow the established intake protocol. You force them to deal with a system rather than an individual.
Finally, you offer a resolution that requires zero effort from your team. You direct them to the corporate travel portal. This proves that you are not trying to sabotage their consultants. You are simply pointing them to the correct, self-service tool that exists for exactly this reason. You give them a path to solve their own problem without spending a single minute of your assistant's time.
The phrase to anchor on
Must go through the centralized workload queue.
How to deliver it
Deliver this response with crisp, unyielding professionalism. If the peer manager is standing at your assistant's desk, you must physically stand up, approach the desk, and insert yourself into the conversation. You are the manager. You intercept the threat.
Maintain direct eye contact with the peer manager, not your assistant. Your voice should be even and entirely devoid of apology. Do not soften the delivery with a smile. Treat this interaction exactly as you would treat a vendor trying to bypass a procurement process. Once you deliver the script, turn your attention back to your own work, signaling that the conversation is permanently closed and no further debate will be entertained.
Mistakes that cost you the room
The most damaging mistake you can make is asking your assistant if they have time to do it. If you turn to your assistant and ask, "Do you think you can fit this in before noon?", you completely abdicate your role as a manager. You force your subordinate to be the bad guy and say no to a senior person, or you force them to accept the extra work out of fear. You must make the decision and enforce the boundary yourself.
Another critical error is arguing about the importance of the consultants. Do not engage in a debate about whether these six consultants are critical to the business. The priority of their travel is irrelevant to your department's reporting lines. Stay entirely focused on the intake protocol and your team's capacity limits.
Finally, do not offer to do the booking yourself to spare your assistant. While this protects your team in the short term, it severely degrades your own status. You are a frontline manager, not a backup travel agent. If you do the work yourself, the peer manager still wins the resource battle, and you look like a leader who cannot delegate or prioritize effectively.
Practice plan
First, physically rehearse stepping in front of an imaginary desk. You need to train your body to move toward the conflict rather than shrinking away from it in your chair.
Second, memorize the specific name of your intake protocol (whether it is a ticketing system, an email alias, or a formal request form). You must be able to cite the exact name of the system without hesitating.
Finally, run the drill in the Talk Rightly studio. Focus heavily on keeping your vocal register flat and authoritative. Eliminate any upward inflection at the end of your sentences that makes your refusal sound like a question.