Use the current Developer page over an old AD01 PDF
Historical Blue Prism Developer materials identify AD01, but current University instructions govern the examination now offered. At this review, the page lists 60 questions, 75 minutes and a scaled passing score of 600, with no formal prerequisite and a recommendation for learning-plan completion plus practical experience. It also states a three-year certification validity period from 1 July 2026. Older documents show different timing and percentage-style assumptions, so do not transfer those details to a new booking. Follow the live University and authorised registration route.
Select an automation with a clear work item
Use a fictional invoice-entry process with a small queue of fabricated invoices. Define the input fields, validation rules, target application state and meaning of completion. Separate the reusable interaction with the application from the business process that decides what to do next. Write a manual walkthrough first so an incorrect automation can be compared with an understood process. A useful beginner project is small enough to inspect completely and rich enough to expose exceptions.
Build objects that report useful outcomes
Model the target application through supported techniques and keep actions focused. Test a valid navigation, an unavailable screen and an unexpected value. Explain which outputs indicate a successful business action and which indicate a recoverable technical problem. Avoid hard-coded assumptions that silently misdirect data when a screen changes. Keep credentials in approved management mechanisms and use a test application or authorised learning environment. A public portfolio should never include real financial records, passwords or customer screenshots.
Make retries safe
Suppose the application accepts an invoice but the automation loses the confirmation. A blind retry could enter it twice. Define a unique work-item reference and a verification step that determines whether processing already occurred. Distinguish business exceptions, such as an invalid supplier, from system exceptions, such as an unavailable application. Decide when the queue item should stop and require review. The objective is controlled recovery that preserves correct business records, not a robot that keeps clicking until a screen changes.
Observe and operate the process
Add logging that helps an authorised support person identify the failed stage without exposing unnecessary sensitive data. Rehearse restart, retry and manual resolution for a single item. Define who owns unattended execution and who responds when the application is unavailable. Record the tested inputs, expected outcomes and actual results. A successful unattended run is useful evidence, but a diagnosed failure and a safe recovery demonstrate stronger operational judgement. Include assumptions about application version and environment in the runbook.
Prepare with the official learning and assessment route
Map object development, process development, implementation and best practice to exercises in the project. Complete the official learning plan and use the University assessment and practice test as diagnostic tools. Explain syntax and state transitions rather than memorising screenshots. A scaled 600 is not simply 75 percent of questions: the issuer explicitly explains scaled scoring. Check current language, price, booking, retake and renewal terms before paying. Certification supports an automation-development story; it does not establish experience delivering every enterprise RPA programme. Present the process design, queue behaviour, exception logic and recovery evidence alongside the exact credential.
Official references
Certification requirements and programme terms can change. Use the issuer’s current page and your account to confirm details before applying or paying.