Outsourced mortgage team weekly meeting agenda

An outsourced mortgage team weekly meeting should make a small number of operational decisions, not replay every file update. Use a 30-minute agenda with a pre-read dashboard: five minutes on commitments, seven on capacity, seven on quality, six on blockers and decisions, and five on actions and people. Every unresolved item should leave with one owner and one due point.

The meeting works best when brokers, processors and operations leads already maintain the daily record. It is the weekly control point for patterns that cannot be fixed inside one file.

Decide what this meeting is for

Write a one-sentence purpose above the agenda: “Protect service, quality and team capacity by resolving cross-file issues and improving the operating system.” This keeps the conversation away from general updates and toward decisions.

The meeting is not the place to expose customer details broadly, audit individual productivity minute by minute or improvise new credit authority. Use approved records and the minimum information needed to understand a pattern. Route file-specific decisions to the authorised person and record the outcome in the source system.

Send a one-page pre-read

Publish the same dashboard before each meeting so attendees can arrive ready to decide. A practical pre-read contains the current queue, items due in the next operating window, work in progress by stage, oldest active items, blocked items, recent quality findings, service commitments at risk and actions carried over from last week.

Pre-read area	Question it should answer	Useful view
Demand	What entered and left the queue?	Count by workflow stage and week.
Capacity	Where is work accumulating?	Work in progress and ageing by owner or team.
Service	Which agreed response points are at risk?	Due soon, overdue and reason codes.
Quality	What is being returned or corrected?	Sample findings by defect type.
Decisions	What cannot move without authority?	Question, decision owner and latest useful time.
Actions	Did last week's commitments close?	Owner, due date and evidence of completion.

Use the definitions from the outsourced loan processor KPI scorecard so the meeting does not debate what each number means.

Use this 30-minute agenda

Time	Topic	Decision or output
0–5 min	Previous commitments	Close, reassign or escalate each overdue action.
5–12 min	Capacity and flow	Rebalance ownership and agree queue priorities.
12–19 min	Quality and rework	Select one corrective action for material patterns.
19–25 min	Blockers and decisions	Name the authorised decision owner and response time.
25–28 min	People and continuity	Confirm leave cover, coaching and access changes.
28–30 min	Read-back	Repeat every action, owner and due point.

Review capacity without rewarding busyness

Look for flow, not raw activity. A high count of touches can hide repeated rework, unclear instructions or too much work in progress. Ask where items wait, why they wait and whether the team has accepted more work than it can finish safely.

• Limit the review to queues and exceptions that need action.
• Compare work in progress with the team's agreed operating capacity.
• Move priority explicitly; do not tell everyone that everything is urgent.
• Protect review capacity as well as preparation capacity.
• Record any temporary rebalance and when it will be reviewed.

If a service point is repeatedly missed, revisit the mortgage support service level agreement. The answer may be a clearer acceptance rule or dependency, not simply faster work.

Turn quality findings into one improvement

Bring a short summary from the mortgage file quality assurance sample: what was checked, what failed the agreed acceptance point, likely cause and whether the same issue appears elsewhere. Discuss patterns, not public blame.

Choose one proportionate response: clarify an SOP step, improve an intake field, add an example, adjust a review gate or coach a specific skill privately. Give the action an owner and define the evidence that will show it worked. Too many simultaneous corrections make it hard to tell which change helped.

Prepare blockers as decision requests

Do not bring “waiting on broker” as a complete update. Use: issue, impact, checks completed, options, recommended next step, authorised decision owner and latest useful response time. This lets the meeting resolve the blocker or deliberately place it on a decision log.

Items that can be handled in the daily overlap should remain in the remote team handover. The weekly meeting should focus on recurring blockers, cross-team trade-offs and operating changes.

Include people, access and continuity

Reserve a short section for planned leave, backup coverage, training, role changes and access that should be added or removed. Keep sensitive employment matters outside the group agenda. The operational question is whether the work has an approved owner and backup.

When a critical role has no cover or the same dependency fails repeatedly, add it to the mortgage outsourcing business continuity plan and schedule a test rather than merely noting the risk.

Maintain a decision and action log

Meeting notes should be short. Record decisions, changed priorities, accepted risks and actions. Each action needs an owner, due point, success evidence and link to the authoritative record. Start the next meeting by reviewing this log.

Type	Decision or action	Owner	Due	Evidence / record	Status
Decision / action	Specific outcome	One named role	Date and timezone	Link or acceptance check	Open / closed / escalated

If an action has several co-owners, it usually has no owner. Name the person accountable for moving it and list contributors separately.

Avoid weekly status theatre

• Do not read the dashboard line by line; circulate it first.
• Do not solve a private file issue in a broad meeting.
• Do not add a metric unless it changes a decision.
• Do not carry an action forward without reassessing owner and due point.
• Do not let one urgent anecdote replace the full queue view.
• Do not use the meeting to bypass the agreed authority boundary.

Cancel or shorten the meeting when there are no decisions, risks or improvements to address. A stable process should reduce meeting load rather than create reporting for its own sake.

Turn a fictional weekly pattern into one action

Suppose the pre-read shows six items waiting for the same broker decision, while a QA sample found two packs missing the same acceptance field. These are fictional figures used to demonstrate the meeting output, not observed team results.

Observation	Decision or action	Owner / due	Evidence at the next meeting
Six items share one decision dependency	Assign the approved backup reviewer during the primary owner's planned absence	Workflow owner; before the absence begins	Each affected item has the permitted reviewer and a next response point.
Two sampled packs lack the acceptance field	Clarify the SOP and queue check, then inspect five new packs	Process owner; by the next agreed operating day	Updated instruction and separate follow-up findings; five is this example's chosen check count.

Read the actions back at the end of the meeting and link them to the source records. Do not close either action because someone says “the team has been reminded”. At the next meeting, inspect the evidence and decide whether to close, change or escalate it. A zero-blocker screenshot alone does not establish that the revised acceptance step was followed.

Copy this weekly meeting template

1. Purpose and operating window: confirm the week and the outcome this meeting protects.
2. Last actions: close, reassign or escalate; do not silently roll forward.
3. Capacity: review intake, completions, work in progress, ageing and near-term demand.
4. Service: identify commitments at risk and the dependency behind each one.
5. Quality: review sampled findings and choose one corrective action.
6. Blockers: decide, assign an authorised owner or set an escalation time.
7. People and continuity: confirm leave cover, coaching and approved access.
8. Read-back: repeat each decision, action, owner, due point and evidence.

After four weeks, ask whether the agenda shortened decision time, reduced stale work and closed more actions. Remove sections that do not support a real decision and strengthen the records that still require verbal reconstruction.