HDVerityLawVerityLaw Docs
Help Center

Managing a Policy Record

SOP for creating a policy record, reviewing the policy register, and using the current version-history route when it is available.

publicusers

Managing a Policy Record

This page shows you how to create a policy record and how to handle the current policy-review screens honestly.

Product: VerityLaw
Module: Privacy - Policies
Role: Information Officer, privacy operator, administrator
Difficulty: Beginner to Intermediate
Time: 10 minutes
Last Updated: 2026-03-10
Version: Current repo baseline

Before You Start

  • Sign in to the dashboard.
  • Decide whether you need a brand-new policy or a new version of an existing one.
  • Have the policy title, type, and content ready before you open the form.

What is this task?

This task covers three current actions:

  1. Creating a new policy record.
  2. Reviewing the policy register.
  3. Creating a new version from the separate version-history route when you already have access to that route.

When do you use this?

Use this task when a privacy or data-protection policy must be recorded in VerityLaw, or when an existing policy needs a tracked version update.

Where do you find it?

List route: /dashboard/privacy/policies
Create route: /dashboard/privacy/policies/new
Button on list page: New Policy
Version route: /dashboard/privacy/policies/[id]/versions

Important current-state note

The Policies list is review-oriented. It shows policy rows, but the visible list page does not expose an action button to open version history. A separate version-history route exists in the current code, but you should only document it as a route you can use when you already have the policy ID or an internal link to it.

How to create the initial policy record

  1. Open /dashboard/privacy/policies.
  2. Click New Policy.
  3. In Policy Details, complete:
    • Title
    • Type
    • Description if needed
    • Content if ready
  4. In Dates, complete:
    • Effective Date if known
    • Review Date if known
  5. Click Create Policy.
  6. Wait for the app to return you to /dashboard/privacy/policies.
  7. Confirm the policy appears in the table.

How to review the policy register

The current Policies page is the main review screen. Use it to check:

  • Title
  • Type
  • Version
  • Status
  • Effective Date
  • Review Date

How to create a new version when the version page is available

  1. Open /dashboard/privacy/policies/[id]/versions for the policy you need.
  2. Review the Current version value at the top of the page.
  3. Click Create New Version.
  4. Update Title if needed.
  5. Update Content if needed.
  6. Enter Change Summary if you want the change logged clearly.
  7. Click Create Version.
  8. Confirm the version list refreshes and the current version number increases.

What if something looks wrong?

"I can see the Policies list, but there is no button to open version history"

Why this happens: The visible list page does not currently include an actions column.

Fix: Treat the list as a review screen. Only use the version route when you already have a direct route or internal navigation to it.

"I need an approval or publish step"

Why this happens: The screens reviewed here show create and versioning behavior, but they do not expose a visible approval control.

Fix: Do not document an approval action that is not on screen. Follow the current UI exactly.

What's Next

Related Pages

Still Stuck?

  • Search the VerityLaw help set.
  • Use the support bot if your environment exposes it.
  • Contact support: support@veva.co.za

Was this page helpful? [Yes] [No]