Skip to content
MirrorFirm

What does a document sufficiency decision look like on a real home loan file?

A loan processor at Aster Financial receives a home loan application with incomplete income evidence and must decide between proceeding and requesting items, with a measurable downstream consequence.

At Aster Financial, a broker lodges home loan application `APP-2187` for two applicants. The loan processor opens the file and compares it against the income-evidence policy `POL-INC-04`.

**Supplied:** photo identification for both applicants, a signed application form, two payslips for applicant one, and a bank statement covering one month.

**Required by policy:** identification, the signed form, two recent payslips for each applicant, and three months of statements for the nominated account.

The processor finds three gaps: no payslips for applicant two, two missing statement months, and a form version that predates the current declaration wording. The processor does not forward the file to the credit officer. Instead the status of `APP-2187` moves from Received to Awaiting information, and request `REQ-0931` goes to the broker listing the three items, each tied to the policy clause that requires it.

The broker returns the items. The processor re-checks, records each requirement as met, and moves the file to Ready for assessment.

Had the file gone forward as it was, the credit officer would have returned it, adding a second handover and a second review of the same documents.

**What it teaches:** sufficiency is checked against a named policy, the request must be specific and traceable, and the status change is the observable result. A model is judged on the gap list, not on a general reply asking for more documents.

The scenario shows how one early judgement changes a file's status, handovers and rework, which is the signal a model needs to learn.

Audience:
Model labs
Content type:
Scenario
Buyer question:
What it is and why it matters

Content release: r-a220eb6e099b243b

More on Document sufficiency