Overview
An orphaned assignment is one that was created while completing a Checklist but no longer applies once the Checklist is finally submitted. This article explains how they happen and what becomes of them.
Users must be Super Users or have the following Role to view a Result:
Results: View
Why this matters: An Assignment created mid-inspection can be saved to the system before the Checklist is finished. If the situation changes before submission, that Assignment shouldn't silently vanish — surfacing it as "orphaned" keeps a transparent record of what was raised and why it no longer applies.
What are orphaned assignments?
They come from saved (not yet submitted) versions of a Result. An Assignment is created — manually or by a trigger — and the Result is saved locally or to the cloud, which creates the Assignment. When the Result is resumed and changed so the Assignment no longer applies, it becomes orphaned on final submission.
How they happen
Manual creation, then deletion — a User creates an Assignment while filling out a Checklist, then deletes it before submitting. It's orphaned because it wasn't in the final Result.
Triggered, then untriggered — an answer triggers an Assignment, then the User changes that answer (or logic hides the question). The triggered Assignment no longer matches the final answers.
Save and resume — an Assignment is created and the Result saved; on resuming, changes delete it or make the trigger no longer apply; on submission it's orphaned.
Where they appear
Orphaned assignments remain visible to Users with permission, in an Orphan Assignments section on the Result Report.
Best practice: Review the Orphan Assignments section periodically so nothing that was raised in the field is lost, and brief your team on why orphaned assignments occur.