Field method
How Dev Cache Grid designs samples, reads loan origination applications, and writes exception memoranda that credit committees can use.
The shape of fieldwork
A financial audit of loan origination applications succeeds when the sample answers a real control question. We do not begin with a generic scorecard. We begin with the decision you need to defend: campaign quality, override hygiene, disbursement readiness, or policy drift after a product change.
Sampling without theatre
We prefer random or stratified draws from your origination listing for a defined window. Stratification may follow branch, channel, or facility size. You see the draw rules before fieldwork starts so there are no surprise substitutions mid-week.
What we open in each file
Depending on the engagement, testers look for identity and KYC pages, income and employment evidence, affordability worksheets, collateral notes, guarantor packs, approval stamps, and any override rationale. We record page references so your team can re-open the same pack without guessing.
Writing for the committee
Findings use plain severity labels—observation, exception, material exception—tied to policy clauses. We avoid decorative heat maps. If a pattern appears across branches, we say so; if the issue is a single file, we keep it proportional.
Cadence you can plan around
| Phase | Typical length | Your role |
|---|---|---|
| Scoping | 1–3 days | Share listing, policy, and access rules |
| Fieldwork | 1–4 weeks | Answer clarifications; host file room if on-site |
| Draft memo | 3–5 days | Factual review only |
| Final walkthrough | 1 meeting | Decide remediation owners |
Bring us a control question
If you already know the engagement type, open the engagements list. If you need help framing the sample, write to the Bangkok desk with the product line and the decision date you are working toward.