# Amend a commitment

Source: https://docs.tightly.io/help/commitments/amend
Reviewed: 2026-09-07

## The question this page answers

Which of the five numbers is changing, from what to what, on what basis, and why?

## What you see

Amend a commitment moves a number on a declaration that is already armed, as a new version beside the old one; nothing is ever edited. The head names the commitment and the act, Amend the declaration. The read-back is the live position: what is already committed and what is open to commit, each absent with its reason where the position did not answer. The five numbers are one row each: was, now, basis. The drift band is optional. Below them, Why is this changing? asks for a reason from the list of eight, and Note, optional, takes anything the list does not cover. What that arms compiles the version in force and the amended one, writing nothing, as a table of Engine, In force now, Would be in force, and Changes.

The consequences are sentences before the one button. An envelope amended to below what is already committed is a warning, never a block: one sentence with both figures and the one amber dot the page may carry, because a declared promise is at risk. The amendment is scored against version one still. The receipt is the page becoming the record: the new version recorded beside the old, with the write's own figures.

## What to do

Amending takes the Commitments door, an admin or a member given it. The page compiles the amendment and reads Still compiling against your book while it runs; the button opens only on a compiled amendment, and says so where nothing has moved from the version in force. Every number has to carry a value, because an amendment sends the whole block:

> An amendment sends the whole numbers block, so every number has to carry a value.

Pick a reason; the code is required and the note is optional. Press the button. The way back is another amendment: a version is never removed, and the record reads every one. Changing what the commitment covers is a different act, [Re-assign a commitment](../commitments/re-assign), on the same record. [The declaration](../commitments/the-declaration) opens Amend from its head; on [Work the buy](../commitments/the-desk) it is a drawer under On this commitment.

### Date an account launch

In **Channels & accounts**, open the account and set its optional **Launch date** and **End date**. Both dates include that day. Leave either blank to add no account-specific boundary on that side. These dates constrain that account's demand within the commitment window; they do not move the product's launch for other accounts.

Use the normal amendment review and save. The account row shows its dates when you reopen the declaration for amendment, and the saved receipt offers **Review forecast** for the changed account. The forecast opens with the saved account, channel, commitment and date window selected. The prior version remains in history. Clear a date explicitly to remove that boundary.

A dated account needs its own active sales channel. If accounts share one aggregated channel, the amendment is refused because the forecast cannot separate their demand. Resolve the account's channel setup before saving its launch dates.

## When it is empty or failed

> No commitment at this address.

> The declaration did not come back.

A pending declaration has nothing live to amend, and the page says so in place of the fields, with a door to Read it for sign-off:

> Sign this declaration before amending it.

A seat without the Commitments door reads why the button is closed:

> Amending a Commitment needs org-admin access.

The compile's own states each have a sentence:

> Validation failed to load. Compile again.

> The engine refuses the amended declaration. Change the numbers, then compile again.

The server refuses an identical version, because an amendment that changes nothing would be a lie in the record, and refuses an amendment written against a version that has moved since it was read, so re-read and amend again. On a continuity commitment whose categories a live buy plan's company authority controls, a change to its money may be refused, with the sentence to make it through Finance Changes instead. A refused amendment renders as a card, The amendment was not written, with Re-read this commitment beside it, and the fields stand as you typed them.