Only the files that need judgment: exception queues and approval authority

Many lending operations equate control with review: every file crosses an underwriter's desk, so every file is controlled. In practice the underwriter spends most of the day confirming things that were never in doubt, and the files that genuinely need judgment wait in the same line as the ones that do not.

The alternative is not less control. It is control expressed as policy: decide in advance what makes a file need a person, route only those files, and record who decided.

The conditions that make a file need review are usually simple to state: DTI above a product's limit, LTV above a threshold, a critical field that could not be verified, a value two sources disagree on. The mistake is burying those conditions in code or in a checklist. They change, and when they change the change should be an edit to a versioned table, not a deployment.

A good eligibility rule compares a borrower fact against a product fact — this borrower's DTI against this product's maximum — so the threshold lives with the product definition. The outcome is one of three: eligible, ineligible with the reason that fired, or referred to a person.

Referring a file is half the design. The other half is who can resolve it. A routine exception might need any one underwriter. A credit committee decision might need a majority. A policy exception might need every named approver to sign. Those are different authority rules, and they should be configured, not left to whoever picks the file up.

What the reviewer sees matters as much as who they are. A reviewer handed the whole file re-underwrites it. A reviewer shown the blocking findings and the low-confidence fields decides the question that was actually referred — faster, and in a way that is easier to audit afterwards.

In Miji, eligibility runs as versioned rules or decision tables that can compare a borrower fact against a product fact. Threshold routing sends a file to underwriting, credit committee or exception approval, and each gate resolves by any-one, all or majority. Fields your verification policy marks critical or sensitive always require a person. The review queue is exception-based — it holds the cases that need judgment and only those — and every approval lands on the same hash-chained audit trail as the rest of the decision.

The result your team notices is not a new screen. It is a shorter queue, made of files that deserve the time. If that is the problem you are staffing around, we would like to hear about it: hello@mijios.ai.