On this page
Published November 8, 2026
Plan a weekly delegation review on evidence
How to approach: Plan a weekly delegation review on evidence
A weekly delegation review should answer one question: which items need a decision this week, and who will make it. Everything else belongs in the written queue. If the meeting reviews every task, it becomes a status report. Ask whether a new reviewer could act on the record without a conversation.
Choose the items before the meeting. The queue owner should select the items that are blocked, aging, or waiting on an approval. Send a short evidence pack in advance so the meeting starts with the facts. Write the deadline as a date and a local time.
Prepare a short evidence pack
For each item, include the request, the source, the open question, the owner, and the next step. Keep it to one page. A pack that takes an hour to read will not be read. Review the first few notes together before the process expands.
Do not include the entire history. Link the relevant records and summarize the rest. The purpose is a decision, not a demonstration of effort. Keep the evidence with the record rather than in a separate log.
Review items by next action
Group the items by the decision they need: approve, decide, review, or unblock. This turns a list of tasks into a list of decisions. It also shows when one approver is the bottleneck. Keep the evidence with the record rather than in a separate log.
For each group, ask what would change the current position. If nothing would change it, the item may not need a meeting slot. Move it back to the queue with a future review date. Name the owner in the same line as the action.
Limit the meeting to decisions
Do not read updates that everyone already has in writing. Ask the decision maker for a choice, a condition, or a request for specific evidence. Record the answer in the queue during the meeting. Review the first few notes together before the process expands.
If a decision cannot be made, name the missing person or evidence and set a date. Every discussed item should leave with an owner. Name the owner in the same line as the action. Separate what was observed from what was assumed.
Assign owners in the room
An action without a named owner is a suggestion. Assign each next step to one person and confirm that the person accepts it. If the owner is not in the room, confirm the assignment before the meeting ends. A control that depends on memory is not yet a control.
Keep the list of actions realistic for the week. Choose the few that matter most and leave the rest in the queue with their existing dates. Keep the boundary visible in the place where the work is assigned. Review the first few notes together before the process expands.
Follow up and measure movement
Send a short written summary the same day with the decisions, owners, and dates. Check the summary against the queue before sending it. The written record and the system record should tell the same story. Keep the evidence with the record rather than in a separate log.
At the end of the month, review the actions that came out of the review. How many were completed by the date, and how many moved the item forward? A meeting that produces actions but no movement is not working. Record the exception and the person who approved it.