Some things stay yours because the consequences do

Capability is not the criterion
The question people ask is whether the tool can do a thing well. It is the wrong first question, because plenty of tasks that are performed competently should still not be handed over, and the reason has nothing to do with output quality.
A message of condolence can be written fluently. A performance assessment can be drafted persuasively. A decision about who to let go can be argued cogently. In each case the objection is not that the result is poor but that the work was the point, and delegating it changes what the act means.
This is a category people discover late, usually after doing it once and feeling wrong about it afterwards. Deciding the boundaries while nothing is at stake produces better lines than deciding them at eleven at night with a deadline.
Where the process is the product
Some work is done in order to have been done. Reading the material yourself before a decision, thinking through an argument, going over a colleague’s draft properly, sitting with a difficult problem long enough to change your mind — the output is a by-product, and obtaining the output another way delivers none of it.
Personal communication belongs here too. The value of a note to someone who is grieving, a reference for a former colleague, an apology or a thank-you is that a specific person spent their attention on a specific person. Substituting a generated version preserves the words and removes the thing they were evidence of.
The plain test is whether the recipient would feel differently on learning how it was made. That reaction is information rather than sentimentality, and if the answer is that they would mind, then the honest options are to write it yourself or to say what you did.
Accountability does not transfer
When work goes out under your name, you are answerable for it, and the fact that a tool produced the wording provides no defence to anyone. This is obvious stated plainly and quietly forgotten in practice, particularly when volume goes up and review gets thinner.
Professional obligations add a further layer that varies by field and jurisdiction. Advice given in a regulated capacity, work certified as reviewed, filings, assessments and anything carrying a duty of care may have specific requirements about human involvement, and those rules are not uniform.
The workable habit is to ask what you would say if you had to explain a decision afterwards. If the honest answer is that you did not check because it looked right, that is a warning about the review step regardless of whether anything went wrong on this occasion.
Irreversibility deserves a person
Some actions cannot be taken back: money sent, a message published, a record deleted, a contract signed, something said to a customer. Reversibility is a better guide than importance, because a reversible mistake is a nuisance and an irreversible one is an incident.
This argues for a specific arrangement rather than abstention. Let the preparation be automated and keep the irreversible step manual, with a person who reads what is about to happen and confirms it. The efficiency is preserved and the point of no return has a human at it.
The confirmation has to be real to be worth anything. A person clicking through forty approvals in three minutes is not reviewing, and a process designed that way has the appearance of oversight without the substance. Fewer, meaningful checkpoints work better than many that are ignored.
Write the line down before you need it
A short list is enough: what is never sent without being written by a person, what is never sent without being read by one, what must never be pasted in, and who decides when a case is unclear. Four sentences, agreed in advance, prevent most of the awkward decisions.
It should be revisited, because the tools change and so does what is normal. A line drawn a year ago may now be unnecessarily strict in one place and far too loose in another, and reviewing it is a short conversation rather than a policy exercise.
What matters is that the boundary is chosen rather than defaulted into. Left unstated, the line ends up wherever convenience puts it, and convenience is a poor guide to which parts of your work were carrying the responsibility.
Common questions
What is the clearest test for something I should not delegate?
Whether the recipient would feel differently on learning how it was produced, and whether the process itself was the point rather than the output. Condolence, apology, personal references and the reading you do before a decision all fail on one or both counts.
Does using a tool affect who is responsible for the result?
No. Work published or sent under your name remains yours to answer for, and in regulated fields there may be specific requirements about human involvement that vary by jurisdiction. The tool is not a party to anything and cannot carry any part of the obligation.
How should irreversible steps be handled?
Keep the preparation automated and the irreversible action manual, with a person who reads what is about to happen. For this to mean anything the checkpoints must be few enough to be read properly; a queue of approvals cleared in seconds provides the appearance of review and none of its value.
Deputy editor, Prompt After Prompt
Adrian has written about prompt craft, writing with ai, images & audio for most of the last decade and prefers a plain explanation to a clever one.