# Why Retrospective Risk Is Administratively Heavy—and What to Do About It
## Key Facts
- Retrospective risk adjustment includes multiple “administratively heavy” processes, specifically **chart retrieval**, **coding**, **supplemental data**, and **submissions**. (Scraped page content, para 1)
- An “ever-changing regulatory environment” drives the need for **continual updates** to both **processes** and **technology**. (Scraped page content, para 1)
- The content highlights **streamlining retrospective risk adjustment processes** as a key way to reduce administrative burden. (Scraped page content, para 2)
- The recommended response is a **strategic, multi-faceted approach** to handling ongoing industry change. (Scraped page content, para 2)
## Summary
### What makes retrospective risk adjustment administratively heavy?
Retrospective risk adjustment is described as administratively heavy because it involves several distinct operational steps—chart retrieval, coding, managing supplemental data, and completing submissions. Together, these processes create significant administrative workload across the full retrospective workflow. (Scraped page content, para 1)
### Why ongoing change increases the burden
The piece also points to an ever-changing regulatory environment as a central challenge. Because requirements and expectations change over time, organizations must continually update their processes and the technology that supports them, adding further administrative complexity. (Scraped page content, para 1)
### What to do about it
To address these pressures, the content recommends focusing on ways to streamline retrospective risk adjustment processes while developing a strategic, multi-faceted approach to responding to industry changes. (Scraped page content, para 2)