...
Paragraph number
Description; explain in more detail what this requirement entails.
Implementation date; when was this requirement effected
Last changed date; latest legislative amendment
Link to requirements
Claimants; notices from stakeholders
Current; tick if it is valid as of now, uncheck when the claim is no longer valid, do not delete this claim
Requirement groups
Most users end up with a large number of single detailed requirements. To make compliance assessments as easy as possible, create different relevant requirement groups and tag the relevant detailed requirements for each group. For each crequirement group, you must register title:
...
You can also add data such as:
Description
Responsible, to ensure who is responsible for updating this
Organization, shows where relevant
Process, will cause it to appear in the resource view
Position/role, will activate the filter on this field in the process map.
Register and edit detailed requirements
First, add all requirements in the system to the list of detailed requirements. Be sure to add where the requirements are coming from in the metadata. This way, when you view the detailed requirements elsewhere in the system, they will be grouped by source. Watch this video:
Register and edit requirement groups
Look over the list of requirements collected and try to group them into requirement groups based on topic. You will later perform compliance assessments per requirement group, so grouping similar requirements together will reduce repetition in your compliance statements (when you explain what processes, checklists, and other things are in place to ensure compliance with all requirements in that requirement group). Watch the following video for an explanation of how to do this: