The operating manual nobody writes

Every well-run private office has an operating manual. Most of them exist only in the head of the person who has been there the longest.

This is not a criticism. It is simply what happens when a role is built gradually, when trust is earned over years, when the knowledge of how things work accumulates through experience rather than documentation. The PA who has been with a principal for a decade holds an extraordinary amount of information. They know which florist, which car, which table at which restaurant. They know what the principal means when they say handle it and what they mean when they say run it past me first.

None of that is written down. And when that PA is ill, or on leave, or moves on, the knowledge disappears with them.

This has always been a vulnerability. It is now also a missed opportunity. Because the operating manual — the document that captures what would otherwise be lost — is increasingly the foundation on which effective AI integration depends.

What goes in it

An operating manual for a private office has two layers. The first is structural — the information that anyone covering the role needs in order to keep things running. The second is preferential — the accumulated knowledge of how the principal likes things done.

Both layers matter for the same reason they have always mattered: continuity. But they now carry additional weight. Every piece of information documented in an operating manual is a piece of context that does not need to be explained again — to a covering colleague, to a new team member, or to an AI partner being asked to help with a task.

The structural layer includes:

Key contacts — who does what, with numbers, emails, and any relevant notes about how they prefer to be approached. An AI working from this does not need to ask who handles the principal's travel, or which solicitor to copy on a particular matter. It already knows.

Regular commitments — the recurring events and obligations that shape the principal's calendar each week and month. With this documented, scheduling support — whether from a person or an AI — can be given without a full briefing each time.

Active tasks — what is currently in progress, what is outstanding, and what is waiting on someone else. This is the live state of the office. Shared with an AI partner, it means any request for a progress update or a next-step recommendation is answered with accuracy rather than assumption.

Access and accounts — not passwords, but a map of what systems exist and where to find the relevant information.

Emergency protocols — what happens if something goes wrong, and who to call first.

The preferential layer is more nuanced and more valuable — and it is where AI integration moves from useful to genuinely capable.

Communication preferences — how the principal likes to receive information, in what format, at what level of detail. An AI briefed on this does not produce a bullet-pointed summary for a principal who prefers prose, or a lengthy report for one who wants three lines.

Scheduling preferences — when they work best, what they dislike being interrupted for, how far in advance they want to know about changes. With this documented, AI can assess a proposed meeting against known preferences rather than simply finding a free slot.

Household standards — the specific expectations that define how the home operates. These are the details that take years to absorb through observation. Documented, they can be applied immediately — by anyone, and by any system given the right brief.

Relationship notes — relevant context about the people the principal sees regularly. This is the layer that allows correspondence to be drafted with the right register, the right level of familiarity, and the right awareness of what has come before.

The more completely these layers are documented, the less an AI partner needs to be told each time it is asked to act. A thorough manual does not just support AI — it enables it to work with a degree of autonomy that would otherwise require constant supervision.

Why most offices don't have one

The most common reason a private office lacks a documented operating manual is time. Documenting what you know takes time away from doing what you know. And in a role that is often reactive, documentation sits permanently at the bottom of the list.

The second reason is that it can feel presumptuous — as though writing things down implies you might leave, or that your knowledge needs to be made transferable, which is an uncomfortable thing to consider when the relationship is built on personal trust.

Neither obstacle is insurmountable. The solution to the first is to build documentation into the rhythm of the role rather than treating it as a separate project. Five minutes at the end of a task, noting what was done and how. Ten minutes on a Friday afternoon, updating active items. Over months, these small additions become a complete picture — and a progressively more powerful brief for any AI working alongside the team.

The solution to the second is a reframe. The operating manual is not a sign that you might leave. It is a sign that you are serious about what happens when you are not there. It protects the principal, it keeps the office resilient, and it is the groundwork for using every available resource — including AI — to its full capability.

Where to begin

If there is no documented operating manual, the place to start is not at the beginning. It is with the most urgent gap.

Ask: if I were unavailable tomorrow for two weeks, what would be most likely to go wrong? Start there. Document the contacts, the context, and the preferences that relate to that area. Then move to the next.

An imperfect operating manual — partial, still being built — is infinitely more useful than the complete one that has never been started. And every section added is both a gap closed and a brief made stronger.

The Modern Private Office will be publishing a template for a private office operating manual as part of The Library. It covers both the structural and preferential layers, with prompts to help surface what is easy to overlook. It will be released alongside the forthcoming book, The Private Office.