Insights from the operations floor

Why your turn-time report is lying to you

Nearly every turn-time dashboard we audit starts the clock at file submission. That is a convenient moment to measure because the platform stamps it automatically. It is also the moment after the slowest part of the process has already happened.

In the twelve reviews we ran during 2025, the median gap between first borrower contact and a submittable application was 1.9 business days. None of those days appeared in the client's reported turn time. Leadership was optimising a number that excluded a quarter of the real elapsed time.

The fix is not complicated. Capture an intake timestamp at first contact, report both figures side by side, and let the difference become a managed metric with an owner. Three of those twelve clients cut the intake gap by more than half within a quarter simply because someone was finally accountable for it.

• Add an intake timestamp distinct from submission
• Report intake-to-submission as its own metric with a named owner
• Break the gap down by referral source — it is rarely evenly distributed

Six conditions templates every lender duplicates

Template sprawl is the single most common finding in our configuration audits. It starts innocently: an underwriter needs a slightly different wording, cannot edit the existing template, and creates a new one. Five years later there are four hundred templates, sixty of which are in real use.

The consolidation exercise we run in week one is deliberately blunt. We export every template, sort by last-used date, and archive anything untouched in eighteen months. Then we cluster the remainder by intent — income, assets, property, title, insurance, identity — and rewrite one canonical version per cluster with variable fields for the details that actually change.

The measurable outcome is not storage. It is decision time: underwriters stop scanning a long list and processors stop sending borrowers two versions of the same request.

Training that survives staff turnover

In one quarter of 2024 we watched three clients lose the only person who understood their configuration. In each case documentation existed. In each case nobody opened it, because it had been written as a two-hundred-page reference rather than as a set of answers to the questions people actually ask.

We changed our handover format afterwards. Runbooks are now organised by task — “how to add a new condition template”, “how to change a milestone owner” — each one under a page, each one with a screenshot from the client's own environment. Recorded walkthroughs are three to six minutes, never longer.

The test we use before handover: hand the runbook to someone who was not in the training session and ask them to complete the task. If they cannot, the document is not finished.

The four numbers an operations lead should see every Monday

Dashboards fail by being complete rather than by being wrong. Our default weekly view has four numbers and nothing else: files in pipeline by stage, files aged beyond stage target, exceptions opened versus cleared, and capacity used per processor. Everything else lives one click deeper.

The discipline matters more than the tool. We have built this in Power BI, in Tableau and directly inside origination platform reporting. The clients who kept using it are the ones who agreed, in advance, which single person would act on each number.