Skip to main content

How to track a caregiver's signature packet progress

This guide explains how to check the status of a caregiver's signature packet in the Agency Dashboard to resolve inquiries about incomplete or pending document signing

Written by Diana Pasos

When to use this guide

Use this process when:

  • A caregiver reports they keep receiving notifications about documents they believe they already signed

  • A manager asks about the status of a caregiver's signature packet

  • You need to verify whether a caregiver has completed their part of the signing process


Step-by-step

  1. Go to the Agency Dashboard Log into the platform and navigate to the Agency Dashboard tab.

  2. Search for the caregiver Click on the Search All Caregivers tab. Type the caregiver's name in the search bar and their profile will appear.

  3. Review their profile Once you're in their profile you can see:

    • Tasks that are outstanding or completed

    • Documents they need to sign

    • The current status of their signature packet

  4. Open the signature packet If the packet shows as "In Progress", click into it to open it.

  5. View the caregiver's signing progress Once inside the packet, a green "Sign Document" button will appear. Click it to access the exact view the caregiver sees — this shows you exactly where they are in the signing process and what still needs to be completed.


What to look for

Once you're in the caregiver's view, you can determine:

  • Caregiver has signed — their portion is complete, waiting on manager to sign

  • Caregiver hasn't signed yet — they still have action required on their end

  • Packet is waiting on multiple parties — check who still needs to sign


Important notes

  • If the caregiver has completed their part but the packet is still showing as "In Progress", it means a manager still needs to sign. In this case use the macro response to reassure the caregiver that they are good and waiting on the agency side.

  • Do not tell the caregiver to log back in if the system is still sending incorrect notifications — this will not resolve the issue and will cause more confusion.

Did this answer your question?