HDVerityLawVerityLaw Docs
Help Center

Working in Diligence and Tenders

SOP manual for due-diligence review and tender monitoring covering data-room triage, issue registers, policy mapping, bid scoring, and response review.

publicusers

Working in Diligence and Tenders

This page shows internal users how to review due-diligence material and tender activity using the routes that are live now. It stays inside the visible UI and does not assume document-upload, tender-creation, or drafting workflows that are not exposed on these screens.

Product: VerityLaw
Module: Diligence and Tenders
Role: Diligence analyst, transaction reviewer, bid manager, legal operations reviewer
Difficulty: Intermediate
Time: 10 to 12 minutes
Last Updated: 2026-03-10
Version: Current repo baseline

Before You Start

  • Sign in to the internal VerityLaw dashboard.
  • Know the deal, bid, or workstream you are reviewing.
  • Have the correct client, tender, or document reference on hand.

What does this module cover?

This module covers two adjacent areas:

  • M&A / Due Diligence for data-room triage, issue review, and policy-to-control mapping.
  • Tenders for tender tracking, bid scoring, and response-section review.

When do you use this?

Use these routes when you need to classify diligence documents, review extracted issues, compare policy statements to controls, track tender status, or judge whether a bid is worth pursuing. If you need richer authoring workflows, check the route first and do not assume the page can create records just because the requirement language sounds broader.

Where do you find it?

Primary path: Dashboard -> left sidebar -> M&A / Due Diligence and Tenders

Current routes:

  • /dashboard/data-room
  • /dashboard/diligence
  • /dashboard/diligence/issues
  • /dashboard/policy-mapper
  • /dashboard/tenders
  • /dashboard/tenders/bid-scoring
  • /dashboard/tenders/response

The /dashboard/diligence/issues route is useful for a more detailed issue register, even though it is not labelled separately in the sidebar.

How do you work in these areas?

Triage data-room documents

  1. Open Data Room Triage.
  2. Review the workstream counts shown in the stat cards.
  3. In Triaged Documents, check the File Name, Workstream, Document Type, Confidence, and Status.
  4. Pay attention to rows marked Duplicate before repeating review effort.
  5. Treat this screen as a classification and indexing board, not a file-upload page.

Review diligence issues

  1. Open Diligence Issues.
  2. Review totals for Total Issues, Critical, Confirmed, and Dismissed.
  3. Scan each row for Severity, Workstream, Description, Owner, Status, and Remediation Ask.
  4. If you need the expanded register with created dates and more status states, open /dashboard/diligence/issues.
  5. Use the issue pages to review and triage extracted findings, not to assume a full case-management workflow exists here.

Map policy statements to controls

  1. Open Policy-Control Mapper.
  2. Review the totals for Approved, Pending, and Rejected mappings.
  3. Check each mapping for Policy Statement, Control Type, Owner, Evidence Source, Frequency, and Status.
  4. Treat missing owner or evidence fields as real follow-up gaps.
  5. Use the current page as a mapping register and review board.

Review the tender pipeline

  1. Open Tender Review.
  2. Review the summary cards for Total Tenders, Received, Under Review, and Total Value.
  3. In All Tenders, confirm the Title, Client, Deadline, Value, Assigned To, and Status.
  4. Use this page to track existing tenders and confirm workload.
  5. Do not promise a visible tender-creation workflow from this route, because the page is list-first in the current build.

Score the bid and review the response

  1. Open Bid Scoring.
  2. Compare the weighted fields for Margin, Legal Risk, Capacity, Deadline, Strategic, Total, Recommendation, and Decision.
  3. Open Response Drafting.
  4. Review the Completeness cards and the Response Sections table.
  5. Use reviewer, status, and last-updated information to decide whether the response is ready to move forward.

These tender routes are currently review surfaces. They do not expose a full drafting editor or approval workflow from the page itself.

What if something does not look right?

"The page tells me to create a record, but I cannot see a create button"

What it means: Some empty-state wording is broader than the visible controls.

What to do: Treat the live page as a monitoring screen unless you can see the actual create action in the UI.

"I need a more detailed diligence register"

What it means: The sidebar route and the deeper register route are not identical.

What to do: Use /dashboard/diligence/issues when you need the extended issue table.

"The response area looks too thin for drafting"

What it means: The current route is a section-review board, not a full tender editor.

What to do: Use it to check completeness and review state, then escalate content drafting outside this screen if needed.

What's Next

Related Pages

Still Stuck?

  • Recheck whether you are in M&A / Due Diligence or Tenders.
  • Use the screen map if a register route is missing from the sidebar.
  • Contact support: support@veva.co.za

Was this page helpful? [Yes] [No]