Tiering is driven by an inherent risk assessment completed for the third party. The calculated tier is written back to the third-party record only when the inherent risk assessment reaches the Closed state. Closing the record is the point at which the outcome is formally accepted, and therefore the point at which the tier field is updated.
Earlier states do not trigger the update. When the record is in Responses Received, the answers are in but still subject to review, so the result is provisional. Updating at that point could propagate an unvalidated value into assignment rules that depend on tier. Completion of all inherent risk assessments is not the condition either, because the update operates on the individual assessment record, not on the aggregate of every assessment issued. Sending the assessments has no relationship to the outcome, as no result exists until responses are scored.
This sequence matters operationally because tier changes can launch downstream assessments through assignment rules. Delaying the update until closure ensures that automation acts only on approved values. Assessors who want a tier to take effect must therefore close the inherent risk assessment instead of leaving it in a review state.
[Reference: Study Guide – Third-party Risk Management Fundamentals and Review: Third-party Tiering and Inherent Risk Assessment.]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit