Certificate verification - validate units of competency
CompletedIt's awesome to see aXcelerate implemented the QR Code and public page for certificate verification yet current function only pulls the Qualification data not the units.
For example if students obtain 1 unit of competency out of a qualification they get a Statement of Attainment issued which lists the unit they received the training of. The current certificate verification function only verifies the certificate being true showing they have been award [Qualification] rather than that [Unit].
Image scan the QR code on a certificate and the page brings out all the unit of competency the student has achieved including dates. For RTOs who deliver short courses and issue Statement of Attainment to students who did not obtain the whole qualification (which happens often) this is really crucial in regards to validating certificates.
Please support me if you feel the same. Cheers.
-
Official comment
Hi Esther,
I know you're following the other post, but for full transparency and for others who may come across this post, below is what I have said in the other thread.
As a result of client feedback, our next release on the evening of November 18th will include the following improvements:
- Surname will now optional when validating a certificate. Only a certificate number/id is mandatory.
- We have added the type of award (Statement of Attainment or Qualification) to the validation page
- We have added the qualification code to the Award section when the award is a full qualification
- We will now list all units of competency achieved for both SoA and full qualifications.
Thanks again.
Cheers,
Rod.Comment actions -
Hi Rod, not sure which thread to put this concern on, but we had a client this week try to validate an SOA that was issued to a student.
The validation page presented every unit of competency, even the units the student had not successfully completed and were not listed on their certificate.
It also excluded a unit that was successfully completed but has since been de-activated in our system.
This is a huge issue for compliance.


Please sign in to leave a comment.
Comments
2 comments