# How Operational Analytics Pinpoint Bottlenecks in Your Lending Workflow _Published: 2026-06-05T10:00:00.000-04:00_ Your efficiency ratio shows you're behind; operational analytics shows you where. Analyze your own data and benchmark against peer institutions. _Efficiency ratios tell you there's a gap to close. Operational analytics shows you where to take action._ Your efficiency ratio can tell you you’re behind, but operational analytics can tell you exactly where to look. That distinction goes beyond the capabilities of financial reporting or standard business intelligence tools. Efficiency and cost management tops the priority list for [51% of bank executives and 59% of credit union executives,](https://www.crnrstone.com/gritty-insights/research/the-journey-toward-2030-becoming-a-smarter-bank) according to recent research from Cornerstone Advisors. If you're in operations leadership, that statistic probably doesn't surprise you. The pressure to improve is nothing new. The opportunity is figuring out exactly _where _to improve and having the data to act on it. The same research found that most regional institutions [hover above a 60% efficiency ratio, while top performers push toward the low 50s.](https://www.crnrstone.com/gritty-insights/research/the-journey-toward-2030-becoming-a-smarter-bank) You probably know where your institution stands in that range, but knowing the number isn't the same as knowing the cause. A 63% efficiency ratio confirms you trail a peer at 57%, but it doesn't tell you why. The drag could be revenue you're losing when deals stall in underwriting queue time, document collection, or the handoff between credit analysis and approval, or the added cost of working through that friction in the first place. Lending workflow systems generate the operational data that can close that gap — timestamped records of when deals move between stages, where they sit idle, and how long each step takes. The right lending workflow platform captures that data in a way that makes it usable for diagnosis, giving you stage-level visibility that aggregated exports and summary reports can’t provide. ### **The Blind Spot of Efficiency Ratios** Efficiency ratios measure institutional cost performance but not where operational drag originates. Your efficiency ratio is a reliable indicator of cost efficiency at the institution level, and it’s one of the most watched numbers in banking for good reason. Where it reaches its boundary is breaking down by business line, workflow, or loan stage. It can tell your boardroom that the institution has room to grow, but your operations team needs a different lens to see _where. _ Finding the 'where' requires different data. You need **process metrics, **like loan cycle time by stage, average stage duration, pull-through rate, volume by product type, and origination channel. These are what actually locate the problem. Process metrics** **require event-level workflow data: timestamped records of when a deal entered each stage, how long it waited, when it moved, and where it stalled or moved backwards. Aggregated statement exports just can’t produce that. Imagine you’re a regional bank with a 63% efficiency ratio. Leadership knows that you’re trailing a peer institution sitting at 57%, but you don’t know which part of the process accounts for that gap. Maybe underwriting is taking 16 days when similar institutions run it in 11. Maybe there’s a bottleneck in the handoff between relationship managers and credit analysts. Standard financial reporting doesn’t contain this kind of stage-level data. It’s not a flaw, just a limitation. Financial reports measure results; process data measures what created them. More than half of banks report that siloed data prevents real-time operational decisions, [according to Cornerstone research](https://www.crnrstone.com/gritty-insights/research/the-journey-toward-2030-becoming-a-smarter-bank). The data to answer those operational questions exists and lives inside lending workflows. The opportunity is connecting it to the decisions that matter most. ### **Your Lending Workflow Data Has the Answers, Not Your Reports** Operational analytics use event-level workflow data to identify process bottlenecks and measure them against peer performance. That process-level data is captured with every transaction. The data that answers the most important operational questions — stage-level cycle times, handoff delays, peer benchmarks — already exists inside your lending workflow system. Every time a commercial loan moves through your system, it leaves a trail. When the deal entered underwriting. How long until it advanced to approval. Which team member last touched it. You have time-stamped records of these events. That event sequence is the raw material for stage-duration analysis — the kind that identifies where deals sit idle between handoffs, not just how long the _entire_ process took. Business intelligence tools that pull from core banking exports receive aggregated outcomes like loan volume by quarter, approval rates by month, and total production by officer. That level of reporting serves executive dashboards and board presentations well. Operational analytics goes a step further: it can show you which stage is driving your own cycle time, then benchmark the milestones every institution shares — creation to approval, approval to booked, and creation to booked — against peers processing similar deal types at your asset size. Embedded operational analytics draws on loan stage transitions, user interactions, and timing events to surface stage-duration analysis at the process level, and benchmarks that data against peer performance. [nCino Operations Analytics](https://www.ncino.com/operations-analytics), for example, benchmarks against anonymized data from over 1,600 financial institutions. ### **Three Questions Your Analytics Should Answer Out of the Box** Knowing the definition of operational analytics is only important if you know what to do with it. There are three questions any analytics platform in your lending workflow should be able to answer. #### Which Stage Is the Bottleneck — and How Do You Compare? Total cycle time is a familiar metric, and you probably track it already. What’s harder to see is stage-level cycle time: the average duration of each stage by loan type, so you can locate where time accumulates inside your own process. Pair that with peer benchmarking on total cycle time, and you learn not just where your time goes but whether your overall pace is competitive. Imagine your commercial cycle time runs 23 days against a 17-day peer average. Peer benchmarking tells you you're behind, and it points to where: most of the gap is in the approval phase, not booking. From there, your own stage-level data tells you why, with underwriting running 14 days. Without that view, 23 and 17 are just numbers you can't act on. With it, you know exactly where to start. That context changes what an operations leader does next. #### Where Are Deals Stalling Between Handoffs? Cycle time measures how long the full process takes, but the more actionable question is where time accumulates within that process. Is the constraint in the handoff from relationship manager to underwriting? Underwriting to credit committee? Approval to closing? Stage-duration data locates the accumulation point. Event-level data from the workflow shows exactly which handoff is the holdup, and where deals loop backward into rework instead of moving forward. That's what turns a broad efficiency concern into a pinpointed place to start fixing it. #### Is the Problem the Deal or the Process? When your cycle times look different from a peer's, it’s typically because of either the deals you're handling or how you're handling them. Operational analytics is how you tell those two things apart. Start by segmenting before you compare. A raw cycle time average blends your smallest, most straightforward deals with your largest and most complex. Compare by loan type and size first. Separate originations from renewals too, since those are frequently different processes that shouldn't sit in the same average. If the gap persists within the same category, the deals aren't the explanation. Look at variance, not just averages. A 14-day average underwriting duration could mean every deal takes roughly 14 days, or it could mean half take a week and others take three. High variance within the same loan type usually points to a process problem, like teams handling the same deal type with no standard process between them. Look at where time accumulates inside the stage. A long underwriting stage doesn't always mean underwriting is the problem. If most of the time is idle — waiting for documents before analysis even begins — the bottleneck is upstream in the handoff. This kind of diagnostic surfaces a clear pattern at scale. The [nCino Research Institute](https://www.ncino.com/research-institute) analyzed 490 U.S. financial institutions and found that **process consistency** — how closely loans follow standardized workflows — showed the strongest correlation with financial performance of any operational metric studied. The fastest institutions weren't the most profitable. Institutions that [prioritized speed without process visibility underperformed](https://www.ncino.com/blog/the-consistency-paradox-why-bankings-fastest-isnt-always-first) their more methodical peers by a 3-to-1 margin on ROAA. Institutions that mastered both consistency and speed delivered 127% better ROAA and 120% better ROAE. Strong consistency with slower processing still produced 77%. Speed without consistency only resulted in a 26% increase. That distinction determines what happens next. A deal-mix problem means your timelines may be appropriate for the complexity you're handling. A process problem means there's inconsistency you can standardize, and that's where the diagnostic pays off. ### **If It Requires Custom Development, It's Reporting — Not Analytics** If an analytics platform requires custom development to show stage-level cycle times and peer-benchmarked cycle times, it’s reporting infrastructure, not embedded operational analytics. True operational analytics does more than produce a dashboard. When evaluating your platform look for three capabilities: - You have access to what’s happening inside the lending workflow itself — timestamped records of when deals enter and exit each workflow stage, which user performed each action, and how long deals wait between transitions. - You can store and track that data over time so you can identify trends, not just see a snapshot of where things stand right now. - You can compare your data against peers processing similar deal types at a similar asset size so you know whether a number represents a problem or a benchmark. Most business intelligence tools are built for the second and third, but not the first. They receive aggregated exports from core banking systems — loan volume by quarter, approval rates by month — which means the event sequences that enable stage-duration analysis aren’t part of the picture. When you're evaluating an analytics platform, ask the vendor to show you something specific: which stage is adding the most time to your commercial loan cycle, and whether your total cycle time is competitive with peers at your asset size, _without _custom development. If they need a scoping call, an integration project, or additional licensing to deliver that, you're looking at reporting infrastructure, not embedded analytics. ### **Closing the Diagnostic Gap** Imagine walking into your next board meeting with all the answers. You’re able to tell them your efficiency ratio is 63%, six points above target, and that the opportunity for growth is in CRE underwriting. You can show them that your total cycle time runs 18 days compared to a 12-day peer average, and that your own stage data points to the handoff between document submission and underwriting assignment as the bottleneck, where deals sit 4.5 days. And you have a plan: piloting an automated assignment workflow in Q2 that can reduce that to under two days, based on peer data showing what's achievable. That level of specificity comes from operational analytics, not aggregated reports. A better chart of the same lagging indicators tells you **where you’ve been,** but operational analytics tells you **what to do next.** The next time you’re evaluating a new analytics platform, or the one you already have, ask this question: “Can it show me which loan stage is adding the longest delays to my cycle time, and whether my total cycle time is competitive with peer institutions at my asset size, without custom development?” The answer tells you if you have reporting or operational analytics. The diagnostic capability of operational analytics directly impacts your bottom line. Institutions that master both process consistency and speed outperform peers by 127% on return on average assets, according to the nCino Research Institute's analysis of 490 U.S. financial institutions. **Ready to see where your institution stands?** nCino Operations Analytics surfaces stage-level cycle times, cycle-time peer benchmarking, and process insights, all without custom development. [Start turning your operational data into strategic intelligence.](https://www.ncino.com/operations-analytics) --- [View sitemap](https://www.ncino.com/api/markdown/sitemap)