Track conditions without losing the next action.

Keep the requirement and its source together.

Keep the current requirement and its source in the approved file system. A short label may help people scan the list, but retain the exact wording the reviewer needs. When instructions change, mark the current version. Keep history as the applicable process requires.

Assign follow-up separately from the review decision. Under the agreed scope, a processing contact may chase an open item. The lender or another authorized reviewer decides whether the response resolves it. Make those roles clear in the tracker.

Use statuses that describe observable events.

A fictional tracker might show “awaiting response,” “received” and “awaiting review.” If all use “pending,” the team cannot tell whether to chase an item or wait for a decision. Agree a few clear labels. State what evidence allows each change.

A response in the approved system supports a “received” status. It does not prove the response is enough. If the reviewer asks for more detail, record the next step and owner. Keep the condition linked to the decision that resolves it.

• Current requirement and authoritative source
• Next action and responsible person
• Response location and receipt record
• Authorized review result or remaining question

Escalate uncertainty instead of hiding it in the list.

A condition with no owner or conflicting instructions needs a decision, not another reminder. Ask the designated contact and record the answer where the team can see it. Include open questions in the next handoff. Do not assume a list explains them all.

Fannie Mae’s loan-quality resources give lender-focused context. This tracking method is an editorial suggestion. It does not replace lender requirements or a formal quality-control program. Follow the reviewer’s actual instructions and the agreed scope when acting on a condition.