---
title: "Current, Proposed, and Difference views"
slug: "current-proposed-and-difference-views"
description: "Understand the difference between proposed and committed changes in Fullcast to ensure accurate CRM exports and effective territory management."
updated: 2026-08-11T22:05:41Z
published: 2026-08-11T22:05:41Z
canonical: "support.fullcast.com/current-proposed-and-difference-views"
---

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

# Current, Proposed, and Difference views

Changes you make in Fullcast, such as moving accounts, carving territories, rerunning rules, don't reach your CRM the moment you make them. They start in a staged, proposed state and only export once you commit them. Knowing the difference between the **Change State** you're viewing and whether a change has actually been committed is what keeps "what I see" and "what's live" helps during planning.

## Switch between current, proposed, and difference

1. Go to **Territories > Manage Accounts.**
2. In the dropdown beside the territory name, toggle between **Current**, **Proposed**, and **Difference**.

![](https://cdn.document360.io/369efcf7-66f9-4f6b-9d45-9ca24a5b06cf/Images/Documentation/image(704).png)

## What you see vs. what's committed

Two things sound alike but do different jobs:

- **The Change State you're viewing.** The **Change State** control — **Current**, **Proposed**, or **Difference** — sets how you're looking at the plan. Toggling between change states never changes your data; it only changes what's shown. This is not the same as a [**saved view**](/plan-and-pay/docs/manage-saved-views-in-territory-plan), which stores a set of columns, filters, and metrics for the grid.
- **Whether a change is committed.** This is the status of an individual change — still **proposed** (staged, not final) or **committed** (finalized). It's what determines whether the change reaches your CRM.

The rest of this article covers committing first, because the change states are easiest to understand once you know what "committed" means.

## Proposed vs. committed changes

Every change you make starts out **proposed** — staged inside Fullcast. It's saved, visible to you and your team, and reversible, but it does **not** export to your CRM. Committing is the separate, deliberate step that finalizes a change and queues it for the next scheduled export job.

- **Nothing reaches your CRM until it's committed.** A proposed change is safe to review, adjust, or undo; committing is the point of no easy return.
- A **yellow dot** marks accounts and nodes that have proposed, uncommitted changes.
- **Undo** discards proposed changes before they're committed. Once a change is committed, undo no longer reverses it — you'd make a new change instead.

To actually commit a change — from the territory hierarchy menu or the grid's **Actions** button — see **Commit territory changes** under **Related articles**.

## The three change states

| Change State | What it shows | When to use it |
| --- | --- | --- |
| **Current** | The **committed** state — what's live in Fullcast and reflected in (or on its way to) your CRM. Proposed, uncommitted changes do **not** appear here. | To see where things actually stand today. |
| **Proposed** | The committed plan **plus** your staged, not-yet-committed changes. This is where you build and see staged changes; drag-and-drop moves are available only in the **Proposed** change state. | While you're planning and making changes. |
| **Difference** | The **delta** between Current and Proposed, so you can see exactly what would change before you commit. | To review impact before committing. |

In the **Difference** change state, each change is labeled:

- A **green plus** marks an account added to a node.
- A **red minus** marks an account removed from a node.

## How change states and committing fit together

The change state you're viewing and a change's commit status describe the same change from two angles:

- A **proposed** (uncommitted) change appears in the **Proposed** change state and is highlighted in the **Difference** change state — but it does **not** appear in **Current**, which shows only committed data.
- Once you commit the change, it becomes part of the **Current** state and exports to your CRM on the next export job. The **Current** and **Proposed** states then match for that change, so it drops out of the **Difference** change state — there's no longer a difference to show.

So if a change looks like it "disappeared" when you switched to **Current**, it hasn't been lost — it just isn't committed yet. Switch back to **Proposed** or **Difference** to see it.

## Related

- [Fullcast MCP prompt library](/fullcast-mcp-prompt-library.md)