Guarded Recurring Runs for property management

Collect property data repeatedly. Evidence every run.

Defined property data often sits across several browser interfaces. Lokbox repeats the retrieval workflow you demonstrated, prepares the monthly overview and pauses before defined external actions.

The frame

WHAT / WHEN / NEVER / EVIDENCED

Four inputs keep the recurring run understandable and verifiable.

The problem

Distributed data. The same monthly rhythm.

Recurring portal checks across several properties demand attention. If a screen changes or a field is missing, the workflow must not continue silently.

The controlled run

Prepare the monthly overview. Keep control.

You demonstrate the defined browser workflow once. Lokbox repeats it at the chosen time, parks on drift and documents the run in the Run Certificate.

The run in four inputs

Clearly bounded. Clearly evidenced.

The workflow stays understandable even when it spans several browser steps.

ART. 01

What it does

Retrieves defined property data from approved portals and prepares it for the monthly overview.

ART. 02

When it runs

At the monthly cut-off you define.

ART. 03

What it must never do

No defined external action without your approval.

ART. 04

What it did

Run ID, steps, approval decision, outcome, hash and QR in the Run Certificate.

Run Certificate

The run leaves a verifiable record.

The same certificate format records steps, decision and integrity.

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

Example data — no production business data.

FAQ

Three practical questions.

Does Lokbox trigger payments or messages on its own?

No. Lokbox only repeats the browser workflow you defined. Before every defined external action, the run waits for your approval.

What happens when a portal screen changes?

Lokbox parks the run at the point of drift. A failed or parked run uses 0 credits.

What remains after the monthly run?

A Run Certificate with the run ID, time window, steps, approval decision, outcome, integrity hash and QR verification.

Your first Guarded Recurring Run

Set up the next property run with traceable evidence.

Try for free