Inspector General

  • |

    The Postal Service Put Management on Hold

    I have completed the paperwork autopsy, and Exhibit A had a pulse. A July 27 USPS Office of Inspector General audit connected weak management conditions and below-average facility efficiency to nearly $437 million in annual questioned costs. That is not a finding that somebody stuffed cash into a postal uniform; it is an estimate of efficiency losses associated with conditions management can influence. The suspicious label on the body reads “workplace culture,” which is apparently how institutions describe an operational problem when they hope it will remain atmospheric.

    The OIG did not reach for a national crystal ball. It compared five low-performing districts with five high-performing districts, using employee surveys, interviews, site visits, staffing information, and operational indicators. The result was a measurable difference between places where supervision and engagement were functioning better and places where the machinery was coughing into a government form. Management conditions were not floating separately from performance. They were in the same file folder, underlined.

    That distinction matters because the Postal Service is not a boutique inconvenience for people waiting on a birthday card. The report ties its public-service stakes to more than 170 million delivery addresses. Workers operate the system, families depend on it, businesses build schedules around it, and the public pays attention whenever “modernization” arrives carrying a clipboard and quietly removes another chair. If management treats staffing, supervision, engagement, and efficiency as unrelated weather systems, the people standing in the rain get to pay for the umbrella.

    Then came the administrative thunderclap: USPS management disagreed with both corrective recommendations in the audit. The OIG found a pattern worth addressing; management rejected the proposed route toward addressing it. One can almost hear the records room whispering, “Please attach a measurable fix.” Instead, the accountability envelope appears to have received the oldest postal treatment in the book: insufficient management commitment, return to sender.

    The country does not need workplace dysfunction renamed as climate. It needs public institutions capable of reading their own evidence before the evidence develops a forwarding address. The mail may be delayed, but the response to oversight arrived instantly: return to sender.

  • |

    Baltimore County’s IEP Oversight Audit: “Sufficient Processes,” No Recommendations, Endless Parent Breadcrumbs

    I read the U.S. Department of Education Office of Inspector General’s July 7, 2026 inspection of Baltimore County Public Schools’ IEP oversight the way I read any document that has “oversight” in its job title: like it’s about to start talking… and also like it’s trying not to.

    The comfort-blanket language is right there in the findings: the report says Baltimore County had “sufficient processes” and that, “exclusive of a small number of exceptions,” required IEP information was included in the sample and sampled students received the services described in their IEPs.

    And then—because this is an inspector’s report, not a bedtime story—the paper admits exceptions existed, just not enough (in the inspector’s framing) to justify recommendations. That’s the paperwork magic trick: you can acknowledge the bruise, catalog it as statistically inconvenient, and still stamp the file “no recommendations” as if the stamp were the same thing as a fix.

    So the bureaucratic outcome isn’t exactly “nothing happened.” It’s more like: everything the report needed to check is reported as checked, everything it noticed that didn’t fit is placed into the “small number of exceptions” box, and the inspector walks away without ordering changes. For families, that can feel like an officially notarized breadcrumb trail—oversight occurred, the case is closed in the document, and the hallway of compliance still stretches on.

  • |

    SSA Deletes the Wrong Death, Forgets the Why

    I’m Hugh Jass, serious investigative reporter with absurd gravitas, and I have bad news and good news—both in the same envelope. The SSA “deletes the wrong death,” the beneficiary gets unfrozen, and everyone claps because the calendar finally stops yelling. Then the contradiction kicks in—because the system often deletes the outcome without keeping the reason, so the Evidence Screen (EVID) doesn’t explain itself. The document coughed; Exhibit A had a pulse; the fix still can’t prove how it learned.

    A reader seeing the article title will immediately understand why this article accompanies the piece because the phrase “deletes the wrong death” points to the correction, while “forgets the why” points to the missing documentation that makes the correction un-auditable.

    In an OIG review of incorrect-death corrections in a sample spanning Jan. 2020 through Dec. 2024, SSA corrected cases at a fairly healthy clip: 54% of the time, technicians made changes in line with policy. So the part that “works” definitely works. The part that doesn’t is the part that lets anyone else verify what happened next time.

    Here’s where the haunted paperwork starts: for 45% of the cases where the record was corrected, the technician didn’t document the reason the death was recorded/removed on EVID. Worse, in 61 of 78 cases within the review sample, there wasn’t even an EVID entry present—meaning the system’s own evidence door is left wide open, and then everyone acts surprised when accountability walks right through.

    And because government fixes love a sequel, the OIG also noted payment follow-through problems. In at least two cases, payment records weren’t updated to reinstate benefits for beneficiaries whose incorrect-death status had been corrected. That’s not a philosophical glitch—it’s the difference between “we changed the record” and “we fixed the life attached to it.”

    So yes: the SSA can correct an incorrect death posting. But if the “why” doesn’t live in EVID, the agency can’t show its work, future mistakes can’t be filtered, and the public is left with a transcript edit where the exhibits are missing. If you’re alive but the government’s records say you aren’t, you don’t just deserve a correction—you deserve receipts that stay filed after the clerical smoke clears.

  • |

    The Watchdogs Forgot the Forms, Again

    I’m Hugh Jass, Serious Investigative Reporter With Absurd Gravitas, and Exhibit A had a pulse: I assumed the federal watchdog that’s supposed to police OIG misconduct investigations would, at minimum, follow its own legally required process. Then GAO opened the folder and the compliance paperwork blinked first—because the Integrity Committee (the panel that reviews complaints about senior OIG personnel) can’t consistently hit timeframes, document everything it’s required to document, or reliably complete the review work inside the statute’s clock.

    GAO-26-107922, publicly released June 15, 2026, is specific about what broke. In the matters GAO reviewed, GAO estimated that only 24% met all time-frame requirements, while 76% missed at least one timeline requirement. And in GAO’s reviewed sample, none of five investigations were completed within the 150-day legal time frame. That’s not a “rare bad day” story—that’s a pattern where the system designed for consistent, timely misconduct review keeps missing the deliverable it sells to the public.

    Because deadlines aren’t the only deliverable, GAO also found documentation problems. The report describes required materials that were missing or insufficient, plus limited oversight related to assisting OIGs’ compliance. Put differently: even when the Integrity Committee is the “watchdog for watchdogs,” it still depends on other pieces of process staying properly assembled—and GAO found the assembly line for evidence, records, and review discipline was sometimes running without the full paperwork.

    So what does the government’s promised improvement look like when the problem is paperwork physics? GAO’s recommendations focus on strengthening secondary reviews, improving required reporting, and improving reimbursement documentation. Which is official-language for the thing my filing cabinet says every time it exhales: you don’t fix a haunted stapler by removing the stapling—apparently you fix it by stapling more carefully, with extra checklists, and a more detailed receipt trail for the stapler you already lost control of.

    In other words, the watchdog unit can’t reliably meet its own legally required timelines and documentation, and the response effectively treats “more compliance” as the remedy for compliance failure. That’s the only truly consistent finding here—records-room thunder, footnotes with luggage, and the same conclusion you get when you ask a compliance system to audit itself: when the watchdog drops the basics, the fix is never fewer forms. It’s more forms, more process, and the same haunted subscription plan.

  • |

    The Watchdog Found the Locked Filing Cabinet

    The law was supposed to open the filing cabinet, but now the Justice Department inspector general is reviewing how Epstein-related records were identified, handled, redacted, and released, which is how daylight becomes a hallway with one flickering bulb and a compliance binder breathing in the corner.

    I am not here to declare a bombshell hiding behind every black bar. That is amateur séance work. The official absurdity is enough: the public asked for records and got a process about the process, a custody trail about the custody trail, and administrative fog so dense the document coughed. In the end, the smoking gun has been replaced by a sweating folder labeled PROCEDURE, and Exhibit A had a pulse.

  • |

    SBA’s Cybersecurity Is Basically Schrödinger’s Firewall—Defined But Not Implemented

    In the quiet labyrinth of government filings, the Small Business Administration (SBA) has managed to create a cybersecurity scenario worthy of a mystery novel. According to a recent Inspector General audit, nine out of ten Federal Information Security Modernization Act (FISMA) control domains are defined in principle but vanish like a digital specter when practical implementation is needed. And yet, amid this vanishing act, the incident response domain remarkably pops up with an ‘optimized’ rating. Welcome to the bureaucratic underworld where policies have a pulse but no footprint.

    This puzzling discovery from the SBA’s May 20, 2026, audit paints a picture of administrative fog where preparatory documents are plentiful, yet follow-through resembles a ghost town. It’s a saga of definitions meeting an untimely demise in the space between plans and execution. The audit’s tale tells us of governance systems canceled in their infancy and inventories that seemingly disappear in a puff of digital smoke.

    The SBA, perhaps recognizing the spectral nature of its cybersecurity measures, has agreed to a fresh batch of 17 recommendations. This is a significant number, implying a hearty return to the drawing board, given that previous commitments have mysteriously remained unfulfilled. The filing cabinet seems to clear its throat, yet remains bare.

    The stakes here are far from academic. For small businesses relying on the SBA’s digital skeleton, the risk to sensitive data is not just a plot point but a real concern. Trust in SBA’s digital infrastructure is slowly being hollowed out, much like the paper trails that never turned into policy footprints.

    What makes this audit a comedy rather than a tragedy is the curious case of misplaced priority—a bustling incident response amidst a landscape of digital tumbleweeds—suggesting that while backup plans can be optimized, the primary defenses lie unattended. In this paper empire, one supremely efficient doorman surveys the ruins of an absent city.

    As we leave this peculiar chapter, let one thing remain clear: defined but unimplemented policies offer as much security as an umbrella for a sinking ship. This table, never intended for reading, still longs for implementation—a bureaucracy’s apparitional antic, indeed.

    Sources

End of content

End of content