The agent drafts it. A person you name commits it.

When we show elan1 Work to a finance head, the first question is usually about speed. How quickly can the agent add the field, change the workflow, fix the tax template? The honest answer is: very quickly, on a copy. The second question, which matters more, is when that change reaches the live system. The answer is: only when a person you have named says yes.

We put that answer in the product's own line because it is the design decision everything else follows from. The agent drafts it. A person you name commits it.

Drafting and committing are different jobs

Drafting a change is a technical task. Read the request, turn it into a precise plan, build it, test it. Agents are good at that and getting better. Committing a change is a decision about the business. It says that this change is wanted, that its consequences are understood and that someone will stand behind it if it goes wrong.

Even if that figure were 99%, the second job would not move to the agent. A trial balance that still ties proves the books hold. It does not prove the change was a good idea, that it matches the dealer agreement, or that the finance head wants it before the quarter closes. Those are judgements, and they belong to the people who answer for the books.

What the agent does before it stops

1. 01Turns a request written in plain words into a plan anyone can review.
2. 02Builds the change on a copy of your system, never on the live one.
3. 03Runs your own checks: does the trial balance still balance, does stock still reconcile, does the GST return still generate, is the audit trail intact?
4. 04Writes a summary of what changed, what was checked and what passed, and puts it in front of the person you named.

What the agent never does

Some actions are outside the agent's reach however the request is phrased. In elan1 Work the agent will never make a payment, change bank details, post into a closed period or amend a filed return. It prepares e-invoices; a person files them. It never holds the live credentials: the change goes live through elan1 Govern, with credentials the agent does not see.

Who the person is

Usually the finance head, sometimes the plant controller, often with the company's chartered accountant reviewing alongside. A CA can see every change and its checks from their own console, which matters for the many Indian businesses whose CA is the closest thing they have to an internal auditor. I have written a short guide on putting an agent to work through your CA.

The person approves in the console or by phone, with the summary in front of them. If they are not sure, they say no, and nothing happens to the live books. If they say yes and later regret it, every change can be reversed for 30 days, and the reversal is checked too.

What the pause costs

It costs time. An agent that committed its own changes would be faster by however long your approver takes to read a page. For most ERP changes that is minutes. For a change made late on the last day of the month, it might be the next morning. We think that is the right trade. A change that waits until morning can still be made. A change that broke a GST return three weeks ago costs far more to unmake, as one illustrative case shows.

elan1 Work is designed, not yet generally available. It starts on Frappe/ERPNext and Twenty CRM, with Zoho CRM next. The status of each part is on the elan1 Work page.