The Off-Duty DUI and the Restraint That Wasn't in the Report
Officer Danny Ruiz, 29, with three years of service, was arrested at 0140 by a county deputy after his personal truck struck a parked car in a convenience store lot. His breath test result was 0.16. On the deputy's body camera, Ruiz said, "Come on, man, I'm one of you - can't we handle this off the books?" He was booked for first-offense DUI and released on his own recognizance. His sergeant placed him on 30 days of administrative leave, and the chief imposed a 5-day suspension after an internal review. Separately, four months earlier, Ruiz arrested a man for obstruction. His report describes "a controlled takedown." The jail's intake video shows Ruiz applying a rear chin restraint for roughly 12 seconds after the man was already handcuffed. A use-of-force review found the restraint within policy but noted the report "could have been more detailed." No one has contacted POST. The chief tells the sergeant, "The DUI is a misdemeanor and the restraint was within policy - we're not reporting either one."
1. Must the agency report either event to POST? Address the chief's reasoning directly.
Read the worked answer
Yes, both, and the chief's reasoning gets the test backwards.
The reporting duty is triggered by the conduct and the allegation, not by how the agency chooses to dispose of it internally. The Commission's interest is in whether a certified officer remains fit to hold a certificate, which is a separate question from whether the agency imposed discipline.
The DUI arrest. A certified officer has been arrested. The fact that the charge is a misdemeanor affects the criminal penalty, not the notification requirement. Add to it the body-camera statement - an officer asking another officer to "handle it off the books" during a criminal investigation goes directly to honesty and to the public trust that certification protects.
The restraint. The internal finding that the restraint was within policy resolves the force question. It does not resolve the reporting question. A 12-second chin restraint applied after handcuffing, described in an official report as "a controlled takedown," is a report-accuracy issue. Failing to document force that was applied is the kind of conduct that gets certificates revoked, and the agency's own review flagged it.
Trading silence for a resignation does not work either: the duty attaches to the agency, and it survives the officer leaving.
The sergeant should report through the agency's designated POST contact, in writing, and keep a copy. If the chief directs otherwise, the sergeant should document the directive and escalate - a sergeant disciplined for following the statute is in a defensible position; a sergeant who quietly helped bury it is not.
2. What may POST do in response, and what process is due to Ruiz?
Read the worked answer
Authority. The Commission may investigate, and depending on what it finds, dismiss the matter, impose a reprimand or conditions, suspend the certificate, or revoke it. Revocation is not limited to felony convictions; sustained dishonesty and serious misconduct bearing on fitness are the classic grounds, and the DUI plus the statement plus the understated report can be considered as a pattern rather than three unrelated events.
Process. Ruiz is entitled to written notice of the allegations, a meaningful opportunity to respond, and a hearing before the Commission acts against his certificate, with the right to be represented. The agency's internal investigation is evidence, not the adjudication. He may also be placed on conditions or a probationary status rather than losing the certificate outright, depending on the facts and his record.
Interim status. The agency decides his duty status day to day; the Commission's process takes longer. He should not be in a position where he is collecting use-of-force statements or writing reports for a case that will be litigated while a report-accuracy allegation is pending against him.
What the sergeant should ensure is preserved now: the body camera from the DUI stop, the jail intake video, the original arrest report, the use-of-force review packet, and the internal affairs file. Body camera and jail video are on retention schedules that are shorter than an administrative process. If the video is overwritten before the Commission sees it, the case changes.
3. What should the sergeant do about the report discrepancy itself, separate from the POST question?
Read the worked answer
Handle the report problem as a report problem, on its own timeline.
1. Preserve the evidence first. Pull the jail intake video into the internal affairs file with a preservation letter today. Do not rely on the jail's retention schedule.
2. Get a truthful supplement on the record. Either Ruiz or his supervisor should prepare a supplemental report or memorandum describing the restraint accurately - duration, position, that the subject was handcuffed, and why it continued. Late and accurate beats never. A supplement is not an admission that the original was a lie; a missing supplement is what makes it look like one four years later in a deposition.
3. Ask the honest question. The use-of-force review called the report "not detailed enough." That phrasing hides the real question: was the omission careless, or was it deliberate because the officer knew the restraint looked bad? The answer determines whether this is a training and supervision issue or a conduct issue. The video usually answers it - 12 seconds of a chin restraint after handcuffing, omitted from a report, is a hard thing to call an oversight.
4. Fix the systemic cause. If the agency's review process routinely accepts "controlled takedown" as a complete description of force, the problem is bigger than one officer. Reports should require the specific technique, the duration, the subject's position, and the reason for continuing force.
5. Don't let the DUI swallow the other case. They are separate investigations with separate evidence and separate findings. Bundling them lets the more serious-looking charge (DUI) mask the more damaging one (a report that did not match the video).