Executive support scope of work: a practical template

Start with the real decision

What belongs in a scope of work for executive assistant or executive operations support? The answer should follow the leadership team's real workflows, risks, and capacity rather than a generic rule. A useful scope of work translates a broad request for leverage into observable services. It names the supported leaders, workflows, outputs, response windows, working hours, exclusions, client dependencies, access boundaries, and the person who accepts work. It also explains how priorities change. The document should be specific enough to guide a normal week and a stressful exception without pretending that every future request can be predicted. Treat it as an operating agreement that sits beside the commercial contract, confidentiality terms, and applicable employment or vendor documents.

Avoid the common shortcut

Avoid a task dump such as calendar, inbox, travel, projects, and other duties as assigned. Those labels hide volume, decision rights, and completion standards. Calendar management could mean entering accepted invitations or actively negotiating access across five stakeholders. Inbox support could mean tagging messages or drafting replies in the executive's voice. The scope must distinguish preparation from approval and coordination from authority. It must also avoid unsupported promises such as always available or zero errors, which encourage unsafe workarounds when demand spikes.

Map the work

Open with outcomes and service recipients. Name which executive or leadership group receives support and the operating result each workflow should create. For calendar work, an outcome might be protected preparation time and accurately briefed meetings. For board support, it might be a complete packet routed by the approved cutoff. Outcomes help both sides evaluate a request that was not listed word for word while still preventing the scope from expanding into unrelated functional ownership.

Make ownership explicit

Create a workflow table. For each service, record its trigger, required inputs, output, ordinary response window, accountable approver, systems used, and escalation condition. Include estimated frequency or capacity assumptions. A travel workflow might cover research and booking from an approved profile while excluding immigration, personal security, or approval of policy exceptions. Examples make the boundary teachable and give a backup person something more useful than a job title.

Test the operating model

Write decision rights in verbs. State whether support may collect, draft, schedule, route, recommend, approve, send, purchase, or commit. Link monetary limits and sensitive actions to named approvers. Include a safe default for missing authority, usually pause, preserve the current commitment, and escalate with context. Clear verbs prevent a provider from interpreting broad ownership as permission to create obligations on behalf of the executive.

Protect access and judgment

Define client dependencies and access. The client may need to provide timely approvals, current travel preferences, system accounts, source owners, and a priority decision-maker. List information that must remain in client-approved systems and how access will be provisioned and removed. The Federal Trade Commission recommends knowing what personal information a business holds, keeping only what it needs, protecting it, and disposing of it securely. Apply that discipline to executive records from the start.

Choose a reviewable first step

Add review and change control. Set a date to compare actual volume with the assumptions, a method for requesting new work, and a rule for urgent exceptions. Explain how either side records an accepted scope change and any effect on capacity, timing, or fees. Include transition deliverables such as current workflow notes, open commitments, file locations, and access-removal confirmation. A scope is healthier when it can change explicitly than when both sides rely on memory.

Example for a leadership team

For a founder, the initial scope might include one calendar, one inbox triage pass each weekday, preparation for a Monday leadership meeting, domestic travel booking, and a weekly commitments list. The assistant may propose meeting moves but needs approval before changing customer, investor, or personal appointments. The founder supplies a current priority list by Monday morning and answers escalations within four business hours. A monthly review compares request volume and missed windows. Board packet ownership, recruiting coordination, and personal purchases are excluded until separately scoped. This short example is more actionable than a long list of possible administrative tasks because it connects service, authority, and dependencies.

Measure whether the choice works

Review whether outputs arrive on time, approvals are easy to locate, requests return for missing inputs, and out-of-scope work appears repeatedly. Repeated exceptions may show a real need to amend the scope. Repeated rework may show that the acceptance standard or source owner is unclear. Use the review to change the system, not to build a record of blame.

Review the evidence before approval

Before approving this service design decision, hold a short evidence review with the executive, the person who will manage the work, and any owner responsible for security, people, tax, legal, or specialist questions raised by the scope. Read the actual proposal, agreement, workflow, or candidate evidence rather than relying on a sales summary. Write what is confirmed, what remains an assumption, which conditions must be satisfied before access begins, and who can accept each condition. Use FTC guidance on protecting personal information as a primary reference for the relevant external principle, then ask a qualified owner to interpret requirements that depend on your location or facts. The review should produce a go, revise, or stop decision with reasons.

Write the launch brief

Turn the decision into a one-page launch brief. Include the supported leaders, first workflow, intended outcome, input owner, service window, access needed, authority boundary, escalation contact, success evidence, and review date. Link the operating references, including executive assistant delegation framework and executive support service level agreement, so the person doing the work can find the surrounding rules. Walk through one normal case, one ambiguous case, and one failure case before expanding the scope. If the team cannot agree on the safe action in those examples, the design is not ready for a new assistant or provider to interpret under pressure.

Turn the guide into an action

Use this guide as a working decision record. Write the assumptions, owner, evidence, next review date, and safe response when an answer is missing. Keep executive judgment with the accountable leader and specialist decisions with qualified owners. HireExecutiveTeam helps leadership teams define and staff practical executive support; a useful next step is to compare the framework here with your current calendar, inbox, meeting, board, travel, and follow-through workload before discussing a role or service.

Related resources

• executive assistant delegation framework
• executive support service level agreement
• executive assistant support