> 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/object-management/manage-maintenance-and-inspection-dates.md).

# Manage maintenance and inspection dates

Maintenance and inspection dates help you keep object records current.

They also give technicians service context in the field.

### Why these dates matter

These dates help you:

* see when equipment was last serviced
* prepare future maintenance work
* spot overdue service more quickly

{% stepper %}
{% step %}

### Open the object

Open the object in the BackOffice.
{% endstep %}

{% step %}

### Find the maintenance field

Locate the maintenance or inspection date field.
{% endstep %}

{% step %}

### Enter or update the date

Fill in the correct service date.
{% endstep %}

{% step %}

### Save the object

Save the updated date.
{% endstep %}

{% step %}

### Synchronize the app if needed

Let employees synchronize so they see the latest value.
{% endstep %}
{% endstepper %}

### Frequently asked questions

<details>

<summary>Can technicians update maintenance dates too?</summary>

That depends on your app permissions and settings.

</details>

<details>

<summary>Why keep this field up to date?</summary>

It improves follow-up, visibility, and service quality.

</details>

<details>

<summary>Can these dates support maintenance indicators?</summary>

That depends on your app configuration and object setup.

</details>

### Related topics

* [**View object history**](/marketplace-packages-and-power-ups/power-ups/object-management/view-object-history.md)
* [**Object Management**](/marketplace-packages-and-power-ups/power-ups/object-management.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/object-management/manage-maintenance-and-inspection-dates.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.