> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/policies/dashboard-actions/view-acknowledgement-history-for-an-employee.md). # View Acknowledgement History for an Employee View detailed acknowledgement history for each employee to track policy compliance and audit readiness over time. Sprinto lets you view a complete breakdown of acknowledgement responses for each staff member. This is useful for reviewing an employee’s compliance history over multiple policy campaigns or onboarding cycles. *** ### **Open the Acknowledgement Status tab** 1. Go to the **Acknowledgement Status** tab from the Policies module. 2. Locate the employee whose history you want to review. 3. Click anywhere on the row to expand the view.
*** ### **Understand the acknowledgement history view** The expanded row shows a table containing:
FieldDescription
Acknowledgement nameThe name of the request (e.g. Onboarding Staff Acknowledgement).
Requested onThe date the policy was sent to the employee.
Acknowledged onThe date the employee completed the acknowledgement (or blank if pending).
StatusShows if the employee is Passing, Failing, or Critical for that request.
{% hint style="info" %} Policies listed under a request are not shown individually here, but the overall result reflects the entire bundle. {% endhint %} *** ### **Use cases for acknowledgement history** * Confirm whether a user has acknowledged a specific request * Identify if the employee has repeatedly failed or delayed acknowledgements * Provide this record as evidence during internal audits or HR escalations *** ### **Best practices** * Review history before triggering reminders or assigning policy re-acknowledgement * Combine this view with filters for zone, request, or team * Use in conjunction with version history to track what the employee acknowledged *** ### **Next steps** If acknowledgement is missing or overdue: * Reassign the request via the **Acknowledgement Requests** tab * Contact the team owner for follow-up * Use this data to feed into periodic monitoring check. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sprinto.com/policies/dashboard-actions/view-acknowledgement-history-for-an-employee.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.