UiPath Analyst Needed to Document Large Legacy UiPath Project — No Development Required

Job Description: We are looking for an experienced UiPath analyst / RPA documentation specialist to review a large, old, and lengthy UiPath automation project and produce detailed documentation explaining exactly how it works. This is a documentation-only project. No development, fixes, refactoring, bot changes, or production support are required. The goal is to carefully step through the existing UiPath project and document the logic, workflows, subworkflows, file handling, workbook manipulation, DataTable operations, and column-level transformations. The most important outcome is to understand exactly how the automation manipulates source and target workbooks/files. This will require opening the relevant source workbooks, target workbooks, templates, intermediate files, and output files, then tracing what the UiPath workflows are doing to each file, sheet, row, and column. We need documentation that is detailed enough that another UiPath developer, analyst, or business user could understand the automation without needing to reverse-engineer it again. Main Outcome: The main outcome of this project is to document exactly how each nested file manipulation occurs throughout the UiPath process. This includes: - Which source files are opened - Which target files are created or updated - Which templates or intermediate files are used - Which workflows and subworkflows handle each file - Which sheets, tables, ranges, rows, and columns are read or updated - How data moves from source workbooks to target workbooks - What transformations occur along the way - What columns are copied, created, renamed, updated, removed, filtered, calculated, or written - What DataTables are created and how they are manipulated - What the final output files contain The documentation should explain the existing automation as accurately as possible. Scope of Work: The selected freelancer will review the UiPath project files and document: - The overall purpose of the automation - The main process flow from start to finish - The main workflow and all invoked subworkflows - Any nested workflows where file manipulation occurs - What each relevant .xaml file does - Inputs, outputs, variables, and arguments - Excel files, CSV files, templates, intermediate files, and output files used - Source workbook to target workbook data movement - Sheet-level and column-level handling - DataTable creation, filtering, merging, updating, and writing - Excel activities, workbook activities, read range/write range activities, append range activities, filters, formulas, and lookups - Any calculations, business rules, conditions, joins, or transformations - File paths, folder structures, file naming conventions, save locations, and archive logic Key Requirement: Workbook and File Manipulation Mapping The most important part of this project is documenting the workbook and file manipulation logic. The freelancer will need to open the actual source and target workbooks/files and compare them against the UiPath workflows to trace exactly what is happening. For each relevant workbook or file, we need to know: - Where the file comes from - Whether it is a source, target, template, temporary file, export, or final output - Which workflow opens, reads, creates, modifies, saves, or moves the file - Which sheets are used - Which columns are read - Which columns are modified - Which columns are created - Which columns are deleted or ignored - Which rows are filtered - Which lookups, joins, formulas, calculations, or conditions are applied - Where the data is written - What the output file contains after processing - Any assumptions the automation makes about sheet names, column names, column order, formulas, hidden sheets, formatting, or file structure Expected Deliverables: The final documentation should include the following: 1. High-Level Process Overview A plain-English explanation of what the automation does from start to finish. 2. Workflow and Subworkflow Map A breakdown of the main UiPath workflow and all invoked .xaml files, including nested subworkflows. For each important workflow, document: - Purpose - Inputs - Outputs - Arguments - Variables - Key activities - Business rules - Dependencies - Exception handling - File or workbook operations performed 3. File Manipulation Map A detailed table or document showing how each file is used. For each file/workbook, document: - File name or file type - Source, target, template, temporary file, export, or output - Which workflow or subworkflow uses it - Purpose of the file - Sheets used - Columns used - Data read from the file - Data written to the file - Transformations applied - Output result - Risks, assumptions, or unknowns 4. Column-Level Transformation Documentation A column-by-column explanation of how data moves from source files to target files. This should include: - Source columns - Destination columns - Columns created - Columns updated - Columns removed - Columns renamed - Columns ignored - Filters applied - Calculations performed - Lookup logic - Join/merge logic - Formula logic - Any hardcoded values or conditions 5. Data Flow Documentation A clear explanation of how data moves through the automation, including: - Source workbooks - Target workbooks - Intermediate files - Templates - DataTables - Queues, if applicable - Folders - Output files This can be provided as a table, flow diagram, written explanation, or combination of these. 6. Dependency and Configuration List Document any identifiable dependencies, including: - UiPath packages - Orchestrator assets - Queues - Credentials - Config files - Folder paths - File paths - External applications - Websites - APIs - Shared drives - Templates - Naming conventions What Is Not Included: This is not a development project. The freelancer is not expected to: - Modify the UiPath project - Fix bugs - Refactor workflows - Improve selectors - Rebuild the bot - Create new automation - Run the bot in production - Provide production support - Guarantee that the bot works - Make business decisions about how the process should work The goal is simply to understand and document the existing automation. Ideal Candidate: The ideal candidate has strong experience with: - UiPath Studio - Reading and understanding legacy UiPath projects - Reverse-engineering undocumented automations - Nested workflows and invoked .xaml files - Excel automation in UiPath - Workbook and DataTable manipulation - Source-to-target file mapping - Column-level transformation analysis - Variables, arguments, assets, queues, and config files - Technical documentation - Process documentation You should be detail-oriented and comfortable patiently stepping through a large project to trace exactly what is happening. Important Notes: This project may take a few days depending on the complexity of the UiPath project. The documentation does not need to be overly polished or consulting-style, but it must be accurate, structured, and useful. The main priority is detail and correctness, especially around workbook/file manipulation and column-level data movement. Application Instructions: When applying, please include: 1. Your UiPath experience. 2. Examples of similar documentation, reverse-engineering, or legacy automation review work. 3. Your experience with Excel/DataTable manipulation in UiPath. 4. How you would approach documenting nested workbook/file manipulation. 5. Confirmation that you understand this is documentation only. 7. Your availability over the next few days. Please include the phrase “UiPath documentation only” in your proposal so I know you have read the full job description.