Help article
What counts as completion evidence?
Understand why a completed workflow should be backed by evidence rather than a status label alone.
Applies to: Users reviewing completed compliance workReviewed 2026-08-15
Evidence depends on the task
The correct evidence depends on what was done. Examples can include a submission acknowledgement, assessment, certificate, filed document, payment confirmation, signed output, or another record that supports the stated outcome.
Why Didiserv keeps the evidence with the task
- It separates a claimed outcome from a supportable outcome.
- It gives the client and reviewer a common record of what was done.
- It makes later follow-up, dispute handling, and recurring compliance work easier to trace.
Still not resolved?
Bring the affected business, task, payment, or integration context with you so support can diagnose the real issue instead of starting from a generic description.