Estimate
An estimate is an informed projection of what work, goods or a project may cost when the final scope or quantity is not yet certain. It helps a customer plan and compare options, but the eventual amount can change as the work becomes clearer. The estimate should explain its assumptions, exclusions and period of validity.
Why this matters when you invoice
An estimate gives the customer a realistic planning figure without pretending every cost is already known. Stated assumptions make later changes easier to explain.
Where it appears in the workflow
An estimate should be titled clearly and include its date, reference, expected line items or range, assumptions, exclusions, taxes where relevant, and how long it remains current.
Estimate example
A repair technician estimates three to five hours of labour plus parts because the full fault is not visible yet. After inspection, the technician confirms the final scope before invoicing the completed work.
Common mistakes
- Calling a fixed, approved price an estimate without explaining uncertainty.
- Leaving assumptions and exclusions unstated.
- Issuing the final invoice without explaining material changes from the estimate.
Use the right document
Open the matching document mode, replace the example content and review the details before export.
This page explains common document usage. Your agreement and applicable local rules determine what applies to a transaction.
Frequently asked questions
What is the difference between a quote and an estimate?
A quote normally proposes a defined scope and price; an estimate projects likely cost where important details remain uncertain.
Can the final invoice be higher than the estimate?
It can differ when scope, quantities or assumptions change, but the agreement and applicable rules determine what changes are acceptable.