How recipients complete a request
The person opens their personal email link, reads the document, types their name, and confirms the electronic signature. They do not need a team member account. Historical records may show an acknowledgment completed without a typed name. Those records remain in history. There is no separate acknowledgment-only mode for new requests. See sign a document for the person’s steps.How requests are sent
A request links one person to one document revision and keeps their name and email as they were when it was sent. Emails and reminders use those saved details. Changing a person’s profile does not update existing requests. Correct the profile and send a replacement request when the address or name on an open request needs to change. Personal links grant access to the request. People should use their own link and not forward it for someone else to sign.The recipient experience
The signing page shows the document, your optional note, and a deadline when request expiry is enabled. After an online completion, it offers a receipt. Other pending requests may appear so the person can continue signing.Finding requests without the email link
People can enter their email and a one-time code in the signing portal. It shows their pending requests, signed copies, and documents made available to read through groups.What gets recorded
An online completion records:- The completion date and time.
- The typed signature name for new requests.
- The IP address and browser information.
- The specific document revision and its hash, a fingerprint used to identify the content.
Request lifecycle
A request can be sent, viewed, completed, canceled, or expired. Email delivery events show whether a message was delivered, bounced, failed, or marked as spam. Sending and delivery are separate events; a sent request is not proof that the email reached an inbox. Use Requests for request status and completion statuses for whether a person’s documents are current.Superseded requests
Publishing a new revision does not change open requests. They still refer to the version originally sent. When you send a new request for the same person and document, pending requests for older revisions are canceled. The activity explains that they were superseded by a newer revision. Completed, expired, and previously canceled requests are preserved. See update a document.Sending reminders
A reminder uses the same request link, version, and deadline. It does not create a new request. See send reminders.Paper on file
A team member can complete a pending request by recording a paper signature and uploading the signed paper copy. This records paper evidence; it is not an electronic signature captured in ClearPolicy.
Both count as completion for the relevant revision. See record a paper signature.