Workflow Intelligence —
structured records from the work itself

Inside the record

A record is not a transcript.

Where a value comes from

field value filled by

Someone on the job

hours

8.0

Worker

approval

Approved

Manager

ppe_missing

none

Safety

client_sign_off

Accepted

Client

invoice_status

Ready to Invoice

Finance

The layer itself

ai_summary

pour clean, crew off deck

AI

report_id

RPT-1042

System

billable_hours

7.5

Calculated

When it does not arrive

the field rule the record what happens

Ask again

Retry back to capture

The layer answers in the thread the message came from and asks the sender for the one value it is missing — capture runs a second time on the same record.

Block submit

Held nothing routes

The report cannot be closed while the field is open. In the form the worker sees, the field carries an asterisk — the rule is visible before the gap happens.

Manager review

Moves on flagged

The gap is marked for the manager on the approval route the record already travels. Nothing waits for it: the row lands in the systems downstream carrying its flag.

Default

Moves on filled by the job

Nobody is asked, because the job already answers: the project, the work code and the rates it carries fill the slot the moment the record is created.

Allow empty

Moves on counted as open

The field stays open and the record says so. How much of a report is filled is a column on the row, not a promise — a half-empty report is readable as a half-empty report.

Not asked

Moves on not in this form

This job type never asks for it, so there is no gap to explain. The same form, set up for another kind of work, would put the question back.

The eight roles and the six rules are what the product defines. The form, the field names and the values above are illustrative — drawn to show where a value goes missing and what each rule then does to the record.