Household org chart: butler, house manager, chef, security, PA

A UHNW home without an org chart still has an org chart. It is just informal, contradictory, and rewritten every time a strong personality has a bad day. The chef believes the kitchen is a kingdom. Security believes every other department is a threat vector. The personal assistant believes they speak for the principal in all things. The house manager believes vendors answer only to them. The butler believes standards are their private religion. None of these beliefs are crazy in isolation. Together, without architecture, they produce turnover, leakage, and a principal who becomes the unpaid referee of domestic politics.

This post is a practical architecture guide: how to place butler / estate leadership, house management, chef, residential security, and personal assistant (PA) into a coherent system. Titles vary. Functions do not. Your job is to make interfaces explicit so excellence in each lane does not become warfare at the borders.

Design principles before boxes and lines

1. One household operating lead

Someone must own the integrated residence experience. Often that is an estate manager or senior house manager. In smaller homes, a modern butler-manager hybrid. In larger compounds, an estate manager with department leads beneath. If everyone “sort of” leads, the principal leads by escalation — the worst design.

2. Separate personal bandwidth from property bandwidth

A PA who manages the principal’s calendar, travel, correspondence, and project follow-ups should not also be the de facto facilities manager. Likewise, an estate manager should not become the principal’s shadow executive assistant simply because they are competent and nearby. Blurring these lanes burns people out and hides true workload.

3. Security is a partner, not a servant caste — and not a parallel monarchy

Residential security must have authority over access protocols and emergency response. It should not casually overrule hospitality standards without a defined escalation path, nor be sidelined as “the guys at the gate.” Write the partnership.

4. The kitchen is a department with a customer

Great chefs need creative and operational ownership of food programs. They do not need veto power over family health requirements, guest constraints, budget reality, or security screening of deliveries. Clarify the customer: the family.

5. Paper beats memory

If a rule lives only in one person’s head, you do not have a standard. You have a single point of failure.

Reference org chart A — Lean primary residence (roughly 4–8 staff)

Principal / family
→ Estate manager or butler-manager (household lead)
→ Housekeeping lead / housekeepers
→ Chef or cook (may be full-time or high-day-rate hybrid)
Driver / caretaker as needed
→ Outside vendors (pool, landscape, HVAC) coordinated by household lead

Parallel / dotted:
→ Personal assistant (reports to principal; coordinates with household lead on calendar-driven home needs)
→ Residential security (may be contracted; liaison to household lead for guest lists and vendor windows)

Family office / outside counsel-payroll supports compliance and payments; does not run napkin folds.

This design keeps a single operating brain in the house while protecting the PA’s focus and giving security a clean liaison.

Reference org chart B — Formal household with entertaining (roughly 8–20 staff)

Principal
→ Estate manager (COO of residence)
→ Butler / service lead (front-of-house, service standards, guest choreography)
House manager (back-of-house ops, maintenance, inventories, vendor management) — in some homes these two roles merge; in busy formal homes they split
→ Executive chef → sous / kitchen team
→ Housekeeping manager → housekeepers, laundry
→ Service staff (servers, housemen) under butler on event days
→ Grounds / facilities as staff or vendor-led

Principal’s office
→ Personal assistant / EA (calendar, travel, correspondence, project tracking)
→ Possibly a second PA for family branch or next-gen

Protection
Security director or lead agent → agents / gate / CCTV monitoring partners
→ Dotted line coordination with estate manager for access and events; solid line to principal or family security committee for protective strategy

This is where written swimlanes save marriages and Christmas.

Reference org chart C — Multi-property circuit

Add a layer:

Family office lifestyle / operations lead (or private COO)
→ Estate manager Home A
Estate manager Home B / seasonal opener
→ Traveling staff pool (chef, nannies, security detachments) scheduled against the principal’s calendar
→ Centralized vendor contracts and standards manual

Without the central layer, each home invents its own civilization. With a heavy-handed central layer that ignores local reality, you get compliance theater and quiet rebellion. The art is shared standards with local execution authority.

Role briefs that prevent border wars

Household lead (estate manager / butler-manager)

Owns: staff scheduling across departments (except security duty rosters if separate), service standards, vendor performance, residence budgets in partnership with the office, event operations, property readiness.
Does not own: principal’s corporate work product, protective strategy decisions, legal judgments, tax decisions.
Key interfaces: daily/near-daily with PA on calendar implications; weekly with security lead on access and threats; weekly with chef on menus and ordering windows.

Butler / service lead (when split)

Owns: front-of-house standards, table service, wardrobe systems if in scope, guest flow, ceremony.
Does not own: capital projects, HVAC strategy, security post orders.
Failure mode: becomes a critic of all other departments without operational empathy.

House manager (when split)

Owns: maintenance calendars, inventories, vendors, home systems, sometimes housekeeping.
Does not own: formal service choreography unless cross-trained and mandated.
Failure mode: optimizes the building while the hospitality experience degrades.

Executive chef

Owns: culinary program, kitchen hygiene, kitchen staff, ordering within budget, dietary execution.
Does not own: unrestricted budget, unvetted delivery access, family nutrition policy set in isolation.
Failure mode: genius on the plate, chaos on cost and collaboration.

Personal assistant / EA

Owns: principal time, travel logistics, information flow, follow-ups, often family calendar coordination.
Does not own: becoming secret chief of staff for the entire estate by default.
Failure mode: issues household orders without consulting the household lead, creating dual command.

Residential security lead

Owns: access control, protective routines, emergency response, incident reporting, screening standards.
Does not own: aesthetic veto over all hospitality, or surveillance culture that destroys household trust.
Failure mode: either swaggering overreach or learned helplessness when principals want exceptions every hour.

The interface map (use this as a wall document)

Situation	Primary owner	Must consult	Escalate to
Dinner party for 18	Household lead + butler	Chef, security, PA	Principal for guest list / sensitivities
Last-minute overnight guest	PA (info) + security (access)	Household lead	Principal if policy exception
Kitchen vendor delivery	Chef	Security screening; household lead for timing	Security lead if anomaly
Principal travel week	PA	Household lead (close-up or traveling staff); security	FO for budget / aviation if needed
Staff conflict across departments	Household lead	HR/FO counsel as needed	Principal only if unresolved
Alarm / medical / intrusion	Security	Household lead for family care logistics	Principal / FO crisis protocol
Capital repair in primary suite	House/estate manager	PA (calendar), security (access), principal (taste)	FO for spend authority

If a recurring situation is not on your map, add it after the next incident. Doctrine should be written in calm, not invented in adrenaline.

Cadence: the meetings that keep the chart alive

Daily (15 minutes, household lead + relevant dept leads): today’s calendar, arrivals, sensitivities, maintenance intrusions, menu confirms, security notes.

Weekly (30–45 minutes): staffing two weeks out, budget flags, vendor issues, upcoming events, lessons from last week. PA and security lead attend or send notes.

Monthly with family office: payroll exceptions, overtime trends, contract renewals, incident summaries, capital calendar.

Quarterly with principal: taste and standards review, headcount, major entertaining roadmap, what to stop doing.

Skip meetings and you will rebuy them as emergencies.

Headcount planning: avoid both skeleton crews and palace bloat

Ask:

• What must be covered 7 days a week versus 5?
• What is event-driven surge versus baseline?
• Which roles are resident versus traveling?
• Where does overtime indicate understaffing rather than poor scheduling?
• Which vendors should remain vendors (specialized, episodic) versus converted to staff?

A useful steward metric is overtime plus agency temp spend as a percentage of baseline payroll. Chronically high percentages often mean the org chart is lying about true labor need.

Scored diagnostic: is your household org healthy? (0–2 each, 20 max)

1. Written org chart exists and matches reality.
2. Single household operating lead is clear to all staff.
3. PA and household lead have a defined interface (not improvisation).
4. Security protocols are written and trained, including exception handling.
5. Chef has budget and ordering rules that are followed.
6. Staff know who can hire/fire them.
7. Event ownership is assigned before invitations go out.
8. Dual-command incidents are rare and corrected when they occur.
9. Cross-training exists for critical coverage (without pretending everyone can do everything).
10. Principals escalate through the chart rather than creating side deals with favorite staff.

16–20: durable system. 11–15: tighten interfaces. 0–10: you have talented people trapped in a bad design.

Illustrative failure patterns (labeled)

Dual command. The PA tells housekeeping to reopen a closed wing for a relative; security has it locked for a threat condition; the household lead hears last. Result: staff choose loyalty based on who yelled last.

Kitchen sovereignty. Chef bans security from delivery protocols as “insulting.” A package process becomes informal. Risk accumulates invisibly until it does not.

Lead without lieutenants. Estate manager refuses to develop a deputy. Standards collapse on their leave. Principal concludes “staff these days” — misdiagnosing a succession failure.

Chart as decoration. A beautiful org chart PDF exists in the family office data room. Nobody on property has seen it. Culture follows hallway power, not the PDF.

Building the chart with humans you already have

You may not be hiring from scratch. Map current people to functions honestly:

• Who actually runs mornings?
• Who do vendors call?
• Who does the principal text at 11 p.m.?
• Who mediates chef vs housekeeping?
• Who trains new hires?

Then decide whether to retitle, rescope, upskill, add a seat, or separate someone kindly. Reorgs that ignore informal power create shadow governments.

When changing reporting lines, announce once, in person, with the org chart and decision-rights one-pager. Then refuse to entertain private renegotiations for thirty days unless safety requires it. Consistency is kindness in disguise.

RACI in the residence (keep it human)

Corporate RACI charts can feel sterile in a home. Use a lighter version anyway. For each recurring process — morning open, school run handoff, dinner service, event, property close, travel week — note who is Responsible (does the work), Accountable (owns the outcome), Consulted, and Informed.

Example: Family travel week
- Accountable: PA for itinerary integrity; household lead for property state and traveling domestic staff.
- Responsible: drivers, packing support, security advance, chef for travel food plan if any.
- Consulted: security lead on routes and sites; estate manager on which staff travel.
- Informed: family office on costs and insurance notifications as needed.

When two people both believe they are Accountable, you do not have redundancy. You have a future argument. Pick one Accountable name per outcome.

Coverage and succession: the deputy problem

Org charts die on Sundays and in August. Design coverage explicitly:

• Who is acting household lead when the lead is off?
• Who covers the chef’s off days without lowering safety/hygiene standards?
• Who holds temporary authority for vendor emergencies after midnight?
• What does “security minimum staffing” mean in numbers, not vibes?

Pay acting differentials when people step up. Unpaid endless acting duty is how you train deputies to quit.

Succession is not only for principals’ estates. It is for households. A deputy development plan — shadow weeks, documented SOPs, one event fully led by the deputy — should be a quarterly agenda item for any household above lean size.

Comp architecture across the chart (alignment, not twin salaries)

Different roles sit in different markets. Do not force false equality; do force transparency of philosophy:

• Household lead compensation should reflect leadership burden and scarcity.
• Chef compensation should reflect skill and hours, with clear overtime or alternative structures lawful in your jurisdiction.
• Security compensation should reflect training, risk, and schedule burden — underpaying protection is not thrift.
• PA compensation should reflect proximity to principal decision flow and after-hours reality.

Bonuses work best when tied to measurable stewardship: retention of key staff, overtime reduction via better scheduling, zero serious safety incidents, budget variance within agreed bands, successful major events. Avoid bonuses that reward secrecy or principal favoritism Olympics.

Information walls that protect dignity

An org chart should include information boundaries:

• Security need-to-know versus household gossip risk.
• PA access to sensitive principal communications versus what house staff require.
• Chef knowledge of dietary/medical constraints versus full medical files.
• Family office payroll data versus peer curiosity.

Brief staff that curiosity is not a job requirement. Curiosity without mandate is how NDAs get tested.

Onboarding a new node without destabilizing the chart

Every new hire — especially a senior one — should receive:

1. The org chart and decision-rights one-pager on day one.
2. Introductions in reporting order (not only a cheerful blur of names).
3. A 30-day “observe then adjust” rule for proposing process changes.
4. Clarity on what legacy practices are sacred versus open for improvement.

Principals should avoid anointing a newcomer as “the new sheriff” in a way that humiliates incumbents. Change the system with dignity, or the system will reject the change.

When to split a role versus hire a “unicorn”

Families often hunt a single human who is world-class butler, ruthless operator, gifted chef liaison, security-fluent, and PA-compatible. That unicorn search can take eighteen months and still fail.

Split when:

• Entertaining volume and property complexity are both high.
• The principal’s PA load is itself a full job.
• Security is truly protective, not merely gate ornament.
• You have been “almost hired” three times and each finalist lacked a different critical limb.

Unicorns exist. Betting the household on finding one by Friday is not a strategy.

A one-hour workshop to rebuild your chart

If your household is already mid-chaos, do not start with new hires. Start with a workshop.

Invite: principal (or designated decision-maker), household lead, PA, security lead, chef, and family-office ops contact.

Agenda:
1. Each person writes what they believe they own (10 minutes, silent).
2. Place sticky notes on a printed draft chart; mark conflicts in red (15 minutes).
3. Resolve the top five conflicts into written decision rights (20 minutes).
4. Assign cadence owners for daily/weekly/monthly meetings (10 minutes).
5. Agree on a 30-day communication rule: no side deals that bypass the chart (5 minutes).

Leave with a one-page chart, a one-page interface map, and a date to review. Then socialize it to the wider staff with the household lead speaking, not only the principal. Authority transfers better when the operating lead carries it.

Closing: architecture is hospitality

A household org chart is not bureaucracy for its own sake. It is how you protect the soft goods money cannot repurchase easily: trust among staff, predictability for children, dignity for long-serving team members, and uninterrupted focus for the principal. When the chart is wrong, those goods erode first — long before the financial statements show a problem.

Guests experience warmth. Principals experience quiet. Staff experience clarity. Those outcomes are not primarily about nicer flowers. They are about whether roles, authority, and interfaces were designed like an operating company — because that is what a complex household is.

Place your butler or estate lead, house manager, chef, security, and PA in a chart that tells the truth. Give them cadence. Give them swimlanes. Then let specialists excel without forcing the principal to referee the borders.

If you do only one thing after reading this, print the real org chart, walk it through the kitchen and the security office the same day, and invite corrections from the people who actually run mornings. The chart that survives contact with the staff break room is the only chart that counts. Everything else is stationery pretending to be management — and staff can tell the difference immediately, usually before the ink on the org-chart PDF is even fully dry.

---

Related reading and tools live on the Books and Resources pages. Educational only — not legal, tax, or investment advice for your situation.