A requirement document usually includes the following sections:

****

1. Stakeholder list with their positions, contacts and responsibility areas

2. Glossary (highly recommended)

3. Project scope, process definition (a project can consist of more than one process)

4. End user roles

5. Source Applications – applications or systems used to perform sub-processes or activities of the process

6. AS IS Process Flowchart, which outlines the sequence of steps, the rules and exception handling of manual process.

7. AS IS metric values (optional)

8. TO BE Process Flowchart, which envisioned process after complete or partial RPA-automation

9. TO BE (target) metric values (recommended)

10. Screenshots, web links and other descriptions of GUI & Web used in the process

11. File formats, data formats, API used in the process

12. Requirements for specific algorithms and calculations (if relevant)

Requirement document must be signed-off by your internal customer or your client.

According to internal guidelines the requirement document can be a part or an appendix of a change request or a contract.