Practical guide

Send useful reminders without creating duplicate pressure

Last materially reviewed 2026-09-21

Quick answerUse reminders to clarify an outstanding action, not to substitute for a status check.
What to know

Check whether an action is still needed

Before reminding someone, inspect the original request and the participant’s current state. A reminder is inappropriate when the required action is already complete, the person declined or the document has been superseded. Signaturely documents reminder controls, but a control being available does not make every use sensible. The sender remains responsible for understanding why the request is outstanding and whether another notification is justified.

What to know

Explain the specific next step

A useful reminder identifies the existing document, the requested action and a way to raise a question. Use an actual agreed deadline if one exists. Avoid fabricated urgency or language implying that opening the request commits the recipient to its contents. If the person reports a problem, address that problem instead of increasing reminder frequency. Missing email, unclear wording and a disagreement require different responses from simple forgetfulness.

What to know

Coordinate within the team

Assign one owner for follow-up so several colleagues do not contact the same person independently. Keep a short record of the latest action and its outcome. This does not require copying the agreement into a general chat or collecting private message contents in analytics. A minimal record of who owns the next step can prevent duplicate pressure while leaving the actual document in its appropriate system of record.

What to know

Recognize when reminders should stop

A decline, disputed document or uncertain recipient is a reason to reassess, not to keep nudging automatically. Use the supported controls and the organization’s process to decide what happens next. We do not prescribe a universal reminder schedule or claim that more notifications increase completion. Follow the decline guide for an explicit refusal and the missing-email guide when the recipient cannot access the original request at all.

Continue when useful

Next: The signing email is missing: check delivery before sending again

A missing notification is not evidence that the original document request failed.

Open The signing email is missing: check delivery before sending again →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Manage documents, reminders and edit/resend — Merchant documentation · help.signaturely.com · Merchant-controlled · checked 2026-09-21
  2. Declined documents and multi-signer completion — Merchant documentation · help.signaturely.com · Merchant-controlled · checked 2026-09-21