Make document requests clearer to act on.

Trace the request to its source.

Find the instruction behind a request before asking for another document. It may come from current lender requirements, an authorized reviewer or the agreed workflow. A generic checklist cannot create a new file requirement. If the instruction is unclear, ask the reviewer.

Keep the exact source wording in the approved record. Give the recipient a clear action without losing that meaning. “Send everything again” is too vague. Is the item missing, hard to read, incomplete or waiting for review? Each state needs a different response.

Make the next action specific.

Take a fictional case where a document has arrived but cannot be read. Explain why the existing copy cannot be reviewed. Name the approved way to send a readable copy. Do not suggest the borrower failed to reply or ask for unrelated details just to fill the checklist.

Agree who sends the request so the recipient gets a clear message from the team. Keep sensitive details in the approved system. Use neutral descriptions in planning discussions. Do not put actual borrower material in this site’s worksheets.

• Confirmed missing or unusable item
• Source of the requirement
• Person responsible for the next request
• Approved response channel
• Record that distinguishes receipt from review

Close the request only at the right stage.

Record receipt when the item arrives, then send it to the authorized reviewer. An attachment alone does not meet the underlying requirement. If it raises a new question, keep the original context and explain the next step. Avoid a new message chain that loses the earlier request.

The CFPB’s TRID collection covers disclosure rules and official implementation materials. It is not a borrower-document checklist for every file. CISA gives general account-security advice. Use each source within its scope. Follow the lender instructions and approved security process for the actual request.