Executive assistant board packet workflow
Byline: RemoteExecutiveSupport Editorial Team
A board packet workflow with deadlines, owners, version control, and a final executive review. The useful version is short enough to repeat and specific enough that another person can follow it. Start with the decision or outcome the routine is meant to support, then give each step an owner.
Define the point of the routine
Before adding a checklist, write down what a finished board packet workflow looks like. A morning review may end with a short brief and three decisions. A file routine may end with the right people having access to the current version. If the end state is vague, the routine will collect activity without making work easier.
Use one working record for the routine. Include the date, the owner, the items needing attention, and the next action. Keep background links near the item they explain. This makes the record useful to someone covering the work, not just to the person who created it.
Run the first pass
Start with the fixed commitments and the items that can cause a delay. Review the calendar, open requests, deadlines, and any handoff notes that affect the day. Do not try to solve every issue during this pass. Mark unclear items for a decision and keep moving.
The first pass should answer four questions:
- What cannot move?
- What needs preparation?
- What is waiting for the executive?
- What could become urgent if nobody owns the next step?
Then group the answers by action. Handle routine work, prepare a recommendation for a choice, and escalate items that involve money, legal commitments, personnel, sensitive relationships, or publication.
Make the handoff clear
A good handoff states the context, the requested outcome, the owner, and the time when an update is due. It also states what the assistant may do without another approval. That last line prevents a common failure: a task that is technically assigned but still waits for permission at every step.
Use plain language. "Draft a reply and hold it for review by 2 p.m." is more useful than "handle the message." If the work is blocked, record the missing input and the person who can provide it. A blocked task should not look active in the tracker.
Add a review point
Review the routine at a predictable time. The review can be five minutes if the work is stable. Look for items carried forward twice, requests with no owner, and exceptions that keep appearing. Those patterns usually call for a rule change or a conversation about priorities.
Keep the review separate from a general status meeting. The aim is to improve the routine and close open loops, not to retell every completed task. Close finished items and leave a short note for anything that needs context later.
A small working checklist
- Confirm the outcome and the deadline.
- Gather the current source documents and calendar context.
- Separate routine actions from decisions and escalations.
- Record the owner and the next update time.
- Review exceptions and stale items at the agreed cadence.
For broader weekly context, compare this routine with the executive assistant weekly planning routine. For inbox-related requests, use the guide to prioritizing an executive inbox. The official NIST access control guidance is a useful reference when the routine touches sensitive files or permissions.
What to keep outside the routine
Do not let the checklist become a place for unapproved commitments. An assistant can organize information, draft a message, and propose a next step. The executive or designated owner should approve a sensitive decision, a financial commitment, a personnel action, or a public statement when the authority is not explicit.
FAQ
How often should this routine 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 can require an immediate review.
What should be recorded?
Record the outcome, owner, deadline, current status, and next action. Add the source link or document when another person may need to verify the context.
What if the executive does not respond?
Use the agreed response window. Send one concise reminder with the decision, the consequence of waiting, and the time needed. Escalate only when the delay blocks another commitment or crosses a stated risk boundary.
How do I know the routine is working?
Look for fewer repeated questions, fewer stale items, and clearer handoffs. If the same exception appears often, change the rule instead of asking people to remember a warning.