Executive assistant delegation scorecard
This working method focuses on selecting work for responsible delegation, with the executive and primary assistant together acting as the support lead. Its avoidable breakdown is ranking tasks only by how annoying they feel; a working method check should confirm identity, reference note scope, timing, support lead dependencies, and authorization.
Keep a one-page delegation candidate sheet as the reference note, showing verified working method facts, open review point questions, the responsible support lead, and the useful due time. The review point is whether the work is ready to transfer, needs preparation, or should remain with the executive, supported by a reference note recommendation, real working method alternatives, and the consequence of waiting.
Consider this working method case: a recurring briefing may score well on repeatability but still need a clear rule for sensitive stakeholder commentary. Record what a qualified support lead needs, preserve reference note detail in its approved system, and leave the review point commitment with the executive and primary assistant together.
The observable result is rework, escalations, recovered executive time, and confidence on both sides. Match its review cadence to working method consequence and volume; repeated avoidable breakdown should improve the intake question, support lead rule, access pattern, or reference note handoff.
A delegation scorecard helps an executive choose work that can move safely and meaningfully to an assistant. This guide is for executives and support leads who want to transfer ownership without creating hidden rework. It is designed to help an executive assistant create reliable coordination without taking over decisions that belong to legal, finance, security, people, governance, or the executive.
Start with the smallest useful record and a named owner. Make deadlines reflect when information is still useful, not merely the final event time. Do not score work as delegable merely because it is time-consuming; consequence, authority, and context matter as much as frequency.
Define the outcome before the task
This working method focuses on describing the result rather than a series of clicks, with the person accountable for the business outcome acting as the support lead. Its avoidable breakdown is delegating activity while retaining every meaningful choice; a working method check should confirm identity, reference note scope, timing, support lead dependencies, and authorization.
Keep an outcome statement with completion evidence as the reference note, showing verified working method facts, open review point questions, the responsible support lead, and the useful due time. The review point is what the assistant may decide independently and what requires confirmation, supported by a reference note recommendation, real working method alternatives, and the consequence of waiting.
Consider this working method case: calendar ownership can mean protecting priorities and resolving routine conflicts, not simply accepting invitations. Record what a qualified support lead needs, preserve reference note detail in its approved system, and leave the review point commitment with the person accountable for the business outcome.
The observable result is how often the executive must redo a completed assignment. Match its review cadence to working method consequence and volume; repeated avoidable breakdown should improve the intake question, support lead rule, access pattern, or reference note handoff.
Rate judgment and consequence
This working method focuses on separating routine variation from high-consequence judgment, with the executive with relevant functional owners acting as the support lead. Its avoidable breakdown is treating frequency as proof that a task is low risk; a working method check should confirm identity, reference note scope, timing, support lead dependencies, and authorization.
Keep a consequence and escalation matrix as the reference note, showing verified working method facts, open review point questions, the responsible support lead, and the useful due time. The review point is which scenarios require a pause, specialist review, or executive choice, supported by a reference note recommendation, real working method alternatives, and the consequence of waiting.
Consider this working method case: an assistant can assemble contract signature materials without interpreting contractual obligations. Record what a qualified support lead needs, preserve reference note detail in its approved system, and leave the review point commitment with the executive with relevant functional owners.
The observable result is exceptions caught before action and decisions escalated at the right level. Match its review cadence to working method consequence and volume; repeated avoidable breakdown should improve the intake question, support lead rule, access pattern, or reference note handoff.
This working method focuses on matching permissions and context to the proposed responsibility, with the system owner and the assistant manager acting as the support lead. Its avoidable breakdown is granting broad access to avoid planning a narrower role; a working method check should confirm identity, reference note scope, timing, support lead dependencies, and authorization.
Keep an access checklist linked to approved systems as the reference note, showing verified working method facts, open review point questions, the responsible support lead, and the useful due time. The review point is which permissions are essential now and which can wait, supported by a reference note recommendation, real working method alternatives, and the consequence of waiting.
Consider this working method case: inbox triage may require delegated mailbox access but not visibility into every restricted archive. Record what a qualified support lead needs, preserve reference note detail in its approved system, and leave the review point commitment with the system owner and the assistant manager.
The observable result is access errors, workarounds, and requests stalled by missing information. Match its review cadence to working method consequence and volume; repeated avoidable breakdown should improve the intake question, support lead rule, access pattern, or reference note handoff.
Transfer ownership in stages
This working method focuses on moving from observation to supervised work and then independent handling, with the assistant receiving the responsibility acting as the support lead. Its avoidable breakdown is switching ownership in one step and judging the first attempt as final performance; a working method check should confirm identity, reference note scope, timing, support lead dependencies, and authorization.
Keep a staged handoff plan with review dates as the reference note, showing verified working method facts, open review point questions, the responsible support lead, and the useful due time. The review point is when evidence supports moving to the next level of autonomy, supported by a reference note recommendation, real working method alternatives, and the consequence of waiting.
Consider this working method case: the assistant can first draft meeting decisions, then route them, and later close routine follow-through independently. Record what a qualified support lead needs, preserve reference note detail in its approved system, and leave the review point commitment with the assistant receiving the responsibility.
The observable result is question volume, correction patterns, and timely closure during each stage. Match its review cadence to working method consequence and volume; repeated avoidable breakdown should improve the intake question, support lead rule, access pattern, or reference note handoff.
Review the delegation portfolio
This working method focuses on balancing new ownership with capacity and role clarity, with the executive support lead acting as the support lead. Its avoidable breakdown is adding responsibilities without removing obsolete work; a working method check should confirm identity, reference note scope, timing, support lead dependencies, and authorization.
Keep a current portfolio view of delegated outcomes as the reference note, showing verified working method facts, open review point questions, the responsible support lead, and the useful due time. The review point is what to retain, redesign, automate, return, or delegate next, supported by a reference note recommendation, real working method alternatives, and the consequence of waiting.
Consider this working method case: a monthly review may reveal that travel coordination is stable while stakeholder preparation still consumes executive attention. Record what a qualified support lead needs, preserve reference note detail in its approved system, and leave the review point commitment with the executive support lead.
The observable result is capacity, service quality, executive focus, and assistant development. Match its review cadence to working method consequence and volume; repeated avoidable breakdown should improve the intake question, support lead rule, access pattern, or reference note handoff.
Put the guide into practice
For executive assistant delegation scorecard, use the NIST least privilege definition as a public reference, then apply the organization's own policies. That guidance can clarify delegation principles, but it cannot grant authority or define the company's risk tolerance.
Connect executive assistant delegation scorecard to the executive office operating rhythm so its exceptions receive regular review. For a related executive support pattern, see onboarding an executive assistant.
Test one executive assistant delegation scorecard case, then compare the request, missing delegation context, paused judgment, and backup usability. Keep executive support controls that reduce ambiguity and remove fields that nobody uses.