Designing a family office begins with a deceptively simple question: what is this office here to do? Many families move too quickly to hiring, software, investment managers, or office space. Those choices matter, but they should follow the mandate. The mandate defines the client universe, the services to be provided, the boundaries of authority, the delivery model, the reporting expectations, and the standards by which the office will be judged.
A clear mandate protects both the family and the professionals who serve it. It prevents scope creep, reduces conflict, clarifies who can request what, and creates a common basis for staffing, budgeting, technology, controls, and advisor selection. The service model then translates the mandate into operating reality: what the office will do internally, what it will outsource, what it will coordinate, and how decisions will move from request to approval to execution.
The design should be practical enough to guide daily work and durable enough to survive family change. New family members, new entities, liquidity events, succession transitions, and generational shifts will test the model. A strong design gives the office enough structure to remain disciplined and enough flexibility to adapt without starting over.
17.1 Defining the Client: Individual, Nuclear Family, Branches, Trusts, Entities, and Foundations
The first design task is defining the client. In a family office, the client is not always one person. The office may serve the wealth creator, spouse, children, grandchildren, family branches, trusts, holding companies, foundations, investment entities, family-owned businesses, and household structures. Each may have different legal rights, information rights, cash needs, tax consequences, and expectations.
Client universe: The individuals, entities, fiduciary structures, and institutions the family office is authorized to serve. This should be written down. Ambiguity creates tension when an adult child, spouse, trustee, foundation board member, or business executive expects support that the office was not designed or funded to provide.
The family office should distinguish between the legal client, the economic beneficiary, and the service recipient. For example, a trust may be the legal owner of assets, a child may be the beneficiary, and a trustee may hold decision authority. A foundation may be part of the family’s legacy, but its board may have fiduciary duties separate from the family’s personal preferences. A family-owned business may coordinate with the office, but it is not automatically a client for personal services.
A practical client definition should answer four questions. Who is entitled to services? Who may request information? Who may approve decisions? Who pays for the office? These questions become more important as the family expands across branches. Equal treatment may not mean identical service. A principal may receive comprehensive support, while adult children receive education, reporting, and limited administrative help. Clarity is preferable to informal exceptions.
The office should maintain a client and entity map that shows people, branches, trusts, entities, foundations, fiduciaries, service recipients, and information rights. This map should be reviewed with counsel because service rights and legal rights are not the same. The map becomes a guardrail for staff when requests come from relatives, assistants, trustees, directors, spouses, or outside advisors.
17.2 Determining the Scope of Services
The scope of services is the practical expression of the mandate. It should describe what the office will do, what it will coordinate, and what it will not do. Scope should be organized around the family’s goals and complexity, not around what other families happen to include in their offices.
Service catalog: A documented list of services the family office provides, including service owner, frequency, eligibility, delivery model, decision rights, and reporting output. Typical service categories include investment oversight, financial administration, tax coordination, accounting, treasury, bill pay, entity management, legal coordination, estate administration support, governance, philanthropy, risk management, cybersecurity, insurance, property administration, household coordination, travel support, and family education.
Each service should be specific. “Financial administration” is too broad. The office should state whether it includes cash forecasting, banking relationship management, budget reporting, expense coding, bill payment, capital call funding, debt tracking, and monthly close. “Philanthropy support” should clarify whether the office handles grant diligence, foundation board materials, compliance coordination, site visits, impact reporting, or only payment processing.
The office should also define exclusions. It may coordinate legal advice, but it should not provide legal advice unless licensed counsel is engaged. It may coordinate tax planning, but it should not independently opine on complex tax positions. It may support family-owned business ownership governance, but it should not manage the operating company unless expressly mandated. Exclusions are not negative; they protect the office from being pulled into work it is not designed to perform.
Scope should be prioritized. Some services are mandatory because they protect compliance, controls, liquidity, and risk management. Others are strategic because they support investment discipline, governance, philanthropy, or succession. Others are discretionary because they improve convenience or service quality. This ranking helps the office decide what receives attention when capacity is limited.
17.3 Deciding What to Insource, Outsource, or Co-Source
Once the service catalog is defined, the family must decide how each service will be delivered. The choice is not simply internal versus external. Many effective offices use a blended model: internal staff own strategy, coordination, controls, and family context, while external advisors provide specialized execution.
Insource: Keep the work inside the family office when it requires continuous judgment, sensitive family knowledge, rapid response, direct control, or frequent coordination. Examples often include family office leadership, advisor coordination, consolidated reporting oversight, cash visibility, governance support, document control, and high-sensitivity family communications.
Outsource: Use external providers when the work requires specialized expertise, regulatory infrastructure, scale, independence, or occasional rather than daily capacity. Tax return preparation, legal drafting, custody, investment management, cybersecurity testing, insurance placement, valuations, and specialized due diligence are common examples. Outsourcing is not a sign of weakness. It is often the most professional answer.
Co-source: Share responsibility between internal staff and external specialists. For example, the family office may own the accounting calendar and review outputs while an external firm handles bookkeeping. It may own investment policy and committee materials while an OCIO manages portfolios. It may own cybersecurity governance while an external firm performs testing, monitoring, and incident response planning.
The decision should consider frequency, risk, confidentiality, technical complexity, cost, talent availability, control requirements, and consequences of error. A service that is low frequency but high risk may be outsourced to a specialist. A service that is high frequency and context-heavy may belong internally. The design should also be staged. A newly formed office may outsource more at first, then internalize selected capabilities once volume and requirements are better understood.
17.4 Setting Service Levels and Decision Rights
Service levels convert broad expectations into operational commitments. They define response times, reporting cycles, approval steps, documentation standards, and escalation paths. Without service levels, family members may assume every request is urgent and every request is within scope. Staff then become reactive, and important work competes with convenience requests.
Service levels: The agreed standards for how services will be delivered, including timing, quality, eligibility, and communication. Examples include monthly reporting by the tenth business day, quarterly investment committee materials one week before meetings, bill payments processed within five business days after approval, urgent payment requests escalated to the CFO, and annual insurance reviews completed before renewal season.
Decision rights are equally important. A family office should define who recommends, who approves, who executes, who is informed, and who can override standard procedures. This is especially critical for wires, capital calls, investment commitments, trust distributions, hiring decisions, advisor engagement, property purchases, charitable grants, and family member requests outside the standard service catalog.
Delegation of authority: A written framework that assigns approval thresholds and decision authority by decision type, dollar amount, entity, and risk level. For example, routine invoices below a threshold may be approved by the CFO, while new investment commitments require investment committee approval. Charitable grants may require foundation board approval. Trust distributions may require trustee action. The family office can coordinate, but it cannot replace the authority of fiduciaries or governing bodies.
Service levels and decision rights should also cover information access. Family members may not all be entitled to the same documents. Trustees, beneficiaries, directors, spouses, and employees may have different rights. The office should manage access deliberately, using secure systems and approved communication channels.
Request intake should be formal enough to create accountability. The office may use a shared inbox, service portal, request log, or designated coordinator. Each request should have an owner, status, due date, required approval, and record of completion. This prevents family service from becoming a collection of private side conversations.
17.5 Family Office Design Template
A design template helps convert discussion into a practical operating blueprint. The template should be completed before major hiring, technology selection, or vendor commitments. It should be reviewed by the appropriate decision body and updated as the family’s complexity changes.
- Purpose statement: Why the family office exists and what outcomes it is expected to support.
- Client universe: Individuals, branches, trusts, entities, foundations, and businesses in scope.
- Service catalog: Services provided, excluded, coordinated, outsourced, or planned for future phases.
- Delivery model: Which services are insourced, outsourced, or co-sourced, and why.
- Governance interfaces: How the office interacts with the principal, family council, investment committee, trustees, foundation board, business board, and advisors.
- Decision rights: Approval thresholds, delegated authorities, escalation rules, and exceptions.
- Organization design: Roles, reporting lines, required capabilities, interim support, and hiring sequence.
- Technology and data: Systems of record, reporting tools, document management, cybersecurity requirements, and data ownership.
- Advisor model: Key external advisors, provider roles, coordination cadence, and review process.
- Reporting model: Monthly, quarterly, annual, and event-driven reports, including recipients and owners.
- Economics: Budget, cost allocation, service charges, vendor fees, and approval of extraordinary expenses.
- Implementation roadmap: First 30, 60, 90, and 180 days of actions, owners, dependencies, and milestones.
The completed design should not be overly theoretical. It should be usable by the family office leader on the first day of operation. It should answer practical questions: which requests are in scope, which advisor owns a task, who can approve a payment, what report is due, what system contains the document, and when a decision must be escalated.
The template should also include review triggers. Major life events, new family branches, new assets, new jurisdictions, operating business transitions, litigation, cyber incidents, and tax changes may all require updates. A mandate that is never reviewed becomes stale; a mandate that is constantly ignored becomes irrelevant.
The family office mandate and service model should be reviewed at least annually and after major events such as a liquidity event, death, divorce, marriage, new generation entering adulthood, major tax change, business sale, investment loss, cyber incident, or governance dispute. A family office is not a static design. It is an operating model that must evolve while preserving clarity, accountability, and disciplined service to the family’s long-term objectives.
