Skip to main content

Lokbox for staffing agencies

TariTemp and Suva: prepared for review each month.

Recurring monthly cycles and occupation-code assignments demand care. Lokbox repeats the browser workflow you demonstrated, stops on drift and prepares the data for review. 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 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

Make no submission to TariTemp or Suva; you submit the report yourself.

ART. 04

What it did

Outcome, approval decision and checksum in the signed run log.

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 on schedule, stops on drift and makes the prepared data available for review.

Run log

The run leaves a verifiable record.

The signed log records outcome, approval decision and integrity.

Lokbox · Signed audit protocol

Run log

Signature · example
Issued
02.08.2026 · 07:34:09 CEST
Run completed
02.08.2026 · 07:34:09 CEST
Outcome
Completed
Human approval
Approved

External action

Released · 1 logged entry

Checksum · shortened example

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

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 the assignment and submit the report yourself.

What happens if TariTemp or a Suva page looks different?

Lokbox stops the run at the point of drift. You decide how to continue.

What appears in the log after the run?

The signed run log contains completion time, outcome, approval decision and checksum.

Your first run

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

Request a pilot