On this page
Published November 9, 2026
Design a second-reviewer rule for delegated work
How to approach: Design a second-reviewer rule for delegated work
A second reviewer is warranted when an error would be costly, hard to reverse, or visible to a client. Start with the consequence, not the task type. A rule that reviews everything stops being a control. Review the first few notes together before the process expands. The assistant should record the owner before the next task starts. A commitment that is not checked is not a control.
Write the rule as a short set of triggers with examples. The assistant should be able to classify the task without asking. Review the first few notes together before the process expands. Keep the original note beside the corrected version. Test the brief on one real task before expanding the role.
Start from the consequence
Ask what happens if the task is wrong and nobody catches it. A small delay may be fine; a financial loss or a client commitment is not. The answer determines the review. Use the same format for every handover so the next reader can scan it. The review should end with one owner and one date. Test the brief on one real task before expanding the role.
Consider how hard the error is to reverse. A sent email cannot be unsent; a draft can be edited. A control that depends on memory is not yet a control. Write the deadline as a date and a local time. The review should end with one owner and one date. The assistant should record the owner before the next task starts.
Name the reviewer and the evidence
Name the role with the authority to approve or reject. Record the source, the output, and the reason the task was routed. A review without evidence is a second opinion. Name the owner in the same line as the action. A commitment that is not checked is not a control.
Set a review deadline that fits the task. A client-facing statement may need same-day review. Separate what was observed from what was assumed. Use the same format for every handover so the next reader can scan it. Test the brief on one real task before expanding the role.
Keep routine work out of the queue
Reviewing everything teaches the team to treat the review as a formality. Keep routine work on a sampling path. The sample checks quality without adding an approval step. Record the exception and the person who approved it. The review should end with one owner and one date. The principal should see the decision and the evidence on one page.
Revisit the triggers when the work changes. A low-risk task may become high-risk after a new client. Ask whether a new reviewer could act on the record without a conversation. Record the exception and the person who approved it. The assistant should record the owner before the next task starts. A commitment that is not checked is not a control.
Review the rule after an error
When an error reaches a client, ask whether the task should have been reviewed. Update the trigger or the review step. Do not blame the assistant for a boundary the process did not make clear. Keep the boundary visible in the place where the work is assigned. The handover should say what the next person may decide. The review should end with one owner and one date.