> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/using-the-essential-assistant/reviewing-a-bulk-change-from-the-assistant.md). # Reviewing a bulk change from the Assistant When one operation would change more than 15 records, the Essential Assistant groups the proposal into one or more review tables. Requests affecting 15 or fewer records use the ordinary action confirmation card. Nothing changes until you confirm it. Not every action can be reviewed in bulk. Actions such as sending invoices or quotes, creating tasks, or rescheduling visits always use the ordinary confirmation card, however many records they cover. A bulk review can include up to 10,000 changes. If your request exceeds that limit, narrow it into smaller sets. ## Open the review The chat shows a compact **Bulk changes** card with a summary and the number of changes in each table. Choose the primary **Review changes** button to inspect the records on the full review page, or choose **Confirm all N changes** on the card when you have already reviewed the summary and want every row included. Each section of the review page names the action that will run and shows four counts: total rows, selected rows, completed rows, and failed rows. Sort a column by choosing its heading. Use the page controls below a table to move through larger sets. A row can also **add** something rather than change it — for example, each new asset when you ask the Assistant to add dozens of assets to an inspection report. Those rows name the new asset ("New Initiating Device — Floor 3 — Smoke Alarm"), show **Not on report** as the current value, and list what the asset will be filled in with. ## Choose which rows to include Every row starts selected. Clear the checkbox beside a row to leave that record unchanged. The **All** checkbox in a table selects or clears that entire table. Your choices stay in place when you sort the table or move to another page. The confirmation bar above the tables stays visible while you scroll and shows the total number of selected changes across all tables. Choose **Confirm N changes** to run exactly that selection. Choose **Discard** to reject the whole proposal. Some rows depend on each other — for example, several changes to the same asset on a report — and must be confirmed or left out together. If your selection splits such a group, Essential tells you which rows to include or clear before it runs anything. If you change the selection and try to leave before confirming, Essential warns that the selection has not been saved. A partial selection belongs only to that open review page; opening the card again starts from the proposal's full selection. ## If the records changed after the review was built A review shows each record as it was when the Assistant built it. When you confirm, Essential checks the selected records again. If any of them has changed since — someone edited a note, a quote moved to a new status, a record was deleted — nothing runs, and Essential names the affected records. Ask the Assistant for a fresh review so you approve changes against what is there now. ## Follow the outcome When you confirm or discard, Essential takes you back to the page you opened the review from — an inspection report, for example — with the Assistant chat open. The **Bulk changes** card shows the work running, then how many changes are done or failed, and the page behind it refreshes when the work finishes. The Assistant follows up in the chat when the batch is done. The work continues on Essential's servers even if you move to another page. To see the result of each row, choose **Review changes** on the card again. On the review page the checkboxes have become an **Outcome** column, which labels each row as waiting, running, done, failed, skipped, or not selected. A failed row includes the safe error message returned by the action. The page refreshes while work is still running. Some tables run as one bulk action. In that case every selected row in the table has the same outcome. If an earlier action fails, later actions are skipped rather than continuing with only part of the requested sequence. If you opened the review page directly from a link rather than from the chat card, confirming keeps you on the review page so you can follow the outcome there. Choose **Back to conversation** at any time to return to the Assistant chat that created the review. > **Where to find it:** Essential Assistant > Bulk changes card > Review changes ## Related guides * [Asking the Assistant to do things: actions you confirm](/administration/using-the-essential-assistant/asking-the-assistant-to-do-things-actions-you-confirm.md) * [Using the Essential Assistant](/administration/using-the-essential-assistant.md) * [What the Essential Assistant can and can't do](/administration/using-the-essential-assistant/what-the-essential-assistant-can-and-cant-do.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://learn.withessential.com/administration/using-the-essential-assistant/reviewing-a-bulk-change-from-the-assistant.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.