July 12, 2026
What an Agent Should Never Be Allowed to Do Without Asking
As agents earn trust through a track record of good work, it is tempting to widen what they can do unsupervised. Some actions should stay gated permanently, independent of the track record.
Sending anything to an external contact
A draft is internal. A sent message is external and, once sent, cannot be un-sent. This line should never move, no matter how good the agent's drafts have been. A person approves before anything crosses that line, every time.
Stating a number that will appear in a client-facing document
Fee figures, financial projections, or any quantitative claim about a prospect needs a named person confirming the source before it is used. The cost of a wrong number in a proposal is disproportionate to the time saved by skipping the check.
Asserting a fact about a specific relationship
Claims like 'we have not worked with this prospect before' or 'this contact previously declined a similar pitch' touch institutional memory that lives in a firm's own records, not in a model's general knowledge. These claims need to be checked against the firm's actual history before they appear anywhere.
The underlying principle
The pattern across all three is the same: actions that are irreversible, or that assert something specific about a real relationship or a real number, keep a permanent human gate. Actions that are reversible and low-stakes, drafting, formatting, initial research, are reasonable candidates to run with less supervision over time.
How this list should evolve
This is not meant to be exhaustive, and firms should expect to add to it as they encounter their own specific near-misses. The underlying test for whether a new action belongs on the permanent-gate list is simple: if this went wrong, could it be quietly fixed, or would a real person outside the firm have already seen it? Anything in the second category belongs on the list, regardless of how reliable the agent performing it has become.
Keeping the list visible, not just written down
A permanent-gate list buried in a policy document nobody rereads provides little practical protection. Posting it somewhere the team actually sees during the relevant workflow, inside the tool itself, on the approval checklist, in the weekly scorecard review, keeps it operative rather than theoretical, which matters more than how thorough the list is on paper.
Where this leaves a firm
None of this is complicated in principle, which is exactly why it gets skipped under deadline pressure. The question worth returning to before treating letting a tool act across several steps responsibly as settled is what a careful reader would actually notice if the firm got it right. On the point raised above under “sending anything to an external contact,” the answer is usually specific rather than clever: sending anything externally should always require a named person's approval. Firms that build this expectation into how they train new associates find it easier to sustain once experienced staff move on, because the standard lives in a documented habit rather than in one person's memory. The gap between a firm that talks about letting a tool act across several steps responsibly and a firm that actually practices it shows up over several quarters, not in any single engagement, and it tends to show up most clearly in the small, unglamorous checks that a client never sees directly but benefits from anyway.
It also helps to name, plainly, who is responsible for keeping this working once the novelty of a new tool wears off. Someone should own the point raised under “stating a number that will appear in a client-facing document,” check it periodically rather than assume it stays true on its own, and be the person a colleague asks when a new situation does not fit the pattern described here. Put simply: irreversible or relationship-specific actions keep a permanent gate; reversible, low-stakes ones can loosen over time. That kind of ownership, named and specific, is a small addition to a firm's process, and it is usually the difference between a good idea that is followed for a month and a standard that actually holds up over a year of real client work.
None of this needs to be elaborate to be effective. A short, dated note in a shared file, reviewed at the next quarterly check-in, is usually enough to keep the responsibility from quietly disappearing when the person who first cared about it moves on to something else.
Key takeaways
- Sending anything externally should always require a named person's approval.
- Numbers that will appear in a client-facing document need a sourced, human-confirmed check.
- Claims about a specific relationship require checking the firm's own records, not a model's memory.
- Irreversible or relationship-specific actions keep a permanent gate; reversible, low-stakes ones can loosen over time.