Reviewing activity before follow-up
2 min read
Updated Apr 9, 2026
Effective follow-up comes from context. Before you send another email or restart a workflow, check what has already happened in the document timeline and sender-side boards.
Before you begin
A package that has slowed down
Access to the authenticated sender views
A question about what follow-up action is actually needed
Look at the current status first
Status tells you whether the package is active, waiting, completed, declined, or voided.
Do not send reminders blindly without confirming the package is still eligible for them.
Check who is actually blocking progress
In sequential routes, only one participant may currently be able to act.
In parallel routes, you may need to focus follow-up on a single lagging recipient rather than everyone.
Choose the right next action
Use reminder for timing, resend for fresh delivery, void for an invalid package, and replacement drafting for real content changes.
That decision tree keeps the audit trail cleaner and reduces recipient confusion.
Pro Tips
Follow up on facts, not assumptions.
Keep a short note internally if the workflow is high-stakes and several people may act on it.
Use Completed or compliance exports when the question is evidence, not follow-up timing.
Was this article helpful?
Use this as a quick signal while the public knowledge base is static.