The version system
🟦 Purpose and functionality of the versioning system
This text provides background information. What types of text are there?
Version management
The versioning system in Leadtime works like an intelligent memory: it freezes the current status of a project - including all configurations, products, responses, components, discounts and prices. The aim is to make it clear at all times exactly what has been offered, negotiated or commissioned - and to ensure that in the end exactly what was agreed is billed.
What does a version store?
A version contains
- the complete configuration of the project tree (including conditional work packages),
- all added products (with prices, discounts and variants),
- answered questions and resulting structural changes,
- manually added items and unit prices,
- all changes made in the Configuration tab.
This therefore includes both structural and commercial decisions - such as whether a certain add-on is included or not.
💡 Why is this so important?
- Commitment: An offer is always linked to a version. This is the only way to prove beyond doubt which services were sold.
- Negotiation security: If customers want several versions (e.g. with or without hosting), different versions can be saved side by side.
- Billing security: The original contract status remains clearly documented even if changes are made later in the course of the project (e.g. due to questionnaires or new requirements).
How do you recognize that something has changed?
As soon as a change is made in the configuration, Leadtime displays a "NOT SAVED" warning symbol in the top right-hand corner. The app automatically compares the current status with the last saved version.
Important: You don't have to save after every little thing - but it is worth creating a new version after meetings, completed questionnaires or changes to offers.
🛠️ Create a version
- Click on "Create version".
- A "Create new version" dialog opens.
- Enter a meaningful title (e.g. "Project preparation completed", "Variant with hosting", "Billing version").
- The description text is generated automatically by an AI. It is a comparison of the changes between the new and the last version
- Click on Save - done.
🧾 Versions and documents
When creating quotations or specifications in the Documents tab, you must always select a saved version first. The entire price calculation and text structure is then based exactly on this saved version.
🔁 Switch between versions
In the version history, you can see all previous versions including timestamps and changes. There you can:
- view every previous version,
- jump back to an earlier version,
- create a new branch if you are continuing to work on the basis of an old version.
Branches in the version tree work like in Git - you can develop, compare or roll back variants of the project.
Best practice
- Create a new version after completing questionnaires or importing components.
- Save a version before exporting or sending offers.
- Name versions clearly and comprehensibly.
- Use forks when preparing variants for customers.