How should an information governance committee be structured and which departments need a seat at the table?
An information governance (IG) committee gives an organization a single, cross-functional body to set policy, resolve competing demands on information, and hold the program accountable. Because information touches every department, governance fails when it is treated as a records-only or IT-only concern. The committee’s job is to balance value, risk, and cost across the full information lifecycle.
How to Structure the Committee
Effective committees usually operate on three layers:
- Executive sponsor. A senior leader (often a C-suite officer or general counsel) who provides authority, funding, and visibility. Without executive backing, IG decisions rarely stick.
- Steering committee. A cross-functional group of department representatives who set policy, approve retention schedules, prioritize initiatives, and adjudicate disputes. This is the core decision-making body.
- Working group(s). Practitioners who carry out projects, draft procedures, and report progress back to the steering committee.
Define a clear charter that states the committee’s mandate, decision rights, membership, meeting cadence, and how decisions are escalated and recorded. Document who owns each policy so accountability is explicit rather than assumed.
Who Needs a Seat
No single template fits every organization, but these functions almost always belong at the table:
- Records and information management — lifecycle, retention schedules, and program leadership.
- Legal / general counsel — regulatory compliance, litigation holds, and e-discovery obligations.
- IT / information security — systems, storage, access controls, and data protection.
- Privacy / compliance — handling of personal and sensitive data.
- Risk and audit — controls, monitoring, and assurance.
- Business units — the people who create and use the records day to day; their input keeps policies workable.
Depending on the organization, add finance, HR, procurement, or a digital preservation or archives function.
Making It Work
Treat IG as an ongoing program, not a one-time project. Meet on a regular cadence, set measurable objectives, and review policies as laws, technology, and business needs change. Aligning with a recognized framework such as ISO 15489 helps the committee speak a common language and benchmark its maturity.
For related guidance, see the information governance hub.
Sources & further reading
Authoritative government and non-profit references.
- ARMA International — ARMA International
- ISO 15489-1 Records management — ISO
How to cite this page
APA
RM University Editorial. (2026). How should an information governance committee be structured and which departments need a seat at the table?. Records Management University. https://www.recordsmgmt.org/questions/how-to-structure-an-information-governance-committee/
MLA
RM University Editorial. "How should an information governance committee be structured and which departments need a seat at the table?." Records Management University, 16 June 2026, www.recordsmgmt.org/questions/how-to-structure-an-information-governance-committee/.
Related questions
- Big-bucket vs item-level retention schedules: how do I choose between them?
- Can a company be penalized for keeping data too long under privacy laws even if nothing was breached?
- Can a US company store records in the EU, or do data localization and cross-border transfer rules block it?
- Can executives or board members be held personally liable for information governance failures?
- Can information governance help reduce cloud storage costs, and how?