Underwriting conditions: the record shape that lets a rule clear one
In short
An underwriting condition is a named requirement attached to a credit approval that must be satisfied before a file passes a stated stage — not a comment in a notes field. Whether software can clear it is decided by the record: evidence type, acceptable source, a checkable satisfaction rule, an owner, and the stage it gates. Free text can only be closed by a person.
Key takeaways
- A condition is a structured record with a stage gate, not a line in the underwriter's notes.
- The satisfaction rule is the field that decides automatability; free text guarantees manual clearing.
- Stage matters: a prior-to-funding condition blocks money, a post-funding one needs a servicing tickler.
- Evidence has a validity window, so a stalled file quietly re-opens conditions that were already cleared.
An underwriting condition is a requirement recorded against a credit decision that must be satisfied before the file may pass a named stage. The approval is real and it is fenced: a conditional approval says yes, provided these 6 things arrive and check out. What decides whether the system can clear one without a human is not the model reading the document. It is the shape of the condition record.
Condition, stipulation, exception: three objects that behave differently
The three words are used loosely and behave differently. They close by different routes, are approved by different people, and only one of them is evidence of a policy breach.
| Object | What it is | What closes it | If it never closes |
|---|---|---|---|
| Condition | A requirement the approval depends on | Evidence satisfying a stated rule, or a documented waiver | The file cannot pass its stage gate |
| Stipulation | A document or item the borrower must supply | Receipt and validation of that specific item | The condition it feeds stays open |
| Exception | A decision to lend outside written policy | Approval at the authority level the policy names | Not applicable — an unapproved exception is a breach, not a queue item |
The fields that decide whether a rule can close it
- Condition type, from a controlled list. Free-text titles make every condition unique, and a rule can only be written against a class that recurs.
- Stage gate. Which stage this blocks, stated explicitly rather than implied by where it was raised.
- Borrower-facing statement. What the applicant is being asked for, in language that can be sent without editing.
- Required evidence. The document type and the 4 attributes it must carry: issuer, period covered, named party, signature.
- Acceptable source and freshness. Who may issue it and how recent it must be; a payslip 90 days old and one from last week are not interchangeable.
- Satisfaction rule. A predicate over extracted fields: employer matches the application, net pay is at least the declared figure, the period ends within 45 days. This field is the whole question of automatability.
- Owner. Borrower, broker, lender, valuer, insurer — or a third party with no relationship to you at all, which is why files stall.
- Waiver authority. Who may close it without the evidence, at what level, with what recorded reason.
- Closure record. Status, timestamps, who or what closed it, and a pointer to the exact document version relied on.
Income conditions show why the satisfaction rule matters. Income is verified is unimplementable. Average net salary credits over 3 statement months is at least the declared figure is implementable, and carries a known weakness, since a statement analyser can read inflows as income that were never income. Naming the rule makes that weakness visible instead of burying it in a judgement.
Stage gates decide what a condition can actually block
- Prior to approval. The decision is not final until it clears. Anything genuinely credit-critical belongs here, or the approval is not an approval.
- Prior to documents. The agreement cannot be issued — typically identity, valuation and security items whose absence would make the contract wrong.
- Prior to funding. Money does not move. Wire this gate to the disbursement step itself: the payment instruction is its own object, and refusing to create one is a harder control than a status field nobody checks.
- Post-funding. The loan is live and something is still owed to the file: a registration, a certificate, a counter-signature. Without a servicing tickler carrying a 30-day due date and an owner, these are forgotten.
Free text is why nothing automates
A condition reading satisfactory explanation of the large deposit cannot be cleared by software, because the requirement has no test. Rewritten as a predicate — a credit above 40,000 must match a payroll credit, a documented gift with a signed letter, or an asset sale with a contract — it becomes 3 checkable cases plus a residual that reaches a human by design rather than by accident.
A condition nobody can test is not a control. It is a note that stops a loan, and it will be closed by whoever gets tired first.
Moving a condition class from manual to rule-cleared is a staged method with a shadow-running step, and it belongs to rules that clear conditions without a human. What this record shape gives you is inspectable history: which conditions were waived, by whom and under what authority — a question a buyer asks of a loan tape, and the first thing to check when a first payment default is reviewed.
Building the clearing path as small, testable rules, with a permanent maker-checker gate on the classes that must never be automated, is ordinary AI agents and automation work — with the containment patterns of any system acting unattended against real records, as in AI agents in production. It sits inside lending and credit operations, part of the finance systems we build.
Frequently asked questions
Short answers to the follow-ups this page tends to raise.
What is the difference between a condition and a stipulation on a loan file?
A condition is the requirement the approval depends on; a stipulation is a specific item the borrower must supply to satisfy it. One condition can have several — prove 3 months of income is the condition, the payslips and the bank statement are the stipulations. Modelling them separately is what lets a system report 2 of 3 items received rather than a bare outstanding status.
What does prior to funding mean on a conditional approval?
It means the condition blocks disbursement rather than the credit decision or the documents. The 3 gates run in order: prior-to-approval conditions clear before the decision is final, prior-to-documents before the agreement is issued, prior-to-funding before money moves. The strongest implementation makes the disbursement instruction impossible to create while any prior-to-funding condition is open.
Which underwriting conditions can be cleared automatically?
Only those whose satisfaction rule is a predicate over extracted fields — identity documents matching the application, a valuation above a stated figure, an insurance certificate naming the right party for the right period. Anything phrased as satisfactory explanation or underwriter comfort has no test, so it should be rewritten as checkable cases or accepted as permanently manual.
- lending
- underwriting
- data modelling
- loan origination
The work behind this page
Builds from our portfolio that this page draws on.
LoanForge
An AI mortgage loan-origination platform that extracts borrower data from documents, auto-clears underwriting conditions, and drives every loan to clear-to-close.
Real EstateAP Copilot
An AI accounts-payable copilot that reads invoices, matches them to POs, and routes clean approvals
FintechAskVault
An AI internal knowledge-search platform that answers employee questions from your own docs — grounded in citations, with knowledge gaps surfaced and deflection tracked.
Productivity AIRead next
- The loan tape: whether your book is legible to anyone elseA loan tape is one row per loan, assembled to a counterparty's template. It is cheap to produce only if your servicing model stores state transitions rather than current status.definition
- Decline reason codes: what to record at the moment of the decisionA reason recomputed from today's data is not the reason the applicant received. Bureau values, balances and documents move, so the reason belongs in the same transaction as the decision.definition
- First-payment default is an origination defect, not a collections eventA borrower who never makes payment one is rarely a credit decision that aged badly. The instrument was never lodged, the date was wrong, the payment went unattributed, or the income was never there.definition
- A promise to pay is a record with an expiry, not a note in a CRMAmount, date, invoices covered, channel, evidence, state. Six fields turn a collections commitment from a memory aid into something a system can act on.definition
- Invoices sit in approval for days: find the hop where it diedStop chasing approvers and start aging the hop. Time-in-hop, the resolved principal and the notification result identify the stall in minutes, and four of the five causes are configuration rather than behaviour.diagnostic
- Matching fails because the goods receipt has not been posted yetAn exception that resolves itself if left alone for two days is not a receipting failure. Measure the site's receipting lag, then let the system wait instead of a person.diagnostic
Working on something in this space?
Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.
Start the conversation