A new executive assistant often receives system access before they receive judgment boundaries. The calendar, inbox, and expense tools arrive in the first week, while the rules about what may be changed without approval arrive in fragments. That order creates avoidable risk. Teaching decision rights first gives every permission a purpose and a limit. That sequence also makes the first access review easier to explain.
Hiring and Vetting
Train a new executive assistant on decision rights before tool access
An onboarding sequence that teaches decision rights before system access so a new executive assistant can act safely from the first week.
Table of contents
Why access is not the first lesson
Access answers what a person can open. It does not answer what they should decide, what they should prepare, or what they should escalate. A new assistant with an inbox and no boundary may send a reply that sounds authorized. The same assistant may also refuse a routine request because no one told them where their authority begins.
The first week should establish the decision map before the tools. That sequence feels slower because the assistant cannot yet work independently. It is faster than repairing a mistaken commitment or an inappropriate disclosure. The map also gives the trainer a way to explain why each permission exists. A trainer who skips the map will spend the next month answering the same boundary question.
Write three decision buckets
Use three buckets: decide, prepare, and escalate. Decide covers routine actions the assistant may complete within a written limit. Prepare covers work the assistant can draft or assemble but not release. Escalate covers decisions that remain with the executive or another named owner. Write each bucket on one page and keep the examples close to the definitions.
The buckets should use examples from the actual desk, not from a generic onboarding deck. Booking a routine trip within the travel matrix is a decide item. Drafting a client response for approval is a prepare item. Changing a contract term or sharing a board document is an escalate item. The examples make the abstract categories usable.
Use real cases from the first week
Build five short cases from the previous month's work. For each case, ask the new assistant to name the bucket and the next action. Discuss the answer before showing them the tool. The exercise reveals whether they understand the boundary, not whether they can click through a calendar. The trainer should ask for the reason, not only the label.
Include one case where the correct answer is to ask a question. New assistants often think escalation is a failure. A good case shows that escalation is the right action when the source is missing or the consequence is unclear. The trainer should explain what information the executive will need when the question arrives. A clear question is a sign of good judgment, not a lack of independence.
Pair every permission with a review
For each system, record the permission, the reason, the review date, and the person who approved it. A new assistant should not accumulate broad access simply because it is easier to grant. Start with the minimum needed for the first two weeks and add permissions as the work requires them. The approval record should sit with the role description, not in a private note.
The review should happen with a real task, not only a settings page. Ask the assistant to complete a sample action and explain which rule allowed it. If they cannot explain the rule, the training is incomplete. The review is also a chance to remove access that the role does not need. Remove access that the first month shows the role does not use.
Test escalation judgment
Give the assistant a scenario with a missing approval and a deadline. Watch whether they escalate with a clear question or guess and move on. The quality of the escalation matters as much as the decision to escalate. A useful message names the issue, the options, the source, and the time by which an answer is needed.
Repeat the test after the first month with a harder case. The goal is not to catch the assistant but to see whether the boundaries are learnable. If the same confusion appears twice, the rule or the training needs revision. Document the change so the next onboarding starts from a better map. The test should be a conversation about the boundary, not a pass or fail exam.
Document the first thirty days
Keep a short log of the decisions the new assistant made, prepared, or escalated. Note the case, the bucket, and whether the outcome matched the expectation. The log is a teaching record, not a performance file, and it should stay private to the trainer and the assistant. It shows where the boundary was clear and where the training left a gap.
Review the log at the end of the first month with the assistant and the executive. Pick one case that went well and one that needed correction. Use them to update the examples in the decision map and remove any example that no longer matches the work. The next assistant should inherit a better map, not the same unanswered questions.
Revisit the boundaries at thirty days
At thirty days, review the decide, prepare, and escalate buckets with the executive and the assistant. Ask which decisions took too long, which escalations were unnecessary, and which permissions were never used. Adjust one boundary and one access level. A short review is more useful than a large policy rewrite. The review should produce one change that the assistant can apply the next day.
The assistant should leave the review knowing what changed and why. The executive should leave knowing which decisions still need attention. For related research, see our article on tasks that should never be fully delegated. Our executive support services can help structure the first month. The NIST controls provide a useful access review reference, and background is available from the NIST security and privacy controls.
Key takeaways
- Teach decide, prepare, and escalate before granting calendar, inbox, or finance access.
- Use five real cases from the previous month and discuss the bucket before opening the tool.
- Pair each permission with a reason, a review date, and a named approver.
- Revisit one boundary and one access level at thirty days.
Frequently asked questions
Why teach decision rights before tool access?
What are the three decision buckets?
How often should access be reviewed?
Keep reading
Related executive support guides.
How an executive assistant can coordinate interview logistics fairly
Coordinate senior-candidate interviews with consistent access, privacy, timing, and evidence while leaving selection judgments to the hiring team.
How to review executive assistant access before the first day
Prepare least-privilege access, accountable owners, and safe practice work before a new executive assistant begins.
How to run a quality-review sample for executive assistant work
Review representative completed work for accuracy, authority, clarity, timeliness, and learning.