Review processing exceptions without losing context.

Record what differs from the expected workflow.

An exception might be an unclear instruction, conflicting details or a blocked handoff. Describe what you can observe before labeling it. Name the relevant instruction or expectation and its source. Another authorized person should be able to see what needs attention.

A general work log cannot create a policy exception or allow a departure from lender requirements. A request for a decision stays a request until the responsible party answers. Make that clear so a note is not mistaken for approval.

• Describe the issue and the source of the relevant instruction.
• Name the person responsible for obtaining the decision.
• Record the next action and the evidence needed to close it.

Keep the question connected to its answer.

In a fictional file, a changed closing plan conflicts with an earlier instruction. Record the conflict, who was asked to resolve it and whether they replied. When an answer arrives, link it to the question and state the action it allows.

Keep borrower details in the approved file system. Use your organization’s reference method to discuss patterns elsewhere. Keep the log current and available to the right people. A separate spreadsheet that falls out of sync can create more confusion.

Separate an isolated event from recurring friction.

Group recurring issues by the gap they reveal, such as unclear roles, missing details or conflicting instructions. Check the context before assuming similar labels share a cause. Choose a focused change and check it against the handoff that failed.

Fannie Mae’s outsourcing guidance covers seller duties for outsourced work. It does not prescribe this log or give it approval authority. Use the log within actual lender instructions and agreed roles. Close an entry when the responsible owner can show how it was resolved, not just to shorten the list.