Skip to content
SOPCam AI
InvestorsApply for a controlled pilot

The platform

Six capabilities. One operating record.

Each step produces a record the next one relies on. Below is every capability we describe, with its exact status — so you can see what is built and tested, and what is still to come.

  1. Capture
  2. Govern
  3. Train
  4. Transition
  5. Comply
  6. Report
“Built and tested” means the capability exists in our code and passes its automated tests. It does not mean it is in production: no capability is in customer use yet, and we are looking for the first pilot organisations.

01 · Capture & Understand

Start from how the work is really done.

An expert records the task as they perform it, writes it down, or attaches the screenshots they already use. The narration is transcribed, and frames are drawn from the recording, so every later step can point back to its source.

The record
A source recording, its transcript and frames, held as governed media; restricted originals never leave it.
Who decides
The expert chooses what to capture. Nothing is recorded covertly; recording is always visible.
  • Video upload and media processing
    Upload a recording of real work; it is validated, normalised and broken into frames and audio for review.
    Media processing has been proven in tests, not yet on a deployed pilot environment.
    Built and tested
  • Multilingual transcription
    Spoken narration is transcribed so every step can be traced to what was actually said.
    Transcription with a real provider has been proven in our test environment; recording the detected language is still being proven.
    Built and tested
  • AI-drafted procedure from a recording
    A first draft of the steps is proposed from the transcript and frames. It is a draft: a person reviews it before anything is published.
    End-to-end generation with a live AI provider has not yet been proven. This is the next proof, not a shipped result.
    Built and tested
  • Structured authoring from many sources
    Write a procedure by hand, from a brief, from screenshots or from a recording — all converging on one canonical procedure.
    Built and tested
  • Guided screen capture with narration
    An expert shares a screen and narrates; recording is always visible, and the result goes through the same review.
    Built and tested, but not yet exercised with a real person's recording.
    Built and tested
  • Screenshots with redaction and highlights
    Attach images to steps, redact what must not be shown, highlight what matters, and keep restricted originals out of delivery.
    Built and tested
  • Captions, translation and language tracks
    Procedures and captions in the languages your people work in, with regional-language review.
    Built and tested; recording the detected language of a real transcript is still being proven.
    Built and tested
  • Transcript correction with revision history
    Correct the transcript itself, with every correction traced through to the procedure built from it.
    On the roadmap

02 · Govern & Standardise

Turn a draft into the approved way of working.

A draft procedure is proposed from the source material. Its owner reviews it step by step, corrects it, attests to it and approves a revision. Publication is a separate act, and a newer revision supersedes the old one everywhere.

The record
A numbered revision with its owner, its approval and its place in an append-only, hash-chained decision ledger.
Who decides
A named person approves. The AI drafts; it never approves or publishes.
  • Owner review and approval
    A named person reviews the draft step by step, attests to it, and approves it. Approval and publication are separate acts.
    Built and tested
  • A distinct approver (four-eyes)
    Require that the person who approves a procedure is not the person who wrote it.
    On the roadmap
  • Controlled publication, supersession and revocation
    Only an approved version is published; a newer version supersedes it, and revocation takes it out of use.
    Built and tested
  • Revisions, comparison and standards
    See what changed between versions and hold procedures to a shared standard across sites.
    Built and tested
  • Append-only decision ledger
    Approvals and other decisions are recorded in a hash-chained, append-only ledger whose integrity can be verified.
    Built and tested
  • Publication events in the evidence ledger
    Record each publication and revocation as governed evidence, with location-scoped views.
    On the roadmap
  • Roles, locations and enterprise sign-in
    Organisation, location and role scoping on every record; single sign-on and user provisioning for enterprise identity providers.
    Single sign-on and provisioning are built and tested but have not yet been connected to a real customer identity provider.
    Built and tested

03 · Train & Enable

Put the approved version in front of the people who use it.

Training is assigned on the exact approved revision, assessed, verified in person where it matters, and certified. At the point of work, a QR code opens the current version and a revoked one stops working.

The record
Assignments, attempts, verifications and certificates, each tied to the revision they cover.
Who decides
A trainer or supervisor verifies. People are never ranked or scored on productivity.
  • Training assignments, assessments and certificates
    Assign training on an approved version, assess it, verify it in person, and issue an internal certificate.
    Built and tested
  • Recertification and retraining lists
    Spaced re-verification and recertification; after a revision, a list of who was trained on the earlier version.
    Built and tested
  • QR access at the point of work
    A label-bound QR code opens the current approved procedure; a revoked one stops working.
    Built and tested
  • Worker and supervisor checklists
    Visual checklists for the person doing the work and verification checklists for the person checking it.
    Built and tested
  • Offline field packages
    Take an approved procedure offline as an encrypted package and reconcile when back online.
    Proven in automated browser tests; not yet on a real field device. Protected offline video is deliberately deferred.
    Built and tested
  • Governed knowledge retrieval (Knowledge Copilot)
    Ask questions of approved knowledge and get cited answers that respect every access rule, with refusal when the evidence is not there.
    On the roadmap

04 · Transition & Assure

When someone leaves, prove the work moved with them.

A transition case lists the responsibilities that must be handed over. Each one moves from learned to understood to demonstrated to confirmed by a manager. Access is recorded as revoked, transferred or retained.

The record
A transition case with responsibilities, readiness, access custody and an independent sign-off.
Who decides
An independent manager signs off, and signing off early fails, with the reason in words.
Transition Assurance
  • Transition cases and knowledge-transfer plans
    Open a case when someone resigns, retires, transfers or leaves suddenly, and list the responsibilities that must be handed over.
    Built and tested
  • Successor readiness, demonstrated
    Each responsibility moves from learned to understood to demonstrated to manager-confirmed. Watching a video is not a handover.
    Built and tested
  • Independent manager sign-off and handover report
    An independent manager signs the case off; signing off early fails, and says why. No score or rating of any person is stored.
    Built and tested
  • Access and custody records
    Record which access existed and whether it was revoked, transferred or retained. The platform records the decision; it never acts inside another system.
    Built and tested
  • AI-assisted handover planning
    An assistant that drafts the knowledge-transfer plan for a person to approve.
    On the roadmap

05 · Comply & Prove

Keep obligations and their evidence together.

Obligations are registered and scheduled; the evidence that each was met is recorded against it — the procedure version, the training, the sign-off. An exception is decided by someone other than the person asking for it.

The record
Obligations, evidence records and exception decisions an auditor can follow to their source.
Who decides
A second person approves every exception. Nobody approves their own.
Compliance & Evidence
  • Obligations, calendar and evidence records
    Register obligations, schedule them, record the evidence that each was met, and explain why an item is due.
    Built and tested
  • Exceptions decided by someone else
    An exception is approved by a second person against the exact record it covers; nobody approves their own.
    Built and tested
  • Evidence and audit console
    Follow decisions, approvals and training to the records behind them, and export a verifiable segment of the ledger.
    Built and tested
  • Legal hold on recordings
    Place source recordings on hold so they cannot be deleted while a hold applies.
    Built and tested
  • Retention policies, organisation-wide holds and evidence exports
    Retention and legal hold across every record type, customer-managed keys, and governed evidence exports.
    On the roadmap
  • Jurisdiction packs reviewed by counsel
    Pre-built obligation packs for a country, reviewed by qualified counsel before any is offered. Which country comes first is still to be decided.
    On the roadmap

06 · Report & Improve

Report from records, not from recollection.

Report Studio builds reports from the governed records above, shows where every figure came from, and suppresses small groups so no report singles out a person. You can ask for a report in your own words; deterministic rules suggest one.

The record
A saved, reproducible report definition with provenance for each figure.
Who decides
The reader chooses what to run. No AI model is called to suggest a report.
Report Studio
  • Report Studio
    Build, save, schedule, reproduce and compare reports from governed data, with the provenance of every figure shown.
    Built and tested
  • Ask for a report in your own words
    Describe the report you want; deterministic rules suggest one, checked against what you are allowed to see. No AI model is called and the question is not stored.
    Built and tested
  • Privacy-safe aggregation
    Small groups are suppressed so a report cannot single out a person; there is no individual productivity scoring.
    Built and tested
  • Operational dashboards across sites
    Procedure currency, training status and accountability across locations and agencies.
    Built and tested
  • Scheduled reports by email
    Deliver scheduled reports to an inbox.
    On the roadmap

Architecture, at a safe level

Designed so the record can be trusted.

01

One canonical record per procedure

Every source — recording, writing, screenshots — converges on one procedure with revisions, never a parallel copy.

02

Tenant, location and role on every record

Each read and write is scoped to the organisation, the locations and the role of the person making it.

03

Append-only decision ledger

Approvals and other decisions are hash-chained; a segment of the chain can be verified and exported.

04

Human authority for consequential acts

Approval, publication, sign-off and exceptions are taken by named people. Automated components propose.

05

Fail-closed media and access

A restricted original never falls back into delivery; uncertain identity or access is refused, in words.

06

Privacy-safe reporting

Aggregates suppress small groups; there is no individual productivity score anywhere in the model.

Security and trustTake the product tour