On this page
A closing calendar shows the dates borrowers care about, but it does not show the work that has to happen before those dates. Two closings on Friday can mean four different document reviews, three title follow-ups, and a wire confirmation that all land on Thursday. A weekly capacity plan translates the calendar into the processor hours the team actually has. It also shows where a small schedule change will create a large problem.
Count closings by work type, not just date
Start by grouping the week's closings by the kind of work they require. A refinance with clean documents is not the same as a purchase with a repair addendum and a new appraisal. Give each closing a work type such as standard, complex, or high-touch, and list the tasks that type always includes. The grouping is more useful than a raw closing count because it reflects the effort behind the date.
Update the work type when the file changes. A standard file that adds a gift letter and a second appraisal has become complex, even if the closing date did not move. The processor should not have to carry that change silently. A short note in the calendar entry gives the next person the information they need to plan.
Map each closing to its remaining tasks
For each file, list the tasks that still have to happen before closing. Include document review, condition clearing, title coordination, disclosure timing, and the final package check. Mark the owner and the due date for each task. The list should be specific enough that a backup processor can pick up an item without reading the entire file.
Remove tasks that are already complete rather than leaving them in the plan. A long list with several finished items makes the remaining work look larger and hides the real constraints. If a task depends on a vendor, record the expected response time and the follow-up date. The plan should show where the team is waiting, not only where it is working.
Convert tasks into processor hours
Give each task a realistic time range instead of a single optimistic number. A document review might take twenty to thirty minutes on a clean file and twice that when the file has exceptions. Add the ranges for the week and compare the total with the hours the team has available after meetings and routine queue work. The gap is the planning problem.
Use the previous month's actual times to adjust the ranges. If title follow-ups consistently take longer than estimated, the estimate is wrong and the calendar will keep surprising the team. The loan processing support workflow should include a simple time log for the tasks that cause the most variance. Estimates improve when they are based on recent work rather than memory.
Protect review time before the deadline
The plan should reserve time for the reviewer, not only for the preparer. A file that is prepared on Thursday and reviewed on Friday morning leaves no room for a missing signature or a disclosure correction. Schedule the review at least one business day before the closing when the file type allows it. For complex files, reserve two checkpoints.
The review block should be visible on the calendar so that new requests do not quietly consume it. If a manager needs to move the block, the tradeoff should be explicit: something else moves or the closing date is at risk. A calendar that looks full but has no protected review time is not a capacity plan. It is a list of hopes.
Shift work when the calendar compresses
When several closings land on the same day, move preparation earlier rather than asking the team to work faster on the final day. Pull forward document reviews and vendor follow-ups that do not depend on the closing date. Keep the final package check close to the closing, because that is when the latest documents arrive. The goal is to spread the work without spreading the risk.
If the week is genuinely over capacity, decide which files can move before the borrower feels the delay. A short, honest conversation with the loan officer is better than a missed closing. The mortgage operations support lead can help compare the options and protect the files with the least flexibility. Rebalancing is a normal part of planning, not a failure.
Review the plan each Friday
End the week with a short comparison of planned and actual work. Note which estimates were close, which files changed type, and where the team lost time to avoidable follow-ups. Keep the review to a few minutes and record one change for next week. The CFPB's closing disclosure guidance is a useful reminder of the borrower-facing deadlines that constrain the plan, but the internal lesson is about sequencing.
The Friday review should produce a cleaner Monday calendar, not a longer report. If the same task is underestimated every week, change the range. If the same file type always needs a second review, add the checkpoint. Keep the review notes beside the calendar so the next planner can see why an estimate changed. A capacity plan improves through small corrections, and those corrections need a regular place to happen.