Table of contents
A daily queue tells the team what is late today. It rarely shows whether the pod has enough capacity for the next month. The team may be surviving on overtime, skipped checks, or a manager who absorbs the overflow. Those workarounds hide the real gap until a busy week turns into a service failure.
A monthly capacity review makes the gap visible before it becomes a crisis. It uses queue evidence, time estimates, and a short list of upcoming work to decide where to add capacity or reduce scope. It is not a budget presentation or a performance ranking. This guide explains how to run the review and end with one practical change.
Collect the work that actually arrived
Start with the work the pod received, not the work the pod completed. Count new files, conditions, borrower requests, vendor follow-ups, and handoffs for the month. Use the systems the team already works in and avoid building a parallel tracker. The count should cover every lane that consumes pod time.
Separate volume from mix. A month with the same number of files can feel heavier if the files include more conditions or more lender portals. Record the mix by loan type, lender, and complexity. A simple count without the mix can lead to the wrong staffing decision.
Measure the time each lane consumes
Estimate the time per unit for each lane, such as minutes per file setup or minutes per condition. Use a time study, a sample, or a team estimate, and state the method. The estimate does not need to be perfect, but it must be consistent from month to month. A rough number used consistently is more useful than a precise number that changes every review.
Multiply the time per unit by the volume to get the demand for each lane. Add the time spent on meetings, training, and exceptions. The total should be compared with the available hours, not with a theoretical full day. A person who spends two hours in meetings has less capacity than the raw headcount suggests.
Include a buffer for variability. Mortgage work arrives in bursts, and a plan with no buffer will fail in the first busy week. A buffer of ten to twenty percent is a starting point, not a universal rule. The team should adjust it based on the volatility it observes.
Compare capacity with the next month
Look forward as well as backward. Add known closings, lender changes, vacations, and training to the next month's plan. A month with a new guideline rollout may need more review time even if the file volume is flat. A month with a holiday week has fewer available hours.
Calculate the gap by lane rather than only in total hours. A pod may have enough total capacity but a shortage in one lane, such as appraisal follow-up. A lane-level view shows where a temporary reassignment could help. It also prevents the team from hiring for the wrong work.
Mark the assumptions in the plan. If the review assumes a certain volume or a certain time per file, write it down. A plan without assumptions cannot be updated when reality changes. The team should review the assumptions before debating the conclusion.
Identify the queue that needs a change
Choose one queue or lane for action. A review that tries to fix five things at once usually changes nothing. The chosen lane should have the clearest evidence of strain, such as rising age, repeated overtime, or a growing exception list. Name the evidence in the review.
Distinguish a capacity problem from a process problem. A queue that is growing because of duplicate requests may need a condition counter, not another person. A queue that is growing because of volume may need a temporary reassignment. The review should test the cause before recommending the fix.
Consider the cost of the fix and the cost of doing nothing. A temporary contractor may be cheaper than a delayed closing, while a process change may take longer to show results. The review should compare the options in plain terms. The team does not need a full financial model, but it does need a reasoned choice.
Choose one fix and one owner
Write the fix as a specific action with a start date and an owner. "Add capacity" is not a fix, while "reassign two hours of appraisal follow-up to the backup processor for four weeks" is. The action should state what changes, who does it, and when the team will review the result. A specific action also makes it easier to decide whether the fix should continue after the trial.
Set a measure for the fix. The measure might be the age of the queue, the number of late checkpoints, or the hours of overtime. Pick one or two measures and keep them stable. A fix with no measure cannot be evaluated, and a fix with too many measures cannot be explained.
Review the result at the next monthly meeting. If the fix worked, decide whether to keep it or make it permanent. If it did not work, ask whether the cause was wrong or the execution was weak. A failed fix is useful evidence if the team reviews it honestly.
Review the trade-offs with the team
Capacity decisions create trade-offs. Adding a person may require training time, while reducing scope may delay a service the team values. Discuss the trade-offs with the pod instead of announcing a decision. The people doing the work often see consequences that the manager misses.
Be explicit about what will not be done. A plan that adds work without removing something is a plan for burnout. The review should name the tasks that will pause, shrink, or move. The team should agree that the trade-off is acceptable or propose a better one.
Protect the review from becoming a performance conversation. The purpose is to match work with capacity, not to judge individuals on volume. A pod that fears the review will hide problems and inflate estimates. Keep the discussion on the system and the evidence.
Keep the review separate from performance ranking
Use team-level and lane-level measures for capacity. Individual rankings on file count can reward speed over accuracy and discourage help. If individual measures are necessary, keep them separate from the capacity review. The two conversations should have different purposes and different data.
Share the capacity plan with the loan officers and the operations lead. They need to know what the pod can absorb and where the trade-offs fall. A plan that stays inside the pod will not change the promises made to borrowers. The review should improve the whole pipeline, not only the pod's internal comfort.
Repeat the review every month with the same core measures. A consistent rhythm makes trends visible and reduces the chance that a single busy month drives a permanent decision. The team can adjust the plan as the evidence changes. The goal is a pod that can see its capacity before the queue forces the issue.
The Consumer Financial Protection Bureau's mortgage resources show why reliable service matters to borrowers. A capacity review supports that reliability by matching promises with the work behind them. The mortgage operations support team can run the review and track the chosen fix. Pair it with the closing calendar capacity plan so monthly and weekly decisions use the same evidence.