SignWell

Test a completed document with the right names, dates, fields and signer order. A configured template or sent request does not prove that every recipient signed.

The right electronic-signature process depends on the document and jurisdiction. Confirm your organization’s identity, retention and legal requirements before relying on a production signing flow.

Before withdrawing a SignWell signing request, distinguish Cancel from Archive. SignWell says canceling a Sent or In Progress document ends recipient access and permanently deletes it from the sender's account; a completed document cannot be canceled. Archiving also ends recipient access, but the sender can unarchive it later. Check the document's status and retain any required records before using either action on a live agreement.

SignWell Bulk Sending's CSV export lists recipient, document and status fields, but the sender and CC recipients do not receive per-document viewed/completed alerts. After all recipients sign, only the Document Sender receives the completed-batch access link; CC recipients receive a notice without links or signed attachments. Test a small authorized batch and assign who retrieves signed PDFs and reconciles the status CSV before relying on it for records handoff.

Before using SignWell's Update & Resend on a partly signed document, check who has already signed: SignWell says those recipients must sign again. If the document is complete, SignWell says a copy is the only way to resend it; fields and entered information carry over, but recipient signatures and initials do not. Test both paths with a harmless sample and confirm who receives the new request before changing a live agreement.

Before using SignWell SMS for signing requests, confirm who records recipient consent: SignWell says SMS is off until a workspace administrator attests, and the sender chooses Email only, SMS only or both for each recipient. In the US and Canada, STOP opts a recipient out of all SignWell SMS across workspaces; the UK and Australia link has the same broad effect. Rehearse delivery choices and an email-only route with fictional recipients, and check consent and phone records before a live send.

Before sending a long-running SignWell request, check Document Link Preferences. SignWell says document links expire after 30 days by default; changing that setting affects future documents, not links already sent. A manual reminder can reactivate an expired document and reset its expiry. Rehearse the intended expiry and reminder path with a harmless sample, then assign who will follow up before promising a signing window to recipients.

When a signing request reaches the wrong person, check whether SignWell lets the recipient decline or reassign it. The sender can disable both options; if enabled, declining asks for a reason sent to the sender, while reassigning requires the new person's name and email and notifies that person to complete the document. Rehearse a fictional misrouted request with the intended sender settings, then confirm who reviews decline reasons and whether your signing policy permits recipient reassignment before relying on this handoff.

If your team connects SignWell to Google Drive, check both the file you import and the final PDF you expect back. SignWell imports a copy of a Drive file; later Drive edits do not update the signing document. With completed-document saving enabled, SignWell saves a signed PDF to Drive only after every required recipient finishes. It does not save voided, declined or expired documents, or ones canceled or deleted before completion. The completed PDF remains in SignWell. Check the expected Drive folder and track exceptions separately before treating it as a complete records archive.

For a reusable SignWell Template Link on a website or in email, check who can start and complete each generated document. The vendor says the link gives each visitor a copy to complete and can be disabled to stop access through it. Email verification is required when that setting is on or the template has a sending order; with verification off, a recipient can go straight to signing, but a multi-recipient template needs preassigned contacts. Use Default Signers if an internal person must join every copy. Confirm your plan's access, then rehearse verification and link disabling with fictional recipients before publishing the link.

Before sending a sensitive SignWell document, decide whether each recipient should have a signer passcode. In the Send dialog, SignWell lets the sender set a unique code; a recipient shown with a lock must enter it before viewing and signing. The guide allows a hint in the custom message or sending the code separately. Agree on how the intended recipient receives the code, confirm the option in the chosen plan, then rehearse link and code entry with a fictional signer before using the setting for a real agreement.

When a SignWell request contains multiple uploaded files, check how the completed record will be delivered and stored. SignWell's Document Preferences can separate those files and the audit file instead of merging the completed material into one PDF. With separate files, the completion email sends them individually to the document sender and CC'd contacts, and a ZIP can be downloaded from the dashboard or document preview. Before treating that handoff as an archive, ask authorized staff to review a fictional completed example under the intended account setting, identify who receives which files, and confirm the signed files and audit record are retained together. Check current plan access and the organization's retention requirements.

Before retiring a SignWell team member, map the workspace and template handoff. SignWell says archiving disables that member's account access but leaves their name on templates they created. Those templates are reassigned to the Account Owner, who receives email notifications for documents created through them; the document owner for a Template Link can be changed separately. Ask an authorized administrator to review a fictional departure across the relevant workspaces: who still has access, who owns each template and Template Link, and who would receive subsequent template-document notices. Confirm the selected plan, roles and settings before changing live membership.

Before choosing SignWell team roles for sensitive documents, review a fictional document, contact and template with each intended role. SignWell says Members can access only their own documents, yet can access all contacts and templates without editing templates. Managers can manage all documents, templates, contacts and users, but not global account settings such as billing or workspace settings. Admins can access everything except billing, while the Owner has full access. Confirm the selected plan, seats and workspace assignment before inviting staff or sharing real documents.

SignWell says an unsigned recipient is sent automatic email reminders 3, 6 and 10 days after the initial email by default. The sender can disable this in Profile Settings. This cadence is separate from sending a manual reminder from the Documents dashboard and from the document link's expiry. For a workflow where follow-up timing matters, map a fictional unsigned recipient and a signed recipient, check the intended sender's profile control, and decide who will follow up if automatic reminders are disabled. Confirm the account's current setting and actual delivery before promising a recipient schedule; this buyer check sent no document or email.

For a form completed with everyone physically present, SignWell's in-person flow begins from a prepared template. The operator selects Sign In Person and the first signer; each signer enters their name and email, completes fields assigned in the template, then finishes so the next signer can continue. After the last signer completes the document, it can be downloaded or found from the Documents dashboard. Rehearse a fictional single-signer and two-signer form with harmless placeholders, and ask the document owner who prepares fields, checks signer order and secures the resulting file. Confirm plan access and any required identity process before using it; this buyer check created no document or signature.

For teams evaluating SignWell's Business-plan 21 CFR Part 11 mode, check the intended workspace: its controls apply to new documents created while the setting is enabled. SignWell says the downloaded completed PDF keeps the signed document, Electronic Signature Details and audit report together; the web preview omits field IDs, the details page and audit report, and Separate Completed Documents is disabled. For a fictional completed-record handoff, map who would retrieve and retain the complete downloaded package and verify its contents, without sending or downloading a real document. SignWell supplies technical controls but says the organization remains responsible for signer-identity procedures and regulatory compliance.