---
title: "Best Practice for Poor to Good Device Health"
slug: "best-practice-for-poor-to-good-device-health"
updated: 2026-02-24T11:49:14Z
published: 2026-02-24T11:49:14Z
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.

# Best Practice for Poor to Good Device Health

This best practice example relies on using a baseline, knowledge of an environment, and results of investigations to increase the value output and end user experience.

- 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](/documentation/docs/health-status))
- 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) Calculations – 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.