---
title: "Improve Device Health"
slug: "best-practice-for-poor-to-good-device-health"
description: "Follow a four-stage approach to improve device health: baseline measurements, gap analysis, investigation, and resolution in SysTrack."
updated: 2026-09-30T14:58:04Z
published: 2026-09-30T14:58:04Z
canonical: "documentation.lakesidesoftware.com/best-practice-for-poor-to-good-device-health"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.lakesidesoftware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Improve Device Health

Use the following cycle to move devices from a Poor or Fair Health Score to a Good or Excellent one, and to measure the value of that improvement over time.

- Baseline: a snapshot of the data at a point of time, in practice this could be the first of every month.
- Investigate: analysis of the Health Score for devices grouped from Poor to Good, as shown in **Health Status** on the **Dashboard** tab of the **Desktop Visualizer** (see [View the Desktop Dashboard](/documentation/docs/view-the-desktop-dashboard)). For more on Health Score bands, see [Understanding the Health Score](/documentation/docs/health-score-details).
- Remediate: improve and address issues found on the devices Poor to Good categories.
- Measure improvement: at the end of the period, review the baseline against the current state.
- Return on value (ROV): a calculated return of value metric helps to understand the impact of degraded user experience and to aid the decisions for mitigating activities.

Repeat this cycle on a regular basis. Initially, it is good to work on a monthly review cycle. As the issues become easier to mitigate, you can shift this approach to a quarterly process.

> [!TIP]
> **TIP:** Keep a list of devices that have been reviewed and have had issues addressed. These can become samples to re-check over time.