Most documents captured in a session are filed inside a file and belong to a parent record. Occasionally an operator finds a loose document - a document sitting in a box on its own, not filed within any file. Because a loose document has no file to belong to, it must be marked as loose during capture. If it is not, its image is appended to the previous parent record and filed incorrectly.

The Loose Document button

The Loose Document button captures a loose document under a dedicated Loose Document Target instead of attaching it to the previous file. On the live camera feed, it sits next to the button used to capture standard document images (typically the Document button). It can also be assigned to a Stream Deck (mini controller) or a foot pedal. See Mini and Foot Pedal Controllers for how to assign buttons.

How it works

In a typical hierarchy the parent level is a file and the child level is a document, though a workflow can define these levels differently. The Loose Document Target takes the place of the parent record, and each loose document is captured as a child beneath it:

• The first press of Loose Document inserts the Loose Document Target, which becomes the parent record for the loose documents that follow.
• Each press after that captures a loose document as a child of the Loose Document Target.
• Loose documents continue attaching to the target as children until a new parent (file) image is captured.

Grouping loose documents under their own target - rather than under the previous file's parent record - lets each one be indexed individually and correctly identified as having been found loose.

In the hierarchy

The Loose Document Target appears as a parent in the Hierarchy Navigation tree, with each loose document nested beneath it as a child. When the target is selected, the preview displays the following message:

This document was identified as a loose document that was not filed within a file and could not be associated with a parent record. Accordingly, it is considered a loose document.