CORRECTION WORKFLOW
How to handle an incomplete contractor completion return
An incomplete return should not disappear when a corrected version arrives. Keeping both versions makes the operational decision easier to understand.
Reject the submitted version clearly
Record which version is being rejected and why. Avoid a general request to “send this again” when a specific reference, declaration or file descriptor is missing.
Request a bounded correction
Describe the missing or inconsistent item without silently changing the original scope. If the work instruction itself has changed, issue a new instruction version.
Create a new return version
The provider’s corrected submission should be a new version linked to the rejected return. The original remains available for the authorised record.
Accept the exact corrected version
The requester’s final decision and receipt should identify the corrected version that was reviewed. Acceptance alone does not prove the truth of a declaration or the physical quality of work.
APPLY THE WORKFLOW
See the complete instruction-to-return sequence.
Verified Dispatch provides a controlled contractor instruction and completion-return record while preserving the distinction between a digital workflow decision and independent proof of real-world work.
See how Verified Dispatch worksDiscuss a controlled pilot