COMPLETION RETURN GUIDE
What should a contractor completion return contain?
A completion return is most useful when it answers the requester’s stated requirements and remains connected to the exact instruction the contractor received.
Core return information
The appropriate fields depend on the workflow, but the return should usually identify the instruction version, provider, declared action, relevant references and submission time.
Evidence metadata is not evidence authentication
File names, media types, timestamps and provider descriptions can be recorded. That does not independently establish who created a file, where it was created, whether it is authentic or whether the underlying work was adequate.
Make review a recorded decision
The requester should be able to accept the submitted version or reject it with a specific correction request. Acceptance records a workflow decision; it is not automatically a technical certificate or payment approval.
Retain the accepted version
A final receipt should point to the accepted submission rather than presenting an overwritten “latest” record with no visible history.
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