# Editing an ICP

> Source: https://docs.trailspark.ai/docs/editing-an-icp

The ICP edit page is a tabbed surface. Each tab covers one aspect of the ICP's configuration, and the tab set changes depending on which modes are on. A sticky save bar at the bottom tracks your pending changes and determines what kind of save is needed.

## Tab layout

Open any ICP from the ICP Hub and you land on the edit page. The tabs appear in this order:

| Tab | Always shown? | Appears when |
|-----|---------------|--------------|
| **Overview** | Yes | ICP name, motion, mode toggles, default setting |
| **Eligibility** | Yes | Scope rules: which accounts this ICP covers |
| **Ideal Fit** | No | Individual lead scoring is on |
| **Behavior Signals** | Yes | Account activity signals, signal descriptions, cadence |
| **Scoring filters** | No | Individual lead scoring is on |
| **Roles** | No | Build buying group is on |
| **Role Mapping** | No | Build buying group is on |
| **Rubric** | Yes | Read-only preview of the generated scoring rubric |
| **Refinement** | No | At least one feedback entry exists on this ICP |

Tabs appear and disappear in a fixed relative order — the set of visible tabs changes, but the tabs that remain never shuffle position relative to each other.

## Mode toggles on the Overview tab

The **Overview** tab has two toggles that control which tabs appear:

- **Individual lead scoring** — turns on Ideal Fit and Scoring filters. When off, those tabs are hidden and no lead-level scoring or qualification filtering runs for this ICP.
- **Build buying group** — turns on Roles and Role Mapping. When off, role detection stops for this ICP.

Both toggles save immediately when you flip them — they do not go through the save bar. Turning off **Build buying group** will remove roles already assigned; a confirmation dialog appears before that takes effect.

## The save bar

Any edit on a non-toggle field queues a change in the save bar. The bar appears at the bottom of the page with a single action button whose label reflects the highest-impact pending change:

| Pending change type | Save bar button |
|---------------------|-----------------|
| Name, scoring filters, cadence timing | **Save** (and **Save & Close**) |
| Eligibility rules, role definitions, buying-group config | **Save & Re-evaluate** |
| Criteria / signal-description text, rubric weightings | **Review model changes** |

Multiple pending changes stack. If you edit both a scoring filter (cosmetic) and an eligibility rule (retroactive), the bar shows **Save & Re-evaluate** — the highest tier wins.

> [!NOTE]
> **Save & Re-evaluate** (capital R, save bar) and **Save & re-evaluate** (lowercase r, Rubric tab) are two distinct buttons on two different surfaces. The save bar button handles Eligibility, role-definition, and buying-group config changes; the Rubric tab button commits a regenerated scoring rubric.

## Retroactive vs. cosmetic edits

**Save & Re-evaluate** appears when any pending change is retroactive — meaning it affects how existing accounts are scored, not just future runs.

Retroactive changes:

- **Eligibility rules** — changing which accounts this ICP covers reassigns accounts to a different Primary ICP immediately. You choose whether to also trigger a fresh scoring run on affected accounts.
- **Role definitions** — any edit to a role's name, intent, targeting note, or demographic criteria changes how leads are matched to roles. The targeting note in particular feeds the scoring model directly, so every field on a role definition is retroactive.
- **Buying-group config** — confidence threshold, roles-per-person setting, and tiebreak order all affect which contacts fill which roles. Changes here are retroactive.

Cosmetic changes (saved with **Save** or **Save & Close**, no re-evaluation prompted):

- **ICP name** — display only, no effect on scoring.
- **Scoring filters** — forward-only: accounts and leads that fail these rules are skipped on future runs, but past scores are unchanged.
- **Cadence timing** — lookback window, signal thresholds, cooling-off periods. These change the conditions for when a future evaluation fires, but they do not re-trigger evaluations that already ran.

When **Save & Re-evaluate** is clicked, a dialog shows the estimated cost and gives you the option to save without re-evaluating if you want the rule change to take effect for new runs only.

## Model-tier changes and the Rubric tab

Editing the free-text criteria fields on **Ideal Fit** or **Behavior Signals** is a model-tier change. These fields feed the scoring model that generates your rubric — editing them does not produce a new rubric automatically.

When criteria edits are pending, the save bar shows **Review model changes**. Clicking it:

1. Switches to the **Rubric** tab.
2. Triggers a regeneration of the rubric preview using your updated criteria.

The **Rubric** tab is otherwise read-only. It shows the current generated rubric text — the plain-language scoring instructions the model uses to evaluate accounts and leads. A **Regenerate** button on the panel lets you refresh it at any time.

Once the regenerated preview has loaded, the **Save & re-evaluate** button on the Rubric tab becomes active. Clicking it opens the re-evaluation dialog and commits the new rubric. You can choose whether to re-evaluate existing accounts against the updated model.

> [!NOTE]
> If you edit criteria and then edit an eligibility rule before saving, the bar shows **Review model changes** (model tier outranks retroactive). Clicking it takes you through the rubric review flow; the eligibility change is saved as part of the same commit.

## The Refinement tab

The **Refinement** tab appears once feedback exists on this ICP's scoring chain. It surfaces your model-refinement history — the record of corrections and adjustments that have shaped the current model.

For how feedback accumulates and how refinement works, see [Model Refinement](/docs/model-refinement).

## Next steps

- [Eligibility and Qualification](/docs/icp-eligibility-qualification) — how Eligibility rules and Scoring filters work and how changes propagate
- [Managing multiple ICPs](/docs/managing-multiple-icps) — priority order, Primary ICP, and scope conflicts
- [Defining Roles](/docs/defining-roles) — how to configure buying-group roles and their demographic criteria
- [Signal and Role Attribution](/docs/signal-role-attribution) — how to wire signals to roles in Signal Mapping
- [Buying Groups overview](/docs/buying-groups-overview) — how role-aware buying groups operate