Mortgage Pipeline and Workflow Management

Mortgage pipeline management keeps every lead, prospect and active application moving from first contact to settlement, with an owner and next action for each file. Start by documenting your workflow, then measure where files wait before changing how the team works.

What a Mortgage Pipeline Covers

A mortgage pipeline covers six stages: enquiry, fact find, recommendation, application, approval and settlement. Give each stage an owner, a task checklist and an expected duration based on your brokerage’s experience.

StageOwnerTasks Before Moving OnExpected Duration
EnquiryBroker or intake teamRecord the enquiry and arrange the first discussion.Your target for first contact and booking.
Fact findBroker, with processor supportUnderstand the client’s needs and collect supporting documents.Your allowance for receiving and checking a complete file.
RecommendationAuthorised brokerAssess suitable options and explain the recommendation.Your target once the required information is available.
ApplicationBroker, with processor supportCheck the submission and lodge the complete application.Your internal preparation and lodgement target.
ApprovalBroker and assigned processorTrack lender assessment and resolve conditions.The lender’s indicated turnaround plus your response allowance.
SettlementBroker or settlement coordinatorCoordinate documents and confirm readiness with the conveyancer.The time available before the agreed settlement deadline.

Enter a working duration beside each stage in your own board. Separate your team’s response target from a lender’s assessment time so an external wait does not hide an overdue internal task.

Document the Process Before Changing It

Draw a simple flowchart for the work your team actually does. Use one box per stage, in this order:

  1. First enquiry: record the client’s request and assign the file.
  2. Fact find: collect information and identify what is missing.
  3. Recommendation: assess the options and confirm the proposed loan.
  4. Application: check the documents and lodge.
  5. Approval: record the decision and clear outstanding conditions.
  6. Settlement: complete preparation and confirm the loan settles.
  7. Post-settlement review: confirm the client can use the loan and schedule the next review.

Connect each box to the next. Add a return path when a missing document or unresolved condition sends the file back for more work. Revisit the affected steps whenever a lender changes policy.

Time one full application from first enquiry through settlement. Log every step that takes more than five minutes, including repeated document requests and information copied between systems. Record waiting time separately from hands-on work so you can see whether to remove a task or improve a handoff.

Map Your Process and Fix the Bottlenecks

Record how long files sit at each stage over a month. Note when each file enters and leaves, who owns the next action and why it waits. Compare the results with the expected durations on your board.

A file waiting for a document that nobody has requested has a follow-up problem. Repeated lender requests for information already needed at lodgement point to a submission-quality problem. Where the submission is complete, check the lender’s assessment queue before changing your preparation process.

Measure progress as well as activity. Twenty calls do not prove the pipeline is moving if the same ten files remain in the same stages. Choose one recurring cause of delay, change the relevant step and compare stage times over the next month.

Where Files Stall Between Stages

Track the transitions through pre-approval, conditional approval and formal approval separately within your approval stage. Pre-approval can leave property or verification requirements unresolved. Conditional approval leaves named conditions to clear. Formal approval still needs the documentation and settlement work that follows.

Match policy before price. Check the client’s circumstances against lender requirements before pursuing a rate that the application cannot support. Lodge when documents are complete, not when they arrive: collect them as they come in, then check the full submission before sending it.

Treat automated underwriting as triage. Its output never replaces the broker’s responsible-lending inquiries or verification of the client’s financial situation. The Australian Securities and Investments Commission (ASIC) explains these obligations in RG 209 Credit licensing: Responsible lending conduct.

Take your last three applications and time each stage transition. Record the gap between receiving a lender condition, requesting the evidence and sending the complete response. If the delay sits inside your team, give that handoff an owner and response target.

Delegate Unlicensed Work

Keep advice, loan structuring and lender negotiation with the broker authorised to do that work. A mortgage loan processor can handle administrative file preparation, document collection and follow-ups within the licensee’s procedures.

Define the boundary in the checklist. The processor requests an outstanding payslip and checks that it arrived. The broker assesses what it means for the recommendation. Refer questions about loan choice or a change in structure back to the broker.

Assign client updates at fixed milestones, whether or not there is news. If an assessment is still pending, the update can state what is outstanding and when the client will hear from you again. Give the processor a clear escalation point when a promised response is overdue.

Keep Data Current and Protected

Record each interaction against the client file when it happens. Include the promised next step, its owner and its due date. A colleague covering the file must be able to see what the client has been told without searching personal inboxes.

Identity documents and financial records need controlled access and secure storage. Use individual accounts, restrict access to people who need the file and follow the licensee’s retention and disposal rules. Keep document sharing inside the approved collection process.

When clients share account information, record the authority for that sharing and use the approved channel. The guide to open banking for mortgage brokers explains consented data sharing for applications.

Tools That Carry the Work

Test a broker customer relationship management (CRM) system against your documented process before adopting it. Run a representative file through document collection and stage changes. Check how the CRM handles your aggregator’s feeds, assigns tasks and records the next action.

A reminder only helps when it reaches the person responsible and closes after the task is done. Check what happens when a client uploads part of a request or a lender asks for another document. Confirm the file remains visibly incomplete until the missing work is resolved.

Judge automation on your brokerage’s own numbers. Compare time spent chasing documents and the days files wait before and after the change. Use the loan origination software comparison when you need to compare systems that prepare and lodge applications.

Measure What Matters

Review four numbers weekly: leads received, enquiry-to-application conversion, average days per stage and settlements per month. Keep the definitions consistent so changes in reporting do not look like changes in performance.

Read the numbers together. More enquiries with weaker conversion warrant a look at qualification and follow-up. Applications rising while settlements stay flat can reflect a growing approval queue or the time those applications need to settle. Stage durations help locate the wait.

Compare enquiries from the same intake period when calculating conversion. Dividing this week’s applications by this week’s enquiries can mix different groups of clients. Use the fuller mortgage broker KPI set to connect pipeline progress with brokerage performance.

Calculate Conversion From a Defined Cohort

A cohort is a defined group of files followed over a stated period. Record the entry date for each stage and keep the same file identifiers as files move through the pipeline. Define each stage’s entry and exit before counting it.

For each stage pair, divide files reaching the next stage by files entering the starting stage, then multiply by 100. Keep withdrawals and declines in the starting denominator. Show them separately from files still open so a slow file does not look like a lost application.

For example, take 20 applications lodged in one four-week intake window. At 30 days after each application’s lodgement, 12 have settled, three were withdrawn, one was declined and four remain open. The observed application-to-settlement conversion is 12 ÷ 20 × 100 = 60%.

That cohort is unfinished because four applications still have no final outcome. Keep its conversion labelled provisional and continue following those same 20 files. Also measure days from lodgement to settlement for settled files, with the still-open count beside it. A lower provisional conversion can reflect a longer turnaround.

Compare Like-for-Like Completed Cohorts

The following synthetic example compares a brokerage’s referral enquiries from two separate four-week intake windows. Each file has an enquiry entry date and 120 days of follow-up from that date. Every file has reached a final outcome by the end of that observation period.

In both periods, an enquiry begins at the first recorded request for assistance. An application begins when the complete file is lodged with the lender. Settlement means the loan has settled, confirmed on the file.

Application rows follow the lodged subset of the same enquiry cohort. Withdrawn and declined counts show files that close before reaching the next named stage. A file reaching that next stage stays in the reached count even if it later closes without settlement.

Period and Stage PairStarting FilesReached Next StageWithdrawn Before Next StageDeclined Before Next StageStill Open
A: enquiry to application40 enquiries24 applications1060
B: enquiry to application40 enquiries30 applications820
A: application to settlement24 applications18 settlements420
B: application to settlement30 applications21 settlements630

Enquiry-to-application conversion rises from 24 ÷ 40 = 60% to 30 ÷ 40 = 75%. Application-to-settlement conversion falls from 18 ÷ 24 = 75% to 21 ÷ 30 = 70%. More enquiries reach lodgement, but a larger share of lodged applications closes without settling. Investigate the recorded withdrawal and decline reasons at that stage.

The example holds the referral channel constant. If your channel mix changes, calculate each channel separately before comparing the total. Keep the stage definitions, cohort entry rule and follow-up period identical, including the treatment of withdrawals and declines. Compare settlement times alongside conversion to distinguish lost files from longer waits.

Keep the weekly activity numbers as a separate view of work entering and leaving the team. They do not replace cohort conversion. Use a peer series only when its stage and cohort definitions match yours. Broker market share measures the channel’s share of lending, so it cannot supply an application-conversion target.

Communicate So Files Keep Moving

Send clients a status update at every stage change. Explain what is complete, what happens next and who must act. A clear next update date also gives the client a reason to wait without repeatedly checking in.

Send clean lender submissions and respond to conditions promptly with the complete requested evidence. Keep the lender’s request and your response together on the file so the next person can see what remains unresolved.

Prepare clients for settlement before the deadline approaches. Stay in contact with the conveyancer, supply requested documents promptly and confirm the settlement figures well ahead of the day. Record any funding gap or outstanding signature as an assigned task.

Record and Confirm an Application Withdrawal

When a client asks to withdraw, record the instruction and identify the exact application before notifying the lender. Check who must authorise the request under your licensee’s process, including any joint applicants. Send the notification through the approved channel to the team handling that application.

Copy these fields into the client file and complete them for the request:

Client name and file identifier:
Instruction received, including date, time and channel:
Client's exact instruction and scope:
Affected application and lender reference:
Authority checked, including required applicant instructions:
Person completing the authority check:
Lender recipient and notification sent date:
Acknowledgement received, including date and application status:
Remaining tasks, with owner and due date:
Related consents reviewed and action required:
Client confirmation sent:

Use this factual notification after recording the authority:

We received the client's instruction to withdraw the application identified below.
Client name:
Application and lender reference:
Instruction received date:
Authority checked by:
Please withdraw this application and acknowledge its status.
Please identify any remaining action required from the client or brokerage.
Reply to:

Retain the application history and the lender’s acknowledgement. Until acknowledgement arrives, record the request as withdrawal requested and keep a follow-up task open. Tell the client when the lender confirms the outcome.

Withdrawing one application does not automatically close every related file or cancel each data-sharing consent. Review those separately against the client’s instructions and your licensee’s procedures. Preserve records under the applicable retention policy, and assign any remaining action to a named person.

Give your five oldest stalled files a dated next action this week. Each action needs a named owner and a result that allows the file to move forward. At the next review, check whether those actions happened and whether the files changed stage.

Track My Trail

Trail analysis, simplified

Less time checking your trail, more time growing your book.

See how it works

7 days free · No credit card

Track My Trail Team

Read more

We develop software to simplify trail book management for mortgage brokers. Our tools provide fast and practical insights to help brokers get the most out of their trail books.

Track My Trail
See how it works

7 days free · No credit card