This is the plain-language edition of the raid-phone update. Same facts, none of the form numbers or legal citations, and nothing collapsed into boxes. Every claim below is stated again on the cited edition, with the video placed on one clock so you can watch it yourself.
Here is a small thing that turns out to be a big thing. On the afternoon of the raid, you can line up three separate recordings — one officer’s body camera, a second officer’s body camera, and a reconstruction of what was on the first officer’s phone — and set them all to the same clock. When you do, they tell one continuous story about who was talking to whom while the police were inside the house.
Start with the paperwork, because the paperwork has times on it. A judge signed the search warrant at 5:37 in the evening. That is the moment the police were allowed to go in.
Fourteen minutes later, at 5:51, one of the lieutenants has his phone out, and his body camera catches the screen. There is a text on it that says the warrant was approved and the team is moving up right now. He opens the contact card for the chief of police — the man at the very top of the department — and he places a call to him. You can watch the phone do it.
Then you hear his half of the call, because it is picked up by the microphone on his own chest. He tells the chief: no forced entry, five people in custody, we’ve got the main target too, I’ll coordinate with the detectives. A minute later he makes a second call, this time to the head of investigations, and says the same thing, and they talk about where to put everyone — a holding cell, bring them down.
And here is why the second camera matters. A different officer, standing a few feet away in the same house, has his body camera pointed toward the doorway. On his footage, at the very same second, you can see the lieutenant standing there with the phone against his ear. Two cameras, filmed by two different people, showing the same man make the same call at the same instant. That is what it means to say it is on one clock.
Now, why does any of this matter beyond being a neat piece of footage? Because when someone later argues that a police department did something wrong, the department’s usual answer is that the boss did not know — that whatever happened was a decision made by people on the ground, and the chief only found out afterward, from a report. That answer is much harder to give here. The record shows the chief was told, by text, that the operation was approved and moving, and then got a live phone call about how it went while it was still going on. He was not reading a summary days later. He was on the line.
And it matters that it was the chief he called, and not just any officer. The legal rule that lets you hold a whole police department responsible for a decision only works when the person who signed off is the department’s final decision-maker — and for how a raid is actually run, that person is the chief of police. Under Utah law the chief has a sheriff’s authority inside the city. The mayor and the city council control his budget and who gets hired, but none of them tells him how to execute a warrant in the field. So on the exact question this case turns on — how this operation was conducted — the chief is the top of the ladder, and the buck stops with him. A sergeant getting the same phone call would not count; his say-so is not the city’s. That is why it is telling that the lieutenant did not phone a colleague, or even the head of investigations, for this. He scrolled to the chief of police’s name and called him.
To be fair about it: we only have the officers’ side of these calls. We do not have the chief’s words. This page is not saying the chief ordered anyone to do anything. What it is saying is narrower and solid — that the man at the top was in direct, back-and-forth contact about the operation as it happened, which is a fact you can check on the department’s own video.
There are two more things worth knowing, and they are about what the public was and wasn’t shown. First: when the department released this footage, it held some clips back. One of the ones it held back is an interview in which a man who was detained explains, in his own words, that the whole thing was his idea — that the others were just doing what he said, that it was for a fundraiser, that he got the neighbor’s permission to film. That is the kind of thing the people accused in this case are entitled to have, because it points away from the story the state is telling, and it was not in the public release.
Second: the officer who actually swore out the warrant — who signed the statement that convinced the judge — had his own body camera turned off for the entire stretch of that afternoon in which he swore it and the judge signed it. His camera was rolling earlier, when he was booking a different arrestee, and it came back on later, when the team lined up to go in. But for the hour and a half in the middle, the part where the case for the warrant was made, there is no video at all. The only record of that window is the piece of paper he wrote.
And two more things about the people in this story. The first is about the officer who made the calls. He has been sued once before, in federal court, over how he used force. In that earlier case a man says the officer shocked him with a Taser while he was on his knees, surrendering, and that another officer covered the camera so it would not be recorded. Those are only allegations, and that case was never decided. But it is the same move — turn the camera off, keep it off the record — that this whole story turns on. When the same officer keeps turning up with the same pattern, that is exactly the kind of thing that makes it hard for a department to argue, later, that no one could have known.
The second is a quiet detail in the warrant itself. The officers told the judge that a cooperative homeowner had reported the “stolen Lego” story — the sort of neutral tip a judge is supposed to be able to lean on. But on the body camera, that homeowner is riding in the lieutenant’s own truck during the operation, and the two of them know each other from serving together in the National Guard. A tip from a friend riding along in your truck is not the neutral stranger the paperwork made it sound like. (To be clear, that homeowner has nothing to do with the LEGO business this site usually covers; the point is only about how the warrant was described to the judge.)
The fair counterpoint. Swearing this kind of warrant is often done by phone or at a desk, and police do not usually film that, so a camera being off then is not proof that anything went wrong. And every officer named here is presumed innocent; nothing on this page is a finding that anyone committed a crime. But set the fairness beside what is simply true: a judge signed the warrant at 5:37, the phone said “moving up” at 5:51, the chief was on a live call getting the count while the raid was underway, and the officer who wrote the warrant had his camera off for the whole time he was writing it. Those are not opinions. They are timestamps.
The BAM Map is independent reporting on matters of public concern. Nothing here is a finding of any person’s guilt; the criminal charges referenced are unadjudicated and every defendant is presumed innocent. Sources are linked so readers can check the record. · Home · Map · The law · Bodycam