Published October 22, 2026
Executive assistants often handle personal tasks: a gift, a family appointment, a household repair, a travel booking that mixes business and leisure. The work can be legitimate and helpful. It can also blur authority, privacy, and employment boundaries.
A written scope table prevents the blur. It says which personal tasks are in scope, which require approval, which are out of scope, and how private information is handled.
Table of contents
- Why a written scope matters
- Build the task table
- Separate errands from decisions
- Protect private information
- Handle gifts, family, and mixed travel
- Review the scope when the role changes
- Sources
- Frequently Asked Questions
Why a written scope matters
Verbal flexibility is common in small teams: "Help with whatever comes up." That works until a task involves money, family information, or a decision the assistant should not make alone. The assistant is then exposed to ambiguity, and the owner may not realize how much authority was implied.
A scope table is not a lack of trust. It is a shared definition that lets the assistant say yes quickly to the right things and route the rest without friction.
Build the task table
| Task type | In scope | Approval needed | Out of scope |
|---|---|---|---|
| Personal appointments | Schedule and confirm | None, within stated hours | Medical decisions, legal advice |
| Household vendors | Collect quotes | Spend above threshold | Signing contracts |
| Gifts | Research and purchase | Above gift limit; recipient list | Personal messages written in owner's voice |
| Family logistics | Coordinate calendar | Any change to a family member's booking | Discussing family matters with third parties |
| Mixed travel | Book business portion | Personal extension and cost | Using company funds for personal guests |
| Errands | Arrange delivery or pickup | Address disclosure | Handling identity documents |
The table should name the threshold amounts and the approver. "Reasonable" is not a threshold.
Separate errands from decisions
An errand has a clear object and a finish: book the appointment, collect the quote, deliver the package. A decision has alternatives and consequences: choose the school, accept the medical recommendation, settle a family dispute.
Assistants can execute errands. They should not make personal decisions for the owner or the owner's family. When a task drifts from execution into judgment, stop and ask.
The same rule applies to business tasks that look personal: a team dinner, a condolence gift, a congratulatory note. The assistant can arrange logistics and draft from an approved tone; the owner decides the message and the recipient.
Protect private information
Personal tasks generate sensitive data: home addresses, family names, health appointments, school details. Collect only what the task requires, store it in the approved system, and do not copy it into general notes or chat.
Access should be limited to the assistant and the owner. If a backup covers the role, the owner should approve the access and the backup should follow the same rules. The NIST Privacy Framework provides a useful structure for minimizing data and controlling access; it does not replace the owner's personal preferences.
Do not discuss the owner's personal affairs with vendors beyond what the task requires. A florist needs a delivery address and a message, not a family history.
Handle gifts, family, and mixed travel
Set limits in advance:
- maximum gift value without approval
- approved recipients and occasions
- whether alcohol, cash, or regulated items are allowed
- how receipts are recorded
- who may contact family members
- how personal days are added to business travel
For mixed travel, split the cost before booking. Record the business portion, the personal portion, and who pays for each. A clear allocation prevents an awkward expense review later.
Review the scope when the role changes
Review the table when the assistant changes, the owner's family situation changes, the company policy changes, or a task creates discomfort. Add examples from real requests so the table stays concrete.
If the owner asks for something outside the table, the assistant should ask for a written exception rather than assume the table is obsolete. Exceptions can become the new rule, but only deliberately.
Sources
- NIST Privacy Framework
- O*NET OnLine: Executive Administrative Assistants
- U.S. Department of Labor: Hiring
- Bureau of Labor Statistics: Occupational Outlook Handbook
Frequently Asked Questions
Is it appropriate for an assistant to handle personal tasks?
It can be, when the scope is written, the assistant consents, local employment rules are respected, and private data is protected. The arrangement should be explicit, not assumed.
What if a family member contacts the assistant directly?
Follow the owner's written instruction on who may request what. Verify identity for anything involving money, access, or personal information.
Should personal tasks appear on a business timesheet?
Follow the employer's policy. Many organizations require personal time to be recorded separately or handled outside paid hours. Do not disguise personal work as business work.
Review cadence
Review the boundary monthly with the executive and the assistant. Discuss the tasks that blurred personal and business work, the information that was shared, and the questions that should have been routed. Update the written examples and remove any task that no longer fits the role. The boundary is only useful if both sides can explain it.
