Documentation formats allows the project team to define "standards" or format(s) for their documentation effort. You can build out a series of formats that will contain a specific list of documents that you can attribute to a specific entity (i.e. organization, process, project and event, IT application, or custom entity). Upon selecting a format, the lists of expected documents are created as placeholders within the selected entity.
You can control the formats, their name, description and how many you'd like to employ. Typically, you would expect a few formats (1-3) for both organizational unit-level and process-level documentation, totaling 3 to 5 formats. The distinction between formats will be determined by the team and driven by the level of depth required. For example, "high-risk" processes may require one standard of documentation while medium priority processes may require a different set of documentation.
Below is an example format for a high criticality process. Note the category, type as well as the name of the required documents is listed.
The table below illustrates some sample formats. Each client will create their own formats and determine the number of required documents included in each format.
Name |
Purpose |
Number of documents |
Organization - Entity Level |
Documents required at the entity level to support/articulate control framework |
25+ documents |
Process - High Criticality |
Documentation template for high criticality processes |
1 to 5 documents |
Process - Medium Criticality |
Documentation template for medium criticality processes |
1 to 3 documents |
Note: Protiviti's Governance Portal does not limit users to a specific number of document formats. The number of documents listed above does not represent the maximum number of documents you can house within the documentation areas of the Governance Portal.