> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/library-packs/hardware-management/physical-endpoint-rightsizing.md).

# Physical endpoint rightsizing

**Physical endpoint rightsizing** helps you evaluate whether endpoint hardware matches actual employee needs. By combining hardware specifications with user behavior and business context, the solution enables you to identify devices that are correctly sized, oversized, undersized, or mismatched. This supports smarter endpoint allocation, refresh planning, and lifecycle management.

### **Problem** <a href="#problem" id="problem"></a>

IT teams often lack a consistent view of how well endpoint hardware aligns with employee requirements. Devices may be overpowered for some users, underpowered for others, or poorly matched to mobility and external display needs. Without correlating hardware configuration with actual usage patterns and business context, these mismatches are difficult to detect, resulting in unnecessary hardware costs, reduced employee productivity, and inefficient refresh planning.

### **Solution** <a href="#solution" id="solution"></a>

Continuously evaluate your device fleet using real user behavior, hardware characteristics, and business requirements. The solution combines a reusable **Device Fleet Fit Analysis** dashboard with a workflow that maintains the custom fields required for device classification. This enables you to identify devices that are rightsized, oversized, undersized, or mismatched and make informed hardware allocation and refresh decisions.

### Benefits and outcome <a href="#benefits-and-outcome" id="benefits-and-outcome"></a>

By implementing the **Physical endpoint rightsizing** library pack/solution you:

* Enable data-driven endpoint refresh and allocation decisions.
* Reduce hardware costs by identifying opportunities to downsize overpowered devices.
* Improve employee productivity by identifying underpowered or mobility-mismatched devices.
* Improve hardware planning through visibility into compute, mobility, and display requirements.

### **Getting started with Physical endpoint rightsizing** <a href="#getting-started-with-x-solution" id="getting-started-with-x-solution"></a>

Configure and start using your packs by following these links:

* ​[Usage guide: Physical endpoint rightsizing](/platform/library-packs/hardware-management/physical-endpoint-rightsizing/usage-guide-physical-endpoint-rightsizing.md) for standard users.
* ​[Configuration guide: Physical endpoint rightsizing](/platform/library-packs/hardware-management/physical-endpoint-rightsizing/configuration-guide-physical-endpoint-rightsizing.md) only accessible to users with an [administrator](broken://spaces/ZeA7tTt086G6thc9T1wB) role.


---

# 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://docs.nexthink.com/platform/library-packs/hardware-management/physical-endpoint-rightsizing.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.
