Notice of incompleteness
How do we send a notice of incompleteness listing exactly what is needed and the deadline, chase the responses and close or complete the file on the date?
Make the notice a list the process already knows. When an application is missing information the lender needs to decide, Callvu classifies the gaps from the document and verification processes, produces the notice of incompleteness naming each item and a reasonable deadline, delivers it by the consented method, chases each item with the party that owes it, updates the file as responses arrive, and on the deadline either completes the application (starting the 30-day decision clock) or closes it with the right notice and the HMDA action.
In scopeComplex: multi-party handoffsCallvu moves: classify, chase and verify, write back
Last updated November 7, 2026.
The problem today
The file has been 'waiting on the borrower' for 45 days, and no notice was ever sent.
A mortgage application stalls because a document never came. The processor's needs list is an email. Weeks pass. Reg B requires the lender either to send a notice of incompleteness, naming the information needed and a reasonable time to provide it, or to send an adverse action notice within 30 days; it does not allow a file to sit. The HMDA register needs an action taken and a date, which a sitting file does not have.
The notice is a courtesy to the borrower and a protection for the lender: it stops the 30-day clock in a documented way, and it makes the close-out on the deadline lawful. Done by hand, it is sent late, lists items vaguely, and is not followed.
The missing items are already known to the process that chased them. The notice is a report on that list.
How it runs
From the requestto the system of record.
An application reaches the point where the lender needs information to decide and the document and verification processes show items outstanding past the policy's threshold. Callvu opens the incompleteness case.
- Processor
- Confirms the list where the policy requires and sees the deadline and the responses.
- Borrower
- Receives the notice and provides the items, or does not, by the deadline.
- Callvu
- Classifies the gaps, produces and delivers the notice, chases, updates the file and acts on the deadline.
Classify the gaps
The outstanding items from the document and verification processes are classified as information the lender needs to decide (versus conditions that follow a decision), which is what the notice may list. The deadline is set by the lender's policy as a reasonable period from delivery.
Produce and deliver the notice
The notice of incompleteness names each item specifically, states the deadline and that the application will not be considered further if the information is not received, and is delivered by the consented method inside the 30 days from the application. The delivery is recorded.
Chase and verify
Each item is chased with the party that owes it through links, as in document collection; responses are read and matched to the items; the file shows what remains and the days left.
Decide on the deadline and write back
If every item arrives, the application is marked complete on that date and the 30-day decision clock starts; the file proceeds. If not, on the deadline the application is closed for incompleteness with the notice the lender's policy chooses (a reaffirmation of the incompleteness notice or an adverse action notice) and the HMDA action 'file closed for incompleteness' with its date; everything is written to the LOS.
Where it ends: The borrower was told exactly what was needed and by when, the items were chased, and on the deadline the file was completed with the decision clock started or closed with the right notice and HMDA action. The Decision Trace shows the gap classification and the deadline; the Audit Trace shows the notice, the chases and the outcome.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The file's own outstanding items; the borrower meets the process in the notice and the links.
The back office
The processor confirms the list where required and sees the deadline; the file never sits without a date.
The Decision Desk
- A list the classification cannot settle (whether an item is needed to decide or is a condition), or a request to extend the deadline, goes to the processor or underwriter in the Decision Desk with only the allowed outcomes.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
Questions
What buyers ask next,answered plainly.
What does the notice list?
Each specific item the lender needs to decide, taken from the file's outstanding items, with a deadline and the statement that the application will not be considered further without them.
What happens on the deadline?
The file is completed, starting the 30-day decision clock, or closed for incompleteness with the notice the policy chooses and the HMDA action and date.
Does the notice stop the TRID clock?
No. The Loan Estimate clock from the application date runs regardless; both are tracked on the file.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.