Guarded Recurring Runs for fiduciaries
Heterogeneous client systems make the start of each month repetitive and hard to evidence. Lokbox repeats the browser workflow you demonstrated, parks on drift and waits for your approval before every defined transfer.
The frame
WHAT / WHEN / NEVER / EVIDENCED
Four inputs keep the recurring run understandable and verifiable.
The problem
One client provides data through a portal, the next through another interface, a third with its own export logic. Manual collection consumes attention; a changed screen increases the risk of missing a step.
The controlled run
You demonstrate the data pull once. Lokbox repeats that workflow at the chosen time, prepares the monthly data in the AES-256-GCM encrypted client dossier and pauses at the approval point.
The run in four inputs
The workflow stays understandable even when it spans several browser steps.
ART. 01
Retrieves defined monthly data from approved client systems and prepares it for review.
ART. 02
At the chosen monthly cut-off — for example, the second business day at 07:30.
ART. 03
No defined transfer or external action without your approval.
ART. 04
Run ID, steps, approval decision, outcome, hash and QR in the Run Certificate.
Run Certificate
The same certificate format records steps, decision and integrity.
Lokbox · Signed audit protocol
Recorded steps
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
Example data — no production business data.
FAQ
No. You demonstrate the recurring workflow once in the browser. Lokbox repeats the defined path through the approved interfaces.
Lokbox parks the run at the point of drift instead of guessing. Failed or parked runs use 0 credits.
The client dossier is encrypted with AES-256-GCM. Access appears in the access log; hosting is in the EU, in Germany.
Your first Guarded Recurring Run