---
title: "Sending Fixes to Remediation Teams"
slug: "sending-fixes-to-remediation-teams"
updated: 2026-11-11T11:37:54Z
published: 2026-11-11T11:37:54Z
canonical: "docs.databee.buzz/sending-fixes-to-remediation-teams"
---

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

# Sending Fixes to Remediation Teams

Once you know what needs fixing, Frontier AI packages the work and sends it to the teams that have to do it — normally as ServiceNow change requests. Each package lists exactly which fix to apply, which servers need it, and which findings it will clear.

## Start sending work

You can start from several places — whichever is closest to what you are looking at:

- The **Compile** button on a row in the Applications list.
- The **Compile** button in a cell brief on The Week's Work.
- **Compile remediation work** at the bottom of an application's details panel, or **Compile this fix** on its Fixes tab.
- The **Compile** button for a team on the Ownership tab.
- The **Compile** button in a vulnerability event. See [Responding to a New Vulnerability](/user-manual/docs/responding-to-a-new-vulnerability).

If the button is greyed out, there is nobody on file to send the work to. Assign an owner first.

## Choose how to send it

The **Compile remediation work** window opens with sensible defaults set by your administrator. You can adjust them for this dispatch only:

![The Compile remediation work window. Choose how to group the work, how to send it, and which teams receive it.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/frontier-ai-10-compile-modal%282%29.png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A24%3A09Z&se=2026-11-11T14%3A24%3A09Z&sr=c&sp=r&sig=%2B1yzxsKCwQXM4A2Zfl2NowEtwI%2FkB1O3MY0bs%2BgELRo%3D)

*The Compile remediation work window. Choose how to group the work, how to send it, and which teams receive it.*

1. **Group as** — how to bundle the work:
2. *One per fix* (default) — a separate item for each fix. Easiest for teams to work and track.
3. *One per application* — everything for this application in one item.
4. *One per owner* — everything a team owes, across all their applications.
5. **Send as** — *ServiceNow* (a change request), *Email*, or both.

When you select *ServiceNow*, the window shows which ServiceNow connection the work will go to. If the tenant has one connection, it is chosen automatically. If it has more than one, the default set by your administrator is preselected and marked "(default)", and you can choose a different connection for this dispatch. If there is more than one connection and no default, choose one before **Send** is enabled. If no ServiceNow connection is available, ServiceNow is unavailable, a message explains why, and *Email* is selected instead.
6. **Copy the business owner on every item** — keeps the application's business owner informed.
7. **Dispatch to** — when several teams are involved, tick the ones you want to send to now.
8. Review the preview of each item. It shows the priority, short description, assignment group, and one section per fix with **What needs to be done**, the **Affected configuration items** (servers), and the **Findings cleared**. Untick any fix you want to leave out.
9. Select **Send**.

Priority is set automatically: **1 – Critical** for anything on the CISA KEV list, **2 – High** for other Critical-severity work, and **3 – Moderate** for everything else.

Fixes that were already sent appear greyed out and are not sent twice. If a team has no email address on file, their items are created in ServiceNow only.

## Tracking what you sent

Every dispatch is recorded on the application's **Dispatches** tab. This is where Frontier AI is most different from a ticketing system: **it judges progress by what later scans find, not by whether the ticket was closed.** Closing a ticket never closes a finding — only a scan showing the problem is gone does.

![The Dispatches tab shows each dispatch, its delivery state, and whether scans show it as fully remediated.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/frontier-ai-08-drawer-dispatches%282%29.png?sv=2026-02-06&spr=https&st=2026-11-11T13%3A24%3A09Z&se=2026-11-11T14%3A24%3A09Z&sr=c&sp=r&sig=%2B1yzxsKCwQXM4A2Zfl2NowEtwI%2FkB1O3MY0bs%2BgELRo%3D)

*The Dispatches tab shows each change request, its ServiceNow state, and how many of its findings scans have confirmed as fixed.*

Each dispatch shows who it went to, when, its current ServiceNow state, and a progress line such as “12 of 14 findings fixed by scan evidence.” Watch for these labels:

- **Fully remediated** (green) — scans confirm every finding in the dispatch is fixed.
- **Closed, still detected** (amber) — the ticket was closed but scans still find the problem. Follow up with the team.
- **No movement in 7d** (amber) — the ticket has not changed state in a week or more.

Frontier AI also adds the scan evidence back onto the change request as a comment, so the team working the ticket can see the same picture.

## Next steps

- [Tracking Remediation Activity](/user-manual/docs/tracking-remediation-activity)
- [Configuring Scoring and Routing](/user-manual/docs/configuring-scoring-and-routing)