Published October 22, 2026
Delegation usually fails quietly. A task sits with the owner for approval, the assistant assumes it is approved, and the deadline passes. A weekly review exists to catch those gaps before they become missed commitments. It should take fifteen minutes, not an hour, and it should review the system rather than recite every task.
The meeting is not a performance review for the assistant. It is a short control on a shared queue.
Table of contents
- What the review must decide
- The fixed agenda
- Prepare the one-page view
- Ask about blockers, not activity
- Record decisions and owners
- Sources
- Frequently Asked Questions
What the review must decide
A useful review answers four questions:
- What is waiting on the owner, and by when?
- What was reopened or reworked, and why?
- What is coming next week that changes capacity?
- What rule or source needs fixing?
If the agenda does not produce a decision on at least one of these, the meeting is probably a status update that could have been written.
The fixed agenda
| Minutes | Item | Output |
|---|---|---|
| 0–3 | Waiting on owner | Decision or new due time for each item |
| 3–6 | Defects and rework | One root-cause fix, not a blame discussion |
| 6–9 | Next week's commitments | Confirm capacity and absences |
| 9–12 | One improvement | Assign an owner and a test date |
| 12–15 | Open questions | Route or close |
Keep the order. Starting with whatever feels urgent crowds out the system issues that create urgency next week.
Prepare the one-page view
The assistant prepares a single page before the meeting:
- Waiting on owner: task, requester, decision needed, age, due time.
- Waiting on someone else: external party, last attempt, next check.
- Reopened: task, reason category, count of reopenings.
- At risk: deadline within seven days with an open dependency.
- Next week: travel, leave, board or client commitments, known heavy days.
The page should link to the underlying record, not duplicate it. If a task cannot be found from the page, the record is incomplete.
Ask about blockers, not activity
" What did you work on?" produces a list. "What is blocked, and who owns the next step?" produces action.
Useful prompts:
- Which item has been waiting the longest for my decision?
- Which task was sent back more than once, and what was missing the first time?
- What did we promise this week that we cannot support next week?
- Which request arrived without enough information to start?
The assistant should answer with facts from the queue, not guesses about the owner's preferences. The owner should answer with decisions, not new instructions that reopen completed work.
Record decisions and owners
Every decision gets a line in the review record: date, item, decision, owner, effective time. If a decision changes a recurring process, update the task brief rather than relying on memory.
Track two measures over time:
- Reopen rate: the share of completed tasks returned for material rework.
- Owner wait time: the median age of items waiting for an owner decision.
A rising owner wait time is often a capacity problem above the assistant. A rising reopen rate is often a brief or quality-bar problem. Neither is solved by asking the assistant to try harder.
The O*NET administrative assistant profile treats information coordination and record maintenance as core work. A review that updates the record is part of the job, not an interruption.
Sources
- O*NET OnLine: Executive Administrative Assistants
- Bureau of Labor Statistics: Occupational Outlook Handbook
- U.S. Department of Labor: Hiring
- NIST Privacy Framework
Frequently Asked Questions
What if there is nothing to discuss?
Keep the meeting but shorten it. Confirm the waiting list is empty, check next week's capacity, and end. Cancelling repeatedly makes the review unreliable when a real issue appears.
Should the assistant run the review?
The assistant can prepare the page and keep time. The owner should make the decisions. Rotating facilitation is fine if the decision owner is named for each item.
How do we avoid turning it into a status meeting?
Use a one-page view that everyone can read in advance, and spend the meeting only on decisions and exceptions. If an item needs a long discussion, schedule it separately.
Review cadence
Keep the review to 30 minutes and end with three named actions. Review the previous actions first, then the new requests, then the capacity question. If the agenda consistently runs long, cut the number of items rather than the review. The meeting exists to make the next week easier, not to document how busy everyone is.
A good agenda leaves time for the capacity question: what should stop, what should move, and what needs a decision before the next week. Without that section, the review becomes a status report and the same items return. End by confirming the three actions in writing and the date they will be reviewed. A short written recap is the difference between a meeting and a decision. Keep the recap short, specific, and tied to the next review date.