The Processor’s Playbook.

Identify purchase or refinance, occupancy, property type, borrower entity, self-employment profile, statement type and period, expense treatment, deposits requiring explanation, reserves, prepayment terms, and the intended integrated or manual lender. Do not label a file merely “bank statement” when the qualifying method has not been selected.

Verify application data, property, vesting, liabilities, REO, income fields used for disclosure or AUS purposes, loan purpose, occupancy, product, fees, compensation, and contact roles. Record the alternative-income method in the approved notes or task structure without putting sensitive documents in informal channels.

Keep personal and business statements in chronological order, identify every account and missing page, separate calculation worksheets from source statements, and flag large or irregular deposits for the lender’s required treatment. ARIVE’s own guidance says all documents should remain in ARIVE as the system of record.

For an integrated lender, verify the functions that ARIVE actually supports—pricing, loan submission, document submission, or portal sync are not universal. For a manual lender, export the current MISMO 3.4 file when appropriate and reconcile the imported lender record before uploading the indexed package.

Map every lender condition to a responsible party, responsive evidence, submission date, and current lender status. Keep superseded calculations and statements out of the active response package while preserving the brokerage’s required record.

Confirm the property state, occupancy, purpose, borrower profile, product parameters, reserves, asset documentation, credit events, appraisal path, and any broker or lender overlays. Program names and requirements can change, so save the guide version used for the submission decision.

Collect the identity, credit, asset, property, title, insurance, occupancy, purchase or payoff, entity, and explanation documents required by the current guide. Do not upload income or employment material by habit if the selected program and lender instructions do not call for it.

Verify the submitted loan purpose, occupancy, property, borrower, assets, declarations, liabilities, loan amount, fees, compensation, and program selection. A clean portal record matters because later appraisal, change-of-circumstance, CD, and condition workflows depend on the lender’s actual loan data.

Upload evidence to the applicable condition or lender workflow, add concise context only when it helps the reviewer, and record the package submission point. Change publishes self-service workflows for uploads, locks, appraisals, changes of circumstance, and CD requests; the processor uses the current workflow for each action.

Track submission and review status, but keep borrower response, appraisal, title, broker decisions, lender review, disclosure, and settlement dependencies separate. Current portal status and lender communication control the file plan.

The lender’s Encompass configuration can use standard or enhanced conditions and role-based permissions. Verify what the brokerage user can view or edit, work from the live condition list, associate documents with the intended condition, and confirm that the status changed after upload rather than assuming the file transferred.

Use the broker’s authorized EASE access and the current UWM workflow for document delivery, conditions, appraisal, disclosure, and closing tasks. Reconcile the EASE record with the brokerage LOS, then use UWM’s current support and escalation lanes for a question that requires lender action.

A good response contains the exact requested document set, all pages, legible data, a short explanation when context is necessary, and no conflicting duplicate. If one document answers multiple conditions, follow the portal workflow without creating contradictory versions.

Those are different states. The processor records when evidence was sent, confirms the portal received it, monitors lender review, and does not report a condition as cleared until the lender’s live status says so.

Name the loan, exact condition, prior submission, open question, requested decision, and time-sensitive dependency using the approved secure channel. Do not bury the issue in a general status email or send borrower nonpublic information through unapproved tools.