Checking What Is Live, Partial, or Still Missing

This page helps you tell the difference between current product truth and future scope so the docs do not lie.

Product: VerityLaw
Module: Reference and Traceability
Role: Any user, support, QA, documentation author
Difficulty: Intermediate
Time: 5 minutes
Last Updated: 2026-03-10
Version: Current repo baseline

Before You Start

• Use this page when you need a status answer, not a task walkthrough.
• Be ready to compare the route map with the requirement register.

What is this page?

This is the manual honesty page. It maps the current help set to what is live, what is partial, and what is still missing.

When do you use this?

Use this page before promising a feature to a user, when writing or reviewing docs, or when a requirement in feedback or backlog material sounds richer than the screen in front of you.

Where does the status come from?

This page is grounded in:

• the current /dashboard and /portal routes
• the VerityLaw functional register
• the existing help pages

How to use this page

1. Find the workflow area below.
2. Check whether it is marked live, partial, live to partial, constraint, or missing.
3. If it is missing, do not turn it into a fake SOP.
4. If it is partial, document only what users can truly do now.

Coverage map

Manual area	Current surface	Build status	Documentation rule
practice core: dashboard, clients, cases, documents	live dashboard pages	live	document as normal workflow
finance core: billing, time entries, trust	live dashboard pages	live	document as normal workflow
contracts core: contracts, repository, obligations, negotiations, playbook	live dashboard pages	live	document as normal workflow
core privacy records: data map, consent, dsr, notices, policies, training, breach	live dashboard pages	live	document as normal workflow
portal dashboard, cases, messages, invoices, compliance	live pages	live	document as normal workflow
governance core: entities, authority, board packs, resolutions, delegations	visible dashboard routes	live to partial	document what the current routes show and avoid invented approval depth
Information Officer and compliance health	visible dashboard routes	partial	document role expectations plus current route behavior only
PAIA manual, PAIA report, appeals	visible or referenced routes	partial	document carefully and avoid claiming full statutory lifecycle automation
privacy intelligence: sentinel, dsr factory, campaigns	visible dashboard routes	partial	treat as intelligence or review surfaces unless end-to-end workflow is proven
contract intelligence: heatmap, benchmarks, ai negotiator, order risk	visible dashboard routes	partial	document as review or assistant surfaces, not as guaranteed autonomous engines
diligence, tenders, disputes, remediation, enforcement risk, sector packs	visible dashboard routes	partial	document the current screen honestly and avoid pretending the full backlog exists
verification	visible dashboard routes	live to partial	document the current check surfaces and visible drill-down only
legacy admin and law apps	supporting repo surfaces	constraint	do not treat them as the main docs baseline unless the environment explicitly uses them
Information Regulator registration and wider IO filing obligations	register says missing	missing	do not document as a current system task

What if the requirement sounds richer than the UI?

"The feedback says this should be a full governance platform"

Why this happens: The end-user feedback and requirement register describe a wider governance model than the currently confirmed dashboard and portal routes prove end to end.

Fix: Document the live route, note the partial state honestly, and do not invent missing user actions.

What's Next

• Finding the Right VerityLaw Screen
• Running Compliance Operations

Related Pages

• Running Admin and Governance Operations
• Using the VerityLaw Client Portal
• Module Manual Index
• Task Manual Index

SA Compliance Reference

• POPIA - governance and data subject rights duties still apply whether the product flow is complete or partial.
• PAIA - manual and access workflows should only be documented as live where current product support is confirmed.

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]