How to automate mortgage application disposition and required notices
TLDR
Start the applicable notice clock from the actual application event. Track incomplete files, withdrawals, counteroffers and adverse decisions separately, then record delivery evidence and any work that must survive a stop.
Start the applicable notice clock from the actual application event. Track incomplete files, withdrawals, counteroffers and adverse decisions separately, then record delivery evidence and any work that must survive a stop.
Follow the loan manufacturing workflow to see where this work starts and what depends on it.
Can the lender stop a silent applicant’s file as withdrawn?
Silence by itself leaves withdrawal unverified. Determine whether the application is complete or incomplete under the applicable rule, preserve the original deadline, and route any required notice to its authorized owner.
Example. The applicant has not replied to a request for a missing bank statement. Keep the file in the applicable incompleteness workflow. A documented express withdrawal can stop unnecessary reminders while preserving the file and any remaining duties.
Who owns the action. The authorized lending or compliance owner confirms the disposition and notice. Loan operations stops affected work after the decision.
What starts the work and what should be recorded?
Record the file or cohort, governing program and rule version, original event and timestamp, current evidence revision, authorized owner, open reason and due date. Store the disposition and actual destination receipt separately.
Reconcile existing activity by the original operation key before attempting an authorized repeat. Preserve the earlier record when corrected evidence changes a decision.
What should the workflow check at each step?
Record actual completeness and the action deadline
Record when the creditor received the completed application. For applicable consumer applications, Regulation B generally requires notice of approval, counteroffer or adverse action within 30 days of that event. Escalate an approaching deadline even while the decision is pending.
Handle incompleteness and returning evidence
For applicable incompleteness the applicant can complete, select the permitted action or written incompleteness notice within the relevant 30-day period. An incompleteness notice specifies what is missing, a reasonable response deadline and the consequence of no response. A timely response reopens the affected review steps.
Track actual counteroffer notification and later acceptance
Record when the applicant was actually notified and whether they expressly accepted or used the credit. If an applicable counteroffer is unaccepted, track the separate 90-day adverse-action deadline unless a compliant combined notice already satisfied the requirement.
Prepare and confirm an authorized notice
Use the current authorized decision and applicable notice requirements. When giving specific reasons, use the actual principal reasons for the decision. Preserve the authorized notice version, recipient, dispatch evidence and corrections. A draft or queued send leaves the delivery state open.
Stop affected work and preserve surviving duties
Record an express withdrawal or other authorized disposition. Cancel affected orders and reminders the lender can stop, reconcile fees, and keep any surviving notice, retention and reporting obligations open. For an applicable rescission, route actual notice, creditor refund or security-interest action, and any later tender through their separate events and authorized owners. CFPB right of rescission.
Retain records and reconcile reporting
For covered consumer applications, Regulation B generally sets a 25-month retention period with different anchors by disposition and applicable holds. Route reportable actions to the HMDA reporting owner and preserve their action dates separately from the notice clock.
Test the decision with synthetic records
| Case | Deciding evidence | Expected result |
|---|---|---|
| Completed and undecided | Actual completed receipt is known and the decision is pending. | Keep the original action deadline active and escalate before it is due. |
| Silent and incomplete | The applicant has not replied or expressly withdrawn. | Keep the applicable notice obligation and assigned owner. |
| Express withdrawal | Authorized evidence records the applicant's express withdrawal. | Stop affected reminders and retain the record. |
| Unaccepted counteroffer | Actual notification is recorded and no compliant combined notice exists. | Track the applicable follow-on notice clock. |
| Adverse notice queued | Authorized content exists with no confirmed dispatch evidence. | Keep notice delivery open. |
Run this example with Python 3. It evaluates the named synthetic decision and makes no system changes.
def next_action(complete, express_withdrawal):
if express_withdrawal:
return "stop affected reminders and retain records"
if complete:
return "track action deadline from completed receipt"
return "review incompleteness notice requirement"
assert next_action(False, False) == "review incompleteness notice requirement"
assert next_action(True, False) == "track action deadline from completed receipt"
assert next_action(False, True) == "stop affected reminders and retain records"
print("Silence, a completed application and an express withdrawal produce distinct outcomes.")
Build it yourself with AI
Use actual application and notice events, the authorized decision, the
applicable rule and approved notice template. Determine the exact source event,
due date and responsible owner. Return the disposition, governing evidence,
notice version, delivery receipt or open reason, and the work to stop or retain.
Do not infer withdrawal from silence or issue a credit decision. Keep dispatched
notices, superseded records and downstream reporting references separately.
Keep the exact accepted source versions and the approved comparison. A pending external act remains an owned item until its actual receipt or authorized disposition is recorded.
