TracegenceNever fear a document audit again
Create a tenantCustomer login
Internal SOPs & policies

Controlled documents, versioned and audit-trailed.

Treat any internal document - SOP, work instruction, training record, policy - as a versioned, role-restricted, audit-logged artifact. Restore old versions in one click.

Partial - see below
Create a tenantCustomer login
Team reviewing controlled documents at a meeting table
Honest note: The primitive - versioned uploads with restore, controlled access, expiry alerts - ships today. A dedicated SOP authoring wizard with attestation tracking is Q4 2026.
SOP-7 SANITATION · v1Jan 2025SOP-7 SANITATION · v2Jul 2025SOP-7 SANITATION · v3Mar 2026REVERTEDSOP-7 SANITATION · v1restoredCURRENTrestore

What you get today

Live

Immutable version history

Each upload creates a new DocumentVersion row. Old versions remain. The current_version pointer can move, but never delete history.

Live

Restore on regression

Bad SOP rollout? Click "Restore" on any prior version. The pointer flips back; the bad version stays in history with its own audit-log entry.

Live

Folder + tag organisation

Folder path + freeform tags per document. Sidebar tree on the repository page. Filter by folder, tag, status, document type.

Live

Role-based access

Five-role hierarchy. Owner / Admin / Manager see everything; Client sees what they've uploaded; Auditor sees only their engagement scope.

Live

Expiry alerts

Tag a policy with a review date. We email the owner at 30 / 21 / 14 / 7 / 1 days out. Re-upload bumps the cycle automatically.

Roadmap

SOP authoring wizard + attestation tracking

Today: upload PDFs. Q4 2026: in-app authoring with reviewer comments, attestation collection, comprehension quiz on publish.

A policy-update lifecycle

  1. 01

    Author drafts

    Author writes the SOP in their tool of choice (Word, Google Docs). Exports to PDF, drops it in Tracegence as version 1.

    POST /documents
  2. 02

    Reviewer approves

    Optional approval workflow: sequential or parallel approvers. Each step HMAC-signed. Approver leaves a note that lands in the audit log.

    apps/workflows/
  3. 03

    Publish

    Status transitions to successful. Document becomes visible per its access scope.

    Document.status
  4. 04

    Iteration

    Author uploads v2 next quarter. Reviewers compare v1 → v2 in the version-history view. Approve → v2 becomes current.

    document_versions
  5. 05

    Restore

    v2 had a bug. One click on v1 restores. The chain shows: v1 (current) → v2 (was current Q3) → v1 (current again).

    POST /documents/.../restore
  6. 06

    Review reminder

    Annual review date hits. Owner gets an alert at 30 / 7 / 1 days out. Re-upload (or extend the review window).

    apps/notifications/

Internal document types we handle

Standard Operating ProcedureWork instructionQuality manualTraining recordCalibration certificateInternal audit reportMock-recall reportSanitation logPest control reportCustom (define in admin)

SOP authoring is next

Dates are targets, not commitments. Design partners get earlier access.

Q4 2026

  • In-app SOP authoring (markdown / rich-text)
  • Attestation collection per SOP version
  • Comprehension quiz on publish
  • Read-receipt tracking per role

Replace the controlled-document spreadsheet.

Try it on one folder of SOPs - version control, restore, and audit log included.

Create a tenantCustomer login