DAT vs. line crew: what separates damage assessment from restoration
If you've ever had a mutual-aid crew leader radio in asking whether they're "assessing or fixing" on a given circuit, you already know the line between damage assessment and restoration isn't always as clean as the ICS org chart makes it look. It matters enough to get right, though, because misreading it costs hours you don't have during the first 48 after landfall or a derecho sweeps through.
What a damage assessment team actually does
A damage assessment team, or DAT, exists to answer one question: what's broken, and where. DAT members drive or walk assigned circuits with a laptop or tablet, log pole breaks, conductor down, transformer damage, and blocked access, and feed that into the outage management system or a shared damage log. They don't carry line trucks, bucket trucks, or digger derricks. They're not cutting brush or setting poles. A two-person DAT in a pickup can cover a lot of ground in a day, which is the point. Speed of information beats speed of repair in those first hours, because nothing gets sequenced correctly without a damage picture.
Most DAT members aren't journeyman linemen, either. Utilities often staff these teams with engineering techs, vegetation management staff, or even trained office personnel pulled onto storm duty, sometimes paired with a lineman for safety and technical judgment on energized equipment. The job is observation and documentation, not repair.
Where restoration crews pick up
Restoration crews are the ones with the trucks, the material, and the authority to re-energize. A line crew shows up with a job package, usually generated from what the DAT found, and does the actual work: replacing poles, re-stringing conductor, swapping transformers, clearing the tree that took the line down in the first place. Tree crews, underground crews, and substation crews all fall under this umbrella too, each working from damage that's already been identified and prioritized.
The confusion is rarely about job duties, since a bucket truck crew and a DAT look nothing alike in the field. It shows up in sequencing: which circuits get a restoration crew dispatched first, and whether that decision is based on a DAT that's physically reached the circuit, trouble tickets phoning in from customers, or something else entirely. In a storm with hundreds of circuits down across a multi-county footprint, DATs can't be everywhere at once, and ticket volume alone tells you where people are angry, not where the wire is actually down.
Why the line between them gets blurry during mutual aid
Mutual-aid crews arriving from out of state often don't know your territory's circuit layout, access roads, or staging logistics. Some coordinators send them out paired with a local guide to do combined assessment-and-repair on the fly, especially on circuits where the damage is obviously severe and waiting for a formal DAT pass wastes daylight. That's a reasonable call in some situations, but it blurs the DAT-versus-crew distinction in a way that can leave gaps in the damage log if nobody circles back to document what got fixed without a formal assessment first.
For a lot of coordinators, the damage picture driving the DAT dispatch order is built from the last storm's ticket patterns and whatever windshield surveys crews can manage. That means the first circuits DATs reach aren't necessarily the worst ones, just the most accessible or the loudest. A pre- and post-event imagery comparison across the service territory, built to flag where damage is concentrated before every circuit has been walked, gives coordinators something to sequence DAT and crew dispatch against on the same day imagery comes in, instead of waiting for assessment teams to physically cover ground that satellite or aerial passes already show is torn up.
Getting the DAT-to-crew handoff right starts with knowing where to point the DAT in the first place. See what a same-day damage comparison looks like for your territory.