The Flagged queue — when hundreds share one reason

My Carriers — your slice of the queue

The My Carriers toggle narrows the list to the carriers you personally own. In the walkthrough that produces the all-clear state: zero documents, nothing waiting on this person. It is how a shared exception queue stays workable across a team — everyone sees their own backlog, and the global list is still one click away.

The row menu

Each row offers View, Detailed View, and Download. View is a quick look at the document; Detailed View opens the full review screen; Download pulls the original file for anything you need to send outside KnowDoc.

The three-pane review screen

Detailed View is laid out for one decision. The AI recommendation sits on one side, the data currently in your system on the other, and the source PDF beside both — so you are comparing two claims against the page that either supports them or doesn't, without switching windows.

• AI recommendation — What KnowDoc read, and the flag it raised.
• Current data — What the TMS already holds for this load.
• The PDF — The document itself — the tiebreaker.

Clear Flag

Clearing a flag steps both the queue counter and the sidebar badge down together. Clear when the document answers the flag — the missing POD is on page two, the load number was in an unexpected field. Do not clear to make the number smaller: a flag cleared without a reason is worse than a flag left standing, because the next person assumes it was checked.

What hundreds of identical flags actually mean

They mean one fix, not hundreds of reviews. A queue dominated by one reason on one carrier is a configuration problem, and the configuration lives on the Carriers page. Clear the individual documents if you must, but the work that makes the queue stay small is upstream — which is exactly what the AI Agent walkthrough sets out to prove.