The "Build" stage of the Blue Prism Delivery Methodology is the phase where the actual development and configuration of the automation solution take place. Following the blueprint provided by the Solution Design Document (SDD), developers use the Blue Prism interactive client (Studio) to create the necessary Process and Visual Business Object diagrams. This stage involves writing the logic, configuring application interactions, and performing initial developer-led unit testing to ensure individual components function as designed. The primary output of this stage is the initial version of the automated process, which is then passed to the formal Test stage.

A. This describes the 'Define' stage, where the as-is process is analyzed and documented in the Process Definition Document (PDD) before any design or build work begins.

B. This describes the 'Design' stage, where the Solution Design Document (SDD) is created to detail the technical approach for how the process will be automated.

D. This describes the final part of the 'Test' stage, specifically User Acceptance Testing (UAT), which validates the solution's readiness for production deployment.

1. Blue Prism Portal Documentation, Robotic Operating Model (ROM) v2, The Delivery Lifecycle: The official methodology outlines the "Build" phase as the third stage. It is explicitly defined as: "The automated solution is built in the Blue Prism development environment, based on the PDD and SDD. The build is carried out by a developer with Blue Prism accreditation." This directly confirms that "Build" is the development of the process.

2. Blue Prism - Delivery Roadmap (within ROM documentation): This resource details the key inputs, activities, and outputs for each stage. For the "Build" stage (often labeled as "Configure & Unit Test"), the key activity is listed as "Configure the solution," reinforcing that this is the development phase. The input is the SDD (from the Design stage), and the output is the configured solution ready for the Test stage.