Work Order Line Items are created under an existing Work Order, usually once you know a job has more than one task. You can add them by hand from the related list, or generate them with automation and the API. Field Service must be enabled in the org first.
- Open the parent work order
Find the Work Order record that needs subtasks. The line item always belongs to a work order, so you start from that parent rather than from a standalone tab.
- Add a line item from the related list
On the work order page, locate the Work Order Line Items related list and click New. This pre fills the Work Order lookup so the new record attaches to the right parent.
- Describe the task
Enter a Description for the subtask, then set Status and, if you use templates, choose a Work Type to pull in default duration and skills.
- Add scheduling and pricing if needed
Set Duration and Duration Type so the scheduler can place the work. If you bill at the line level, add a Pricebook Entry, Quantity, and any Discount.
- Save and book the appointment
Save the line item, then create a Service Appointment against it so a resource can be scheduled to the specific subtask.
The parent work order this line item belongs to. Required, and it sets the record into the right job hierarchy.
The current state of the subtask, drawn from the configurable WorkOrderLineItemStatus values such as New or Completed.
A short note describing what the subtask involves, so technicians and dispatchers know the work at a glance.
- Closing every line item does not close the parent work order on its own. Build a flow or rollup if you want that behavior.
- Pricing fields are optional. Many teams handle billing on the work order or elsewhere and leave line item totals blank.
- Hierarchy depth is limited. Keep the parent and root structure shallow, usually one or two levels, so it stays readable.