I’m sure you’re not the only one who creates a copy of your estimate every week—or day, or hour—as you approach the estimate due date. When it comes to preparing your estimate, there’s always the possibility that you’ll want to roll back to a previous iteration—whether that’s a significant scope change, strategy decision, or price update. Or maybe you just want to know where you were this time last week. It also provides the reassurance that you can recover sensitive data should your current estimate become unusable… or someone changes it without your knowledge.
Many companies put the revision directly in the estimate name. Others use a dedicated field to tag this information. However, because these best practices can’t be enforced, the estimate catalog typically contains a mix of conventions and results in a state of confusion and uncertainty. Does this sound familiar?
How do you manage the mass of estimates that are created? And how effective are you at purging the unnecessary iterations once the proposal is delivered and the client makes a final decision?
We have a solution: Eos Navigator’s new estimate versioning feature. This feature provides the ability to:
- Formalize a common, industry-standard revision management workflow
- Remove congestion by displaying only the current estimate version
With estimate versioning, you can:
- Create an estimate snapshot
- Provide summary comments at the time of versioning
- Track estimate progression
- Retain estimate version history for approved and/or archived estimates
- Restore a previous estimate version and make it your current version
- Copy a previous estimate version to a new project
- Delete previous incremental versions
Bring order to the madness of managing your preconstruction estimates using Eos Navigator’s estimate versioning feature.
Please visit our Eos Navigator webpage for more information about Eos Navigator, or contact us if you’re interested in learning more about the other new features planned for Eos Navigator 2.1, which is scheduled for release in mid-February.
Look for our next blog post where we’ll talk about our expanded project and estimate locking functionality.