The problem
Many portals. Recurring renewal work.
Reviewing portfolio data and collecting renewal information follows a familiar rhythm. Different interfaces and changed fields still make manual repetition error-prone and hard to evidence.
Guarded Recurring Runs for insurance brokers
Collect renewal data from portals before anything goes out.
Recurring portfolio and renewal checks are spread across different browser interfaces. Lokbox repeats the workflow you demonstrated, bundles defined data for review and waits for your approval before every external action.
The frame
WHAT / WHEN / NEVER / EVIDENCED
Four inputs keep the recurring run understandable and verifiable.
The controlled run
Prepare the data. Keep the decision.
You demonstrate the defined portal workflow once. Lokbox repeats it to schedule, prepares the data in the AES-256-GCM encrypted dossier and pauses before every defined transfer.
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 portfolio and renewal data from approved portals and bundles it for review.
ART. 02
When it runs
At the point you define in the renewal cycle.
ART. 03
What it must never do
No external action and no defined transfer 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
Recorded steps
- 01Approved source opened✓
- 02Accounting period selected✓
- 03Data set prepared for review✓
- 04Approval gate reachedDECISION
- 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 assess or recommend insurance offers?
No. Lokbox repeats the browser workflow you demonstrated and prepares defined data. Assessment, decision and approval remain with you.
What happens when a portal changes?
Lokbox parks the run at the point of drift instead of guessing. Failed or parked runs use 0 credits.
How is the workflow documented?
The Run Certificate contains the run ID, time window, steps, approval decision, outcome, integrity hash and QR verification.
Your first Guarded Recurring Run