How to keep the history of contract amendments and replacements without losing prior versions?

Jestor organizes every document linked to a contract with a version number, status, and type — original, amendment, or replaced — keeping the full history accessible in the documents tab, without deleting any previous version.

Why does preserving older contract versions matter?

Contracts typically go through amendments and renegotiations over time. If each new version simply replaced the previous one with no trace left behind, it would be impossible to prove what was agreed at each point — an operational and legal problem alike.

How does document versioning work in Jestor?

Every new contract automatically enters as version 1.0, with active status and type "original contract."
When an amendment is added, it's registered as a new document — version 2.0, for example — linked to the same contract.
The original contract has its status manually changed to replaced.
All versions remain available in the documents tab, filterable by status: active, replaced, or archived.

Document type	Possible status
Original contract	Active or replaced
Amendment	Active, linked to the original contract
Archived version	Kept in the history, never deleted

Why choose Jestor?

Since every document carries a version number and a link back to the original contract, Jestor delivers a complete, traceable history without relying on loose folders or manually managed file names.

Frequently Asked Questions

Is the original contract deleted once an amendment is created? No, it just has its status changed to replaced, remaining accessible in the history.

Can I filter to see only active documents? Yes, the documents tab has a status filter, including active, replaced, and archived.

Is the version number generated automatically? The document is numbered (like 1.0, 2.0) as it's registered in the flow.

Reference video

Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support.

Get to know Jestor at jestor.com and discover how to take your company's management to a new level of efficiency and integration.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize