This article explains how the Last Published date is calculated for policies in Secureframe, what actions update it, and what to check if it looks incorrect.
Quick answer
The Last Published date reflects the most recent time a policy was published (not just edited).
Edits saved as a draft (or changes that are not published) will not change the published date.
If you just published a policy, it can take a short time for all views to refresh.
What updates the Last Published date
Publishing a policy from the policy editor.
Publishing a new version after changes (when versioning is enabled in your workflow).
What does not update the Last Published date
Draft edits that are not published.
Non-substantive metadata changes that do not create a new published version (varies by policy workflow).
If the date is not updating, check these items
Confirm you actually published: open the policy and verify the latest changes are in the published view, not only in a draft.
Check your permissions: if your role cannot publish, your edits may be saved without producing a new published version.
Refresh timing: after publishing, wait a few minutes and hard refresh the page.
Policy acknowledgments: if your process requires acknowledgments after publishing, confirm the policy version you expect is the one currently assigned.
What to send Support if it still looks wrong
Policy name and link
What date you expect and why
Whether the change was an edit to an existing policy or a new policy/version
Screenshot of the policy header showing the Last Published date
If your question is about how policy templates, mappings, and acknowledgments work, you may also find your existing policies FAQ helpful.