Lokbox.
Try for free
Menu

Run Certificate

What the run did — as a signed protocol.

After every run, Lokbox creates a PDF Run Certificate with the run ID, steps, approval decisions, hash and QR verification.

Example

LB-DEMO-2026-0042

Non-production demonstration data.

Full example

One run. One verifiable dossier.

The annotations explain what each field establishes.

Lokbox · Signed audit protocol

Run Certificate

✓ Signature verified
Run ID
LB-DEMO-2026-0042
Time window
02.08.2026 · 07:30–07:34 CEST
Task
Prepare monthly data
Status
✓ Completed

Recorded steps

  1. 01Approved source opened✓
  2. 02Accounting period selected✓
  3. 03Data set prepared for review✓
  4. 04Approval gate reachedDECISION
  5. 05Approved action executed✓

Approval decision

Approved · User ID DEMO-14 · 07:33:41

Integrity hash · shortened example

SHA-256 · 67c9 2a10 4f71 8b25 … d18b

Example QR · not scannable

What the fields establish

Traceable, without overclaiming.

  1. 01Run IDUniquely links the protocol to one individual run.
  2. 02Time windowShows when the run started and ended.
  3. 03Recorded stepsDocument the sequence and outcome of every executed step.
  4. 04Approval decisionRecords the time and user ID of the human decision.
  5. 05Integrity hashEnables a check whether the presented certificate was changed.
  6. 06QR verificationPoints to the certificate verification view.

QR

How QR verification works conceptually.

The QR code contains a reference to the verification view. There, the identifier and signed certificate data are checked against the presented protocol. The QR replaces neither approval nor the access log.

Honesty note

Not an official document.

The Run Certificate is a signed Lokbox audit protocol. It is not an official document or a qualified electronic signature.

Your first Guarded Recurring Run

Set up a run with a verifiable close.

Try for free