A scope sheet is the field record of what was damaged, room by room: dimensions, materials, the damage observed, and the photographs supporting each of them. It is the source document behind the estimate, and it is what gets tested when a carrier’s desk adjuster challenges the scope. A documentation system enforces the capture order, requires the measurements and images the estimate will need, and keeps every photograph tied to the room and the observation it supports.
What goes missing in the field
Measurements exist in three places and none of them agree
A laser measure display, a sketch on a printed floor plan, and a number typed into a phone. By the time the estimate is written the hallway is 14 feet in one record and 12 feet 8 inches in another.
Photographs are a pile, not evidence
Four hundred images sit in a camera roll in capture order, with no room, no orientation, and nothing indicating which observation each supports. When a desk adjuster asks about the drywall in the upstairs hallway, finding the three photos that answer takes longer than the inspection did.
The second trip is for what was missed
The estimator opens the file and needs a ceiling height, a flooring transition, or a shot of the underside of the sheathing. None was required at capture, so none exists.
Structure and contents get documented as one undifferentiated thing
Dwelling damage and personal property end up in the same notes and the same photo set. Separating them afterward is guesswork, and the contents inventory has to be rebuilt from photographs taken for a different purpose.
The person who scoped is not the person who estimates
Field shorthand makes sense to the adjuster who wrote it and nobody else. Material abbreviations, a circled note about a transition, an arrow on a sketch. The estimator calls to ask what four entries mean.
Room-by-room capture spec that survives a challenge
This is the capture standard we build forms against. Each row names an element the field record must carry, the entry required, the photograph that has to accompany it, and why that pairing matters when someone on the carrier side questions the scope months later.
| Capture element | Required entry | Photo requirement | Why the pairing holds up |
|---|---|---|---|
| Room identity | Room name, floor level, and a room number fixed for the life of the file | One wide shot from the doorway showing the whole room | Every later note and line item ties to a room number a third party can follow |
| Dimensions | Length, width, ceiling height, with offsets and closets measured separately | The laser reading or tape at each governing wall | Square footage becomes reproducible rather than asserted |
| Finishes and materials | Floor, wall, ceiling, and trim material with grade or profile noted | Close shot of each material plus one transition or seam | Matching and grade questions turn on the material photograph, not the description |
| Damage observed | Condition tied to the reported peril, surfaces affected, extent in feet or square feet | A wide shot placing the damage in the room, then a close shot with a scale reference | The wide-then-close pair lets a reviewer locate the damage without having been there |
| Moisture and drying | Meter readings by surface with date, time, and instrument, repeated each visit | The meter display against the surface being read | Dated, instrumented readings can be compared visit to visit instead of recalled |
| Systems and fixtures | Make, model, and serial from the data plate of any affected appliance, HVAC unit, or water heater | A legible data plate, then the unit in place | Age and replacement class come off the plate, and the photo is the only proof of it |
| Contents | Item, room, quantity, brand or model where visible, condition before the loss | The item plus any label, tag, or receipt found with it | Keeps the personal property inventory separable from the dwelling scope |
| Rooms with no damage | Recorded explicitly as inspected with nothing found | One wide shot per undamaged room | A recorded negative reads differently than silence, which reads as a room nobody entered |
Building the capture and the record behind it
The form follows the walk, not the estimate
Capture order matches how an adjuster moves through a property: exterior elevations, interior by floor, systems, then contents. Forms organized around estimate structure make the adjuster jump around the house, and that is where things get skipped.
Room numbers assigned once and carried everywhere
A room gets its identifier at first entry and keeps it through photos, notes, moisture readings, supplements, and any return visit. A supplement filed eight weeks later uses the same number.
Photographs attach to the field that required them
An image taken under the ceiling height field belongs to that field, not to a general gallery. That single decision is what makes retrieval work later, and it costs nothing because the camera opens from inside the field.
Required fields that actually hold, with a recorded override
A room cannot be marked complete without a ceiling height and at least one wide shot. Overriding is possible, because field conditions are real, but it takes a reason and carries the name of whoever did it.
An export the estimator can work from directly
The room list leaves with dimensions, materials, and observations in the order and units the estimating platform expects, and photos export with room and field in each filename. What goes into the estimate stays the adjuster’s work.
Where the field record goes next
- mobile capture form automation — Conditional room sections and required photo fields, built for a phone held in one hand in a wet hallway.
- document assembly and versioning — Scope sheets and photo exhibits assembled into a dated file record rather than dropped in a shared folder.
- custom field application development — Offline capture in a property with no signal, syncing to the file record when the device reconnects.
Is this a fit for your business?
A good fit when
- More than one adjuster or field rep documents losses for your firm
- The person who scopes is not always the person who estimates
- You have been asked to produce photographs supporting a specific line item
- Return trips for missing measurements happen more than occasionally
Probably not a fit when
- You want software that writes or prices the estimate
- One person scopes and estimates every file and the shorthand has never caused a problem
- You are looking for a sketch and floor plan tool rather than a field record
What to have ready
- Whatever scope form or checklist you use now, including a paper one
- A recent file with its full photo set, so we can see how images are actually taken
- The estimating platform your firm writes in and how it prefers to receive room data
Questions we get asked
Does this replace Xactimate or Symbility?
No, and it should not try to. Those platforms own pricing, line item structure, and the estimate itself. This sits upstream and owns the field record: rooms, dimensions, materials, observations, and photographs.
Our adjusters use different phones and tablets.
That is normal, and it is a design constraint rather than a problem. We build capture as a browser-based form that runs on any current device instead of a native app installed on hardware the firm does not own. Offline capture uses local storage and a sync step.
What about aerial roof measurement reports?
The report attaches to the file as a document, and roof planes use the same identifier scheme as rooms, so a photograph of the north slope and the measurement of the north slope point at the same thing.
Can the system flag when a scope looks thin?
It checks completeness, not quality. A room with no photographs, a wall with no dimension, or a moisture reading with no instrument gets flagged before the scope can be marked complete. Whether the scope is correct is the adjuster’s professional judgment.
Related
- claim intake and adjuster assignment
- supplement requests and carrier response tracking
- form automation for field data capture
- workflow automation for appraisal and adjusting firms
Tell us what the process looks like now and we will map what a system would need to do. No obligation, and you keep the map either way.