Once a process has been identified as a good candidate to be automated, it is time to
This documentation will then serve as the basis for implementing the software robot that will take over and handle the process in the future.
During this requirements gathering phase, the business unit needs to get familiar with the current process and the business domain in which it is executed. This often means sitting next to the user when the process is run, asking all relevant questions, and exploring all possible cases.
The result of this analysis phase is collected in a document and video called Process definition document (PDD), which is then shared with all the relevant people involved, approved, and signed off.
We are happy to share our process definition document (PDD) template for you to use freely in your next Process Automation.
The process definition document template includes indications about how you should fill the various sections. Remember to delete the explanation text.
What should a process definition document achieve? A good PDD document should provide clear answers to the following questions:
(Depending on your organization size, not all the sections will be needed.)
Here is an example of a completed Process Definition Document. This example can you help you think about how to create your own PDD.
Good luck!
Rich Handler
CEO, AR Proactive