Executive assistant project intake checklist
A project intake checklist clarifies the outcome, sponsor, deadline, dependencies, and support required before work begins. The best version is a small operating habit with a visible result, a named owner, and a sensible point for review.
Define the outcome before building the checklist
Start by describing what should be true when the executive assistant project intake checklist is complete. The outcome might be a prepared executive, a clean decision record, a protected block of focus time, or a request that has reached the right owner. Write that outcome in one sentence so the routine can be evaluated without guessing.
Use one working record for the process. Include the date, the responsible person, the relevant source, the current status, and the next action. A shared record makes coverage easier and prevents the routine from depending on a private inbox or a person’s memory.
Run a focused first pass
Begin with fixed commitments and items that can create a delay. Review the calendar, open requests, deadlines, and handoff notes that affect the work. Do not solve every issue in the first pass. Mark decisions, missing inputs, and risks for the right review point.
Sort each item into one of four actions: complete it, prepare a recommendation, request missing information, or escalate it. Escalate work involving legal commitments, personnel decisions, sensitive relationships, material spending, or public statements unless authority has been explicitly delegated.
Make ownership and timing visible
A handoff should state the requested outcome, owner, due date, source context, and the action the assistant may take without another approval. “Draft the reply and hold it for review by 2 p.m.” is more useful than “handle the message.” When a task is blocked, record the missing input and the person who can provide it.
Keep due dates meaningful. A date should reflect when the work is needed, not merely when someone hopes to look at it. For work with dependencies, record the upstream step first and set a review point before the final deadline.
Add a review and escalation point
Review the record at a predictable cadence. Look for items carried forward twice, requests with no owner, and exceptions that keep appearing. Those patterns usually need a rule change, a clearer decision boundary, or a conversation about priorities.
Escalate with context rather than alarm. State what is waiting, why it matters, what decision is needed, and the consequence of waiting. This lets the executive decide quickly and keeps routine coordination separate from genuine judgment calls.
A compact working checklist
- Write the desired outcome and deadline.
- Gather the current calendar, requests, and source documents.
- Assign one owner and record the next action.
- Separate routine work from decisions and escalations.
- Review stale items and recurring exceptions at the agreed cadence.
For related operating context, see the executive assistant weekly planning routine and the guide to prioritizing an executive inbox. When the process includes access to sensitive systems, the official NIST access control guidance is a useful reference point.
Keep authority boundaries explicit
An assistant can organize information, draft communication, propose a next step, and keep a commitment visible. The executive or designated owner should approve a sensitive decision, financial commitment, personnel action, or public statement when the authority is not explicit. Document the boundary so coverage does not silently expand.
FAQ
How often should this process run?
Run it whenever the work changes hands or a deadline makes a missed step costly. Stable recurring work may need a daily or weekly cadence, while an exception may require an immediate review.
What belongs in the working record?
Record the outcome, owner, deadline, status, next action, and source link. Add a short note when another person may need to understand the decision later.
What if the executive does not respond?
Use the agreed response window. Send one concise reminder naming the decision, consequence of waiting, and time required. Escalate when the delay blocks another commitment or crosses a stated risk boundary.
How can the routine improve over time?
Review repeated questions, stale items, and recurring exceptions. Change the rule or record structure when the same failure appears instead of relying on people to remember another warning.