Write a processing update people can act on.

Lead with the current position and next action.

Start with what the reader needs now: the current stage, what changed and the next step. Keep the full history in the approved record instead of repeating it in each message. An update should help someone act, beyond showing that messages were sent.

Separate facts from plans. “Response received and awaiting review” describes what happened. Say a file is ready only when the responsible authority has confirmed that status. Do not turn a planned event into an approval or closing promise.

Give each recipient the context they need.

A fictional internal update could say that an item arrived, the reviewer has the next step and a question stays open. The follow-up owner needs the question and source. A manager may need to decide who owns it. Leave out borrower details that neither person needs.

Use the agreed channel and keep full context in the approved system. For a task, name the role and the reply you need. If the message is just for awareness, say so. Make it clear who should act and who only needs to know.

• Verified change since the previous update
• Current unresolved item or decision
• Next action and named role
• Where the authorized record can be found
• Whether acknowledgment or a decision is needed

Make uncertainty explicit.

If the next event depends on someone else, say who or what you are waiting for. Do not invent an estimate. When an earlier assumption changes, correct it and explain the new action. Replace an outdated summary so readers do not act on it.

CISA’s Secure Our World guidance covers phishing and account protection in general. It is not a complete mortgage communication policy. Follow your approved security process. The status-update builder uses planning choices only. It is not a place for borrower details and does not send working-file information.