Scope of Loss Development Worksheet
A Scope of Loss Development Worksheet for documenting damaged building components by trade after a loss event. Use it to turn site observations into a clear repair-estimate foundation with fewer missed items.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Property Insurance · Restoration Services · Construction Estimating · Facilities Management
Overview
The Scope of Loss Development Worksheet is a field form for organizing observed damage after a property loss by trade and building system. It gives inspectors, adjusters, and estimators a structured way to record what was damaged, how much was affected, and whether the item should be repaired or replaced.
Use this template when you need a repair-scope foundation after a fire, water, wind, impact, or similar loss event. The form starts with submission details and loss/property context, then moves through roofing, framing and structural, interior finish, and mechanical/electrical/plumbing sections. It ends with repair assumptions, excluded items, and follow-up notes so the reviewer can see what was observed versus what still needs verification.
This template is not meant for a final priced estimate, a full claim narrative, or a general incident report. It works best when the damage can be broken into component-level observations and when the team needs a consistent way to compare field findings across properties. It is less useful for minor losses with only one affected item, or for situations where no repair scope will be developed.
Because the form may capture project references and other sensitive details, keep the fields limited to what the team will actually use. Clear field types, conditional logic, and a defined submission-confirmation line help make the worksheet easier to complete, review, and defend later.
Standards & compliance context
- If the worksheet collects project references or other PII, apply GDPR data minimization and collect only the fields needed to document the loss scope.
- If the form is used in a public-facing workflow, make the submission notice and consent/disclosure language clear so users understand what happens after they submit.
- Use an audit trail for edits and follow-up notes so scope changes can be traced back to the original field observations.
- If the worksheet is adapted for health-related property environments, keep collection to the minimum necessary principle and avoid unnecessary personal details.
- Design the form to meet WCAG 2.1 AA expectations with clear labels, logical tab order, and accessible validation messages.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Submission Notice
This section establishes who submitted the worksheet, when it was filed, and whether anonymous submission is allowed in your workflow.
- Submission Type
-
Anonymous Submission
Select this if you want to submit without your name attached to the record where allowed by your workflow.
- Project / Claim Reference
- Submission Date
Loss and Property Details
This section gives the reviewer the basic loss context needed to understand the property type, event date, cause, and affected area.
- Property Type
- Date of Loss
- Cause of Loss
-
Affected Area Summary
Briefly describe the rooms, elevations, or building areas affected.
Roofing Scope
This section captures roof-related damage by component so repair or replacement decisions can be tied to specific observations.
- Is roofing damage present?
- Damaged Roofing Components
- Estimated Roofing Quantity
- Roofing Repair or Replace Decision
Framing and Structural Scope
This section records structural damage and stability concerns that may affect safety, sequencing, or the need for engineering review.
- Is framing or structural damage present?
- Damaged Framing Components
- Estimated Framing Quantity
- Structural Stability Concern
Interior Finish Scope
This section documents visible finish damage and measured affected area so drywall and finish repairs can be scoped accurately.
- Is drywall or finish damage present?
- Damaged Finish Components
- Estimated Drywall Area (sq ft)
- Finish Level
Mechanical, Electrical, and Plumbing Scope
This section separates MEP damage into trade-specific components so the estimate can be assigned and priced correctly.
- Is mechanical, electrical, or plumbing damage present?
- Damaged Mechanical Components
- Damaged Electrical Components
- Damaged Plumbing Components
Scope Notes and Estimate Foundation
This section records assumptions, exclusions, and follow-up needs so the final estimate is grounded in documented field findings.
-
Repair Assumptions
List any assumptions used to develop the scope, such as access limitations, matching requirements, or concealed damage assumptions.
-
Excluded Items
Document items that are known but intentionally excluded from the current scope.
-
Follow-Up Required
Select if additional site review, measurements, or trade verification is needed before estimate finalization.
- Follow-Up Notes
How to use this template
- Set up the submission notice fields first, including project reference, submission date, and whether anonymous submission is allowed for your workflow.
- Enter the loss and property details, then describe the affected area in plain terms so reviewers can understand the site context without reading the full narrative.
- Complete only the trade sections that apply, using conditional logic to show roofing, framing, interior finish, or MEP fields when damage is present.
- Record quantities, component names, and repair-or-replace decisions with measurements or counts that match the field observations.
- Add repair assumptions, excluded items, and follow-up notes before submitting so the estimate team knows what is confirmed and what still needs review.
- Review the worksheet for missing fields, unclear component names, and unsupported assumptions, then route it to estimating or project management for action.
Best practices
- Use conditional logic so users only see trade sections that apply to the loss, which reduces errors and completion time.
- Mark each field as required or optional based on whether the information is needed to build the estimate, not because it is convenient to collect.
- Capture quantities with the right field type, such as numeric inputs for counts and square footage for area, instead of free-text notes.
- Separate observed damage from repair assumptions so reviewers can tell what was seen on site and what was inferred.
- List excluded items explicitly when they are outside scope, inaccessible, or not part of the current loss event.
- Add a follow-up required flag when the inspector needs moisture readings, structural review, or trade verification before pricing.
- Keep the affected area summary concise and specific, naming rooms, elevations, or roof sections rather than using broad labels.
- Use progressive disclosure for sensitive or rare details so the form stays short unless the user needs to expand it.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this worksheet used for?
This worksheet is used to document damaged building components by trade after a loss event so an estimator can build a repair scope from consistent field notes. It helps separate roofing, framing, interior finish, and MEP damage into clear sections. The result is a cleaner estimate foundation and fewer gaps between the site walk and the final scope.
When should I use it during the claims or repair process?
Use it during the initial site inspection or loss walkthrough, before repair pricing is finalized. It is especially useful when multiple trades are affected and the damage needs to be organized by component rather than by narrative notes. If the scope is already fully defined and priced, this worksheet adds less value.
Who should complete this template?
It is typically completed by an adjuster, estimator, contractor, project manager, or restoration lead who is documenting observed damage. A field inspector can fill it out on-site, then a senior reviewer can use it to confirm assumptions and exclusions. The key is that the person completing it can identify trade-specific damage and note what still needs verification.
Does this template replace a final estimate or repair proposal?
No. This worksheet is a scope-development tool, not the final priced estimate or contract. It captures observed damage, quantities, repair-or-replace decisions, and follow-up items so the pricing team has a reliable starting point. A final estimate may still require measurements, photos, code review, and trade-specific pricing.
How does it help with compliance and documentation?
It creates a structured record of what was observed, what was assumed, and what still needs follow-up, which supports an audit trail. That matters when you need to show why certain items were included or excluded from the scope. If the form collects project references or other PII, keep the data minimized and include clear submission and disclosure language.
What are the most common mistakes when using it?
The most common mistakes are leaving trade sections blank without marking them as not damaged, using vague component names, and skipping quantities or measurements. Another frequent issue is listing repair assumptions without noting what evidence supports them. A final pitfall is failing to separate observed damage from excluded items, which makes the estimate harder to defend.
Can this be customized for different property types or losses?
Yes. You can tailor the component lists, add conditional logic for specific trades, and adjust the affected-area summary for residential, commercial, or mixed-use properties. For water, fire, wind, or impact losses, you may also add loss-specific prompts such as contamination, access limitations, or temporary stabilization needs. Keep the form focused on only the fields you will actually use.
What integrations or handoffs does this template support?
This template works well as a handoff between field inspection, estimating, and project management. It can feed a photo log, estimate software, claims workflow, or document repository if your process supports attachments and status tracking. The important part is preserving the scope notes, exclusions, and follow-up items so downstream reviewers can trace decisions.
How should we roll it out to a field team?
Start with one loss type or one branch, then standardize the field names, required vs optional fields, and review steps. Train users to complete the worksheet immediately after the walkthrough while details are fresh and photos are still linked to the observed damage. Review a few completed forms for consistency before making it the default template.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
See how connected 1:1 tracking, employee audit history, and LMS completion records turn scattered processes into verifiable workforce documentation.
-
See how bank branch managers use MangoApps scheduling to fill shifts, communicate policy updates, and eliminate last-minute coverage chaos.
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
-
See how MangoApps embeds AI directly into inspections, safety incidents, and SOPs — so frontline workers get answers in context, not in a separate tool.
Ready to use this template?
Get started with MangoApps and use Scope of Loss Development Worksheet with your team — pricing built for small business.