A pipeline that respects lock status
Applications, approvals, clear-to-close, and funded volume separated by lock state and days in stage, so an aging locked file is visible while there is still time to act on it.
Industry · Mortgage lending
Locked pipeline, originations, pull-through, cycle time, and branch versus loan officer profitability in one live view. A senior US-based engineer builds it on your loan origination system and general ledger, secures it by branch, and keeps it refreshing. Most builds land in 3–5 business days.
Representative dashboard — sample data
One view of the book
Loan origination systems are built to move a file from application to funding, and they do that well. What they rarely do well is answer the questions leadership asks on Monday: where is the pipeline concentrated, which cohorts are actually pulling through, what a funded loan costs us to produce, and whether a branch is carrying its own weight. A Power BI dashboard for mortgage lenders answers those by joining LOS milestone data to the general ledger, the pricing engine, and payroll, then holding the definitions steady from one month to the next.
That last part is the difference. Most lenders already have the numbers somewhere. They exist as a pipeline report from the LOS, a branch P&L from accounting, a commission file from payroll, and a lock report from secondary — each with its own idea of what counts as a unit and when. We fix those definitions once, in a governed model, so the number in the board deck matches the number the branch manager sees.
What we build for lenders
Buy a block of prepaid Flex hours and, if you're unhappy within the first 4 hours, we refund you in full — no questions asked. Hours are deducted only for work you've reviewed and approved, there's no project minimum, and your banked hours never expire.
Why lending teams call us
You send the request; a senior engineer maps your LOS, ledger, and commission data into one model built for how lending actually works.
Applications, approvals, clear-to-close, and funded volume separated by lock state and days in stage, so an aging locked file is visible while there is still time to act on it.
Applications followed from the month they were taken through to funding or fallout, rather than a ratio of this month's fundings to this month's applications that moves whenever volume does.
Revenue per funded loan against commission, direct branch cost, and allocated overhead — so a high-volume branch with thin margin stops being mistaken for the strongest one.
Days from application to close broken into processing, underwriting, conditions, and closing, so the constraint is identified as a stage and an owner rather than a company-wide average.
Loan sale revenue net of hedge results, concessions, and pricing exceptions, tied back to the branch and product that produced the loan instead of sitting in a separate secondary workbook.
Row-level security by branch, region, or loan officer, so one report serves the whole shop and nobody circulates a spreadsheet containing every other branch's margin.
Three families of data. Origination: applications, borrowers, properties, products, milestone timestamps, lock records, and adverse action reasons from the LOS. Financial: the general ledger by cost center, commission and payroll detail, and the branch expense structure. Secondary: investor commitments, sale proceeds, hedge results, and pricing exceptions. The model joins them on loan number and period, which is what makes a per-loan margin figure possible at all.
The hard part is agreement, not visuals. Does a unit count at application, at lock, or at funding? Is a withdrawn file fallout or was it never real? Which month owns a loan taken in March and funded in May? Does a branch carry allocated corporate overhead? We fix those choices in the model as documented DAX measures (opens in new tab) rather than as formulas typed into individual charts, so the definition cannot quietly differ between two reports. Our Power BI data modeling and DAX service covers how that layer is built, on a star schema (opens in new tab) the way Microsoft recommends.
Every lender is different, but the set below is where we usually start. It covers the pipeline, the production result, the efficiency of getting there, and the profitability of the people and places producing it — with the systems each figure typically comes from.
| Metric | What it answers | Typical source |
|---|---|---|
| Locked & in-process pipeline | How much volume sits at each stage, and how much of it is rate-locked | LOS milestones and lock table |
| Originations (funded units & volume) | What we actually produced, by product, channel, branch, and period | LOS funding records, reconciled to the GL |
| Pull-through rate | What share of an application cohort reaches funding | LOS application and funding history |
| Fallout & denial reasons | Where files die, at which stage, and why | LOS status changes and adverse action codes |
| Application-to-close cycle time | Days spent in processing, underwriting, conditions, and closing | LOS milestone timestamps |
| Cost to originate per loan | Fully loaded production cost against each funded unit | GL by cost center, payroll, LOS unit counts |
| Net marketing income (NMI) | Loan sale revenue after hedge results, concessions, and pricing exceptions | Pricing engine, investor commitments, secondary records |
| Branch profitability | Branch revenue against direct cost and allocated overhead | GL cost centers joined to LOS production |
| Loan officer profitability | Units, volume, pull-through, and margin per originator | LOS originator fields plus commission and payroll detail |
| Lock expiration exposure | Which locks expire soon and what extensions are costing | Lock and extension records from the LOS or pricing engine |
The LOS is the anchor — Encompass by ICE Mortgage Technology, Empower, MeridianLink, Calyx, and Byte are the platforms we meet most often. Extraction depends on the vendor and your contract: an API, a reportable database or reporting replica, or a dependable scheduled export. We establish which of those your agreement actually allows before designing around it, and we confirm the method and any vendor charge for data access in the scope estimate, because in this sector data access is sometimes a paid add-on rather than an included feature.
Around it sit the general ledger for cost centers and branch expense, payroll or the commission engine for originator cost, the pricing and hedging platform for lock and sale economics, and the CRM for lead source and marketing spend. Lenders with long production histories get incremental refresh (opens in new tab), which Microsoft documents, so each nightly run processes only what changed instead of reloading years of loan-level detail.
Through row-level security in the model. Each user account maps to a branch, region, or originator ID, and every visual filters to that scope automatically. It is enforced by the model rather than by which file someone was sent, so a branch manager opening the report simply cannot see another branch's margin, and executives see the consolidated view from the same report.
Microsoft documents the mechanism in its guide to row-level security in Power BI (opens in new tab). We configure the roles, test them against real accounts before go-live, and document who can see what — a useful artifact when an auditor or an investor asks how originator-level compensation data is controlled.
Lenders subject to the Home Mortgage Disclosure Act already assemble a loan application register; the reporting requirements and data points are published by the Consumer Financial Protection Bureau (opens in new tab). What most teams lack is a way to look at that data before the deadline rather than during the scramble.
We build the analytical layer: application and action-taken distributions, pricing and denial patterns cut by product, channel, and geography, and completeness checks that flag missing or implausible fields while there is time to correct them at the file level. To be clear about scope — this supports your compliance review and your own counsel's interpretation. It is a reporting tool, not a filing service, and we do not offer legal or compliance advice.
You buy prepaid Flex hours that never expire, with senior hourly work from $100: Starter is 20 hours ($2,500), Growth is 40 hours ($4,600), and Power is 80 hours ($8,000). A first pipeline-and-production dashboard on a single LOS usually fits inside one block. Adding branch profitability, secondary marketing, and HMDA views generally moves a lender to the second tier, because that is where the general ledger and commission data have to be reconciled rather than simply loaded.
There are no project minimums, nothing starts before you approve a scope estimate, and hours are deducted only for work you have reviewed. That structure suits a business whose volume moves with rates: bank hours in a busy quarter, spend them when a channel changes or an investor changes its reporting. See how prepaid Flex hours work, including the published tiers.
Independent mortgage banks, bank and credit union lending divisions, and wholesale or correspondent shops running somewhere between a handful and a few dozen branches — large enough that manual consolidation is a real monthly cost, not so large that an internal data team already owns it. It also fits lenders who have just acquired a branch network and inherited a second LOS. Credit union lending divisions usually want this page for the mortgage desk and our Power BI dashboards for credit unions for the membership, share and deposit, and branch reporting that sits around it. Lenders in the Charlotte banking market can see how the same build is delivered on Eastern-time hours on our Power BI consultant Charlotte page.
If your interest is the finance function rather than production — budget versus actual, cash flow, and the board pack — start with our Power BI dashboards for finance teams. If you hold the property side as well, our real estate portfolio dashboards cover NOI, occupancy, and investor reporting across owned assets. Lenders who want reporting delivered inside their own broker or borrower portal instead of the Power BI service should read Power BI embedded analytics. Lenders who want the Encompass side specifically — Data Connect versus Developer Connect, field-ID mapping and milestone turn times — should read our Encompass Power BI dashboard build page, which covers getting the loan data out and modelled. Groups that also run an insurance agency alongside lending face the same contractual data-access question in their AMS — the Applied Epic Power BI dashboard page covers how policy and renewal data gets out of Applied Epic. Contact is form-only — send your request and we'll reply with a scope estimate.
business days, typical
hours, never expire
own everything
Bank hours in a busy quarter and spend them when rates move the plan. See Flex pricing →
How it works
Tell us your LOS, how many branches and channels you run, and which questions go unanswered today. We reply with a scope estimate and the hours needed before any work begins, including how we would extract your LOS data.
A senior US-based engineer maps loans, branches, originators, and cost centers into one model, writes the DAX for pull-through and per-loan margin, configures branch security, and reconciles funded volume to the ledger — typically 3–5 business days.
We publish to your Power BI workspace, set nightly or incremental refresh, and hand over the model and credentials. You own everything; we keep the refresh healthy and add views from your banked hours.
Representative perspective
Our pipeline report and our branch P&L never agreed, so every leadership meeting started by arguing about whose number was right. Putting both on one model ended that in a week.Operations executive, independent mortgage bank
Representative perspective
Seeing pull-through by application cohort rather than by report month changed which branches we thought were performing. The ranking was genuinely different once the loans were followed properly.Lending CFO, credit union mortgage division
Tell us your loan origination system and how many branches you run. We'll scope the task and tell you the hours before any work begins — drawn from prepaid Flex hours that never expire, with no project minimums and no obligation.
FAQ
Any LOS that exposes an API, a reportable database, or a dependable scheduled export. Encompass, Empower, MeridianLink, Calyx, and Byte are the ones we see most often. Vendors differ in what they expose and some charge for data access, so we confirm the extraction method and any vendor cost in the scope estimate before hours are used.
By cohort. Every application is tagged to the month it was taken and followed through to funding or fallout, so the rate measures the same loans over time rather than dividing this month's fundings by this month's applications. We agree the denominator and the fallout definitions with you before the measures are written.
Yes. Row-level security maps each signed-in user to their branch, region, or loan officer ID, and every visual filters automatically. One report then serves the whole organization, which is both safer and far less work than maintaining a separate file per branch and emailing it out each week.
We build the analytical views: application, action taken, and pricing distributions cut the way examiners look at them, so questions surface well before a submission deadline. The dashboard supports your review. It does not replace your compliance team's filing process or a formal legal review of the results.
Most requests are delivered within three to five business days of your approval, and a first pipeline and production dashboard usually fits inside one prepaid block. Flex hours never expire: Starter is 20 hours ($2,500), Growth 40 hours ($4,600), and Power 80 hours ($8,000), with senior hourly work from $100.
Book a free demo
Tell us the task. We scope it, you approve, and a senior consultant delivers — typically in 3–5 business days. Prepaid hours that never expire.
The fastest way to reach us is the form — tell us the task and we'll reply within one business day.