Most conversations about close protection focus on the principal and the security team, as if the two operate in isolation. In practice, a family engagement in Morocco almost always includes a third layer: household staff. A nanny handling the children's routine, a personal assistant managing the itinerary, a private chef, a driver already familiar with the family's preferences. None of them are part of the security detail, but all of them are inside the operating envelope of one — and treating that layer as an afterthought is one of the more common gaps we see when we take over a poorly planned trip.
Two Very Different Kinds of Staff
The first distinction that matters is where the staff came from. Staff a family brings with them — a long-serving nanny, a PA who's worked for the principal for years — are usually already vetted in the sense that matters most to the family: the employer trusts them completely, knows their habits, and has years of working history to draw on. What they don't have is familiarity with Morocco. They don't know which neighborhoods a school run should avoid at certain times, how a hotel's back-of-house delivery access works, or what "normal" looks like on a Marrakech street versus something worth flagging. That's a briefing gap, not a trust gap, and it's solvable with a proper security orientation before the trip starts.
Staff that come with a rented property are the opposite case. A villa booked for a two-week stay often comes with its own housekeeper, gardener or on-site caretaker — people the family has never met, didn't hire, and knows nothing about beyond what the rental agency or previous guests have said. These are the people who often have the property's keys, alarm codes and layout memorized long before the family arrives. From a security standpoint, that's a population that needs its own vetting pass — background checks, a conversation about who they report to during the stay, and a clear understanding of what access they retain once the family is on-site — handled the same way we'd approach it for a longer-term residential security engagement, just compressed into the run-up to a shorter visit.
Integrating With Staff, Not Working Around Them
A close protection team that treats existing household staff as background noise ends up duplicating effort, working with incomplete information, or — worse — creating friction that undermines the operation. The better model is integration from the outset:
- A briefing for household staff on the security protocols in place for the stay — not just for the protection team's own procedures
- Shared schedules, so a nanny's school run or a chef's market visit is planned alongside the detail's movements, not discovered after the fact
- A clear, written answer to who has access to the property and when — staff, deliveries, contractors — rather than an assumption that everyone already knows
- A single point of coordination between the household and the security team, so instructions don't arrive from two directions at once
Take a nanny doing a school run in Casablanca or Rabat. If the security team hasn't been told the route, the timing or which entrance the children use, that's a daily gap in coverage that has nothing to do with the quality of the detail and everything to do with poor coordination. The fix isn't putting a bodyguard in the car for every errand — it's making sure the person already doing the errand knows the basic protocols (which route to favor, what to do if the plan changes, who to call) and that the detail knows her schedule well enough to notice if it changes unexpectedly.
Confidentiality Runs Both Ways
Families often think carefully about what the security team is allowed to know, and less about what household staff end up knowing simply by being present. A private chef receiving grocery and specialty deliveries at the villa gate sees who comes and goes. A PA managing the day's calendar knows the family's location at every hour. A nanny hears conversations in the car that were never meant for her. None of that is a criticism of the staff — it's simply a description of proximity — but it means the same need-to-know discipline that applies to the protection team has to extend to household staff as well: what gets shared with whom, what stays inside the family, and what a driver or housekeeper should say if asked about the family's whereabouts by someone outside the household.
This matters most when staff and security answer to different people. A driver who's worked for the family for a decade and a close protection lead who's been on the ground for three days need an explicit, not assumed, agreement on where authority sits during the trip — particularly if a security decision (delaying a departure, changing a route) runs against what household staff were originally told to expect.
Building This Into the Trip From the Start
The families who avoid friction on this front are the ones who raise it early, during the same risk assessment conversation that shapes the rest of the detail — not as a side issue once the team is already on the ground. It's a natural fit for the broader planning that goes into private client engagements, and it's a theme that shows up just as often in Gulf family travel to Morocco, covered in more depth in our piece on planning security around Gulf family visits. Household staff aren't an obstacle to a security plan — they're part of the environment it has to work in, and the plans that account for them from day one are the ones that run quietly.