Claude Scheduled Task for Stagnant Loan Tasks: A Weekly Pipeline Accountability Loop

A mortgage team can review every file in the pipeline each Friday and still lose track of which ones have not moved all week. That was the gap on this team, even after Claude had started turning the call transcripts into tasks.

The people involved were a mortgage lending team lead, an operations coordinator, and a group of loan officers. The weekly pipeline review was recorded, and tasks were being created from it. The remaining problem was accountability between reviews. If you run a loan team with the same blind spot, see how we approach it on our page for mortgage loan officers.

The situation

The team already ran a recorded pipeline review every Friday. Claude, connected to ClickUp, Google Calendar, and Gmail, read the transcripts and created tasks for each person. The task creation itself worked. On review, the tasks were being made correctly.

The trouble started after that. The workflow did not help anyone see what happened next.

What was leaking

Three problems showed up on the review call.

First, Claude put the tasks on the calendar as separate events scattered across different days. A team that wants one Friday review ended up with a pile of stray calendar entries. Second, nothing flagged a task that sat idle before the next weekly review, so a stalled file looked the same as a healthy one. Third, the loan officers' phone calls existed only as MP3 recordings with no transcripts, so no tasks could be pulled from them at all.

What we built

We fixed the workflow in layers, starting with the calendar problem.

• Calendar fix: a dictated prompt plus a screenshot of a correct example. Review notes and each person's tasks now go in the notes field of the existing recurring Friday invite, with no new events created. The last instruction was to save that behavior to Claude's memory.
• Scheduled task: Claude looks for tasks idle for more than three days and pulls the stagnant or overdue ones into the Friday review event, with a plan to resolve each. It runs early on Friday, at 6am, before the call. A dry run is available so the team can check it first.
• Dashboard: Claude also built a live artifact dashboard.
• Planned next: daily Gmail drafts to each loan officer listing overdue task titles as a short, gentle bullet reminder, and a 6am inbox sweep that marks tasks complete in ClickUp when officers reply.

What changed

The dry run pulled everything up correctly and showed 38 stagnant and overdue tasks. Those are tasks the weekly review had no way to flag on its own. Now they arrive in the review event already flagged.

The loop is not closed yet, and we want to be plain about that. Missing call transcripts were named the single biggest blocker. Until the loan officers' calls are transcribed, the workflow can only see what happens in the recorded review.

How to roll it out without a fight

The rollout advice was to keep week one small: transcript-only accountability, with no ClickUp logins for the loan officers. They get the benefit through the Friday review and the reminders before they are asked to learn another tool.

For the missing transcripts, the first move is to ask the phone vendor to enable transcription. If that is not available, the fallback is a nightly Claude Code job that transcribes the recordings into Google Drive.

Frequently asked questions

How does Claude find stagnant tasks in a mortgage pipeline?

A scheduled task checks ClickUp for tasks idle for more than three days, plus anything overdue, and pulls them into the Friday review event with a plan to resolve each one. In the dry run it surfaced 38 stagnant and overdue tasks that the weekly review had no way to flag on its own.

Why put tasks in the notes of the recurring Friday invite?

The first version created separate calendar events across several days, which buried the review. Putting each person's tasks in the notes of the existing recurring invite keeps everything where the team already looks, and it creates no new events to clean up.

What if loan officer calls are only saved as audio files?

Then no tasks can come out of them, which is why missing transcripts were called the biggest blocker. Ask your phone vendor to turn on transcription. If it cannot, a nightly Claude Code job can transcribe the recordings into Google Drive as a fallback.

Do loan officers need to log in to ClickUp?

Not in week one. The advice was to start with transcript-only accountability and add reminders by Gmail later, so officers see their overdue items without learning a new tool before they have seen any value.

If your pipeline review ends with good intentions and no follow-through, book a 30-minute AI follow-up and reporting audit. We map where tasks go quiet on your team and show you the loop that catches them.