Why it matters
A processor's day is a queue: files with documents to chase, uploads to review, and packages to get out. Deals that sit in collecting docs for a week usually die there. Working the queue in the same order every day keeps the oldest files from slipping.
No separate queue screen
The CRM does not have a dedicated document queue page today. Your queue is the Deals screen filtered to the stages where documents matter, plus the checklist on each deal. The steps below set that up.
Step by step: build the queue
- 1Open Deals and switch to Table.
- 2Open the Stage filter and pick App In - Collecting Docs and Contracts Signed - Final Stips. These are the two stages where files wait on paperwork.
- 3Sort by In stage so the deals that have waited longest are on top. Days in stage turn amber at 7 and red at 14.
- 4Optionally filter Age in stage to 3+ days in stage to see only files that are starting to stall, or Rep to work one rep's book.
- 5Bookmark the page. The filters are saved in the address, so the same queue opens tomorrow.
- 6Open each deal. The Documents & stips tab shows how many checklist items are missing, and the yellow Before Ready for Submission box names them.
Processors see every deal in the organization, not just their own. The Processor shown on a deal is set by a manager (in the deal's Edit window); the Deals filters do not filter by processor, so filter by stage and rep instead.
Working each file
On every deal you open
0 of 5Use Tasks (Overdue and Today) alongside the board. Tasks you get from a teammate's note (Notify…) link straight to the deal.
Tips
- Run the same filter with Ready for Submission to see files waiting for a package (see Preparing the submission package).
- The dashboard's open pipeline groups deals into collecting docs, with funders and closing, which is a quick read on how heavy the queue is.
Try it in the app
Signed in? Open the screen this lesson covers.
Finished this lesson?
0 of 8 lessons in Processor playbook
Progress is saved in this browser. Sign in to keep it across devices.
Related lessons
- Processor playbookReviewing, verifying and tagging documentsCheck every upload before it goes to a lender: right type, right month, all pages. Verify it, reject it with a reason, or fix its type.
- Sales rep playbookRequesting documents and stips from the merchantSet up the deal's document checklist, send the merchant one clear request for everything outstanding, upload what comes back and keep the count honest.
- Sales rep playbookRunning your deals on the boardRead the Deals board, move deals between stages, see what each stage needs before it lets a deal through, and spot stale files before they die.
- Start hereTasks, notes and the timelineWhen to write a note, log a call or set a task, how status changes appear on the timeline, and how due dates, assignment and the Tasks page work.