The update isn't good, and your hand is already reaching for another email instead of the phone. Say what changed, separate what you know from what you don't, and take responsibility for the next update.
That's the short answer to a question loan officers run into: how do you deliver bad news without making a hard situation worse?
I've put it this way: bad news doesn't age like wine. It ages like milk.
The longer you wait to deliver bad news, the more credibility you lose. You haven't made the problem smaller by avoiding the conversation. You've just left somebody else trying to guess what is happening.
Don't make them solve the mystery before you explain the problem
Start with the part that changed. Not a long speech about how busy everybody is. Not a list of people who were copied on the last message.
A useful update answers a few ordinary questions. What do you know? What is still being checked? Who owns the next step? When will you update the person again?
Those are communication questions, not a promise about a loan decision. If you don't know the answer yet, say that. Don't turn a guess into a fact because an uncertain answer feels uncomfortable.
There is a difference between being direct and acting like you know everything. One helps somebody understand the situation. The other gives you another conversation to clean up later.
A copied email is not the same as an owner
Everybody can be on a message and nobody can be responsible for the next move. That's not a plan. That's a crowded inbox.
Before ending the conversation, make sure the next task belongs to a person, not a vague group. If the task isn't yours to complete, you can still say who is handling it and what you are waiting to hear.
Don't invent a deadline on someone else's behalf. Ask what they can actually commit to. Then keep your own commitment about the update.
If a loan officer is comparing business models, this is worth asking about. Not just which tools appear in a presentation, but who handles a problem when the normal process gets stuck. A good question doesn't require you to insult the people in another model.
Don't confuse an update with a prediction
An update describes what has happened and what is being done. A prediction tells somebody how you think it will turn out. Keep them separate.
You can explain that a question is under review without promising the answer. You can say that a document was requested without saying that supplying it settles everything. You can give a time for your next conversation without promising a completion date you don't control.
That isn't a reason to hide behind vague wording. Be specific about the things you do know. Be equally plain about the things you don't.
People can ask useful questions when they understand where the uncertainty is. They can't do much with a reassuring sentence that doesn't tell them anything.
Keep your word on the small part you control
The Marine Corps taught me a simple rule: do what you say you're going to do.
That applies to the next phone call just as much as the big announcement. If you said you'd update somebody, update them. You don't need a perfect ending before you can keep a communication commitment.
Sometimes the honest update is that you're still waiting. Say what you are waiting for and when you'll check again. Don't pretend that waiting is progress. Don't disappear because there isn't a new answer yet.
And if you missed your own commitment, own that part. Adding a speech about somebody else's mistake doesn't change whether you made the call you said you would make.
Model versus model, not good people versus bad people
I spent ten years in retail. I'm not mad at retail. I started asking better questions.
Communication is one of those questions. If you're considering a different setup, ask how an ordinary issue gets handled. Who can answer it? Who follows up? What happens if the first person isn't available?
Ask those questions about the model you're in, too. The point isn't to collect complaints or make a move because somebody had a difficult day. It's to understand how the work gets done.
A different logo doesn't make the difficult call for you. Whatever model you work in, your own communication still belongs to you.
Before the next difficult call
Take a minute to write a short note for yourself. Put the confirmed change at the top. Put the unanswered question beneath it. Then put the person responsible for the next task and your own next communication commitment.
Keep private file details in the proper secure channel. This is not a suggestion to paste borrower records into a social conversation or a public contact form. The lesson is about taking responsibility, not making somebody's information public.
Then have the conversation. Give the other person room to ask what they need to ask. If you need to check an answer, check it instead of improvising one.
Questions loan officers ask
Do I need every answer before calling?
No. You need to be clear about which facts are confirmed and which questions remain. An honest update is different from a final decision.
Should I promise a result to calm somebody down?
No. Explain the next step you can actually take. A promise you don't control isn't a communication plan.
Is this a reason to switch companies?
Not by itself. Compare how the models handle the work, and be honest about your own habits. One difficult situation isn't a complete business comparison.
Make the call you keep putting off
If you're a retail loan officer trying to understand a different business model, read my story and the model behind it. Ask the operational questions before making a decision.
For a general question about working with Kenneth Travis, use the contact form on this page. Don't include borrower names, documents or private file details.
The next call doesn't need a speech. It needs the truth you have and a next step you own.
A loan officer with questions? Read KT's story or contact Kenneth Travis.
This is not a commitment to lend. All loans subject to credit approval. Guidelines subject to change without prior notice. Rates, programs and figures mentioned in this article reflect the date it was published.




