Request and Share Details

The Request/Share Details provide additional information that enables the user to track to the progress and history of requests and shares. 

Request/Share Details are available from any row in the Request/Shares tab on both the Third Party Portfolio and the Customer Portfolio. 

Table of Contents

• Common Data Across Request/Shares
• Steps
• Data Recency Scenarios

Common Data Across Request/Shares

Request/Share Type	The type of request or share. Possible values are Assessment Request, Validation Request, Document Request, Assessment Share, Validation Share, or Document Share
Company Name	The name of the third party in the Third Party Portfolio or the name of the Customer in the Customer Portfolio
Current Status	The current status of the request or share. Possible values are Pending, Approved, Denied, Delivered, Revoked, or Archived
Current Status Date	The date the current status was set
Requested By or Shared By	User who initiated the request or share
Requested Date or Shared Date	The date the request or share was created
Framework	The name of the framework requested or shared. The framework only be displayed on Assessment Request or Assessment Shares
Data Recency	A timeframe that indicates how current the attested date must be to meet the customer requirements and fulfill a data request. Possible Values are Up to 12 Months, Up to 24 Months, up to 36 Months, or No policy requirements. Data recency will only be displayed on Assessment Request and Validation Request.
Recipients	The individuals who were notified regarding the request or share

 

Steps

The steps a request or share must progress through, who has ownership of each step (Third Party, Customer, or ProcessUnity), and the date when action was taken on the step. 

Once a request or share is ‘Delivered’, the step details will no longer be updated. Each step will reflect data that led to the delivery of the request or share, not any changes that happened after delivery. 

Progress Indicator 

Indicates that a step is pending. If icon and step name are disabled, it indicates that a prior step must be completed before the user can complete this step. Ex: a third party must complete the questionnaire before they can submit the questionnaire. 

Indicates that a step is completed

Steps per Request or Share Type

• Assessment Request/Assessment Share
  • Respond to Request/Respond to Share
    • Completed when the request or share has been either Approved or Denied
    • Once completed, shows either ‘Approved’ or ‘Denied’, the date the action was taken, and the user who took the action
  • Complete Questionnaire
    • Completed when all the controls in the framework associated with the request or share have been completed
    • Shows the progress of completed controls out of the total number of requested controls, the last updated date, and the last updated user for any controls in the requested framework
  • Submit Questionnaire
    • Completed when the Complete Questionnaire step is completed and the questionnaire has been submitted (attested)
    • Once completed, shows the date the questionnaire was submitted (attested) as well as the user who submitted it
• Validation Request
  • Respond to Request
    • Completed when the request has been either Approved or Denied
    • Once completed, shows either ‘Approved’ or ‘Denied’, the date the action was taken, and the user who took action
  • Complete Critical Controls
    • Completed when all critical controls are completed
    • Shows the progress of completed critical controls out of total critical controls
  • Submit for Validation
    • Completed when critical controls have been submitted for validation
    • Once completed, shows the date the critical controls were submitted for validation and the user who submitted them
  • Validation Round 1
    • Completed when the first round of validation is completed
    • Once the validation round is in progress, displays the date of the last assessor update
    • Once the round is complete, displays the date round 1 was completed
  • Provide Additional Evidence and Resubmit for Validation
    • Completed when critical controls have been resubmitted for validation after round 1
    • Once completed, shows the date that critical controls were resubmitted for validation and the user who resubmitted them
    • It is possible to skip this step entirely if validation is finalized after the first round
  • Validation Round 2
    • Completed when the second round of validation is completed
    • Once the validation round is in progress, displays the date of the last assessor update
    • Once the round is complete, displays the date round 1 was completed
    • It is possible to skip this step entirely if validation is finalized after the first round
  • Finalize Validation
    • Completed when validation assessor attestation is complete
    • Once completed, shows the date the validation was attested by an assessor
• Validation Share
  • Respond to Share
    • Completed when the share has been either Approved or Denied
    • Once completed, shows either ‘Approved’ or ‘Denied’, the date the action was taken, and the user who took the action
• Document Request/Document Share
  • Respond to Request/Respond to Share
    • Completed when the request or share has been either Approved or Denied
    • Once completed, shows either ‘Approved’ or ‘Denied’, the date the action was taken, and the user who took the action
  • Upload Documents
    • Completed when any documents have been uploaded

 

Data Recency Scenarios

Data recency only applies to assessment and validation requests (it does NOT apply to sharing data or requesting document data). Based on the customer's data recency requirement, the business logic determines whether a request can be fulfilled based on the data's recency. 

Here are some examples of how data recency can affect the completion of a request: 

Example 1 – Assessment request last attestation date is outside of data recency and does not become ‘Delivered’ on approval 

1. Customer A submits an assessment request to Third Party B with a data recency value of ‘Up to 12 Months’ on January 1, 2025 

2. Third Party B approves the request and previously attested to the questionnaire on December 1, 2023 

3. The request cannot be completed by the previously attested questionnaire data because it was attested more than 12 months before the request was created.  

4. The steps in the request details will show the ‘Complete Questionnaire’ and ‘Submit Questionnaire’ steps as pending until Third Party B resubmits (re-attests) the questionnaire. 

5. The status of the request will remain ‘Approved’ until Third Party B resubmits the questionnaire (re-attests). Upon Third Party B resubmitting the questionnaire (re-attesting) the status of the request will become ‘Delivered’ 

Example 2 – Assessment request last attestation date is within data recency and becomes ‘Delivered’ on approval 

1. Company A submits an assessment request to Third Party B with a data recency value of ‘Up to 24 Months’ on January 1, 2025 

2. Third Party B approves the request and previously attested to the questionnaire on December 1, 2023 

3. Third Party B automatically fulfills the request with the previously attested questionnaire data because it was attested less than 24 months before the request was created. 

4. The steps in the request details will show the ‘Complete Questionnaire’ and ‘Submit Questionnaire’ steps as complete 

5. The status of the request automatically becomes ‘Delivered’ on approval 

Example 3 - Third party previously completed validation on October 1, 2024. Customer requests an assessment and validation on September 1, 2025, with 'Up to 12 Months' data receny requirement. Third party must complete validation again in order to fulfill. 

1. Company A submits an assessment + validation request to Third Party B with a data receny requirement of 'Up to 12 Months' on September 1, 2025
2. Third Party B must undergo a new validation cycle since their prior validation completion date is more than 10 months from current date in order to ensure 12 month freshness at time of delivery. (Prior validation completed October 1, 2024 ; Request placed 11 months after that date). 
3. Third Party B completes assessment and validation process. 
4. Third Party B approves customer A request for assessment data, approves request for validation data. Status of requests become marked as 'Delivered'. 
5. The steps in the request details for the assessment request and the validation request will be shown as complete.