Who clears a request that the inspection app never saw?

That is happening here. The PLC contractor calls received 'done', while the developer means inspection finished. I'll get those names agreed before the timing discussion.

A table helps, but make them walk through a disconnect with a request outstanding; otherwise both can agree on bit names and still build incompatible recovery.

The drawing is useful. I would still keep the table as the precise definition. Draw the wait states as well as the successful exchange, or the page makes every problem look momentary.

They've agreed the app acknowledges acceptance, not completion. PLC holds the request until that acceptance. Restart with an outstanding job is still blank, so Aisha's example is next.

Give that example an actual job reference, and ask both developers what they would display after reconnecting without knowing whether the inspection finished.

And Maya, ask who gets called when it stays in that state. Our supplier gave a very neat answer that depended on a programmer being on site. Expensive little footnote.

We've added an unresolved state to the proposal. No automatic second inspection from that state. The two developers still disagree on which side retains the job details through restart.

Hazel, thank you for the callout question. Neither support quote covered reconciling an interrupted job. I have asked them to price and explain that work explicitly.

Is the retention decision still open? I would leave a named owner beside it in the handover draft. Otherwise this is exactly the sort of blank people assume the other contractor filled.