CEO Executive Assistant
A colleague asks the CEO to introduce them to an investor, customer, candidate, or partner. The request sounds small, but it spends relationship capital, exposes contact information, creates expectations, and may imply an endorsement neither party has accepted.
The operational problem is not a lack of effort. It is that the request, decision boundary, and proof of completion often live in different systems or in one person’s memory. A workable process gives the assistant enough structure to move ordinary work quickly while making consequential exceptions visible to the right owner.
This guide is distinct from executive-reference-request-protocol because it covers consent and relevance for connecting two people rather than responding to a request that the executive endorse or serve as a reference. It is a new workflow for a separate customer decision, not a renamed or re-dated version of that earlier article.
Authoritative sources used
- Protecting Personal Information: A Guide for Business — Federal Trade Commission; checked 2026-10-06.
These sources provide current control principles for verification, access, privacy, continuity, or records. Applying them to executive-assistant work is our operational synthesis, not legal, security, privacy, employment, travel, procurement, or compliance advice. Use qualified owners for requirements specific to your organization and jurisdiction.
Clarify the requested outcome
Ask who the parties are, why the connection is relevant now, what specific next step is requested, what information may be shared, and whether there is a deadline. Distinguish a warm endorsement from permission to pass along a short note.
Check relationship and conflict context
Confirm the CEO actually knows the target well enough for the proposed framing. Route conflicts, active negotiations, recruiting sensitivities, regulated matters, or competitive concerns to the appropriate owner. Do not infer consent from an old email thread.
Use double opt-in by default
Ask the receiving party privately whether they are open to the introduction and share only the minimum context needed to decide. If they decline or do not respond, close the loop with the requester without disclosing private reasons.
Close after the connection, not the outcome
Once both parties consent, send an accurate, bounded introduction that does not promise interest or a result. Record that the introduction occurred and retire contact details or background notes that no longer have an operational purpose.
Use this operating record
Capture requester, proposed recipient, purpose, requested framing, deadline, relationship owner, conflict check, information approved for sharing, consent status for both parties, final wording owner, send evidence, and retention or deletion action.
Mark each consequential fact as verified, assumed, disputed, expired, or pending. Add a source owner and checked time where the fact can change the decision. Link to restricted evidence in its proper system rather than copying confidential material into a general task tracker. Access to an inbox, calendar, document library, signature image, purchasing tool, or executive device does not create authority to decide.
The record should show four gates. At intake, define the observable outcome and consequence of delay. Before execution, verify identity, version, audience, authority, and required inputs. During execution, stop when a material fact changes. At closure, inspect the destination state and reconcile temporary access, copies, notifications, reservations, or follow-up obligations.
Work through a realistic exception
Test the workflow with one ordinary case and one exception before relying on it. Change a single fact: the requester is unfamiliar, the recipient changes, the owner is unreachable, a deadline moves forward, a source conflicts with the brief, or the destination system shows a different state. Ask who detects the difference, which stop rule applies, who may authorize resumption, and what evidence proves the corrected result.
For example, imagine the request arrives near the last useful decision time. The assistant should not hide uncertainty to make the workflow look fast. Instead, surface the verified facts, the missing fact, the safe options still available, the consequence of each option, and the named owner who can accept the residual risk. Urgency changes the update cadence; it does not manufacture authority.
Measure the workflow without rewarding shortcuts
Review introductions sent without recipient consent, requests lacking a specific purpose, declines where private reasons leaked, follow-ups that implied executive endorsement, old contact details copied into broad trackers, and response time for complete requests.
Review a small sample monthly during rollout, including both smooth cases and exceptions. Look for work that appeared complete in the tracker but was not complete in the destination system. A low escalation count is not inherently good if people have learned to conceal ambiguity. The useful measures reveal whether the office reached the intended state with proportionate control and recoverable evidence.
Roll it out in 30 days
During the first week, trace two recent examples across email, chat, calendar, documents, and the destination system. In week two, agree on owners, minimum fields, approval boundaries, stop conditions, and closure evidence. In week three, pilot the record on low- and medium-consequence work, including one tabletop exception. In week four, remove fields nobody uses, repair unclear handoffs, document the backup path, and set a review trigger for changes in people, policy, vendors, systems, or risk.
The point is not to create a longer checklist. It is to make the safe path understandable to another authorized person without requiring them to guess at the executive’s intent. That reduces avoidable back-and-forth while preserving the decisions that genuinely belong with the CEO or a qualified functional owner.
Final review questions
- What exact destination state are we trying to create?
- Which facts are current, and who owns each source?
- What remains outside the assistant’s authority?
- Which material change invalidates the present approval?
- What is the last useful decision time, including time zone?
- Which evidence will prove closure without exposing excess information?
- What temporary access, copies, or obligations must be removed afterward?
For hands-on help building reliable executive workflows, review our project and task coordination service or start a conversation.