Mortgage support service-level agreement template

A mortgage support service-level agreement should make daily work predictable. It should say what enters the queue, when the clock starts, what “complete” means, who approves consequential steps, how blockers are escalated and which evidence is reviewed. It should not promise that every file will finish in the same number of hours regardless of missing documents, lender response or broker decisions.

The practical approach is to attach a short service schedule to the wider commercial agreement. The schedule runs the work; the executed contract handles legal terms. Use this template for an outsourced loan processor, mortgage broker assistant or remote administration team, then adapt it with your provider and advisers.

Start with shared definitions

SLA ambiguity can arise when two teams measure different events. “Received” might mean an email arrived, the task was created, or all required inputs were available. “Completed” might mean the assistant finished a draft, the broker approved it, or the lender accepted it. Define the state changes before inserting a target.

Term	Working definition	Evidence
Ready	Required inputs are present, readable and assigned to the correct queue.	Timestamp and intake checklist.
Accepted	The support team has reviewed the request and named any obvious missing input.	Owner and accepted timestamp.
Blocked	Work cannot continue without a defined input, decision or access change.	Blocker category, owner and raised time.
Prepared	The agreed support output is ready for the named reviewer.	Output link and review request.
Accepted output	The reviewer confirms the output meets the written acceptance check.	Approval or correction category.

Use the same status names in the CRM or work queue. A spreadsheet SLA beside different production labels creates manual reconciliation and unreliable reporting.

Separate service classes

One target for every request encourages either missed expectations or excessive urgency. Create a small number of service classes based on actual business need. Keep the list short enough that staff can choose consistently.

• Critical: a genuine deadline or customer-impacting issue that needs immediate triage by a named person.
• Time-sensitive: a task tied to an agreed same-day or next-business-day event.
• Standard: normal queue work with complete inputs.
• Planned: batch maintenance, reporting or non-urgent improvement work.

Define who may mark an item critical and what evidence is required. If everything is urgent, normal prioritisation disappears and true exceptions receive no different treatment.

Measure response, preparation and waiting separately

A response target is the time to acknowledge and triage a ready request. A preparation target measures the ready-to-prepared interval under the agreed clock rule. Record hands-on handling time separately from elapsed time and waiting. A resolution target may depend on the broker, customer, lender or another third party. Keep these clocks separate so the report shows where work waited.

Service class	Acknowledge	Prepared for review	Update cadence while blocked
Critical	Within the agreed rapid window	Case-specific estimate after triage	At each material change
Time-sensitive	Same operating period	By the agreed event deadline	Before the deadline is at risk
Standard	Within one working window	By the standard lane target	At the daily handover
Planned	When scheduled	By the planned batch date	At the weekly operations review

Replace the descriptive targets with times that match coverage hours, complexity and staffing. Record which timezone applies and which public holidays or planned closures pause the clock.

Define acceptance before turnaround

Turnaround without an acceptance rule rewards work that appears finished but returns to the broker. For each workflow, write the smallest useful checklist that a reviewer can apply consistently. A factual CRM update might require source, date, owner and next action. A prepared document pack might require correct applicant mapping, complete pages, readable files, naming convention and recorded exceptions.

Use the mortgage file QA sampling checklist to separate routine acceptance from periodic quality review. Track first-pass acceptance and material rework. Do not count a broker's preference change the same way as an avoidable execution error.

Keep approval authority explicit

The SLA must not accidentally grant authority. List the steps the support person may prepare, the person who reviews them and the events that always return to the broker or another authorised role. Examples include unclear customer instructions, policy exceptions, conflicting information and any action outside the approved task boundary.

A workflow RACI matrix helps connect each service target to the responsible worker and accountable approver. The SLA then measures the handoff between those roles rather than blurring them.

Design the escalation ladder

Every escalation should identify the issue, affected item, deadline, attempted checks and decision required. Route it to a role, not only a person's private inbox. Include a backup when the primary contact is unavailable.

1. Workflow question: route to the process owner and add the answer to the SOP if reusable.
2. Deadline risk: notify the queue owner before the target is missed and agree the next update.
3. Access or security concern: stop the affected activity and use the approved incident path.
4. Customer or lender exception: move the item to the named authorised decision-maker.
5. Repeated quality issue: open a corrective action with cause, owner, due date and follow-up sample.

Report a balanced monthly view

Report demand, flow, quality and controls together. Include items received, work in progress, age by stage, first-pass acceptance, rework by cause, blocked time, target performance by service class, escalations, access changes and corrective actions. Show the denominator and exclude no item silently.

Use the outsourced loan processor KPI scorecard for a practical structure. A missed target should lead to a cause and action, not a debate over whether the dashboard is technically correct.

Control changes to scope and volume

Add a change process for new workflows, sudden volume, system changes and extended coverage. Before a new task enters the SLA, define its inputs, output, acceptance check, owner, access and baseline. A chat message saying “can you also do this?” is not enough for a durable operating change.

Review targets after a controlled 30-day mortgage outsourcing pilot. Tighten or relax them using observed work, not sales promises. Keep a version date so staff know which schedule applies.

Work through a fictional service clock

Assume this example schedule operates Monday to Friday, 9 am to 5 pm Sydney time. Its illustrative standard target is 15 minutes to acknowledge a ready request and 60 minutes from ready to prepared, excluding a recorded wait for a broker decision. These are chosen example targets, not a recommendation for every workflow.

Event	Timestamp	Clock treatment
Complete request becomes ready	9:00 am	Acknowledgement and preparation clocks start.
Processor acknowledges and accepts	9:10 am	Acknowledgement is 10 minutes.
Conflicting input sent to named reviewer	9:30 am	Recorded broker-decision wait begins.
Reviewer returns the decision	11:30 am	120-minute wait ends; preparation clock resumes.
Output moves to prepared for review	11:50 am	Ready-to-prepared elapsed time is 170 minutes.

Under this schedule, measured preparation time is 170 − 120 = 50 minutes, so both example targets are met. The report must still show the full 170-minute elapsed interval and the 120-minute dependency. The 50-minute unblocked interval is not proof of 50 minutes of hands-on labour; measure active handling separately if needed. Broker acceptance remains a later event, and an incorrectly logged pause should be corrected rather than silently improving the SLA result.

Copy this SLA schedule

• Service scope: included workflows and explicit exclusions.
• Coverage: days, hours, timezone, holidays and backup coverage.
• Queue rules: intake channel, ready definition and priority owner.
• Targets: acknowledgement, preparation and blocked-update clocks by class.
• Acceptance: reviewer, checklist and rework categories for each output.
• Authority: preparation rights, approval points and mandatory escalations.
• Reporting: measures, denominators, review cadence and data owner.
• Change control: how new scope, volume or systems are approved.
• Continuity: backup owner and handover requirement.
• Review date: when targets and lessons will be reconsidered.

A useful SLA is short enough to use and precise enough to resolve ambiguity. If staff cannot tell whether the clock is running, what acceptable work looks like or who must decide an exception, the schedule needs another pass.