When organizations within your Data Collector have completed their requirement package/s it is time to start to review the results. To see what has happened in your Data Collector, the event log found in the Statistics sidebar can be a good place to start to find out which organizations that have finished their requirement package/s.

When reviewing an individual requirement package, the first thing you want to do is to calculate its fulfillment. You can always calculate the fulfillment of a requirement package by opening the requirement package from the Data Collector Overview by clicking it, and hit the Calculate fulfillment button to the right:

If all the individual requirements are met it will get the status Fulfilled. 

If you want to review organizations based on the completion status on their requirement package/s, you can filter by Status in the Data Collector Overview.

By filtering on the status Fulfills you will find all organizations that have one or more fulfilled requirement package/s.

In the Data Collector Overview the fulfilled requirement package/s will be shown in green text sided with a checkmark icon:

Any requirement package/s that have had their due date passed will be assigned the status Require action. This status indicates that no more reminders will be automatically sent to the organization why the next step is to contact the organization and see why they haven't responded to the information request. 

Requirement package/s that require action will be in orange text in the Data Collector Overview and sided by a warning triangel icon:

As the organization asking for information you always have the choice to make exceptions to answers that doesn't meet the predefined individual requirements you have set up for your requirement package/s. To set an exception, you first need to open the requirement package in which you want to make the exception. To open the requirement package, simply click on it in the Data Collector Overview. 

For all objects that do not meet your requirements, you will see a button called Set exception. Click the button and choose the option that meets the requirement criteria and hit Save. You can also leave a comment on why you choose to make this exception.

When you have set the exception you will be able to see both the answer from the recipient and the exception that you have made.

Requirement package/s that have one or more exceptions will be marked with an exclamation mark:

Any requirement package/s that contain objects that contain the individual requirement Manual Assessment will be assigned the status Assessment needed. This means that you have to manually assess the answer/s in the requirement package/s in order for them to be fulfilled. Requirement package/s that require manual assessment is indicated by a question mark in the Data Collector Overview.

To perform a manual assessment, you first need to open the requirement package that you want to assess. To open the requirement package, simply click on it in the Data Collector Overview.

For all objects that needs to be manually assessed, you will see a button called Set fulfillment. Click the button and choose what fulfillment status that should be assigned to the object, and hit Save.

If the requirement package have to be signed by the recipient before submitting the answers, you will find a digital signature along with the answers when reviewing a requirement package. The digital signature will be stored as a pdf-file and can be found if you open the requirement package from the Data Collector Overview, and look to the right beneath Previously signed documents:

From here you can review and download the digital signature.