Skip to content
⚠️ Staging environment, test only, not production
Sign In

Demolition

Xactimate Code DMO|DMOPU — Demolition

Category Demolition, measured in EA.

SEL code
DMO|DMOPU
Unit of measure
EA
Category
Demolition (DMO)
Price
Varies by price list and region, why pricing varies by region

Real-world usage of DMO|DMOPU

Appears in 65 of 358 scopes ESXPress has analysed and in 136 of 598 converted customer scopes. Usage is measured from real claim documents, never estimated. How this is measured.

Frequently estimated with DMO|DMOPU

Codes measured in the same claim scopes as DMO|DMOPU, from scopes processed through ESXPress. The count is how many scopes carried both lines.

Most-used Demolition codes

Other Demolition (DMO) codes ranked by how often each appears in the claim scopes ESXPress has processed, most-used first. Every code below carries its own measured-usage page.

What it is

DMO|DMOPU is a Demolition (DMO) Xactimate SEL code used for this work, measured in each (EA).

ESXPress’s reference documents DMO|DMOPU. Across processed claim scopes, ESXPress observed 71 line items written against this code — 69 of them (97.2%) measured in EA, and 2 line items in WK.

The code appears in 65 of the 358 scopes analysed (about 18.2%) and in 13 of the 61 converted customer scopes.

When to use it

Use DMO|DMOPU when the scope calls for this code — Demolition work measured in each (EA). Across processed scopes, 71 of the 71 observed line items (100.0%) were written as “this code”.

The co-occurrence data below comes from processed scopes; the strongest pairing is with PNT|PNTRJACK — the same scopes, 22 times, lift 1.78. It also appears alongside Chimney flashing (RFG|RFGFLCH, 22 scopes) and Continuous ridge vent (RFG|RFGVENTR, 15 scopes).

Within the Demolition category, the lines most often seen in the same scopes are Dumpster (DMO|DMODUMP, 67 scopes) and DMO|DMODTRLR (54 scopes).

How to use it

Measure the work in EA: 69 of the 71 observed line items (97.2%) used EA and 2 in WK. The unitAsUsed analysis puts EA at a 97.2% share, making it the safe unit for conversion.

The observed line text is “this code” (71 of 71 line items, 100.0%).

ESXPress’s Completeness Advisor has no rule that references this code, so its usage evidence is purely observational: 65 scopes and 71 line items.

Often used together

Two kinds of related codes are listed below. First, codes that appear in the same scopes as DMO|DMOPU — co-occurrence measured across the claim scopes processed through ESXPress with support of at least 3 scopes and lift of at least 1.5. Second, other frequently used Demolition (DMO) category codes, ranked by how often they appear in the analysed scopes. Descriptions are from the ESXPress code reference.

Questions & answers about DMO|DMOPU

When is DMO|DMOPU used in Xactimate?

DMO|DMOPU is the line item for this work — Demolition work measured in EA. Across processed claim scopes, 71 of the 71 observed line items (100.0%) were written as “this code”.

What unit is DMO|DMOPU measured in?

each (EA) — 69 of 71 observed line items (97.2%) were measured in each (EA), and 2 in WK.

What does DMO|DMOPU get used with?

Its strongest co-occurrence is with PNT|PNTRJACK — the same scopes, 22 times (lift 1.78). Other frequent neighbours are Chimney flashing (RFG|RFGFLCH, 22 scopes) and Continuous ridge vent (RFG|RFGVENTR, 15 scopes).

How often does DMO|DMOPU appear in real claims?

In 65 of the 358 scopes ESXPress analysed (about 18.2%) and in 13 of the 61 converted customer scopes, with 71 line items observed.

Browse all Demolition codes (DMO)

Need the full picture? Convert a carrier scope PDF to an import-ready Xactimate ESX file with every line mapped to its correct SEL code, Convert PDF to ESX or read the step-by-step guide.

Convert a scope PDF to an import-ready ESX file

Every line mapped to its correct Xactimate SEL code, accurate, code-matched, and ready for Xactimate.

Xactimate is a registered trademark of Verisk Analytics. ESXPress is an independent tool and is not affiliated with or endorsed by Verisk. Prices are not published. Usage and pairing data are measured from claim scopes processed through ESXPress. Built by Chaz Jaco.