Classifying Claim-File Information Types

Welcome. This first module establishes the discipline behind reliable photo-based estimating: before deciding what to scope, you must be able to say exactly what the file establishes and what it does not. A familiar Xactimate line item can look plausible long before the claim file actually supports it; separating evidence from assumptions prevents that problem.

In this lesson, you will classify each claim-file statement as observed, reported, inferred, or unknown. This is not a coverage decision and it is not a final causation opinion. It is a practical evidence-control method that makes preliminary estimates, notes, requests for information, and later discussions with reviewers much more defensible.

A useful study rhythm is about 40 minutes: 8 minutes of reading, 7 minutes of video, 20 minutes working through the framework and image example, and 5 minutes reviewing the workflow.

---

The four evidence labels

A claim file is a mixture of photographs, measurements, statements, sketches, invoices, weather information, mitigation records, and prior-loss records. Those materials do not all prove the same things. Your first job is to classify the individual proposition being made, rather than labeling an entire photograph or document as “evidence.”

Label	Meaning	Safe estimating language
Observed	Directly seen, measured, photographed, or otherwise recorded by an identified person or device.	“Photo 14 shows…”; “Field measurement records…”
Reported	A statement made by an insured, contractor, plumber, occupant, or other source. The statement is attributed, not adopted as fact.	“Insured reported…”; “Plumber’s invoice states…”
Inferred	A reasoned conclusion drawn from observed and reported information. It must state its basis and remain proportionate to the evidence.	“The pattern may be consistent with…”; “Based on Photos 14–18 and the sketch…”
Unknown	The file does not establish the fact; evidence is missing, unclear, inaccessible, or contradictory.	“Source is not documented”; “Extent behind ceiling is unknown.”

The distinction seems simple, but it has major consequences. Consider the statement: “A pipe leak caused the ceiling damage.”

That is not one fact. It contains several separate propositions:

1. There is ceiling damage.
2. The damage is water-related.
3. A pipe leaked.
4. That leak caused this particular ceiling damage.
5. The leak occurred at a particular time.

A photograph might support the first proposition. A moisture reading could support a current moisture condition. An insured might report the third and fifth. A plumber’s signed report may strongly support the third. The connection between pipe failure and ceiling condition may be an inference, depending on the evidence. If no source investigation, plumbing report, or opening exists, the claimed source may remain unknown.

Do not allow a sentence to become more certain merely because it has been repeated. A reported assertion copied into an estimate note is still reported unless you have independent support for it.

---

Observation is not causation

A frequent estimating error is to treat a visible condition as proof of why it happened. In practical claim work, these are separate questions:

• What condition is present?
• Where is it present?
• What caused it?
• When did it happen?
• How far does it extend?

The first two are often observable from competent photos, measurements, or a site inspection. The later questions commonly require corroboration, specialist input, testing, records, or carefully stated inference.

For an estimator, you usually do not need to solve every cause question yourself. You do need to avoid silently converting a possible explanation into a scope-driving “fact.” A scope can be preliminary, but its evidence status must stay visible.

For example:

• Too certain: “Remove wet ceiling due to plumbing leak.”
• Evidence-led: “Remove ceiling finish in documented stained area; reported plumbing leak is pending plumber documentation. Concealed cavity conditions are unknown.”

The second note permits a reviewer to see both the proposed work and the boundary of your knowledge.

---

What counts as observed when you work remotely?

Because you may be estimating from someone else’s field photos, “observed” needs careful wording.

If you personally attended the site, you can write:

Observed irregular brown staining on the dining-room ceiling near the north wall.

If you only received photos, write:

Photo 12 depicts irregular brown staining on a ceiling panel; the room designation and dimensions are not visible in the image.

The image is observable to you. The condition depicted is observable in the image. But details outside the frame, the date the photo was taken, whether it is current, the material on the concealed side of the ceiling, and whether the surface is actively wet may all remain unknown.

A photo can also be real yet insufficient. Good documentation uses several views:

• a close view for material condition;
• a wider view establishing the affected area’s position in the room;
• views of adjacent rooms, the space above, and the area below when relevant;
• a measurement reference, moisture-meter display, or sketch where extent matters.

This lets you distinguish “not shown” from “not damaged.” The first is unknown. It is not evidence of absence.

---

Reading a damage photo without overclaiming

Use the ceiling image as a controlled example. Imagine it is the only file material you received.

Statements you can classify as observed

These statements stay close to the image:

• “The photo depicts irregular brown discoloration across several ceiling panels.”
• “Dark green-black spotting is visible on portions of the stained ceiling surface.”
• “Staining is visible on the upper section of the adjacent wall and near the crown molding.”
• “The image shows a suspended ceiling system with panel joints.”

Notice what is deliberately absent: no claim that the dark spotting is “mold,” that the ceiling is wet, or that a plumbing leak caused the staining.

Statements that would be reported

These require attribution to a source:

• “The occupant reported a bathroom overflow occurred above this room three days earlier.”
• “The property manager reported that the ceiling had been stained before the current loss.”
• “The mitigation contractor reported elevated moisture readings in the ceiling cavity.”
• “A plumber’s report states that a failed supply fitting was repaired above the affected area.”

A contractor report can be highly useful, especially when it identifies its methods, date, observations, and conclusions. Yet its contents are still the contractor’s reported findings unless you independently verify them. In a claim file, never write “the plumber found” without identifying the document and its author.

Statements that may be inferred

Inference is necessary in estimating; it is not a mistake. The mistake is hiding it.

• “The stain distribution may be consistent with water migrating from above the ceiling.”
• “Because staining appears on both ceiling and upper wall surfaces, additional investigation of the assembly above and adjacent wall area may be warranted.”
• “The visible spotting may indicate a microbial-growth concern requiring the responsible party to determine whether an environmental assessment or protocol is needed.”

Each inference should answer two questions:

1. What facts support this conclusion?
2. What alternative explanation or missing fact limits it?

For example, a ceiling stain may be consistent with a leak above, but roof intrusion, condensation, an old resolved leak, or another pathway may also be possible. The photo alone cannot select among them.

Statements that remain unknown

With only this image, all of the following are unknown:

• the actual source and cause of moisture;
• whether moisture is active or historic;
• whether the dark spotting is mold, dirt, staining, or another material;
• the room name and exact affected dimensions;
• conditions above the ceiling panels;
• whether insulation, framing, wiring, or mechanical components are affected;
• whether the ceiling panels contain a hazardous material;
• the date of loss, duration of exposure, and pre-loss condition;
• whether the damage is related to a claimed event.

“Unknown” is a productive classification. It tells you exactly what must be requested before a final scope is built.

---

Reported information: preserve the speaker and the wording

An insured may describe the loss accurately, partially accurately, or inaccurately. The point is not distrust; it is precision. A person who says, “The ceiling is moldy because the upstairs toilet leaked,” may be reporting:

• what they saw: “I saw water on the bathroom floor”;
• what they believe: “the toilet leaked”;
• a conclusion: “the ceiling damage was caused by that leak”;
• an interpretation: “that black material is mold.”

Those are different propositions and should be separated in your notes.

When you capture a report, include four details in your claim notes:

1. Who made the statement.
2. What they said, using their terms where important.
3. When they said it and, separately, when they say the event or discovery occurred.
4. Whether supporting documentation exists.

For example:

Insured reported on June 12 that water was first noticed at approximately 7:00 a.m. on June 10 below the upstairs bathroom. Insured stated a plumber repaired a toilet supply line the same day. Plumber report and invoice not present in file.

This statement is usable because it neither accepts nor rejects the reported cause. It identifies the next evidence needed.

---

Inference: make the reasoning inspectable

An inference connects facts. It becomes defensible when a reviewer can retrace that connection.

Use this sentence pattern:

Based on [specific observed and reported evidence], [limited conclusion] is consistent with / may indicate / requires confirmation of [issue]. [Key limitation or next step].

Examples:

Based on the ceiling staining visible in Photos 12–16 and the insured’s report of water observed in the bathroom above, the ceiling condition may be consistent with water migration from above. The actual source and concealed damage extent require confirmation.

Based on the continuous flooring shown in the sketch and the insured’s report that the kitchen leak reached the adjoining hallway, affected flooring beyond the kitchen may require evaluation. The photo set does not document the hallway condition or the flooring transition.

Avoid two opposite errors:

• Overstating: “The stain was caused by a long-term roof leak.”
• Being so vague that no action follows: “There may be some damage.”

A useful inference identifies an issue while stating its limits. It can justify a targeted request, a provisional allowance only where company practice permits, or referral to the appropriate professional. It should not become an unsupported reconstruction scope.

---

A repeatable classification routine

Before building any scope, run each meaningful claim-file statement through this six-step desk routine.

1. Break the file into atomic propositions

Do not classify a whole paragraph as observed or reported. Separate it.

For example, from an invoice saying, “Emergency drying was performed after a dishwasher supply-line failure damaged the kitchen floor,” identify:

• an invoice exists;
• a vendor says emergency drying was performed;
• a dishwasher supply line failed;
• the kitchen floor was damaged;
• the failure caused that damage.

You personally observe that the invoice exists. The invoice’s substantive statements are vendor-reported information. Any conclusion about cause remains reported or inferred depending on the other evidence.

2. Identify the source and directness

Ask:

• Did the photographer, inspector, meter, or document creator directly record this?
• Did someone tell us this happened?
• Is this a conclusion assembled from other evidence?
• Is there no adequate support in the file?

A moisture-meter photo can support an observed reading if its location, material, meter mode, date, and reference standard are documented. A photo of a wet-looking surface alone does not establish a moisture content.

3. Assign one primary label

Choose the label that describes the proposition’s epistemic status in the current file. If the file develops later, you may reclassify it. Classification is not permanent; it records what the available evidence supports at that time.

4. Record the evidence reference

Use a stable reference such as:

• Photo 12;
• Sketch, Room 3;
• Insured recorded statement, June 12;
• Plumber report, ABC Plumbing, June 10;
• Mitigation daily log, Day 2.

A reviewer should never have to guess where a statement came from.

5. State the limitation

Examples:

• “No scale in photograph.”
• “Date of photo not available.”
• “No access above ceiling.”
• “Vendor report lacks moisture readings.”
• “Insured and contractor descriptions conflict.”

6. State the next information needed

Unknowns become manageable when they are converted into a precise request:

• close and wide photos of the alleged source;
• a measurement sketch with room labels;
• moisture readings with material and location identified;
• plumber’s cause-of-loss report and invoice;
• photos above the ceiling or of the floor above;
• pre-loss photos, maintenance history, or prior-loss documentation.

This sequence will be the foundation for the room-by-room damage matrix in the next lessons.

---

A compact evidence log you can use today

In your claim notes or preliminary estimate workbook, use a simple four-column log before entering scope items.

Proposition	Classification and source	Limitation	Estimating consequence
Brown staining visible on ceiling panels	Observed: Photos 12–16	No scale; room not confirmed	Do not calculate final ceiling quantity from photos alone
Toilet supply line failed June 10	Reported: insured statement	Plumber report absent	Request plumbing documentation; do not state cause as established
Ceiling condition may relate to water from above	Inferred: staining plus reported upstairs event	Source and cavity condition unverified	Identify as assumption/pending investigation
Insulation condition above ceiling	Unknown	No above-ceiling photos or opening record	Do not include removal or replacement without support

The last column matters for estimating. A label is not merely an administrative note. It controls whether you can:

• scope confirmed work;
• include work as a clearly labeled preliminary assumption under your organization’s process;
• request additional documentation;
• refer an issue to a qualified trade or specialist;
• exclude an item pending evidence.

A well-controlled preliminary estimate may have fewer line items than an aggressive one, but it is easier to revise and defend because its boundaries are explicit.

---

Key takeaways

The four labels are a safeguard against unsupported scoping:

• Observed means directly documented; identify what was seen or measured and by whom.
• Reported means someone asserted it; preserve the source, wording, and date.
• Inferred means you reached a limited conclusion from stated evidence; show the reasoning and limitation.
• Unknown means the file does not establish it; convert that gap into a specific request rather than guessing.

For every potential scope-driving statement, separate visible condition, alleged cause, timing, extent, and pre-existing condition. They may carry different labels even when they appear in the same photograph, invoice, or conversation.

Next, you will use this evidence discipline to distinguish loss-related damage, pre-existing conditions, and unrelated deterioration without turning a visible condition or a reported story into an unsupported conclusion.