Work Order Checklist Results vs Versions

Modified on Sat, Mar 11, 2023 at 1:42 AM

TABLE OF CONTENTS


Work Order Checklist Result Lifecycle

The scheme shows the lifecycle of the Work Order checklist result, depending on who uploads a result and where (Close-Out dashboard or mobile app).


If you upload a new result or a version of the item, that has already been approved, or rejected, or marked as 'do not submit', a new result of the checklist item will be created. The result status depends on how you have uploaded it.

 

To zoom in the image → right click and open the image in new tab.





A note on Versions vs Results

Results

Checklist Items are just "to-dos" and the same Checklist Item can appear in many WOs/Dispatches.

  • If the work scope was the same, a Dispatcher might have attached a Checklist Item to both WO #1 and WO #2 even if they are in different Sites.

Results are created when a user takes a Checklist Item photo or uploads a document for it or add just a comment.

  • A Result uploaded by a crew on WO #1 is specific to that WO and is not seen by the crew in WO #2.
  • The WO #2 crew will upload their own Result for the Checklist Item under WO #2.




Versions

Users often retake or reshoot photos if the previous one is not good. This produces additional Versions of the Result.


The Reviewer sees the latest Version uploaded by default, but can go back and look at older Results if desired. They can approve an older Version and not use the latest one if they want.


Normally just one Result is produced per checklist Item: when the Package is exported, there is 1 file per Item.

But it is possible to export multiple files for a single Item if multiple Results are uploaded for it and approved.


Finally, Reviewers can create Results from Versions. This is useful if 2 Versions are both good, and you want to export them both in the Package.

 


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article