Know which employees have signed your handbook.

Organizations use the terms differently. Here, both describe a person confirming a policy through a recorded sign-off. ClearPolicy collects a typed-name electronic signature tied to the document version, with signing details and request activity. The wording in your document determines what the employee is being asked to confirm.

No. Owners and administrators can send policies and track signatures directly in ClearPolicy. Add people individually or import names and email addresses from a CSV spreadsheet. You can keep using your existing tools for payroll and other employee tasks.

No. Employees open their personal request link, review the policy, and type their name to sign. The signing portal lets them return to pending requests and signed copies using their email address and a six-digit code, without account registration.

Automatic renewal dates are based on each person’s most recent completion, not a shared calendar date. If your organization runs a coordinated policy review, plan that rollout separately and send requests when ready. Turning on Auto-renew does not replace the first request to someone who has never signed.

A reminder follows up on an unfinished request using its existing link and document version. A renewal asks for a new signature after a previous completion becomes due. Smart Follow-up handles reminders; the document’s Renewal and Auto-renew settings control recurring requests.

Publishing a revision leaves an old pending request tied to its original version. Sending a replacement request for the same person and document cancels pending requests for older revisions. Employees then use the new request link or their signing portal. Earlier completed signatures remain in history.

For an online signature, you can download the signed document and a Certificate of Attestation—a record of who signed, when, and which version of the policy they signed. You can also review when the request was sent, delivered, viewed, and completed. Earlier signed records stay linked to their original policy version when you publish an update.

Electronic signatures are the default path in ClearPolicy — fast, trackable, and audit-ready. When someone cannot complete a request online (no email, preference, accessibility, or a wet-ink requirement), a team member can record paper on file: upload the signed paper copy on the pending request. That person counts as complete for that document version, and the uploaded file stays with the request so your compliance record stays in one place. Paper on file is not an ESIGN electronic signature and does not produce an attestation certificate. It is a real workflow for keeping a complete record when electronic is not possible.

Yes. For policy attestation workflows, ClearPolicy records the signer's intent, typed name, timestamp, IP address, browser details, electronic consent, and the exact document version completed — the core elements ESIGN and UETA require. Some documents may still require wet ink or notarization; you decide whether electronic attestation is appropriate. When needed, team members can record paper on file by uploading a signed paper copy so status and the file stay in ClearPolicy — separate from the electronic signature path.