> 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/f-gases-forms-koudsmart/use-koudsmart-in-work-orders.md).

# Use KoudSmart in work orders

KoudSmart fits into the work order flow when technicians handle refrigerants on site.

That keeps registration close to the actual service moment.

### Typical KoudSmart inputs on a work order

* installation context
* filling or recovery details
* quantities and reasons
* cylinder information

{% stepper %}
{% step %}

### Open the work order

Open the work order that involves refrigerant handling.
{% endstep %}

{% step %}

### Check the linked object

Make sure the correct installation or object is linked.
{% endstep %}

{% step %}

### Complete the KoudSmart part

Register the handling details through the available KoudSmart form flow.
{% endstep %}

{% step %}

### Save the work

Save the form and complete the work order according to your process.
{% endstep %}
{% endstepper %}

### Frequently asked questions

<details>

<summary>Why should the object be linked?</summary>

It improves installation-level traceability.

</details>

<details>

<summary>Is KoudSmart needed on every work order?</summary>

No.

Use it when the work includes refrigerant handling.

</details>

<details>

<summary>Does this data affect reporting?</summary>

Yes.

Work order data can feed the KoudSmart registration.

</details>

### Related topics

* [**Use KoudSmart in forms**](/marketplace-packages-and-power-ups/power-ups/f-gases-forms-koudsmart/use-koudsmart-in-forms.md)
* [**Object Management**](/marketplace-packages-and-power-ups/power-ups/object-management.md)
* [**Understand refrigerant registration**](/marketplace-packages-and-power-ups/power-ups/f-gases-forms-koudsmart/understand-refrigerant-registration.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/f-gases-forms-koudsmart/use-koudsmart-in-work-orders.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.