Why Did a Field Change That I Didn't Want Changed?

A field on your transaction changed after an AI Update, and it held a value you wanted to keep. Here's why it moved, and how to set it right.

Applying the Update Writes Every Change You Didn't Rewind

The summary of changes is a list of everything the new document moves, and applying it writes all of them — except the ones you rewound. A field you scrolled past without touching gets the document's value.

That's the design: the review screen is where you decide, and the apply step is the commitment.

Protect the Field Before You Apply

Rewind it while you're still on the review screen:

  1. Find the field in the summary of changes.
  2. Hover its rewind control to see the value it held before.
  3. Click the rewind control to put that value back.
  4. Click [Apply Updates] once you've been through the rest.

That field keeps its original value while every other change goes through.

Set It Back if You've Already Applied

Nothing is stuck. Open the transaction, edit the field, and type the value you wanted — a plain edit, the same as any other. The update didn't lock anything, and running AI Update again on a later document won't undo your correction unless that document restates the value.

Still Stuck?

If a document keeps changing a field it shouldn't — pulling a value from the wrong clause, for instance — tell us. Send the transaction name, the source document, and the field, and we'll use it to improve the read.

Learn More

A counter-offer lands, the terms change, and you never retype a field — AI Update reads the new document, shows you what moved and where, and you decide what to apply.

See Pipeline AI Update

Still Have Questions?

Didn't find your answer above? Email us at help@paperlesspipeline.com and we'll help.