Which of the following would not typically be a stakeholder in an RPA Governance Board?

An RPA Governance Board (often part of a Centre of Excellence or a Design Authority) is primarily focused on the strategic, technical, and operational oversight of the automation program. Its core members typically represent the key functions required for successful delivery. This includes Business Representatives who own the processes and pipeline, IT Representatives who manage infrastructure and security, and the Head of RPA who leads the program. While Human Resources (HR) is a vital stakeholder in the broader change management and workforce transformation aspects of automation, they are not typically a standing member of the core governance board that makes decisions on technical standards, architecture, and pipeline prioritization.

A. IT Representatives are essential for ensuring automations comply with security, infrastructure, and architectural standards, making them a mandatory member.

C. Business Representatives are crucial as they own the processes being automated, provide subject matter expertise, and help prioritize the automation pipeline.

D. The Head of RPA is the leader of the automation program and is central to the governance function, often chairing the board or committee.

1. Blue Prism, "Robotic Operating Model (ROM) - Overview". The official Blue Prism ROM documentation consistently describes the core governance structure as a partnership between the Business, IT, and the RPA Centre of Excellence (CoE). The Design Authority, a key governance body, is composed of technical and business leads. HR's involvement is framed within the "People" and "Change Management" components of the operating model, which is adjacent to, but distinct from, the core governance board. (Accessed via Blue Prism University/Portal).

2. Blue Prism University, "ARA02 - Blue Prism Certified Developer" Courseware. The module on the Robotic Operating Model (ROM) details the composition of governance forums like the Design Authority. It specifies that typical attendees include the Head of RPA, Enterprise Architect (IT), IT Security, and Business Process Owners. This composition underscores the focus on technical, security, and business process alignment, distinguishing it from workforce management functions handled by HR.