Process Definition Document (PDD): Write One Without an RPA Tool
A process definition document records the steps, rules and exceptions a developer needs to automate a process. Build it from an agreed process map, with any RPA tool.
A process definition document records the steps, rules and exceptions a developer needs to automate a process. Build it from an agreed process map, with any RPA tool.
The short version
- Map the agreed manual process before writing any technical detail.
- Mark the line between what the bot does and what a person does.
- Give every exception route an owner, so the bot has somewhere to hand work back.
- Keep the chart as the reference after go-live, and version it when the rules change.
Continue with process documentation
- Automation Anywhere Process Discovery alternative
- UiPath alternative for process documentation
- Which RPA vendor documents your process? Compared
- RPA candidate assessment
- Process mapping without RPA
- Business analyst process documentation
- Process exception mapping template
- To-be process map template
- Version control for process documentation
Draw the automation boundary on the process map
Three stages from the manual task to a map that shows where the bot starts and stops. Open the example to adapt it to your own process.
Receive and classify the work
Start with “Work item received” and “Classify task and exception risk”. Classification is what lets you say later which items the automation may touch.
Split the manual and automated routes
After “Within automation scope?” one route runs “Perform documented manual task” and the other “Run approved automation in external system”. This split is the automation boundary the PDD describes.
Assign owners and exceptions
The decision “Output passes review?” returns failures to “Resolve exception manually”. Check that the reviewer and automation owner lanes hold those steps.
Write the PDD from a map that is already agreed
A process definition document (PDD) is the hand-off from the people who know a process to the people who will automate it. RPA vendors generate one from their discovery tools, but the content is not tied to a vendor: it is the trigger, the steps, the systems and inputs, the business rules, the exceptions and the expected outcome.
Most of that content is easiest to agree on a picture. When the analyst, the process owner and the developer look at the same map, a missing exception shows up as a branch with nowhere to go. Writing the map first also keeps the PDD short, because the document can refer to the chart for the flow and spend its words on rules and data.
Use the chart below to walk through the order of work. Start with the manual task, add the automation boundary, and finish with the exception owner. Then export or share the chart with the written PDD.
How it works
Map the current manual process
Draw the trigger, every step, each decision and its outcomes, and the person responsible. Include the exceptions people handle today.
Mark what is in scope for automation
Label the steps a bot would perform, the systems and inputs it needs, and the steps that stay manual.
Write the rules and data around the chart
Reference the chart for the flow. Use the written document for business rules, input and output fields, volumes and access.
Review and version the pair
Walk the chart with the process owner and the developer, record the agreed version and note the review date.
Try QueryChart free
Map, review and share the process your team needs to maintain.
Related guides
Sources
Frequently asked questions
Is a process definition document the same in every RPA tool?
The name and the template vary, and the content is similar: trigger, steps, systems, rules, exceptions and outcome. Check the template your automation team or vendor expects.
Can QueryChart generate a PDD?
No. QueryChart does not produce a bot-oriented PDD. It holds the agreed process map that a PDD refers to, and you write the rules and technical detail in your own document.
Who should approve the PDD content?
The process owner confirms the steps and rules; the developer confirms they can be built. Record both reviews against one version of the chart.