Metal Work
Xactimate Code MTL|MTLBIDITM — Metal Work
Category Metal Work, measured in EA.
- SEL code
- MTL|MTLBIDITM
- Unit of measure
- EA
- Category
- Metal Work (MTL)
- Price
- Varies by price list and region — why pricing varies by region
Real-world usage of MTL|MTLBIDITM
Appears in 5 of 358 scopes ESXPress has analysed and in 2 of 550 converted customer scopes. Usage is measured from real claim documents, never estimated. How this is measured.
How it's written in real claims
From 5 line items across 5 scopes processed through ESXPress — the exact operation text and unit of measure adjusters actually write:
- “Metal Structures & Components (Bid Item)”4 lines
- “Metal Structures & Components- shed”1 line
Dominant unit of measure: EA — used in 100% of samples.
Frequently estimated with MTL|MTLBIDITM
Codes measured in the same claim scopes as MTL|MTLBIDITM, from scopes processed through ESXPress. The count is how many scopes carried both lines.
- RFG|RFGVENTE (in 3 scopes)
- RFG|RFGRIDGCS (in 4 scopes)
- SFG|SFGGUTA (in 3 scopes)
What it is
MTL|MTLBIDITM is a Metal Work (MTL) Xactimate SEL code used for this work, measured in each (EA).
ESXPress’s reference documents MTL|MTLBIDITM. Across processed claim scopes, ESXPress observed 5 line items written against this code — every one measured in EA. The line appears in 5 of the 358 scopes analysed (about 1.4%).
When to use it
Use MTL|MTLBIDITM when the scope calls for this code — Metal Work work measured in each (EA). The real-world act texts track the reference wording: 4 of the 5 observed line items (80.0%) were written with this code.
The co-occurrence data below comes from processed scopes; the strongest pairing is with Exhaust cap (RFG|RFGVENTE) — the same scopes, 3 times, lift 3.33.
How to use it
Measure the work in EA: 5 of the 5 observed line items (100.0%) used EA. There is no unit variation for this code in the processed scopes.
This code accounts for 4 of the 5 sampled lines (80.0%). Estimators also write “Metal Structures & Components- shed” (1 line).
Often used together
Two kinds of related codes are listed below. First, codes that appear in the same scopes as MTL|MTLBIDITM — 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 Metal Work (MTL) category codes, ranked by how often they appear in the analysed scopes. Descriptions are from the ESXPress code reference.
Real-world examples
Each example is an anonymised line from a processed claim scope: the exact operation text and unit of measure adjusters wrote, with the observed line-item count. The count is line frequency across the analysed samples — never a price and never a quantity from a specific claim.
- In a real claim, this line appeared as: “Metal Structures & Components- shed”, EA, qty 1.
Questions & answers about MTL|MTLBIDITM
When is MTL|MTLBIDITM used in Xactimate?
MTL|MTLBIDITM is the line item for this work — Metal Work work measured in EA. Across processed claim scopes, 4 of the 5 observed line items (80.0%) were written with this code.
What unit is MTL|MTLBIDITM measured in?
each (EA) — all 5 observed line items (100.0%) were measured in each (EA).
What does MTL|MTLBIDITM get used with?
Its strongest co-occurrence is with Exhaust cap (RFG|RFGVENTE) — the same scopes, 3 times (lift 3.33). Another frequent neighbour is Hip / Ridge cap (RFG|RFGRIDGCS, 4 scopes).
How often does MTL|MTLBIDITM appear in real claims?
In 5 of the 358 scopes ESXPress analysed (about 1.4%), with 5 line items observed.
Browse all Metal Work codes (MTL)
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.