Executive Operations Systems for a Four-Principal Office by Katrina LeeExecutive Operations Systems for a Four-Principal Office by Katrina Lee

Executive Operations Systems for a Four-Principal Office

Katrina Lee

Katrina Lee

Prior-role systems work

These systems were built and run in a prior executive support role, not as a client engagement. Portfolio graphics are template recreations using sample data.

Overview

I built the operating systems that kept 1 Director and 3 Deputies scheduled, prepared, and following through in parallel. The system combined a tiered calendar triage protocol, a fixed 1-page pre-read standard, and a cross-office action-item tracker with an escalation trigger. I later recreated each as a portable template and documented AI-assisted admin workflows.

The operational challenge

Four senior leaders, 1 support desk, and no shared rule for whose time won.
Meeting requests arrived as judgment calls that landed on a principal's desk. Briefing materials sometimes arrived the same day as a meeting. Commitments lived in personal notes, inboxes, and memory. Scheduling and follow-through decisions kept escalating to the people whose time the system was meant to protect.

What I did

Built a 4-tier classification for meeting requests, applied at intake, so conflicts resolved by rule.
Set a fixed format and deadline for briefing packages, with the submission cutoff enforced upstream.
Created 1 tracker for every meeting commitment, recording its owner, due date, and source meeting before the room cleared.
Established a weekly review pass, with status updated by the owner.
Set automatic escalation at 7 days past due.
Documented 6 recurring admin workflows as repeatable AI-assisted processes, each with a prompt set and handoff document.
Defined guardrails for workflows that never run unattended, including correspondence sent in a principal's name, client-identifying details, personnel or payroll records, final numbers, contract or financial figures, and legal or compliance language.

Systems created

Multi-Principal Calendar Triage Protocol

Every request was assigned 1 of 4 tiers at intake. Tier 1 covered statutory, congressional, and Secretary-level commitments. Tier 2 protected standing leadership cadence and deep-work blocks. Tier 3 covered internal working sessions that could move within the same week. Tier 4 covered optional and courtesy items, batched into 2 windows each week or declined with a template. Only 2 Tier 1 conflicts in the same slot reached the principal.

1-Page Pre-Read Standard

Every briefing package used a fixed format: the issue in 1 sentence, decision requested, what changed since the last touch, positions in the room, and risks or open items. Each package ended with 1 explicit ask and was due 48 hours before the meeting.

Cross-Office Action-Item Tracker

A single tracker captured the action, owner, source meeting, and due date in the room. Owners updated status during a weekly review, and escalation triggered automatically at 7 days past due.

AI-Assisted Admin Workflow Library

The library covered meeting notes to action items, inbox triage, correspondence first drafts, travel research, fact-checked research summaries, and recurring report assembly. Each workflow included a prompt set, handoff document, and human review step.

Outcomes

4 leaders scheduled in parallel across 13 years.
Zero double-booking escalations.
Preparation moved from same-day delivery to a 48-hour standard.
The pre-read format was adopted by adjacent offices without a mandate.
6 admin workflows were documented and handed off, each with a prompt set and handoff document.

My role

Executive Operations Partner. I designed and ran the tier definitions, pre-read format and deadline structure, tracker and escalation rule, and workflow library and guardrails. I now offer this work as fractional executive support for founders and small teams.
Like this project

Posted Sep 3, 2026

Prior-role executive operations systems for multi-principal scheduling, briefing, and follow-through.