Sometimes, a signature is required for compliance. eSignatures allow SwipeGuide users to confirm that a task has been completed, even when they aren’t logged into the platform.
In this first version, a biometric hand signature can be added to the end of an executed Checklist in the web-app to enhance compliance. This little feature is handy in situations when:
1. A user doesn't have a login.
Frontline workers use the platform without a personal SwipeGuide login (no e-mail/password or SSO). The eSignature confirms their identity when they’ve completed a task.
For example, a company is using SwipeGuide to train and onboard new warehouse employees. They use the fully accessible version of SwipeGuide, where content is available for anyone with the link.
That means that the new employees don’t need a personal login to the platform. With eSignatures, the company can track training completion by requiring employees to sign in order to confirm that they have been trained.
2. Added compliance.
A signature is sometimes needed for additional compliance purposes, even in situations when users are logged in to the platform and it’s easy to identify who performed a task.
Note ⚠️
The SwipeGuide eSignatures are NOT using a digital certificate from a trusted Certificate Authority (CA). This means that signing a checklist with a SwipeGuide eSignature does not officially confirm the signer’s identity from an official database.
The first version of eSignatures is available for all users of Checklists in the web-app (but it's not yet available in the frontline app).
➡️ Read more about SwipeGuide features that support compliance here.
