Digital Signatures

Priority Bulletins

We introduced priority bulletins to allow managers to request an acknowledgement from their team members. What's more, we now require that your team members enter their secret PIN to acknowledge a bulletin. In accordance with the Electronic Transactions Act 1999, this is a legally binding electronic signature. 

Use of this feature should ideally be restricted to critical information for which you would usually require (back in the day) a hard copy signature from your team, when the information is communicated to them. Examples include: critical procedure updates, inductions, toolbox talks, pre-starts, blast zone clearances etc.

How it Works

To request an acknowledgement from your team, it's as easy as ensuring the 'Priority (response required)' checkbox is checked before sending your bulletin. See below for an example.

Once sent, the bulletin will appear on your team members mobile app with a large acknowledge button below. The bulletin will remain at the top of their newsfeed until the bulletin is acknowledged, upon which the bulletin enters the normal newsfeed flow and the button disappears. As we mentioned before the user will need to enter their secret PIN to complete the digital signature process.


The Signature

You're now wondering what happens with the record of the signature. The signature is a date/time stamp that is securely stored for the life of the bulletin (which is forever, unless you delete the bulletin). You can view this by clicking the 'View Stats' button for that particular bulletin. You can also download a CSV file with the records for that bulletin by clicking 'Download CSV'.

We hope this process will greatly reduce the time it takes for you to communicate important information in an effective way with your team.

Not satisfied with a signature? Why not send out a quiz that tests how much information was retained by your team. This is especially important for things like inductions. Check out our Polls, surveys and tests guide for more information.


Have more questions? Submit a request
Powered by Zendesk