What should a roofing estimate packet say about unverified measurements?
Format: Article.
A roofing estimate packet should show where each measurement came from. It should also show whether a qualified estimator has accepted it for that use. Put unchecked dimensions in a clear review section. Do not make them look like final quantities.
A photo, a customer sketch and a provider report are different inputs. None should lose its source label when the office prepares a summary. Tell the estimator which sources are on hand. Show what is unclear and which part of the property each one covers.
Eagleview describes Bid Perfect as a source of preliminary roof data and measurements. Its product page lists Premium Roof Reports separately for ordering.[5] Keep those report types visible in the packet. We are not judging their accuracy or fit for a particular roof.
Preserve the source before copying a number
Save the original file and who supplied it. Record the address, file ID, stated creation date and date received. If the source shows when an image was taken, keep that date too. A download date does not tell you when the image was made.
Copy units exactly. Keep the source's numbers apart from the numbers the estimator has approved for use. If a supplied dimension lacks a unit or location label, mark it incomplete. The office should not infer units from nearby numbers or from what seems normal for a house.
Describe the scope covered by each source. A detached garage, rear addition or separate building may not appear in every file. Even with the right street address, check that the report covers the right building and work.
Copy this source-tracking sheet
| Field | Entry to preserve |
|---|---|
| Property and job | Exact address, building label and job ID |
| Source identity | Provider or sender, file ID and original link |
| Source type | Customer sketch, supplied photo, provider report or staff record |
| Dates | Creation or capture date if stated, plus received date |
| Coverage | Buildings or areas the source says it includes |
| Supplied values | Values and units exactly as provided |
| Uncertainty | Missing units, unclear coverage, unreadable labels or conflicts |
| Estimator review | Reviewer, date and accepted use or hold |
| Working estimate link | The version that uses a reviewed input |
| Replacement history | Which input was replaced and why |
This sheet tracks where each fact came from. That is sometimes called provenance. It is not a measurement method. It does not validate dimensions or provide instructions for accessing or inspecting a roof.
Define estimator holds before building the packet
Ask the estimating supervisor when the office should hold a packet for review. Possible reasons include the wrong property, missing pages, unclear units or an area not covered by the source. If two numbers clash, record how the reviewer settled the gap. Staff should not pick the number that seems most likely.
Also hold an input if no one has said how it may be used. A rough planning number should not quietly become a number used to buy materials. The qualified estimator decides which proof each use needs. Save that decision.
An office summary can say “measurement review pending.” It should not hide the hold in a footer beneath a firm-looking scope or price. Make the uncertainty visible where the affected estimate inputs appear.
Hypothetical example: the addition is missing
A roofing office receives a customer sketch and a provider report for a fictional property. The sketch includes a rear addition. The report's visible coverage does not clearly identify that addition. The customer also sends a recent photo but no checked dimensions for the added area.
The coordinator lists the three sources separately. The packet says “rear addition not yet checked.” It leaves that part of the estimate blank. It does not estimate the missing area from the photo or copy the main building's measurements into that field.
The estimator reviews the source coverage and decides what additional evidence is needed. The record owner gathers that evidence through the company's approved process. Wait for the estimator to accept the input for a named use. Then link it to that version of the estimate.
The photo stays useful as supplied context, not as an AI damage assessment or a claim that the roof needs a specific remedy. The example does not decide insurance coverage, materials or site safety.
Keep revisions traceable through estimating
When a replacement report arrives, preserve the earlier input and identify what changed. If the estimator has already prepared a draft, flag that draft for review rather than silently updating its quantities.
Use the same discipline when the address is corrected. A corrected address does not prove that every prior image or dimension belongs to the new property. Recheck each file link that used the old address.
Test the packet with a source that has no date, a sketch with no units and two buildings at one address. The workflow should expose those differences without inventing a complete measurement set.
Core Agentic can discuss a custom packet that sorts roofing records and shows missing evidence. It would not measure a roof, diagnose damage or decide coverage on its own. Book a Demo to discuss which source checks your estimator needs before an estimate moves forward.
Sources
- Eagleview: Residential Reports | Eagleview.
These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.