Practical boundary: Thebe Desk is compliance-management software. It does not replace current official guidance or professional legal, tax or accounting advice.
What makes evidence useful
- The record should be identifiable: what it is, which obligation or case it supports, who reviewed it and whether the file has passed required safety checks.
- Integrity metadata helps detect whether the stored content changed after approval. A status label alone is not enough if the underlying file cannot be trusted.
- Evidence access should be tenant-scoped and role-aware. A reviewer may need to inspect a document without gaining access to billing, leadership analytics or unrelated employee information.
- Deleted or quarantined evidence should not remain silently downloadable through an old link.
From evidence library to inspection readiness
- Inspection readiness asks a different question from storage: can the business quickly assemble the current proof for a particular control, event or review?
- Control lineage links obligations, controls, evidence and findings so a business can explain not only what document exists, but why it matters.
- If a key item is missing, expired, unreviewed or blocked by malware scanning, the inspection pack should show the gap rather than hiding it.
Read-only roles should really be read-only
- Auditor and reviewer experiences should expose only the evidence, audit and assurance information needed for their work.
- Buttons hidden in the browser are not a security boundary; the API must also deny unrelated financial, HR, tender and administrative data.
- The platform therefore uses restricted-role read allowlists and explicit mutation authorization so a hidden workspace module cannot be fetched directly.
Keep approved proof connected to obligations, controls and review history.
Bring recurring obligations, deadlines and supporting evidence into one role-aware Botswana SME workspace.
See plans and start free