On this page
Setting Boundaries for Personal Requests to Your Assistant

Executives are whole people, and the line between professional and personal logistics is rarely clean. A family flight, a medical appointment, a home repair, a gift for a client's milestone: these arrive in the same inbox as board materials. A good assistant can often help, but without a boundary the role drifts, the assistant's workload becomes unpredictable, and the executive loses clarity about what they can count on.
The answer is not a strict ban. It is an explicit framework that says what is in scope, what needs approval, and what stays with the executive.
Why the boundary matters
A remote assistant works from a defined scope. When personal requests expand without limit, three problems appear. First, the assistant's capacity is consumed by work that was never planned. Second, the assistant may handle sensitive personal data without the controls that apply to company systems. Third, the executive's professional priorities can be delayed by personal tasks that feel urgent.
A written boundary prevents all three. It also protects the assistant from awkward requests they do not know how to decline.
Define three categories
Use three categories: routine personal logistics, sensitive personal matters, and out-of-scope.
Routine personal logistics are low-risk tasks that fit the assistant's existing tools. Examples include booking a personal dinner reservation, coordinating a family travel itinerary using approved channels, or arranging a gift order within an approved budget.
Sensitive personal matters involve health, legal, financial, or family information. These need explicit approval, a defined data-handling rule, and often a different system. The assistant should not improvise here.
Out-of-scope requests include anything that would require the assistant to impersonate the executive, sign on the executive's behalf, or access personal accounts that are not approved for work use.
| Category | Examples | Default rule |
|---|---|---|
| Routine | Reservations, gifts, personal travel logistics | Allowed within budget and tools |
| Sensitive | Health, legal, family, personal finance | Requires explicit approval |
| Out of scope | Impersonation, unapproved accounts, signatures | Not permitted |
Set limits that make the framework real
A category without a limit is an invitation to drift. Set a time budget, a spend threshold, and a frequency cap. For example: up to two hours per week on routine personal tasks, purchases under a stated amount without approval, and no more than two active personal projects at once.
Write the limits down and review them quarterly. When the limits are exceeded, the assistant should surface it rather than quietly absorb the overflow.
Protect data and accounts
Personal requests often involve data that should not sit in a shared work workspace. Use the approved systems for anything that touches the company, and keep truly personal records in a personal system the executive controls. Never share personal passwords with the assistant. Use delegated access with the narrowest scope that works.
If a personal matter involves legal, medical, or financial professionals, the assistant's role is coordination, not advice. Route substantive questions to the right professional. When personal records are stored digitally, apply the same data-security basics described in the FTC's data security guidance.
Give the assistant a way to say no
The assistant needs a script for declining or redirecting a request. Something like: "I can handle this within the personal-task budget. For the account access, I would need your approval and a secure way to grant it." A neutral script removes the personal awkwardness from the boundary.
If the executive pushes past the boundary repeatedly, that is a signal to renegotiate the scope or add capacity, not to ignore the rule.
Handle conflicts between personal and professional
When a personal request collides with a professional commitment, the professional commitment wins by default unless the executive explicitly says otherwise. The assistant should surface the conflict with both deadlines and let the executive choose.
Document the choice. A pattern of personal requests overriding board prep or investor follow-ups is worth reviewing at the next retrospective.
Review the framework quarterly
Once a quarter, look at what actually happened. Which personal requests were frequent? Which consumed more time than expected? Which created data-handling risk? Adjust the categories and limits based on evidence rather than assumption.
Frequently asked questions
Can an assistant book personal travel?
Yes, within the approved budget and tools. Personal travel can often be booked through the same process as business travel, which keeps the record consistent and the data controlled.
Should personal requests go through a separate channel?
A separate channel helps. It keeps personal tasks from mixing with board and investor work, and it makes the time budget easier to track.
What if the executive's family contacts the assistant directly?
Agree in advance on who may contact the assistant, for what, and through which channel. A short allowlist prevents surprise requests and protects the assistant from pressure.
A boundary is a service improvement
An explicit personal-request framework is not a restriction. It is what lets the executive delegate personal logistics confidently, because they know the assistant has the capacity, the access, and the rules to handle them well. If you want a team that already works within this kind of framework, see our executive support services and our guide to the delegation intake form.