Instruction v1
Fictional Aster Quay Facilities records a roof-drainage inspection at unoccupied Unit AQ-4 for Northlight Building Services.
CONTROLLED WORKFLOW
How contractor instructions and completion returns stay connected.
Verified Dispatch records what the requester sent, whether the intended provider accepted it, what the provider returned, any correction and the exact version the requester approved.
- 01
Instruction created
An authorised requester records the bounded scope, intended recipient and operational context.
- 02
Provider response
The intended provider accepts or declines. Acceptance confirms the recorded response, not physical attendance.
- 03
Declared return
The provider submits completion information and evidence metadata against the instruction version.
- 04
Requester review
The requester accepts the submitted version or rejects it with a correction request.
- 05
Versioned receipt
The accepted provider submission, validated receipt and explicit requester sign-off stay connected.
WHOLLY SYNTHETIC PROOF EXAMPLE
See exactly what the record connects.
Every organisation, property, reference, recipient and file descriptor in this example is fictional. It demonstrates the record structure without dispatching real work.
DISPATCHVD-DEMO-1048
Provider response
Northlight records acceptance of instruction v1. This is a response event, not proof of identity or attendance.
Declared return v1
The provider declares its actions and returns metadata for three synthetic files. The files are not independently authenticated.
Correction CR-1
The requester rejects return v1 because the elevation reference is missing and requests that bounded correction.
Declared return v2
Northlight returns the corrected fictional elevation reference AQ4-N against the same instruction.
Accepted receipt
Receipt VD-DEMO-1048-R2 connects instruction v1, accepted return v2 and the requester sign-off.
DEFINITION
What “verified completion” means here.
“Verified completion” means a tenant-bound accepted provider submission with declared evidence metadata, a validated and versioned Verified Delivery receipt, and explicit requester sign-off.
This is a product-specific workflow definition. It is not an assertion that the platform independently verified identity, attendance, location, evidence truth, work quality or regulatory compliance.
Read the complete claim boundary