X-code marking vs. building damage grade: what's the difference?

If you've worked a disaster response, you've seen the spray-painted X on a building wall, a car, a pile of rubble. It's one of the most recognizable marks in emergency management, and it gets confused constantly with damage classification work that happens before a search team ever shows up. They're not the same thing, and mixing them up in a briefing wastes time you don't have.
What the X-code actually marks
The X-code (sometimes called the FEMA search marking, or the USAR structure marking system) is a standardized spray-paint code used by US&R task forces to log what happened during a physical search of a structure. It's painted directly on the building, usually near the primary entry point, in a format that's been consistent across task forces since the National US&R Response System adopted it.
The marking works off four quadrants around the X:
- Top: the searching team's identifier, plus date and time the team went in.
- Left: hazards found inside, structural, chemical, whatever the team flagged.
- Bottom: date and time the team came back out, plus any other notes for the next crew.
- Right: number of victims found, and number of victims removed.
A single diagonal slash before the search is complete means the structure is still being worked. The completed X means someone physically went in, searched it, and logged the result. That's the whole point of it: it's a record of ground truth, written by people who were standing inside the building.
Why that timing matters
An X-code can't exist until after a team has entered a structure. It's documentation of a completed (or in-progress) physical search, which means by definition it happens downstream of the decision to send a team there in the first place. Someone had to decide this building, out of the hundreds or thousands in the affected area, was worth a crew's time before any paint goes on the wall.
That decision, in the first hours after an earthquake, is usually made with whatever's on hand: ground reports radioed in, a windshield survey if roads are passable, sometimes nothing more than which neighborhood sounded worst on the scanner. None of that tells a coordinator which specific structures, out of a damage footprint that can run for blocks, actually need a team first.
A damage grade answers a different question
A per-structure damage grade, built from vertical very-high-resolution imagery taken right after the event, is not a record of what a team found. It's a dated, structure-by-structure read of the affected area, produced before any team has walked the block. It doesn't replace the X-code, and it can't tell you what's inside a building or whether anyone survived in it. What it does is narrow a few square miles of damage down to the handful of structures that look collapsed or severely compromised, so the first teams in aren't guessing which street to start on.
A damage grade is the step that happens before the X goes on the wall. A coordinator looking at a dated grade of the whole footprint can route search assets to the structures graded worst, then let the teams on the ground do what the X-code was built for: documenting, floor by floor, what's there.
The short version
An X-code is ground truth, written by a team that's already inside. A damage grade is a remote triage read, delivered before that team gets there, pointing them at the right address. One tells you what happened in a structure. The other tells you where to send the people who can find out. If you're coordinating the first wave of search assets and working from radio chatter and whoever got there first, FlyPix's building damage classification is built to give that first routing decision something firmer to stand on.
Get in touch if you want to see what a post-event damage read looks like for your response area.