Where should the records officer report in the org chart, and should records management sit under IT, legal, or compliance?

There is no single “correct” box on the org chart for the records officer, but there is a clear principle: the role needs enough authority and independence to set policy across the whole organization, not just one department. Where it formally sits matters less than whether it can reach every business unit and command the support of senior leadership.

What the records officer actually needs

A records officer (sometimes called a records manager or records and information management lead) is accountable for the program that governs records throughout their lifecycle: creation, classification, retention, access, and disposition. To do that effectively, the role generally needs:

• A direct or short reporting line to senior management, so policy carries organizational weight.
• Visibility across all functions, since records are created everywhere, not in one silo.
• Independence from the systems and litigation it oversees, to avoid conflicts of interest.

Leading practice frameworks treat recordkeeping as an enterprise governance responsibility supported by top management, rather than a purely operational or technical function.

IT, legal, or compliance?

Each common placement has trade-offs:

• IT brings systems, storage, and digitization capability, but tends to focus on technology and uptime rather than retention rules, legal obligations, or the business value of records. Reporting solely to IT risks treating records as data to store, not obligations to manage.
• Legal aligns well with retention, litigation holds, and discovery, and gives the program authority. The risk is that day-to-day operational recordkeeping becomes a lower priority behind active legal matters.
• Compliance/risk is often a strong fit, because the program is fundamentally about meeting legal, regulatory, and accountability requirements. It also pairs naturally with privacy and information governance.

In practice, many organizations place records management under compliance, legal, or a dedicated information governance office, with a dotted line to IT for systems support. In U.S. federal agencies, an agency records officer is a designated role with defined responsibilities, typically positioned to coordinate enterprise-wide and work directly with the National Archives.

The practical answer

Pick the home that gives the role the broadest reach and the strongest mandate, then build cross-functional partnerships with the other two. The reporting line should signal that records management is an organization-wide governance function, not the side duty of one department.

For more foundational guidance, see the fundamentals topic hub.