Define the service boundary
List the work the support team owns, coordinates, and does not accept. A clear boundary prevents assistants from becoming the default owner for any task without a home.
ExecutiveSupportStaff Editorial Team | Published
List the work the support team owns, coordinates, and does not accept. A clear boundary prevents assistants from becoming the default owner for any task without a home.
Define urgency by deadline and consequence. State how quickly the team acknowledges a request, who owns it, and when the requester gets a delivery estimate.
The CISA identity guidance recommends limiting access according to role and need.
Name the primary owner, backup, and escalation point for each service area.
The EA performance metrics provide a scorecard, and the escalation protocol defines exceptions.
| Stage | Required output |
|---|---|
| Define | Owner and boundary |
| Operate | Decision and record |
| Review | Updated rule |
What should this process define?
Use an internal operating document to make priorities, ownership, response expectations, and escalation rules clear.
What makes the process reliable?
Define a few urgency levels and reserve the fastest response for work with a real deadline or material consequence.
When should the process be reviewed?
Review missed commitments, rework, unclear requests, workload, and stakeholder feedback.