Track progress and resolve problems

Read recipient visits, routing stages and delivery history, and recover from changes or processing failures.

Track progress and resolve problems

Use the document sidebar to see who is waiting, who has responded and whether completed-copy delivery needs attention.

Before you begin

You need permission to read the document. Sending reminders, recalling, voiding or retrying also requires the corresponding document permissions.

Check recipient progress

  1. Open Documents → All documents, find the document and open it.
  2. Find Recipients & activity in the sidebar. On smaller screens, select Activity to jump there.
  3. In Recipients, expand a person to see their stage, response, verification and recent events.
  4. Select View full timeline, or open Timeline, for the combined document and delivery history.
  5. Use the recipient filter or Activity version to narrow the history. Refresh activity updates it manually; an open page also refreshes periodically.

A person waiting for their turn is in a future routing stage. The active stage must finish before their invitation is sent.

What a visit means

A visit is a PDF visibly displayed in a foreground tab for at least one second. Sender previews are excluded. Link access is recorded separately, including known automated checks. A visit records use of a recipient link, not proof of who read it or why they have not responded.

Completed-copy visits and download requests are separate from signing visits. A download request does not prove that the file was saved. Earlier access records cannot establish PDF display. Times in the sidebar use your browser's time zone; completion-record times use UTC.

Find what needs your attention

What needs you collects your review/signing requests, requested changes and recoverable failures. It may suggest reviewing a follow-up for an active recipient whose invitation has waited for the configured reminder interval. That suggestion does not send an email by itself.

Insights shows counts from accessible documents and can explain supported patterns with AI. Viewing alone cannot establish a recipient's intent or explain a delay.

Correct a document after sending

  1. If a recipient requested changes, open the document and prepare its revised version.
  2. Correct generated content or upload a replacement PDF.
  3. Recheck recipients and fields, then send the new version.

Fresh approvals and signatures are required. Previous versions remain available internally; their old links cannot act on the new version. For an active workflow you need to stop, use Recall and read the confirmation first.

Recover a failure

Void records a later event and preserves an already completed PDF. It does not rewrite that file. Read the confirmation before continuing.

Next steps

Review the completed file and its integrity record, or adjust routing and reminder defaults.