Government risk and safety teams are often asked to do something that sounds impossible on paper. They must manage safety compliance, environmental requirements, workers’ compensation, and risk programs across dozens of departments and employee populations, with a team that could fit in a single conference room. For many public sector organizations, this is the daily reality. A centralized team of five or six people supports 20-plus departments, from public works and utilities to police, fire, and parks. Budget constraints make headcount growth rare. The scope of the work keeps expanding anyway. At Origami Risk’s 2026 Government and Public Entities User Group, practitioners from cities, counties, and state agencies gathered to share how they’re navigating this tension. The Hidden Scale Problem in Government Safety Programs Government risk teams are managing a lot but often underestimate how much they can’t see. One team shared a striking example. Before centralizing their safety inspection program, they estimated they were handling somewhere around 200 to 300 inspections per year. After moving everything onto a single platform, the reality emerged. Inspections topped 1,000 annually and kept climbing. The inspections were always happening. It’s just that departments were completing them using paper forms, spreadsheets, and third-party survey tools. While some findings made it back to the central team, many did not. And without a unified view, there was no way to know which locations were covered, which were falling behind, or where compliance gaps were forming. This is the “hidden scale” problem: the work exists at a volume and frequency most teams can’t fully see until they have a single place to look. That visibility gap is where most programs lose ground. The practitioners at this year’s user group who had closed that gap shared a set of approaches that translate across government organizations, regardless of size or structure. Three lessons came through clearly. Lesson 1: Reframe the Platform Before You Roll It Out Platform rollouts in government environments often stall because departments already have systems, and some of those systems work reasonably well. Asking people to abandon a familiar workflow for an unfamiliar one without a compelling reason naturally creates resistance. Practical advice from the practitioners at this year’s user group was to change the framing before you make the ask. The shift that worked for several teams was positioning the platform as a connector: a shared system for cross-department visibility rather than a mandate to consolidate every tool. Departments contributed incident reporting, inspections, corrective actions, and compliance tracking to the central platform. Specialized tools that served specific functions stayed in place. This framing reduced resistance because it changed the implied stakes. Instead of being asked to give something up, departments were contributing to a shared picture. And Once their data became part of that broader view, the value of connected data surfaced for everyone. Lesson 2: Make the Data Visible to the People Who Own the Behavior Shared visibility changes accountability. When safety inspection counts, open corrective actions, and incident rates are visible only to the central team, responsibility for improving them stays there. When that same data appears in a dashboard reviewed by department directors at a monthly steering committee meeting, ownership becomes shared. Several teams at the user group described variations of this dynamic. One organization used their longstanding safety recognition program as a forcing function. Departments that completed all required inspections received recognition, but in prior years, verification was manual: paper submissions counted by hand, with limited ability to confirm accuracy. After moving to a unified platform, inspection completion data was tracked automatically and made verifiable. The recognition program gained credibility, and participation climbed sharply. The mechanism is straightforward: people pay attention to the metrics they know others will see. When data on inspection participation, overdue corrective actions, and incident trends appears in front of directors alongside every department’s performance, the impetus to act shifts from external pressure to internal motivation. One practitioner put it plainly: no one wants to be the department that’s behind when everyone else can see where they stand. Lesson 3: Let the System Surface What You Don’t Know to Look For The most unexpected value of a unified platform often has nothing to do with the problem it was originally built to solve. One team described a situation that illustrated this well. Occupational health data tracked through the platform revealed an unusual pattern in a specific employee population’s test results. The workers’ compensation team reviewed the data and flagged it to safety, who identified an environmental component. The environmental team addressed the root cause, and follow-up results returned to baseline. No single team would have caught this working from their own data alone. The connection required visibility across programs that, in a siloed environment, would never have been in the same room. Another team made a similarly unexpected discovery. Platform data showed that injuries in one department were concentrated in training activities, not in field operations. That finding prompted a direct change to their safety program, equipment maintenance protocols, and training approach. The insight was always available in the underlying data. The platform made it visible. This is the compounding value of integrated data. Patterns that distributed systems cannot surface become apparent when claims, safety, occupational health, and environmental data share a common foundation. What Comes Next for Government Risk Teams The conversation at this year’s user group extended beyond what teams are doing today. Participants explored emerging capabilities: AI-assisted policy data ingestion, centralized insurance portfolio management, chemical management, and tools that connect risk, safety, and insurance data in ways that were difficult to achieve a few years ago. For lean teams managing complex programs, these capabilities matter most to those who have already done the foundational work. Centralizing workflows, driving adoption across departments, and connecting programs that were previously siloed are the steps that make advanced capabilities useful. The teams investing in that foundation now are the ones best positioned to benefit as the technology continues to develop. Origami Risk’s integrated platform supports government and public entity teams across the full scope of risk, safety, workers’ compensation, and insurance management, helping lean teams operate at a scale that would otherwise require significantly more resources. Learn how Origami Risk helps government and public entity teams scale risk, safety, and compliance programs without adding headcount.