On this page
The two-person rule for executive requests that cannot be undone

Most executive support work can be corrected after the fact. A meeting can be moved, a draft can be revised, and a travel booking can usually be changed for a fee. A smaller set of requests cannot be undone so easily: a payment, a signature, a permanent deletion, or a message sent to a regulator. Those requests deserve a second set of eyes, not because the assistant is untrusted, but because the cost of a mistake is asymmetric.
Why irreversible requests need a different control
A two-person rule is a control, not a sign of mistrust. It requires a second authorized person to review the request before the assistant executes it. The reviewer checks the request against its source, the authority behind it, and the consequence of getting it wrong. This is the same logic behind separation of duties in security frameworks such as NIST SP 800-53, where no single person should control every step of a sensitive transaction (NIST).
The rule works only when the category is narrow. If every expense report and calendar change needs two approvals, the process will collapse under its own weight. Define the irreversible set in advance, write down examples, and review the list each quarter. The goal is a short list that people respect, not a long list that people route around. A short list also makes the reviewer's job concrete.
Define the irreversible set
Start with actions that cannot be recalled or whose reversal requires another party. Payments above a stated threshold, wire instructions, contract signatures, regulatory filings, account deletions, and changes to access rights are common examples. Public statements and messages to clients, investors, or the press also belong on the list because a retraction rarely repairs the first impression. The category should be written in plain language so a new assistant can apply it without asking for permission on every item.
Add requests that create a legal or financial commitment even if they look routine. A verbal promise to a vendor, a discount approved in an email, or a hotel booking made under a corporate rate can all become obligations. The assistant should be able to point to the clause, policy, or prior approval that authorizes the action. If that evidence is missing, the request is not ready for the second review.
Leave reversible work outside the rule. Rescheduling an internal meeting or updating a contact record does not need a second reviewer, and treating it like a wire transfer wastes the reviewer's attention. Keeping the boundary visible protects the credibility of the control and gives the assistant room to move quickly on ordinary work. When a request sits near the line, treat it as irreversible until the owner confirms otherwise.
Assign the two roles, not two warm bodies
The first role is the preparer. This person gathers the request, verifies the source, checks the authority, and writes a short summary of what will happen if the request is approved. The preparer does not need to be the assistant who will execute the action, but that person should be close enough to the work to notice missing context. A preparer who only forwards a message has not prepared anything.
The second role is the reviewer. The reviewer must have the standing to say no and the knowledge to recognize a bad request. A colleague who simply clicks approve without reading is not a control. For financial actions, the reviewer should be separate from the person who initiates the payment. For access changes, the reviewer should understand the role and the data involved.
Name backups for both roles. A two-person rule that stops when one person is on leave becomes a bottleneck and then an excuse. The backup should be trained on the same checklist and should know where the record lives. If no qualified reviewer is available, the request waits or escalates to the executive; it does not proceed with a single pair of hands.
Make the review fast and documented
A good review takes minutes, not hours. The preparer should send four things: the requested action, the source of the request, the authority that permits it, and the consequence of waiting. The reviewer should respond with approve, reject, or return for more context. A free-text discussion is acceptable only when it produces one of those three outcomes. The format matters less than the consistency of the four inputs.
Record the decision in the same system that holds the underlying request. Include the time, the two names, the evidence checked, and any condition attached to the approval. Do not copy sensitive message bodies into the log; a link to the approved record is usually enough. The log should let a later reviewer reconstruct why the action was allowed without guessing.
Set a response window that matches the risk. A wire transfer may need a reviewer within thirty minutes during business hours, while a contract signature may have a one-business-day window. Publish the window so the requester knows when to expect a decision. If the window is missed, escalate rather than skipping the review. The window should be written in the operating rule, not left to memory.
Handle exceptions without erasing the rule
Some situations will not fit the normal path. A safety incident, a legal deadline, or a system outage may require immediate action before a second reviewer can be reached. Write a short exception process that names who can authorize the action, what must be recorded afterward, and when the review happens. The exception should be rare enough that people remember using it.
Review every exception at the next weekly or monthly operations meeting. Look for the cause: an unclear threshold, a missing backup, or a reviewer who was unavailable. If exceptions cluster around one type of request, the rule may be drawn in the wrong place. Adjust the boundary instead of blaming the person who used the escape hatch. The meeting should end with one change to the rule or a decision to leave it alone.
Test the rule before you need it
Run a tabletop exercise with a realistic request. Pick a payment, an access change, or a client message that would be costly to reverse. Walk it through the preparer and reviewer roles, including the evidence they would check and the place they would record the decision. The exercise will expose unclear authority faster than a policy document. Invite the reviewer and the backup, not only the assistant.
After the exercise, update the checklist and the examples. Then test again in a month with a different request type. The rule is working when the reviewer can explain the decision without opening a long policy, and when the preparer can complete the check without slowing the rest of the day. A control that people skip in a busy week is not protecting anything.
Key takeaways
- Define a short, explicit list of irreversible requests and review it quarterly.
- Separate the preparer from the reviewer, and name trained backups for both roles.
- Require four inputs: action, source, authority, and consequence of delay.
- Log every decision and review exceptions for patterns rather than blame.
For the authority layer underneath this control, see the decision-rights charter and the delegation reversibility test. Both explain how to assign approval rights before a request reaches the queue. The research note on reversibility labeling offers a way to classify actions by how easily they can be undone. Use those references to keep the two-person rule narrow and testable. Keep the rule visible in the same workspace as the request queue.