Where the boundary belongs
Abstract
Delegation works best when the task and the accountability are separated. An assistant can prepare a contract summary, but the executive or legal owner still approves the contract. The same pattern applies to access, personnel, board materials, and sensitive communications. This review defines a boundary for tasks that should never be fully delegated. It focuses on decision rights and review, not on distrust of assistants. [1][2][4]
Methodology
The review uses access control, identity, and privacy guidance to identify decisions with irreversible or high-consequence effects. It then maps each decision to a preparation role and an approval role. The mapping is tested against common executive support tasks. The result is a boundary document, not a claim that assistants cannot handle complex work. [1][2][3]
The question and its boundary
The question is which tasks can be prepared by an assistant but must be approved by someone else. The answer depends on consequence, reversibility, and the information required. A routine calendar change is easy to reverse, while a contract signature or a data disclosure may not be. The boundary should reflect that difference rather than the seniority of the person doing the work. [1][2]
The review uses fully delegated to mean that no other person reviews the decision before it takes effect. It does not mean that the assistant cannot draft, research, or recommend. Many tasks can be fully prepared by an assistant and still require a named approval. The distinction is the core of the method. [2][3] A clear separation also makes the assistant's preparation more valuable.
Tasks that carry irreversible consequence
Contract commitments, legal settlements, regulatory filings, and public disclosures usually belong in the approval category. The assistant may assemble the file, check the dates, and draft the summary. The signature or submission should remain with the person who holds the authority. A mistake in this category can create an obligation that is difficult or impossible to undo. [1][2]
Personnel decisions such as hiring, termination, compensation, and performance ratings also require a qualified owner. An assistant can schedule the conversation and prepare the documentation. They should not make the decision or communicate it without authorization. The same logic applies to decisions that affect access to sensitive systems or information. [2][3] The approval owner should be named before the task reaches the assistant's queue.
Tasks that need a second reader
Some tasks can be delegated for execution but still need a second reader before release. A board packet, a client proposal, a press statement, and a sensitive email may fit this pattern. The assistant owns the preparation and the first check. A named reviewer confirms the facts, the tone, and the authority. The second reader is not a sign of mistrust; it is a control for consequential output. [1][3]
Access changes are a clear example. An assistant may request access or prepare the approval form, but a system owner should grant it. The reviewer checks that the access matches the role and that a removal date exists. That step protects the assistant as much as the organization. It also creates a record if the access is later questioned. [2][4]
What the evidence can support
Access control guidance separates identity, authorization, and review. It supports the idea that trust in a person does not replace a bounded permission. Identity guidance supports named accounts and strong authentication rather than shared credentials. Privacy guidance supports minimizing the data used for a task. These sources inform the boundary, but they do not list every executive support task. [1][2][3]
The evidence does not prove that a fully delegated task will fail. It shows that certain controls reduce the chance of unattributed action or excessive access. The review should use that reasoning to prioritize the tasks with the highest consequence. A low-risk task may not need a second reader even if a high-risk task does. [2][4]
How to write the boundary
Create a short table with three columns: task, preparation owner, and approval owner. Add a fourth column for the evidence the approver needs. Keep the table at the level of decisions rather than individual messages. Review it with the executive, legal, security, or whoever owns the relevant risk. A boundary that no one has approved is only a suggestion. [1][3]
For each task, write the condition that makes it routine or exceptional. A travel booking under the matrix may be routine, while a booking that adds a security review is exceptional. The condition should be observable, not a feeling. That makes the boundary teachable and auditable. [2][3] The table should be short enough to use during a live request.
Training and review
Train the assistant on the boundary with real cases. Ask them to identify the preparation and approval roles, then explain what evidence the approver will need. Include a case where the correct action is to stop and ask. The training should also cover how to record an approval and where to find the current owner. [1][2]
Review a sample of decisions each quarter. Look for approvals that were skipped, access that was broader than the task, and tasks that stalled because the approver was unclear. Update the table when a role changes. The review should produce one change to the boundary or the training, not a new policy every time. [3][4]
A worked example
An assistant prepares a vendor contract summary, checks the renewal date, and drafts the approval note. The legal owner reviews the terms, the finance owner confirms the budget, and the executive signs. The assistant has done most of the work, but no single person has both prepared and approved the commitment. The record shows who did which part.
A second example is access. The assistant requests a reporting account for a new team member, the system owner grants the minimum role, and the review date is recorded. The assistant can explain the need but cannot grant the permission. That separation keeps the audit trail meaningful and gives the system owner a chance to challenge an unnecessary request.
What to review first
Start with the tasks that create an obligation, disclose protected information, or change access. Those are the tasks where a missed review is hardest to undo. Then move to tasks that affect a client or a public statement. Routine calendar and travel work can stay in the delegated category with a clear limit and a named reviewer.
Review the boundary with the people who handle the work. They will know which tasks routinely arrive with missing approval or unclear ownership. Their input makes the table more realistic and easier to follow. A boundary written without them is likely to be ignored under pressure, especially when a deadline leaves no time for a debate, so test it against a real request before publishing it. The people who apply the table should also know how to suggest a change.
Limits and responsible use
The boundary is not a judgment about an assistant's ability. It is a way to match authority to consequence and to keep a record of who decided. Some organizations may choose a different boundary because of regulation, client contract, or risk tolerance. The method should be adapted, not copied without review. [1][2] The method should be reviewed with the people who will apply it.
The review also cannot eliminate the need for judgment. A task that looks routine may become consequential when the facts change. The assistant needs a way to escalate when the condition is unclear. For related guidance, see our article on <a href="/blog/train-a-new-executive-assistant-on-decision-rights-before-tool-access">training decision rights</a> and our <a href="/services">executive support services</a>. [3][4] That escalation path should be tested before a consequential request arrives.
Key findings
- Fully delegated means no other person reviews the decision before it takes effect, not that the assistant cannot prepare it. [1][2]
- Contract, legal, regulatory, personnel, and sensitive access decisions need a named approval owner. [2][3]
- Board packets, client proposals, and sensitive messages may be prepared by an assistant but need a second reader before release. [1][3]
- Write the boundary as task, preparation owner, approval owner, and required evidence. [2][4]
- Review a sample quarterly for skipped approvals, excess access, and unclear ownership. [3][4]
Sources
- Security and Privacy Controls for Information Systems, NIST
- Digital Identity Guidelines: Authentication and Lifecycle Management, NIST
- Zero Trust Architecture, NIST
- Protecting Personal Information: A Guide for Business, Federal Trade Commission
- Cybersecurity Framework, NIST
- Computer Security Incident Handling Guide, NIST