Executive Office SOPs¶
Why This Exists¶
This document defines SOP areas for repeatable Executive Office work.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
SOPs make executive coordination repeatable, auditable, and consistent across customers and Practices.
SOP Catalogue¶
| SOP ID | SOP | Purpose | Primary Digital Professional |
|---|---|---|---|
| EXEC-SOP-001 | Daily Executive Briefing SOP | Prepare, deliver, and record daily executive briefing. | Ari and Ava |
| EXEC-SOP-002 | Approval Coordination SOP | Route, remind, escalate, and record approval workflow status. | Ava |
| EXEC-SOP-003 | Escalation Coordination SOP | Triage and coordinate urgent blockers and risks. | Ari and Ava |
| EXEC-SOP-004 | Board Room Decision SOP | Prepare strategic decisions and record outcomes. | Ari |
| EXEC-SOP-005 | Strategy Review SOP | Review and update procurement priorities. | Ari |
| EXEC-SOP-006 | Executive Report SOP | Coordinate reporting pack and executive summary. | Ava and Pulse |
| EXEC-SOP-007 | Practice Performance Review SOP | Review Practice KPIs and improvement actions. | Ari and Pulse |
| EXEC-SOP-008 | Executive Administration SOP | Manage schedules, documents, reminders, and follow-ups. | Ava |
SOP Execution Flow¶
flowchart TD
Trigger[Trigger]
SOP[SOP]
Inputs[Source references and context]
Action[Coordinated action]
Record[Decision, follow-up, or report]
KPI[KPI impact]
Trigger --> SOP
Inputs --> SOP
SOP --> Action
Action --> Record
Record --> KPI
SOP Rules¶
- SOPs must identify inputs, outputs, roles, approval points, and records.
- SOPs must reference source domains instead of copying their ownership.
- SOPs must define when Ari leads and when Ava coordinates.
- SOP outputs must be visible in reports, follow-up actions, or audit records.