> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/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/user-guide/dex-score/dex-score-computation-hard-metrics-and-thresholds.md). # DEX score computation, hard metrics and thresholds DEX is the outcome of cumulative interactions with IT solutions and services over a period of time. Measuring DEX correctly involves monitoring the events that enable or interrupt an employee's flow while working. Depending on the nature of the events, they can either increase or reduce a positive working experience. Read how the DEX score is computed and which metrics and thresholds are considered during that process: * [Computation of the DEX score](https://edocs.nexthink.com/nexthink-infinity/infinity-specifications/digital-employee-experience-dex-specifications/computation-of-the-dex-score) (available to Nexthink Community users) * [List of hard metrics and their default thresholds](https://edocs.nexthink.com/nexthink-infinity/infinity-specifications/digital-employee-experience-dex-specifications/list-of-hard-metrics-and-thresholds) (available to Nexthink Community users) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nexthink.com/user-guide/dex-score/dex-score-computation-hard-metrics-and-thresholds.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.