> 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/customers-and-work/scheduling/reserve-inventory-flag-expected-asset-inspections-and-two-kinds-of-notes.md).

# Reserve inventory, flag expected asset group inspections, and two kinds of notes

Step 1 has a **Parts, Labor & Items** editor, available whether or not your business uses inventory. Add pricebook parts, labor, and one-off items here. The plan appears on the job page, scheduling popover, and technician app without requiring Inventory or Job Costing.

With Inventory off, saving this list does not reserve or deduct stock. With Inventory on, tracked items show availability and saving reserves them from the **Reserve From** location. This replaces the separate Reserved Inventory section. Only tracked stock affects inventory; labor and untracked items work the same in either mode.

The plan and reservations belong to the job, not each visit. Editing any visit on a multi-day job updates the same plan without reserving a second copy. Existing job reservations appear in the editor. Saving the plan does not deduct on-hand stock: actual quantities recorded by the technician consume reservations and deduct stock. Removing an unused planned part releases its reservation; it does not undo already-recorded usage.

Stock warnings compare availability with the work still remaining, including quantities already recorded while Inventory was off. If you remove a part from the plan and later correct its actual usage to zero, it no longer appears as a suggested item in the technician summary; its inventory history is retained.

If Expected Asset Group Inspections is enabled in Settings > Scheduling > Features, an expected-asset-group field with a clipboard icon lets you warn if certain asset groups aren't inspected on this visit.

You can pick specific active, non-deleted asset groups already on the property or pick a type so the technician is prompted to create one if it doesn't exist yet. **Select all** appears when the property has at least two eligible asset groups. Generic type choices are limited to types that have an inspection report. Inactive or deleted asset groups do not appear in the picker and no longer produce missing-inspection warnings. This is optional and only produces a warning.

There are two note boxes, and they are not the same. Technician Instructions are visible to both back office users and technicians. Scheduling Instructions are visible to back office users, and to technicians who can self-schedule when the visit sits in their Open tab (so they can book it the way you intended). Technicians never see them on an assigned visit, so use that box for scheduling context rather than on-site instructions.

> **Where to find it:** All of these live on step 1 (Add Details) of the visit form: Parts, Labor & Items above the instructions, the clipboard field below work orders, and two separate note boxes.

## Related guides

* [Add work orders (visit types) and contacts with reminders to a visit](/customers-and-work/scheduling/add-work-orders-visit-types-and-contacts-with-reminders-to-a-visit.md)
* [Create a new visit](/customers-and-work/scheduling/create-a-new-visit.md)
* [Exact time vs. estimated, duration, technician count, and due date](/customers-and-work/scheduling/exact-time-vs-estimated-duration-technician-count-and-due-date.md)
* [Set a visit's arrival window](/customers-and-work/scheduling/set-a-visits-arrival-window.md)
* [Deleting a scheduled visit is permanent](/customers-and-work/scheduling/deleting-a-scheduled-visit-is-permanent.md)
* [Turn scheduling and GPS features on or off](/administration/settings/turn-scheduling-and-gps-features-on-or-off.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/customers-and-work/scheduling/reserve-inventory-flag-expected-asset-inspections-and-two-kinds-of-notes.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.