> 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/field-operations/inspection-reports/working-with-the-assets-on-an-inspection-report-bulk-pass-skip-delete.md).

# Working with the assets on an inspection report (bulk pass, skip, delete)

## The number on each asset

Each asset card is labelled with its item number — "3." — the number the asset will have on the published report. Assets are numbered in report order; a skipped or deleted asset shows no number and does not take one, so the assets after it move up exactly as they will on the report. Skipped assets use a yellow/orange **Skipped** pill; deleted assets use a red **Deleted** pill. An asset added during this report is numbered right away. The number belongs to the asset, not to the row, so narrowing the list leaves gaps (1, 2, 4, 5) rather than renumbering. If an asset was removed from the asset group after the report was started, its row shows a red **Deleted** pill and no number, and the published report leaves that row out. That row is read-only, does not hold the report back from publishing, and publishing ignores it: no deficiency, service completion, or attribute update is recorded for the deleted asset. Any parts entered on it still count as parts used. Rows without a number — skipped or deleted — sit at the bottom of the list, below the numbered rows. On the asset group page every asset has a position number instead; the two match when the report includes the same assets in the same order.

## Search and filter assets

Use **Not Done**, **Done**, and **All** to narrow an asset list by completion status. Click **View** above the list to open a popover card with a search box, **Filters**, then **Group by**. Type in the search box to match values such as location, barcode, serial number, and dropdown labels.

To narrow the list by one field, click **Add Field Filter** under **Filters** and choose the field. **Filters** also lets you show only assets with a deficiency (**Has Deficiency**) or without one (**No Deficiency**). For a dropdown, select one or more values; an asset can match any selected value. For a text field, enter text that the value must contain. The value counts and matching-asset count update while you configure a filter.

Everything in the panel applies immediately; there is no Apply button. Your search, grouping, and filters appear as chips under the tabs. Click a chip to edit it or click its × to remove it. Multiple field filters stack, so an asset must match every chip. Click **Clear** inside View to remove them all. A dot on **View** shows that something is applied.

## Work through assets by group

To work through a large list one area at a time, click **View** and pick an attribute under **Group by**, such as Location or Floor. The list shows one group for each value of that attribute. Pick the same attribute again to return to the flat list.

Each group shows how many of its assets are inspected and any deficiency count. Click it to open only that group’s assets within the report pane. A light teal bar below the group name shows **Group n of count**, its position in the full group order. The report navigation and preview remain available. Use **All groups** at the top to return to the overview and open another group. Returning preserves your filters and overview scroll position.

Inside a group, **Not Done**, **Done**, **All**, search, filters, and **Select All** apply to that group’s assets. Switching groups clears the selection. On the overview, Select mode lets you select matching assets across groups using each group’s checkbox.

Adding an asset inside a group prefills its grouping value. If you edit an asset’s grouping value, its editor stays open while you finish; returning to all groups shows its new group. Links to a specific asset open its group automatically.

Groups follow the same order as the assets themselves: a group appears where its first asset sits in the asset order. From the group overview, open the **three-dot menu** to the right of **View** and choose **Reorder** to open the **Reorder Groups** screen — drag them into your preferred walk order and click **Save**. Saving puts this report's assets in the group order you set, preserving the order within each group. The asset order is shared across web and mobile. Assets absent from this report keep their existing positions, so they may sit between group members in the full asset list. To reorder items within one group on web, open that group and choose **Reorder** from the same menu. Only that group’s items move; other items keep their places. You can also reorder individual assets on the flat (ungrouped) list.

To make a grouping the default view, click **Save grouping** and confirm. This action is available once the asset group exists; for a new group, publish the report first. All reports for that asset group — past, present, and future, for anyone in your business on web and mobile — use that default when opened. The button reads **Grouping saved** for the saved view; click it and confirm **Remove grouping** to remove the default. Changing or clearing your current grouping stays local until you explicitly save a new default. Removing the saved default keeps your current view and open group unchanged. Each asset group remembers its own choice, so the same equipment type can default to Floor at one property and Building at another.

## Select assets and use bulk actions

When a report inspects several assets, each one is a card you fill in, and you can act on many at once. On web, open the **three-dot menu** to the right of **View** and choose **Select** to turn on checkboxes, then use Select All or Clear Selection; a counter shows how many are selected.

With assets selected you can Skip them (marks them not inspected) or Delete them (removes them from the report) - and Pass them, but the Pass button only appears when the report's definition is set up for bulk pass (it has bulk-pass fields); if the definition doesn't enable it, there is no Pass.

Delete is blocked when it would drop the group below the minimum it requires (the button is disabled and reads "At least N must remain"). After a bulk action an Undo banner lets you reverse it.

On a single asset (its card or the ... menu) you can Skip it (then Undo), Duplicate it to add more copies with fresh answers (if the group allows more), or Delete it (if the group allows fewer). Bulk pass is not available on every asset list. The minimum and maximum number of assets allowed in a group come from the asset type.

## Restore a deleted asset

Deleting an asset can be undone at any time before you publish. On web, open the asset's card: where it said **Delete**, it now says **Restore**. Click **Restore** to bring the asset back into the report with the answers it had; the card stays open so you can keep working. If the group already holds its maximum number of assets, **Restore** is disabled and reads "At most N allowed" when you hover it — delete another asset first. The same limit applies to anything else that would bring a deleted asset back — **Skip** on the deleted asset, or a bulk **Pass**, **Skip**, **Answer**, or **Undo** that includes deleted assets: it is disabled with the same "At most N allowed" reason (hover it, or tab to it with the keyboard, to see why). In the mobile app, open the deleted asset, tap the **three-dot menu** in the top right, choose **Restore Asset**, and confirm.

An asset that was removed from the asset group itself (not just from this report) can't be restored here, because it no longer exists.

## Reorder assets

To reorder an existing asset group, choose **Reorder**, drag the previously saved assets into the order you want, and select **Save**. While you reorder, the rows carry no numbers; the item numbers reappear on the list as soon as you save the new order. Assets created during the current report are not included in an existing group's reorder list until they have been saved. In the mobile app, reconnect before reordering an existing group. Assets added to the group after this report was created do not appear in the report, and reordering here leaves them exactly where they are in the group's order.

You can also reorder assets while the report is creating a new asset group. On the web, **Save** in the reorder view keeps the arrangement in the open form; use the report's main Save action to persist the draft before leaving. On mobile, the draft order can be saved through the offline queue. Publishing creates the new asset group and its assets in that saved order.

> **Where to find it:** On the open report's asset list - use **View** to search, group, and filter the list, or the **three-dot menu** beside it for **Reorder** and **Select**; each asset card also has Skip, Duplicate, and Delete (Restore on a deleted asset)

## Related guides

* [Answer a question on many inspection assets at once](/field-operations/inspection-reports/answer-a-question-on-many-inspection-assets-at-once.md)
* [Editing an inspection report through the Assistant](/administration/using-the-essential-assistant/editing-an-inspection-report-through-the-assistant.md) — the same bulk pass, skip, delete and reorder can be asked for in the chat
* [Can I move an inspection report to another customer or property?](/field-operations/inspection-reports/can-i-move-an-inspection-report-to-another-customer-or-property.md)
* [Duplicate an inspection report](/field-operations/inspection-reports/duplicate-an-inspection-report.md)
* [Save a draft and publish an inspection report](/field-operations/inspection-reports/save-a-draft-and-publish-an-inspection-report.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/field-operations/inspection-reports/working-with-the-assets-on-an-inspection-report-bulk-pass-skip-delete.md?ask=<question>&goal=<user_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.
