Guarded Recurring Runs for staffing agencies

TariTemp and Suva: prepared for the month, submitted only after approval.

Recurring monthly cycles and occupation-code assignments demand care. Lokbox repeats the browser workflow you demonstrated, prepares the review point and pauses before the defined submission. Especially in deployment-heavy sectors like construction and logistics, where CBA supplements and Suva risk groups vary per assignment, the prepared occupation-code mapping matters.

The frame

WHAT / WHEN / NEVER / EVIDENCED

Four inputs keep the recurring run understandable and verifiable.

The problem

Monthly cycle. Personal accountability.

Review data, assign occupation codes and repeat the TariTemp/Suva workflow: the sequence is familiar, but small changes must not pass unnoticed into a submission.

The controlled run

Let it prepare. You decide.

You demonstrate the defined monthly workflow to Lokbox once. The run repeats the steps to schedule, parks on drift and waits for your explicit approval before submission.

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

Repeats the defined TariTemp/Suva monthly cycle and prepares occupation-code assignments for review.

ART. 02

When it runs

At the point you define in the monthly cycle.

ART. 03

What it must never do

No code submission and no defined external action without your approval.

ART. 04

What it did

Step sequence, 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 decide the occupation code itself?

No. Lokbox prepares the assignment along the workflow you demonstrated. You review and decide before submission.

What happens if TariTemp or a Suva page looks different?

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

What appears in the certificate after the run?

The Run Certificate contains the run ID, time window, recorded steps, approval decision, outcome, integrity hash and QR verification.

Your first Guarded Recurring Run

Set up the next monthly cycle with a clear review point.

Try for free