Table of contents
A new mortgage assistant can learn the vocabulary in a day and still make expensive mistakes in the first week. The gap is not intelligence. It is the difference between knowing what a condition is called and knowing which document satisfies it. A shadowing plan closes that gap before the assistant touches a live file.
Set an access boundary before day one
Decide which systems the new person can see and which actions require a reviewer. Read-only access to the loan origination system is enough for the first two days. Keep document upload, borrower messaging, and status changes behind a named reviewer until the assistant completes a sample review. Write the boundary down so nobody grants access by habit.
The boundary protects the borrower as much as the file. A new assistant who sends a message in the company's name creates a commitment the team must honor. A reviewer who sees the draft first can catch an ambiguous promise, a wrong date, or a missing caveat. The extra step is short and it prevents a repair that takes much longer. The Consumer Financial Protection Bureau's mortgage resources describe the borrower-facing documents and timeline that the reviewer is protecting.
Pair observation with a written map
Give the assistant a one-page map of the file lifecycle before the first shadowing session. The map should name the stages, the owner of each stage, and the record that proves the stage is complete. Leave space for the assistant to write questions. The map is a learning aid, not a policy document, so it can stay simple.
During observation, ask the processor to narrate decisions rather than only clicks. The narration should explain why a document was accepted, why a condition stayed open, and why a file moved to the next stage. The assistant writes the reason in a notebook and compares it with the written map. Differences between the map and the narration reveal where the real process lives.
Use sample files with known answers
Build a small set of closed files with the correct outcome recorded. Choose one clean file, one file with a missing page, and one file with a condition that was cleared after a second request. Remove borrower identifiers before the assistant reviews them. The set gives the new person a safe place to practice judgment.
Ask the assistant to write the next action for each sample file before seeing the answer. Then compare the answer with the recorded outcome. The comparison is more useful than a quiz because it shows how the assistant reads evidence. Review the differences together and write down the rule that was missed.
Schedule a daily fifteen-minute review
A short review at the same time each day prevents small misunderstandings from becoming habits. Ask three questions: what did you see, what did you write down, and what are you still unsure about. The assistant should bring one example, not a general report. The reviewer should answer with a rule and an example.
Keep the review separate from the production huddle. The huddle is for the queue, and the onboarding review is for learning. Mixing them teaches the new person that questions are interruptions. A separate slot signals that the team expects questions and has planned time for them.
Add a second-channel test
Mortgage work arrives through the loan origination system, email, borrower portals, and phone calls. A new assistant may learn one channel and miss the others. Give the assistant a sample message from each channel and ask where the record belongs. The answer should include the file, the document type, and the next action.
Test the handoff language as well. Ask the assistant to write a note that another person could act on without asking a question. A note that says "review" is not enough. A note that names the missing page, the borrower, and the deadline is usable. Review the note against the same standard the team uses for live files.
Hand over one low-risk queue
Choose a queue with clear rules, low borrower contact, and a reviewer who is available. Document collection follow-up or post-closing trailing documents often fit. Do not start with a queue that requires judgment about credit, disclosures, or exceptions. The first live task should let the assistant experience the rhythm without carrying the highest risk.
Set a volume limit for the first week and keep it below the normal load. The limit is not a punishment. It creates room for review and correction while the assistant builds speed. Increase the limit only after the reviewer confirms that the notes and the decisions are consistent.
Record what the shadow week proved
At the end of the week, write a short record with three parts: tasks observed, samples completed, and live work reviewed. Include the errors that were caught and the rules that were clarified. This record becomes the starting point for the next week and the evidence for the access decision. Keep the record factual and brief, and store it where the next reviewer can find it.
The loan processing support lead should sign the record, not the trainer alone. A second signature makes the access decision shared and gives the new person a clear owner for questions. It also prevents a trainer from granting access because the week ended rather than because the work was ready. The signature also gives the trainer a reason to document the evidence instead of relying on memory.
Close the week with a written gate
A gate is a short list of conditions that must be true before the assistant works without review. The list might include ten sample files with correct next actions, two clean live notes, and a channel test. Keep the list small enough to verify in one sitting. A gate with twenty items will be waived.
Give the assistant the gate on day one so the expectation is visible. Review the gate on day five and record the result in the personnel file. If the assistant is not ready, extend the shadow week with a specific practice plan. A delayed gate is cheaper than a live error that reaches a borrower. The mortgage operations support lead can keep the gate with the onboarding record so the next trainer uses the same standard.