--- title: Estimator Reports slug: blueprint/estimator-reports docTags: yO7XZ9PJxDCKZ-Mf4TSYB createdAt: 2026-04-17T18:28:53.985Z --- :::CtaButton{label="๐ŸŸข Migrator" openInNewTab="false"} ::: The Estimator provides four report views accessible from the center dropdown within the Estimator Dashboard. All exports trigger a Job โ€” navigate to Jobs and click **Download** (:inlineImage[]{src="https://api.archbee.com/api/optimize/HRPaq4oJ2h9pHAfcjJGa6/MtvNZmEX21pPFD8xlaFyD_screenshot-2024-10-14-141050.png" alt caption width="18" height="17"}) to retrieve the file. *** # Estimator Report Orders all Call Trees by size and complexity, largest first. Use this report to understand migration effort per Call Tree and compare Blueprint-assisted vs. manual migration timelines. ## Exporting - **Export Current View to Excel** โ€” exports two sheets: the dashboard table as displayed, and adjustable metrics at time of export - **Export Consolidated TODOs and Compiler Errors to Excel** โ€” exports three sheets: TODOs grouped by type (parameters removed), Compiler Errors grouped by type (parameters removed), and metrics at time of export - **Export Estimator Template to Excel** โ€” exports a comprehensive migration planning workbook with adjustable productivity metrics, contingency factors, and bot complexity classifications; white-background cells are editable ## Table Columns - **Rank** โ€” Blueprint's ordering of all Call Trees by size and complexity; Rank 1 is the largest and most complex **Metrics** - **Call Tree** โ€” name of the root (Main) process - **Hierarchy** โ€” the folder path of the Call Tree - **Estimated Completion Effort (hrs)** โ€” the effort to bring Blueprint's migrated PAD code to a production-ready state - **Blueprint effort saved (hrs)** โ€” the amount of effort, in hours, Blueprint saves compared to doing the migration manually - **Manual Rewrite effort (hrs) **โ€” the effort to rewrite the selected scope by hand *** # Advanced Estimator Report Orders all Call Trees by size and complexity, largest first. Use this report to understand migration effort per Call Tree and compare Blueprint-assisted vs. manual migration timelines. ## Exporting - **Export Current View to Excel** โ€” exports two sheets: the dashboard table as displayed, and adjustable metrics at time of export - **Export Consolidated TODOs and Compiler Errors to Excel** โ€” exports three sheets: TODOs grouped by type (parameters removed), Compiler Errors grouped by type (parameters removed), and metrics at time of export - **Export Estimator Template to Excel** โ€” exports a comprehensive migration planning workbook with adjustable productivity metrics, contingency factors, and bot complexity classifications; white-background cells are editable ## Table Columns - **Rank** โ€” Blueprint's ordering of all Call Trees by size and complexity; Rank 1 is the largest and most complex **Metrics** - **Call Tree** โ€” name of the root (Main) process - **Hierarchy** โ€” the folder path of the Call Tree - **Completely Migrated Actions** โ€” actions that migrated to PAD without a compiler error - **Actions with Compiler Errors** โ€” actions that migrated but contain a compiler error requiring manual fix - **Compiler Errors** โ€” total compiler error count; a single action can contain multiple errors - **TODOs** โ€” TODO comments requiring review, completion, or refactoring - **Selectors **โ€” total selector count - **Effort Blueprint Saves (Est.)** โ€” estimated hours saved by using Blueprint: *(Completely Migrated Actions รท RPA Developer Productivity) + (Compiler Errors รท Compiler Error Fix Rate)* **Effort to Complete Code with Blueprint** - **TODO Fix Effort (Hrs)** โ€” estimated hours to resolve TODOs - **Compiler Error Fix Effort (Hrs) **โ€” estimated hours to resolve compiler errors - **Selector Fix Effort (Hrs) **โ€” estimated hours to respy non-functional selectors - **Total Effort (Est.)** โ€” sum of TODO Fix Effort and Compiler Error Fix Effort **Manual Migration** - **Total Manual Effort (Est.)** โ€” estimated hours to manually rewrite the Call Tree without Blueprint - **View Call Tree** โ€” click to generate a visual diagram of the Call Tree *** # Selector Report The rows in this report show screens and elements being accessed by the automation, and the PAD selectors that will be used to access them. Notes: - For type UI, the row could represent either an element selector, or a window selector (when element is empty). For type Web, the row is always an element selector. - There might be multiple selectors generated for an element. Clicking the "info" icon that appears in the Selector column will show all generated selectors. :::hint{type="info"} โ“˜ Click **Combine Duplicate Selectors** to merge duplicate selectors that interact with the same web or UI application, even when the page or window name differs. ::: ## Exporting - **Export Current View to Excel** โ€” exports the table as displayed ## Table Columns - **Type** โ€” either UI or Web interaction - **Domain / UI Application** โ€” web domain or name of the UI application - **Web Page / Window Name** โ€” full URL or window name of the UI application - **Element** โ€” name of the element - **Selector** โ€” the selector that will be generated in PAD. click the 'info' icon to view more than one selector - **References** โ€” number of times the element is referenced across different actions *** # Maintainability Orders all Call Trees by maintainability score, least maintainable first. Use this report to identify automations that may require additional cleanup work after migration. ## Exporting - **Export Current View to Excel** โ€” exports the table as displayed plus two additional columns: Process ID and Maintainability Score ## Table Columns - **Maintainability Rank** โ€” ordering of all Call Trees from least to most maintainable; Rank 1 is the least maintainable - **Call Tree** โ€” name of the root (Main) process - **Target Actions** โ€” number of PAD actions in the migrated output, including comments and regions - **Target Actions / Source Actions** โ€” ratio of PAD output lines to source actions in Blueprint - **# Target Regions** โ€” count of regions used in the PAD output - **# User Comments** โ€” count of comments in the export - **# Target Subflows** โ€” count of subflows created in the PAD output - **# Unmapped Reuse Opportunities** โ€” count of reuse opportunities not yet implemented - **# Complex Nested Ifs** โ€” count of if statements nested four levels deep or more - **# Complex Expressions** โ€” count of complex expressions in the export *** # Failed Exports Lists all Call Trees that failed to export during Estimator calculation. Processes in this report are excluded from effort estimates. ## Exporting - **Export Current View to Excel** โ€” exports the table as displayed ## Table Columns - **Process ID** โ€” Blueprint ID of the Main process that failed to export - **Process Name** โ€” name of the Main process that failed to export