How should HVAC teams separate supplier cost updates from approved estimates?
Format: Article.
Save a supplier's new cost in its own record. Do not edit an approved customer estimate to match it. Link the update to the lines it affects. Then ask the estimator with approval rights to review what, if anything, should change.
The office needs to preserve two different facts: what a supplier has now reported and what the company has already offered or agreed with the customer. A new cost does not decide the company's response. It also does not prove that a substitute is suitable or that a customer's price may change.
Microsoft's Field Service guide says revenue and cost items can be added to a work order.[8] That describes Microsoft's product. The map below is our proposed office tool. It keeps source costs apart from price decisions. It is not an installed Core Agentic system.
Keep three layers instead of one live price field
The first layer is the source quote. Save its supplier, reference, received date, quoted item, units and any stated validity information. Preserve the original attachment. If the supplier did not state a validity date, do not create one.
The second layer is the estimate working version. It records which cost inputs the estimator used and which remain unchecked. A revised supplier quote can be linked here for review without replacing the source used in the earlier version.
The third layer holds what the customer received and how they replied. Keep the exact version sent and the work it covers. Link the customer's reply to that version. Do not copy an approval note from another estimate.
The estimate input and version map
| Field | Example entry type | Review purpose |
|---|---|---|
| Estimate family | Customer, property and estimate ID | Keeps all versions together |
| Estimate version | Working draft, sent version or approved version | Identifies which record may be edited |
| Line reference | Stable line ID and supplied item description | Shows the affected part of the estimate |
| Cost source | Supplier quote ID, file and date | Makes the input traceable |
| Basis | Quantity unit, currency and stated inclusions | Exposes unlike-for-like comparisons |
| New input | Revised source, receipt time and changed fields | Shows what prompted review |
| Decision owner | Authorized estimator or commercial manager | Prevents automatic repricing |
| Disposition | No change, revise draft, seek clarification or escalate | Records the next approved step |
Use “unknown” for missing freight, validity or other cost details. A blank cell should not become a zero-cost assumption. This map does not set pricing policy or interpret customer terms.
Review the change before choosing a response
First check the item and unit in the new quote. A new description may mean a different item, not just a new price. Ask qualified HVAC staff about fit or a proposed replacement. Two similar names do not prove that parts can be swapped.
Next identify every estimate version that used the old source. Classify each as an internal draft, a sent offer awaiting response or a version with recorded approval. The estimator can then apply the company's actual commercial process to each case.
Prepare a short change note with the old source, new source, affected lines and unanswered questions. The note should say “new supplier input received,” not “customer estimate updated.” Customer communication is a separate approval step.
Hypothetical example: a quote changes after acceptance
An HVAC office has a customer-approved estimate labeled E-62 version 3. The supplier sends a revised quote for a listed component. It also changes the freight note. The office has not confirmed whether the new quote replaces the original for this order.
The coordinator links the new file to the estimate family and flags both the cost and freight fields. Version 3 stays unchanged. The working review record says “supplier clarification needed.”
The estimator asks purchasing to confirm which quote applies and asks the commercial manager to review the customer commitment. Nobody assumes that the new cost can simply be passed through. Nobody chooses a different component to recover the difference.
Keep the packet on hold until those people record a decision. If they approve a new proposal, give it a new version. Follow the company's customer review steps. This example keeps records apart; it does not set a price or decide what a contract permits.
Test what cannot change silently
Open the approved estimate after adding a new supplier input. Its saved customer-facing content should be identical. A reviewer should still be able to identify the exact quote used to prepare it.
Then test an input with a different unit and one with no quote reference. Both should create questions, not overwrite cost fields. Finally, test a revised draft that has not been sent. It must not appear as the customer's latest accepted version.
Core Agentic can discuss custom software for this review. First, we would need to check access to your tools and records. Book a Demo to discuss how your team could see new costs while keeping approved estimates intact.
Sources
These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.