You do not have to replace the team your executive trusts. You do have to be precise about who is responsible for what.
The memo from outside counsel ran four pages. The chief security officer read it twice, then a third time, looking for the paragraph that would let him not do what it said.
The trip was in eleven days. Dallas, then Houston, back Thursday. The same three men who had traveled with the chief executive since 2019 — through London, Zurich, two evacuations, one hospital. The CEO knew their children’s names. One of them had driven his mother to a funeral.
What the memo said was that the arrangement, as constituted, did not work in Texas.
What the memo did not say was what to do instead. That was the CSO’s problem, and he had until Friday.
The two answers, and the cost of each
When the licensing question finally surfaces inside a company — usually because counsel was asked something adjacent and pulled the thread — it tends to get resolved one of two ways. Both are expensive. One of them is expensive in a way nobody notices until much later.
The first answer is to run the trip anyway. It has worked before. Nothing has happened. The team is excellent, the exposure is theoretical, and the trip is in eleven days.
This is the answer that produces a record. We’ve addressed that exposure separately — what Texas actually requires, which exemptions don’t reach a visiting detail, and why the statute reaches the party who contracts for the service rather than only the party providing it — in When the Detail Lands in Dallas. The short version is that the theoretical quality of the risk is a function of nothing having happened yet, and that the analysis changes the moment something does.
The second answer is to replace the detail for the Texas legs. Counsel says the current team can’t perform the work. A licensed Texas firm can. Engage one, stand the regular team down, run the trip, bring everyone back on Friday.
This is the answer most companies reach, because it is the answer that looks responsive. It resolves the compliance question cleanly and it can be executed in eleven days.
It is also the answer that quietly destroys the most valuable thing in the program.
What the trusted detail actually knows
A protective program is not a set of procedures. It is a set of procedures plus everything the people executing them have learned about one specific person over a period of years.
Which entrance he will actually use, as opposed to the one on the itinerary. That he goes quiet ninety minutes before he speaks and should not be addressed during that window. That his back is worse than he admits and a long stair approach will cost him. What his wife looks like when she wants to leave. Which of his colleagues can be trusted with a room and which cannot. How he behaves when he is frightened, which is not how most people behave when they are frightened.
None of this is in a briefing document, because most of it has never been articulated. It exists as judgment in the people who acquired it.
A replacement detail, however well licensed and however capable, performs a two-day trip from a written summary. That is not a criticism of the replacement detail. It is a description of what a two-day engagement can and cannot include. The company has solved a compliance problem by removing, for the duration of the trip, the accumulated knowledge that made the program effective in the first place.
And it has done so at the moment of highest exposure — travel — which is where most of the risk in a protective program lives.
There is a second cost, less visible. The detail leader who has been quietly managing this gap for years now watches his team stood down as the resolution. The next time he identifies a problem in the program, he will weigh what raising it cost him last time. That is a governance failure, and it will not show up in any register.
The structure that resolves it
The replacement answer treats two separate things as one thing. Once they are separated, the problem becomes ordinary.
The regulated work is one thing. Armed protective service performed in Texas must be performed by individuals licensed in Texas, employed by a company licensed in Texas. That requirement is not negotiable, and no contract term relaxes it. It is not a matter of who is more qualified — the visiting team may well be more qualified — it is a matter of what the state licenses.
The relationship is a different thing entirely. Protectee-facing authority, program standards, the itinerary, the accumulated judgment described above, the person the protectee looks to when something feels wrong — none of that is regulated by anyone. It belongs to the visiting detail leader, and there is no legal reason for it to move.
So it doesn’t move. The visiting detail leader travels. He retains his relationship with the protectee, his program standards, and his authority over how the visit is conducted. He is present, he is in the room, and from the protectee’s perspective very little has changed.
What changes is that the protective work regulated by Texas is performed by Personal Protection Officers employed by a Texas-licensed company, and those PPOs are supervised by the company that employs them.
That last clause is the entire article, and it is the part that gets fudged.
Why the line has to be drawn precisely there
The reason a company wants a licensed program in the first place is that accountability attaches somewhere legible. The employer hires, trains, supervises, disciplines, and answers for the conduct of its employees. That is what makes the arrangement defensible: there is a named entity with a duty and the ability to discharge it. It is why the distinction between employees and contractors matters, and why it is worth paying for.
Now consider the version of this arrangement that sounds more accommodating — where the visiting detail leader “retains command” of the licensed PPOs and directs their protective conduct on the ground.
Ask who answers for a PPO’s use of force under that arrangement. The company that employs, trains, and licenses him, but did not direct him? The visiting firm that directed him, but does not employ him, cannot discipline him, and is not licensed in the state? The client who engaged both?
The honest answer is that it becomes a question rather than an answer. And a question is precisely what the company was trying to buy its way out of. An arrangement that blurs supervision to make a vendor relationship feel more comfortable has reintroduced the exposure the whole exercise was meant to close — while feeling, to everyone involved, like the accommodating solution.
So the line is drawn where the law draws it. Supervision of licensed personnel stays with the licensee. Protectee-facing authority and program continuity stay with the visiting leader. Both roles are real. Neither is ceremonial. And each one is answerable for something specific, which is the only condition under which a program survives being examined.
This is not a workaround. It is what the arrangement actually is, written down accurately.
What the agreement should say
A general counsel reviewing this arrangement has five things to establish, and all five belong in the document rather than in an understanding between professionals.
The performing entity is named, and it holds the license. The party performing regulated protective work in Texas is identified by name and license number, and is a party to the agreement — not a reference in a schedule.
Supervision is stated, not assumed. The agreement says that direction, supervision, and discipline of the licensed personnel remain with their employer. This is the clause that does the work, and its absence is what creates the ambiguity described above.
The visiting firm’s role is defined affirmatively. Program continuity, protectee liaison, standards, itinerary authority. Written down, so that “retains command” never has to be interpreted after the fact by someone with an incentive to interpret it a particular way.
Subcontracting requires written consent. Otherwise the diligence performed on one company describes people employed by another, and the company has a contractual relationship with one entity and a duty-of-care relationship with a set of strangers.
Personnel are employees, not contractors, and the certificate of insurance names the performing entity. The insured on the certificate should be the party on the agreement and the employer of the people in the vehicle.
None of this is exotic. It is the ordinary discipline a company applies to any vendor whose conduct it will answer for. It is unusual in this category mainly because the category has not historically been contracted for with much rigor.
The CSO made the call on Thursday afternoon.
He told the detail leader Friday morning.
The man had been carrying the question for years without raising it. He had reasons, and did not offer them.
He asked one thing — whether he was still traveling.
He was.
General information, not legal advice. Structures like this turn on specific facts and specific contract language; engage Texas counsel for yours.
Questions we’re asked
Do we have to replace our executive’s protective detail when they travel to Texas?
No — and replacing them is usually the more expensive answer, because it removes years of accumulated knowledge about one specific person at the moment of highest exposure. What has to change is who performs the work Texas regulates. Your detail leader travels, retains the protectee relationship, and retains authority over how the visit is conducted. Licensed Texas PPOs, employed and supervised by a Texas-licensed company, perform the regulated protective work. From the protectee’s perspective, continuity holds.
Can our regular detail leader still run the program in Texas?
He runs the program. He does not supervise the licensed personnel — their employer does, because that is what makes accountability attach cleanly if anything is ever examined. In practice this is a narrower change than it sounds: itinerary, standards, protectee liaison, and the judgment calls that come from knowing the person all stay with him. What moves is direction and discipline of the licensed PPOs, and it moves because leaving it ambiguous is what creates exposure.
Who is liable if something happens during the Texas legs?
That depends on the facts and on what the agreement says, which is exactly why the agreement should say it. The design principle is that each party answers for what it actually controls: the licensed employer for the conduct of the personnel it employs, trains, and supervises; the visiting firm for the program decisions it makes; the company for the reasonableness of its vendor selection. Arrangements that blur those lines to feel more collaborative are the ones that produce the worst outcomes when examined. Your counsel should review the allocation against your specific exposure.
What should be in the agreement?
At minimum: the licensed performing entity named as a party; an express statement that supervision and discipline of licensed personnel remain with their employer; an affirmative description of the visiting firm’s role; a prohibition on subcontracting without written consent; and a certificate of insurance naming the performing entity. The subcontracting clause matters more than it appears to — without it, the diligence you performed may describe a different set of people than the ones who arrive.
Does this work for a single trip, or only an ongoing program?
Both, though they are contracted differently. A single visit can be handled under a scoped engagement. A protectee who travels to Texas regularly is better served by a standing arrangement, because the licensed team accumulates its own familiarity across visits — which narrows the gap that made replacement costly in the first place. Companies with recurring Texas exposure generally find the standing version cheaper and materially better.