You receive an email with the subject line "Just checking in."
You open it. The first sentence is "Just checking in on this."
You read the whole message. You still do not know what the sender wants.
Why this phrase stopped working
"Just checking in" has become the default way to follow up on anything. It is so common that it has lost all specific meaning.
When someone says they are "checking in," they are not telling you:
- What they are checking on
- Why they are checking now
- What kind of response they need
- Whether there is a deadline
The phrase has become a placeholder. It signals "I am following up" without actually communicating anything about the follow-up.
That makes it easy to write, but hard to respond to.
What "just checking in" actually says
When you write "just checking in," you think you are being polite and low-pressure.
But here is what the message often communicates instead:
"I do not know how to start this email."
The phrase is filler. It is what people write when they need to follow up but have not thought about what they actually need to say.
"I do not want to sound pushy, so I am using the softest possible language."
The problem is that soft language does not make the request go away. It just makes the request unclear.
"I hope you remember what I am talking about, but I am not going to remind you."
If the recipient has to search their inbox to figure out what you are referring to, you have made the follow-up harder than it needed to be.
What real checking in looks like
A real check-in does three things:
-
It names what you are checking on.
Not "the project" or "this." The specific thing. -
It explains why you are checking now.
Is there a deadline? A dependency? A decision that is waiting? -
It states what you need.
An update? A confirmation? A decision? A file?
When you include those three things, the recipient knows exactly what you are asking for and why it matters.
Example 1: Project status
Vague version:
Just checking in on the project.
The recipient does not know:
- Which part of the project you are asking about
- Why you are asking now
- What kind of update you need
Clear version:
The client asked for a progress update on the design phase. Can you send me a quick status on where we are?
Now the recipient knows:
- You need a status on the design phase
- The client is waiting for it
- You need it soon enough to respond to the client
Example 2: Waiting for a response
Vague version:
Just checking in to see if you saw my last email.
This does not tell the recipient what was in that email, or whether it requires action.
Clear version:
I sent over the contract last week and haven't heard back. Do you need any changes before we move forward?
Now the recipient knows:
- You are waiting on the contract
- You are ready to move forward
- You are asking if there are blockers
Example 3: Confirming a plan
Vague version:
Just checking in about tomorrow.
The recipient has to guess what "tomorrow" refers to. A meeting? A deadline? A delivery?
Clear version:
Are we still on for the 2pm call tomorrow? Let me know if the time doesn't work anymore.
Now the recipient knows:
- You are confirming the 2pm call
- You are open to rescheduling if needed
Example 4: Following up on a request
Vague version:
Just checking in on the report.
Clear version:
I need the Q1 report by end of day Thursday to include it in the board deck. Can you confirm you'll have it ready by then?
The second version gives the recipient:
- A specific deadline (Thursday end of day)
- A reason for the deadline (board deck)
- A clear ask (confirmation)
Example 5: Checking on a decision
Vague version:
Just checking in to see if you made a decision.
Clear version:
Have you had a chance to decide on the vendor? We need to place the order by Friday to meet the launch timeline.
The second version explains:
- What decision you are waiting on
- Why the timing matters
- What happens if the decision is delayed
When "checking in" is actually appropriate
There is one situation where a casual check-in works: when you genuinely do not need anything specific, and you are just maintaining the relationship.
But even then, it helps to be specific about what you are checking on.
Generic version:
Just checking in!
Better version:
How's the new role going? I know the first month can be a lot.
The second version is still casual, but it shows you are checking on something specific. It gives the other person something concrete to respond to.
Why vague follow-ups create more work
When you send a vague follow-up, the recipient has to do extra work:
- Search their inbox to figure out what you are referring to
- Guess what kind of response you need
- Decide whether this is urgent or not
If they guess wrong, you end up with another round of back-and-forth to clarify.
A clear follow-up saves time for both people.
The real cost of "just checking in"
The phrase has been used so many times that it has become a signal itself.
When someone sees "just checking in," they often interpret it as:
- Low priority (because the sender did not bother to explain why it matters)
- Not urgent (because there is no deadline mentioned)
- Possibly ignorable (because the ask is not clear)
That is the opposite of what you want when you are following up.
What to do instead
Before you write "just checking in," ask yourself:
-
What am I checking on?
Name the specific thing. Not "this" or "the project." The actual deliverable, decision, or task. -
Why am I checking now?
Is there a deadline? A dependency? A reason this matters today instead of next week? -
What do I need from the other person?
An update? A decision? A file? A confirmation?
If you can answer those three questions, you do not need "just checking in." You can write a follow-up that actually communicates.
A quick self-check
If you have written "just checking in," try removing that phrase and see what is left.
If the rest of the message is still clear, you did not need the phrase.
If removing it makes the message feel too abrupt, the problem is not the missing phrase. The problem is that the message does not have enough context.
Add the context. Do not add filler.
When the tool is useful
If you have written a follow-up and you are not sure whether it is clear enough, Email Formalizer can help. It is not about making the message longer. It is about making sure the message actually says what you need it to say.
The goal is not to sound more polite. The goal is to make it easy for the other person to respond.
The bottom line
"Just checking in" is not checking in. It is avoiding the work of writing a clear follow-up.
If you want a response, say what you are following up on, why it matters now, and what you need.
Real checking in is specific.