> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/forms/use-forms-with-objects.md).

# Use Forms with objects

Some forms belong to a specific object instead of only to a work order.

This is useful for inspections, maintenance records, and asset history.

### Why object-linked forms help

Object-linked forms:

* keep the result tied to the right asset
* make service history easier to review
* give technicians the right context during the job

{% stepper %}
{% step %}

### Prepare the form

Create the form you want to use in the object-based process.
{% endstep %}

{% step %}

### Make sure the work order has the right object

Check that the work order is linked to the correct object.
{% endstep %}

{% step %}

### Open the form on the work order

Open the form from the work order in the app.

Select the right object if prompted.
{% endstep %}

{% step %}

### Complete and save the form

Save the form.

The result is stored with both the work order and the object.
{% endstep %}
{% endstepper %}

### FAQ

<details>

<summary>When should I use object-linked forms?</summary>

Use them when the result belongs to a specific installation or asset.

</details>

<details>

<summary>Do object-linked forms help with service history?</summary>

Yes.

They make it easier to review work done on one object over time.

</details>

<details>

<summary>Should every form be linked to an object?</summary>

No.

Only use object linking for asset-based processes.

</details>

### Related topics

* [Create a form](/marketplace-packages-and-power-ups/power-ups/forms/create-a-form.md)
* [Object Management](/marketplace-packages-and-power-ups/power-ups/object-management.md)
* [Add objects to forms](/marketplace-packages-and-power-ups/power-ups/object-management/add-objects-to-forms.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/forms/use-forms-with-objects.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.