Protect estimate work before it becomes a job
An estimate is often being built while the office is answering a call, checking a calendar, and clarifying scope with a technician. Losing that work because someone navigated away breaks momentum at the exact point the business is trying to earn a customer’s decision.
This update adds stronger protection around estimate work in progress: the web experience warns before an operator dismisses or navigates away from unsaved work, and customer-facing edits are more tightly controlled once an estimate has been viewed.
A deliberate pause before unsaved work disappears
The workflow now provides an explicit guard when a user tries to leave unsaved estimate work. That gives the operator a moment to save, stay, or intentionally discard the draft rather than losing a change through accidental navigation.
It is not a claim that every interruption—device failure, browser crash, network loss, or unsupported workflow—can never affect a draft. It addresses the avoidable moment where the product knows a user is about to move away from unsaved work.
Protect the customer-facing version
An estimate that has reached a customer is not the same as an untouched internal draft. Careless changes after that point can create confusion about what the customer saw, chose, or expects. The update tightens that boundary without pretending every legitimate revision should be prohibited.
For the full path from scope to payment, see how jobs and estimates connect into a revenue workflow. For customer-choice design, see good, better, best estimate packages, creating and sending estimates, and converting estimates into jobs. The Estimates feature remains the canonical product page for teams evaluating contractor estimate software broadly; this article documents the release-specific safeguard.
Frequently asked questions
Will I be warned before leaving an unsaved estimate?
Yes. The web workflow provides a guard before dismissing or navigating away from unsaved estimate work.
Does this protect against every kind of data loss?
No. It protects the known navigation and dismissal scenario; ordinary device, connection, and operational risks still require sound team practices.
