---
title: "How Policy Compliance Is Calculated for a Selected Date"
description: "Understand historical assignment status, percentage denominators, matrix version scope and the limits of reconstructing past compliance."
url: https://vitextra.com/en/support/kb/10531
language: en
published: 2026-11-08
modified: 2026-11-08
products:
  - "Policy Acknowledgement"
author: "Lidija Reising"
tags: ["compliance as of date", "historical policy report", "compliance calculation", "assignment status"]
---

# How Policy Compliance Is Calculated for a Selected Date

Understand historical assignment status, percentage denominators, matrix version scope and the limits of reconstructing past compliance.

The date filter in Compliance Dashboard calculates an earlier view from the assignment records currently available. It is useful for comparing progress, but it is not a complete event-by-event historical database. Interpret the result with the policy scope, department filter and current record state in mind.

## Select the reporting date

Open Compliance Dashboard with reporting access and choose **Status as of the selected date**. You can select today or an earlier date. Review any policy-specific link, configured category restriction and department selection before comparing results. Those filters determine which assignments enter the calculation.

Assignments created after the selected day are omitted. For a record currently acknowledged, the calculation checks its acknowledgement date: if confirmation occurred later than the selected day, it is treated as open or overdue at that earlier point.

![Selecting the date and scope of a historical calculation](https://static.vitextra.com/articles/10531/historical-date-en.png)
*Selecting the date and scope of a historical calculation*

## Understand historical status rules

| Current record condition | Calculated historical treatment |
|---|---|
| Assigned after the selected day | Not included yet. |
| Acknowledged on or before that day | Acknowledged. |
| Acknowledged later | Assigned or overdue according to the due day. |
| Open with an earlier due day | Overdue. |
| Open with no earlier due day | Assigned. |
| Exempt, paused or review-required | Uses the currently stored special status; earlier transitions are not fully reconstructed. |

The comparisons use day boundaries rather than an exact intraday event replay. Browser date handling can matter around time-zone boundaries. A confirmation earlier or later within the same day is not represented as separate historical snapshots by this filter.

## Calculate the main percentage

Overall compliance divides acknowledged assignments by included assignments after excluding exempt and paused states. Review-required assignments remain in the denominator. The count is assignments, not unique employees.

For example, if the selected scope has 10 assignments, including 6 acknowledged, 1 exempt and 1 paused, the denominator is 8 and the compliance percentage is 75%. An employee with several policies contributes more than one assignment; the employee count shown elsewhere is a different measure.

## Compare the matrix, trend and median

The policy-by-department matrix uses the current version of policies that are currently published or under review. The overall indicator can include other versions in the selected policy scope. Averaging matrix percentages is therefore not a reliable way to reproduce the overall result.

The trend has 6 monthly points, using each month end or the selected date where appropriate. The median acknowledgement duration uses completed assignments assigned within the preceding 90 days and acknowledged by the selected date. The associated UI wording refers to campaigns, but the implementation filters assignment dates rather than campaign-creation dates.

## Know when the result is insufficient

❗ **Important**  
A record exempted today can influence a past-date calculation even if it was not exempt on that past date. Current policy status, current version and assignment department values can also shape the report. Do not describe this view as a complete historical reconstruction or use it alone to establish every past status transition.

For a specific investigation, retain the assignment rows, acknowledgement events, version information and audit entries. A historical export uses the calculated status but still includes current stored date fields; a later acknowledgement timestamp can appear on a row whose historical status was assigned. See [KB10532. How to Export Policy Compliance Assignments to Excel](https://vitextra.com/en/support/kb/10532).

## Reconstruct one assignment by hand

Consider a sample assignment created on day 1, due on day 5 and acknowledged on day 8. Before day 1 it is not included. On day 5 it is still within the deadline. On day 6 it is overdue. On day 8, if its current record has the acknowledgement and date, the historical calculation treats it as acknowledged.

This example illustrates day-level status calculation, not a minute-by-minute event history. If the confirmation occurred late on day 8, the filter still evaluates the selected day as a whole. When exact event timing matters, inspect the evidence timestamp rather than inferring it from a daily percentage.

Now compare a currently exempt assignment. Its historical treatment uses the stored special state rather than finding the date when an exemption took effect. Even if the exemption was decided later, a past-date view can be influenced by that current state. This is why a report based solely on today's records cannot prove every status that existed at a past moment.

## Explain differences between two saved reports

Two exports generated at different times for the same selected day can differ if relevant current records have changed. Policy status or version, stored assignment attributes and special states can affect the result. A difference should prompt reconciliation of the scope and records, not an immediate conclusion that the date filter is randomly changing data.

For comparison, retain the selected date, policy/category restrictions, department and export time. Identify a sample of changed rows and inspect their assignment and evidence records. Determine whether the difference comes from a later confirmation, a special-status change, a different current version or another scope change.

Use wording such as “calculated from the records available at export time” when presenting a historical result with these limits. Do not use the dashboard as the sole source for an assertion about every past exemption or pause. Version history, acknowledgement events and the administrative audit log provide different supporting context, although none should be assumed to capture every possible external SharePoint change.

## Verify a report before sharing

Record the selected date, policy/category scope and department. Reconcile a few known examples manually, including one confirmed after the date and one exemption. Explain the calculation limits alongside any historical conclusion. For a current operational dashboard, see [KB10508. Compliance Dashboard: How to Analyze Policy Acknowledgement](https://vitextra.com/en/support/kb/10508).