What it does
Retrieves defined property data from approved portals and prepares it for the monthly overview.
Lokbox for property management · Preview
Preview: this workflow is not yet available as a product. We clarify it in a pilot conversation and build it with selected firms. Defined property data often sits across several browser interfaces. You describe the retrieval once; Lokbox runs the task again and prepares the monthly overview for your review.
The run in four inputs
The workflow stays understandable even when it spans several browser steps.
Retrieves defined property data from approved portals and prepares it for the monthly overview.
At the monthly cut-off you define.
Do not submit to government authorities; you make those submissions yourself.
Outcome, approval decision and checksum in an issued signed run log.
The frame
WHAT / WHEN / NEVER / EVIDENCED
Four inputs keep the recurring run understandable and verifiable.
The problem
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
You describe the defined browser workflow once. Lokbox runs the task again at the chosen time, stops on drift and tries to issue a signed run log for the completed run; if none is issued, Lokbox shows that.
Run log
The signed log records outcome, approval decision and integrity.
Lokbox · Signed audit protocol
External action
Released · 1 logged entry
Checksum · shortened example
SHA-256 · 67c9 2a10 4f71 8b25 … d18b
FAQ
No. Lokbox does not initiate payments. A scheduled workflow also submits forms, messages and changes on other sites only after your yes.
Lokbox stops the run at the point of drift. You decide how to continue.
It shows the run's completion time, outcome, approval decision and checksum.
Your first run