The RPA Governance Board is a strategic body responsible for the oversight, prioritization, and alignment of the automation program with business objectives. Its membership must include senior stakeholders with the authority to make decisions. The Head of RPA leads the program and is a core member. The CTO provides top-level technology strategy and ensures alignment with the enterprise IT landscape. IT or Application Owners are crucial as they are accountable for the systems the digital workforce will interact with, ensuring stability, security, and feasibility of the proposed automations.

D. Lead Developer: This is a technical delivery role focused on implementation. While their input may be required occasionally, they are not typically a standing member of the strategic governance board.

1. Blue Prism Robotic Operating Model (ROM®) v2 - Enterprise RPA Capability Framework: The ROM® documentation outlines the key roles and structures for a successful RPA implementation. The Governance and Pipeline function (Section 4.3) explicitly details the need for a board comprising senior business and IT stakeholders. This includes the Head of the RPA CoE (Head of RPA), senior IT leadership (like a CTO or equivalent), and owners of the business processes and underlying applications.

2. Blue Prism Robotic Operating Model (ROM®) v2 - Roles and Responsibilities: This document defines the responsibilities for various roles. The Head of RPA is defined as the leader of the CoE and a key figure in governance. The CTO's involvement is implied under senior IT sponsorship and strategic alignment. Application Owners are identified as key stakeholders for assessing the impact on their systems. The Lead Developer role is positioned within the delivery team, focused on technical design and development, not strategic governance.