Work in motion

One job. The whole picture.

See what software can handle, where a person decides, and what happens when something goes wrong.

Explore an example

Illustrative simulation

Who may do what

All people, records and outcomes are fictional. No AI service runs, no message is sent and no business system is connected. State lasts only in this tab; reloading resets it.

What this example shows—and what it doesn’t

It explores a proposed division of work, version-specific decisions, holds and recovery in one simulated plumbing job. The four arrangements are candidate interpretations, not calculated classifications or a maturity ladder. Human involvement can be the intended outcome.

It does not prove real identity checks, reliable execution in a business, or genuine customer consent. Those need to be established with the people, systems and responsibilities of each business.

The example, without playback

JavaScript is needed to explore the changing record. The underlying story is:

Software records an enquiry; the office checks the booking.
A technician records the finding. Software prepares quote options; the office chooses scope and terms.
A named person examines the evidence and signs that quote version. The customer agrees separately.
Completed work supports an invoice. A reported problem holds unsent follow-ups and returns responsibility to a person.
Return work, customer confirmation and an explicit closure support a new check of each held action. Eligible does not mean sent.

.case-bar,#instrument,.skip{display:none}