# Mark an Equipment Instance Out of Service (/how-to/equipment/mark-out-of-service)



When a specific physical unit is unavailable for rental — engine in the shop, water damage from a recent rental, missing paddle, whatever — mark that instance **Out of service**. Resytech reduces the equipment's effective fleet by one for as long as the toggle is off, so new bookings can't oversell against a unit you can't deliver.

Flip the toggle back to **Bookable** when the unit returns to service, and capacity returns immediately.

Before you begin [#before-you-begin]

* You need access to the Resytech Dashboard with the **Resources** permission.
* The unit must already be registered as an instance. If it isn't, [add the instance first](/how-to/equipment/add-instance).
* Existing bookings that already reserved this equipment aren't affected — the reduction only applies to *new* availability checks going forward.

Steps [#steps]

You can flip the toggle from two places — the quick-edit modal or the instance detail page. Both behave the same.

From the instance list (fastest) [#from-the-instance-list-fastest]

1. In the sidebar, click **Equipment** and click into the equipment item.
2. Click **Settings**, then choose the **Instances** tab.
3. Find the unit and click the pencil (quick edit) icon on its row.
4. In the dialog, flip the **Status** toggle to **Out of service**.
5. Click **Save Changes**.

The row updates immediately with an amber "Out of service" pill next to its name.

From the instance detail page [#from-the-instance-detail-page]

1. From the Instances list, click the row to open the detail page.
2. In the **Details** section, flip the **Status** toggle to **Out of service**. Notice that **Save Changes** becomes enabled.
3. Click **Save Changes**.

What happens next [#what-happens-next]

* The instance shows an amber "Out of service" pill in the list, with a wrench icon, so any operator looking at the inventory sees the status at a glance.
* Booking flows that check availability for this equipment now treat the fleet as one smaller. A jet ski equipment with `Quantity = 5` and one out-of-service instance behaves as if `Quantity = 4` everywhere — calendar slot availability, equipment picker on the booking modify dialog, and conflict checks.
* Already-confirmed bookings continue to hold their reservations. Nothing is canceled.
* Reports can still be filed against an out-of-service instance — useful for tracking damage reports on the unit that took it offline in the first place.

Returning the unit to service [#returning-the-unit-to-service]

Flip the toggle back to **Bookable** the same way. Effective capacity grows by one immediately for new bookings. There's no audit log of the toggle history today — if you need to remember why a unit was offline, jot it in the **Notes** field while the toggle is off (e.g., "10/14: engine carburetor, expected back 10/22").

Tips [#tips]

* **The toggle is reversible and cheap.** Flip freely — there's no charge, no booking impact on existing bookings, and you can flip back as often as you need.
* **Use Notes for context.** Future-you (and your team) will want to know *why* a unit is out of service. Notes are right there in the same dialog.
* **Don't delete out-of-service units.** Deleting wipes the unit's report history. Marking it Out of service preserves the history while removing it from availability — almost always the right move unless the unit has truly been sold or scrapped.
* **No instances = no effect.** If you haven't registered any instance rows for an equipment, this feature is dormant for that equipment — `Quantity` stays authoritative.