Each year, a central risk team buys insurance and funds losses for the whole organization. It then sends each business division an internal invoice for that division’s share of premiums and claims costs, and the division pays it from its own budget. Most of these charges are flat amounts based on headcount or revenue, so a division’s bill rarely reflects its own claims history. Business leaders often approve these invoices without being able to trace a single charge to a claim. The invoice tells them what they owe and leaves out how their own decisions shaped the bill. The larger, more important shift is about who owns risk. Risk management often sits with one team, which makes that team answerable for outcomes it cannot fully influence. A better model makes risk a shared goal. Every division gets visibility into its own losses and a reason to reduce them, so teams work together on safety and claims reduction. Finance teams now want risk costs tied to how each unit performs, and a static formula cannot answer that question. Put simply, an allocation changes behavior when each charge traces back to data a unit leader can see and act on. Getting there depends on the records underneath the formula. Why the Data Comes Before the Formula Most of the work in an allocation sits in the data. A defensible allocation draws on claims, incident, and exposure records tied to each business unit. Those records usually live in separate systems, carry different unit codes, and update on different schedules. Reconciling them takes most of the project’s time. Consider a manufacturing unit whose claims sit in one system while its payroll and headcount sit in another, under a different unit code. The charge may look right on paper, yet no one can confirm which losses it reflects. Fixing that mapping usually matters more than adjusting the weights. Once that foundation is in place, the formula becomes the easy part. Weighted formulas can blend exposure ratios with loss experience, so a unit’s charge reflects both its size and its performance. A large unit with a clean loss record should carry a different charge than a smaller unit with frequent claims. The number only works when the inputs hold up. Finance and unit leaders also challenge any number they cannot trace. A charge that cannot be explained turns into a debate about the model, and the conversation about performance stalls. Traceability keeps the program alive. When a unit leader can see which losses drove the number, the discussion moves to what the unit can change. How Charges Drive Safety Behavior The Cheesecake Factory shows how this works in practice. The company operates 318 restaurants, all overseen by one risk and safety team that reports to finance. That structure gives the team visibility into the financial effect of each location’s performance, along with a seat at the executive table. The team uses that visibility to run a claims allocation program designed to reduce claim frequency and severity. Each restaurant has a financial incentive to follow best practices, and participation stays easy. Monthly safety meetings focus on emerging trends, employees can buy company-approved slip-resistant shoes through payroll deduction, and public dashboards highlight initiatives and wins at the location level. Cristian Iglesias, Manager, Risk Services, says the program effectively reduces the company’s workers’ comp claims. “Ultimately this has allowed us to be more proactive in our decision making whenever we see trends,” he says. That kind of visibility lets a risk team act on a pattern before it becomes a line item in next year’s budget. ABM Industries reports a similar pattern. Over five years, its Risk & Safety department achieved a 35% decrease in casualty claim frequency rate and an 18.5% reduction in total cost of risk (TCOR). Allocation was one of several initiatives in that transformation program, so the results reflect the full effort. Making Allocation a Management Tool Risk cost allocation is moving from an annual billing exercise toward a management tool. Leaders want risk costs connected to operational performance, and that link depends on current, connected data. Three steps help start the shift. First, map where claims, incident, and exposure data live today. Next, identify which unit-level charges you can trace to source records. Then choose one business unit and test a performance-based charge before expanding it across the organization. With Origami Risk’s Allocations solution, teams can select cost elements, specify calculated values, and build weighted formulas based on exposure ratio and loss experience. Custom formulas can draw on other data connected in the platform, so a chargeback program can grow as the business changes. Business unit risk management works best when unit leaders can see their charge, understand what drives it, and act on it. Each cycle of connected records makes the next charge easier to defend and the next conversation about performance more productive. Learn how Origami Risk’s Allocations solution connects risk costs to the business units driving them.