Executive Assistant Decision Authority Matrix

Inventory decisions hidden inside tasks

List decisions inside calendar, inbox, meeting, travel, expense, document, contact, and follow-through workflows. Describe consequence rather than task name. Moving a routine internal meeting is different from displacing a customer commitment; drafting a reply is different from making a new promise.

Use verbs that expose authority

Use verbs that show authority: gather, prepare, recommend, approve, execute, communicate, and escalate. For each decision, record scope, value or sensitivity limit, required evidence, excluded cases, decision owner, backup, and review date. A RACI chart alone may not capture the conditions that change authority.

Compare two travel changes

An assistant may rebook travel within an approved itinerary and budget tolerance, but a change that cancels a customer meeting or creates an unusual security concern returns to the executive and relevant owner. The matrix preserves speed for routine recovery while exposing consequential tradeoffs.

Test the boundary with adjacent cases

Test adjacent cases where one changed fact alters authority. A routine meeting move may be delegated until travel, a customer commitment, or a protected preparation block is affected. A purchase may fit an approved budget while still creating a new contractual promise. These paired examples teach the condition behind the rule. Record both the permitted path and the stop condition, then ask another authorized reviewer to classify the cases independently. Disagreement reveals language that needs revision before live use.

Write the evidence required for action

Each delegated decision should point to the approved source the assistant must consult, such as a calendar rule, budget, itinerary, contact classification, or written executive preference. State what record proves the action was accepted. Evidence prevents a vague label such as may handle from becoming unlimited discretion. It also gives the executive a useful review sample. Avoid copying sensitive source material into the matrix when a controlled reference and access rule are sufficient.

Separate system permission from permission to decide

A person may be technically able to send a message, move funds, change travel, or edit a record without having authority to make the underlying choice. Map access to the narrower delegated purpose and use individual identities. When the matrix removes an authority, update system permissions and workflows rather than expecting memory to enforce the change. Review shared credentials, forwarding rules, integrations, and temporary coverage because they can preserve power after the written scope has ended.

Set thresholds that a second reviewer can apply

Use observable conditions: named request classes, approved ranges, affected relationships, information sensitivity, and specific stop events. Then give paired examples to another authorized reviewer and compare classifications. Disagreement shows where the language remains too broad. Do not solve every disagreement with more prose. Sometimes the decision must stay with the executive until the organization has a stable rule or enough operating evidence to delegate it.

Provide a path for urgent exceptions

State who acts when the executive is unavailable, how long temporary authority lasts, and what evidence must be recorded. An emergency action does not automatically become precedent. Review it afterward with the accountable owner, identify whether the matrix needs a lasting change, and close any temporary access. The assistant should be able to stop when the consequence exceeds the approved boundary, even when a stakeholder insists that speed matters more than the documented rule.

Resolve overlapping authority

Calendar, travel, finance, people, security, and customer rules may assign different owners to one request. The matrix should show which rule governs when boundaries overlap and where the assistant routes disagreement. Do not ask the assistant to choose between two accountable leaders without a stated escalation. Preserve the competing instructions and the final decision. Repeated overlap is evidence that the operating model needs an owner-level decision, not that the assistant needs broader discretion to make the conflict disappear.

Review personal and company work separately

Executive support can encounter requests that mix company duties with personal logistics. Identify which services and systems are authorized for each category, how costs and records remain separate, and which matters are outside scope. Company access should not become a general route into personal accounts, and personal convenience should not weaken company controls. When a request crosses the boundary, stop and ask the designated owner to classify it before sharing information, spending funds, or creating a new commitment.

Stop authority growing through precedent

Permission grows through precedent: one emergency action becomes a standing rule without discussion. Matrices use vague labels such as own or support. Leaders retain approval for every detail and then complain about limited delegation. Alternatively, access to a system is mistaken for permission to use every function. Record the approved exception.

Pilot frequent, low-consequence decisions

Begin with frequent low-consequence decisions, review real exceptions, and write thresholds in plain language. Connect each authority to the source system and communication rule. Rehearse borderline cases. Obtain explicit approval and version the matrix so the team can identify the rule in effect when a decision occurred.

Sample real decisions and overrides

Sample decisions for valid authority, required evidence, outcome, exception handling, and review. Track unnecessary escalations, actions beyond scope, repeated overrides, and rules that no longer fit. Update the matrix after role, system, executive, risk, or workload changes, and remove authority promptly when duties end.

Approve, version, and retire authority

Give every matrix an approver, effective date, review date, and revocation owner. Use Executive assistant delegation audit and Executive assistant access onboarding checklist to connect delegation and access onboarding. NIST access control guidance provides current access-control guidance, which should be checked at the source. HireExecutiveTeam can help turn recurring executive work into bounded assistant scope. The executive and authorized domain owners remain accountable for the decisions they delegate or reserve. Ask the assistant and a backup reviewer to classify the final examples independently before launch. Reconcile differences, publish the approved version where work occurs, and archive superseded rules so an old screenshot cannot continue to grant authority.

Related resources

• Executive assistant support
• Executive assistant delegation audit
• Executive assistant access onboarding checklist