How does a Premium Functionality Employer perform verification on an employer, project-based or site-based competency?

Currently the RIW System allows Premium Functionality Employer Admins to verify assigned employer based competencies.  From 16 September 2021, this functionality will be extended to Advanced Project Admins for project and site based competencies.

This article details how a Premium Functionality Employer can review submitted evidence for an employer-based, site-based or project-based competency and verify the award of the competency to a cardholder.   This can occur when the competency has been submitted to the Employer Admin or Advanced Project Admin whose organisation owns the competency.

Employer competencies can be set up in the RIW System as requiring evidence and/or verification (please refer to the RIW Knowledge Centre article How does a Premium Functionality Employer create or edit an employer competency? for more information.  

Verification can only occur by an Employer Admin or Advanced Project Admin who has been assigned this functionality by the RIW Service Desk.  Not all Employer Admins or Advanced Project Admins for the Contractor In Charge will have this functionality.  Please refer to the RIW Knowledge Centre Article How does a Premium Functionality Employer request verification functionality for employer based competencies?

This instruction applies to the following RIW System User Roles: 

  • Employer Admin (Premium Functionality Employer)
  • Employer Admin - No Payment (Premium Functionality Employer) 
  • Advanced Project Admin - (Contractor in Charge Premium Functionality Employer only)

Step 1: Log in to the RIW System

Go to and login using your credentials. 

Step 2: Competencies Pending Verification

To verify submitted competencies, click on the Competencies Pending Verification shortcut available on the Competencies tab.

Step 3: Pending Competencies to be Verified

On the Pending Competencies to be Verified screen, select Employer where a list of all outstanding verifications will display.

Step 4: Verify record

Find the relevant record to verify and select the eye icon in the Evidence column to view the submitted evidence. The View Evidence pop-up will appear, displaying all the evidence submitted for the competency.  Click on the View icon to view the evidence.

Companies should manage their own Business Rules which determines the evidence deemed acceptable to verify the competency.

Once satisfied that the evidence either meets or does not meet internal business rule requirements, close the pop up box by clicking on Close.

If a statutory declaration is present on a cardholders profile that details any name discrepancies, click on the eye icon in the statutory declaration column, and the document will load in a new window. Once satisfied that the statutory declaration is true and correct, close the window and proceed to verify or reject the competency.

Step 5: Verify competency

If the competency evidence is suitable to be verified, tick the Select checkbox next to the record to be verified and then choose Verify.

A pop-up box will appear advising that the competency has been verified. Click OK to confirm.

Step 6: Reject competency

If the competency evidence is not suitable to be verified, tick the Select checkbox next to the record to be rejected and then choose Reject.

A Rejection Reasons pop-up screen will appear.  Select the most relevant reason from the the drop down box as to why the competency is to be rejected.  If a standard reason does not meet requirements, the RIW System User can also select Other - See Notes to enter free text to alert the requester the reason the competency was rejected.  Once complete, click Select.

A further pop-up will appear confirming the competency has been rejected. Click OK to proceed.

For more information about competency rejections, please refer to the RIW Knowledge Centre article How does a company manage a rejected competency?

RIW Knowledge Centre Article Link:

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.