> For the complete documentation index, see [llms.txt](https://docs.licensemeter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensemeter.com/findings/workflow.md).

# Remediation workflow

Assign responsibility and track a finding until a later sync verifies the outcome.

The workflow records what your team plans to do. Detection status records whether LicenseMeter still observes the underlying condition. These are separate.

## Track the work

In a finding, an Admin can set:

* **Remediation status:** Not planned, Planned, Remediation requested, or In progress.
* **Assignee:** a member of the current workspace.
* **Due date:** the date by which the decision or action is needed.
* **External ticket URL:** a link to the work item in your service-management system.
* **Notes:** the decision context, approvals or next steps.

Select **Save workflow**. The sample workspace shows **Workflow preview** instead of saving changes.

## Understand the outcome

Acknowledge a finding when it has been reviewed and should remain tracked. Reopen it if it needs attention again. Neither action changes anything at the provider.

After an approved provider-side action, run another sync. LicenseMeter automatically resolves a finding when the relevant condition is no longer present. A resolved finding can contribute to the **Verified savings (30d)** metric; financial savings still depend on the contract and billing cycle.

Before changing Microsoft licenses, identify the affected account and services, check retention and downstream access, and record the current assignments. Reassigning the original license may restore access if a seat remains available, but it does not guarantee recovery of data already deleted under a service's retention rules. Treat exported remediation scripts as a proposal that requires separate review and execution.

See [Exports](/exports.md) for sharing the findings and downloading a remediation script.


---

# 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.licensemeter.com/findings/workflow.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.