Every doc filed out of Unassigned leaves a record — search it by doc, by transaction, or by the person who did the filing.
Introduction
An agent swears she emailed the disclosure in, and she has the acknowledgement to prove it. It isn't on the transaction where she expected it. Now two people are hunting for one document in two different places.
Almost every time, the doc arrived fine and then somebody filed it. Assignment History is the log of that filing. When a doc leaves the Unassigned Docs queue it writes one line here: which transaction it went onto, who put it there, and when. That's the assignment event by itself, kept apart from everything that happens to a doc afterwards, so you get a short, fast log rather than a full audit trail to read through.
One look usually ends the conversation. The common answer is that the doc went onto the transaction directly above or below the right one, and seeing that is most of the work. From there your trail carries on where the doc now lives: the transaction's own history holds what happened after the filing, including who reviewed it, who changed it, and who took it off again.
How It Works
One log, searchable, covering the moment a doc left the queue.
What It Records
Docs assigned out of Unassigned: the doc, the transaction it went to, and the person who filed it. It's the assignment event specifically — not everything that ever happened to the doc.
Where It Lives
On the left menu of the Unassigned page, alongside the deleted docs bin. Newest first by default.
Search It
You can search the log by doc, by transaction, and by the person who did the assigning, and narrow it to a date range. Accounts running more than one office can widen the view to cover the whole company rather than a single location.
Who Can See It
The full company-wide log is a master admin view. Someone without that reach may see a narrower slice or none of it — which is worth knowing before you ask a colleague to check something for you.
What It Doesn't Cover
Deleted docs aren't assignments, so they aren't here — the deleted docs bin holds those. And once a doc is on a transaction, the transaction's own history records everything that happens next, and that is the fuller audit trail: uploads, assignments, deletions, reviews, all searchable by activity type.
Open Assignment History
The log of everything filed out of the queue, two clicks from the top menu.
Who Can Do This: Master admins see the full company-wide log; other roles may see a narrower view or none.
To open Assignment History:
- Click [Unassigned] from the top menu.
- Click [Assignment History] from the left menu.
The log opens newest first, so the most recent assignments are at the top.
Trace Where a Doc Was Assigned
Find out which transaction a doc ended up on — the fastest answer to "where did it go?"
Who Can Do This: Master admins see the full company-wide log; other roles may see a narrower view or none.
To trace where a doc was assigned:
- Click [Unassigned] from the top menu.
- Click [Assignment History] from the left menu.
- Search for the doc by name, or narrow the log to the date range it would have been filed in.
- Read the transaction it was assigned to, and who filed it.
If it's listed, open that transaction — a doc reported missing has usually been filed somewhere unexpected. If it isn't listed at all, check the deleted docs bin next.
When the Log Comes Up Empty
An assignment that never happened doesn't get logged, which leaves one other way the doc could have left the queue. Somebody deleted it, and that has its own page.
Delete a doc and it doesn't vanish. It lands in Deleted Docs, where it stays for a year with a record of who removed it and when.
See Deleted Docs
Assignment History FAQ
Assignment History logs what left the Unassigned queue, where it went, and who sent it there. Answers to the common questions about how far back it reaches, who can open it, and what it leaves out.