All topics
English

Request documents and signatures · 3 min read

Organize outstanding items and next actions

Turn form returns into service actions without confusing received answers with a completed process.

In this guide
  1. Review before closing
  2. Use tasks with an assignee and deadline
  3. Continue policy entry with received details
  4. Document the handover to service
  5. Checklist for completing this step
  6. Keep learning

For: CRMDAY One users with the Insurance profile.

Review before closing

  1. Check the returned request matches client, template and period.
  2. Open the document and received files; check legibility and the correct person.
  3. Record what was received, what remains and who will act next.
  4. If answers differ from the record, check the correct source before editing contact or policy. An answer does not automatically update every field in the system.

Use tasks with an assignee and deadline

  1. Open the contact and review client Tasks. Avoid duplicating an open task.
  2. Use the new-task action with a specific outcome: “Check Maria’s income proof”, “Confirm form return” or “Review details before creating Policy”.
  3. Set assignee and deadline and check available interaction links.
  4. Save and verify in the list or Kanban. Record the result when completing it.
  5. If something remains, agree another follow-up. Completing a Task does not sign a form or automatically resolve policy pending items.
Contact tasks organize checks and follow-ups. Assign a person and deadline to each outstanding action.
Contact tasks organize checks and follow-ups. Assign a person and deadline to each outstanding action. Open the image to enlarge it.

Continue policy entry with received details

For a signed ACA - Application Form, the new ACA policy wizard may offer Load values from the contact’s most recent signed application. Check the source document, review loaded values and fill gaps. The Policy is created only after user review and confirmation.

Open Enrollment has its own answer review and actions for updates and operational follow-through. Use them where available rather than treating every form as automatic policy creation. Editing wizard details does not rewrite the signed form.

To continue with policy entry, see Create the policy with the wizard.

Document the handover to service

A useful note records the outcome and next step. Example: “Authorization received and reviewed. Maria’s income proof attached, pending review. Alex will follow up on October 28.” Use notes for internal context and the client’s channel for the agreed follow-up.

  • Check history before requesting an already-received document again.
  • Do not mark a policy active merely because a form was signed.
  • Do not send another person’s PDF or link when resolving an issue.
  • Preserve earlier documents and record the reason for a new request.

Checklist for completing this step

  • Correct request and recipient, with delivery checked.
  • Signature and returned files actually reviewed.
  • Record checked through appropriate fields and flows.
  • Pending items with assignee, deadline and next action.
  • Client informed of service continuation.

If something cannot be confirmed, keep follow-up open. This step ends when returned material is reviewed and continuation is clear, not only when the screen says Signed.

Keep learning

Updated October 24, 2026.