Remote Employee Not Responsive During Work Hours: A Manager's Step-by-Step Guide
The short answer: Before escalating, confirm your expectations were actually communicated in writing. Then have a direct conversation. Then document. Then discipline if the behavior continues. Most responsiveness problems resolve at step one or two.
You sent an email at 10am. It’s 2pm and you still have not heard back. This is not the first time. Your remote employee seems to be physically present but functionally unavailable during the hours they are supposed to be working, and you are not sure what to do about it.
This is one of the most common management frustrations in the post-pandemic workplace, and it is also one of the most mishandled. Here is how to address it effectively.
Step 1: Define What “Responsive” Means
Before you address the behavior, make sure you have clearly communicated your expectations. “Responsive during work hours” means different things to different people. To you it might mean replying to messages within an hour. To the employee it might mean replying before the end of the day.
If you have not explicitly defined response time expectations in writing, this conversation starts there, and not with accusation. Put this in writing (in an offer letter addendum, a remote work agreement, or your employee handbook). You cannot hold someone accountable for a standard they did not know existed.
Communication Type Reasonable Response Window
Urgent Slack/Teams message Within 1-2 hours
Standard email Same business day
Non-urgent project updates Within 24 hours
Step 2: Separate the Symptom From the Real Question
Slow response times are a symptom. The real question is: is the work getting done?
If the employee is meeting all their deadlines, producing quality work, and engaging fully in meetings and collaborative work but just does not respond to messages as fast as you would like, this is a communication style issue, not a performance issue. It is still worth addressing, but the conversation is different.
If the employee is missing deadlines, producing substandard work, or disengaged in team collaboration in addition to being unresponsive, that is a performance issue, and the non-responsiveness is one symptom of a larger problem.
Getting this distinction right before you have the conversation matters. It determines what you're actually asking for.
Step 3: Have a Direct Conversation First
The first step is always a direct conversation, not a monitoring tool, not a surprise Zoom call to catch them out, not a passive-aggressive cc’ing of their manager on emails to create a paper trail.
Schedule a one-on-one and be specific:
“I’ve noticed that messages during the day often go several hours without a response. I want to talk about communication expectations for your role. Here is what I need from you, and I want to hear if something is getting in the way.”
Then listen to what they say. There may be a time zone issue, a technical problem, a health situation, a caregiving responsibility, or a structural issue with their role that is contributing. You won't know until you ask. Many responsiveness problems get resolved in a single direct conversation because the manager finally stated the expectation clearly for the first time.
What to Say If This Is a Pattern
If this has happened before and you've already had an informal conversation, be more direct:
"We talked about response time expectations in [month]. I'm still seeing messages go unanswered for several hours, and that's affecting [specific impact on the team or work]. I need this to change, and I want to understand what's getting in the way."
Name the specific impact. "It affects the team" is abstract. "When I can't reach you before our client call, I can't get the information I need in time" is concrete.
Step 4: Set Clear, Written Expectations After the Conversation
After the conversation, document the expectations in writing. Send a follow-up email summarizing what was discussed and what you both agreed to. This doesn't need to be formal; a brief email works fine:
"Thanks for talking through this today. To recap what we discussed: during your core hours of [X to Y], I need you to be reachable via [Slack/Teams/phone] and to respond to messages within [timeframe]. If you're going to be unavailable for more than [timeframe], please give me a heads up. Let me know if you have any questions." After the conversation, document the expectations in writing. Specifically:
• Core hours during which the employee should be available and responsive
• Maximum response time for different types of communication (urgent vs. routine)
• How to indicate when they will be unavailable (brief status updates, calendar blocking)
• How performance will be evaluated: outcomes and output, not hours logged
Written expectations become the basis for any future performance conversation. Without them, you are trying to hold someone accountable for a standard that was never documented. For more on building the written policies that support consistent management, see HR Policies Every Small Business Needs.
Step 5: Document the Pattern Before Escalating
If the behavior continues after the conversation and written expectations, start documenting before you move to formal discipline. Documentation doesn't have to be elaborate. A simple running log works:
Date and time of the unreturned message
How long it took to receive a response (or that no response was received)
Any impact on work or team (missed deadline, delayed client response, etc.)
Whether the issue was previously discussed
Two to three weeks of documented incidents gives you the factual basis for a formal conversation. Without documentation, you have a complaint. With documentation, you have a pattern.
Step 6: Set Up a Brief Check-In Structure
For employees who struggle with remote accountability, a brief recurring check-in can reset the dynamic without surveillance. This doesn't need to be long. A 10-minute morning Slack message or a standing 15-minute weekly call serves two purposes:
It creates a predictable, low-pressure touchpoint that makes the employee feel connected
It gives you a natural opportunity to address issues early before they become patterns
This works especially well when unresponsiveness stems from disengagement or disconnection rather than intentional avoidance.
Monitoring Software: Proceed With Caution
Some employers respond to remote responsiveness concerns by installing software that tracks keystrokes, takes periodic screenshots, or logs application usage. This is legal in most states with appropriate disclosure, but it creates significant trust and morale problems, is expensive to implement, and rarely fixes the underlying issue.
Before going down the monitoring path, honestly ask: have you had a clear, direct conversation with this employee about your expectations? In the vast majority of cases, the answer is no, or the conversation happened once, vaguely, without written follow-up. Start there. The conversation is almost always more effective than surveillance.
If monitoring becomes necessary, consult an employment attorney in your state before implementation. Disclosure requirements and limitations vary.
When to Move to Formal Discipline
If you have:
Communicated clear expectations verbally
Followed up in writing
Given the employee a reasonable period to demonstrate improvement
Documented continued non-compliance
...then formal discipline is appropriate.
Use your progressive discipline process: a written warning that documents the specific expectation, the specific instances of non-compliance, and the required behavior going forward with a clear timeline. If output is the underlying issue, a formal Performance Improvement Plan (PIP) with specific, measurable goals is the right tool.
For guidance on structuring this process, see How to Write a Progressive Discipline Policy.
Frequently Asked Questions
What if my remote employee says they were available but I just couldn't reach them? This is common, and it usually points back to unclear expectations about channel. If your employee checks email three times a day but you need same-day responses, the issue isn't availability, it's that you haven't agreed on which platform is used for what. Define it in writing: urgent matters go to Slack, routine updates go to email. Once the channel and response time expectations are documented, "I was available" is no longer a valid response to unreturned messages.
Can I require a remote employee to be on camera during work hours or stay logged into Slack? Yes, generally, as long as you apply the policy consistently and communicate the expectation clearly before enforcing it. Requiring a status indicator in a messaging platform (active/away) is reasonable. Requiring continuous camera-on during unstructured work time is more likely to create resentment and pushback. Focus on outcomes and availability, not visible presence.
When does unresponsiveness become a fireable offense? When it is persistent, documented, has been formally addressed through your discipline process, and is causing clear harm to the business or team. An isolated incident or two is not grounds for termination. A documented pattern where the employee has received clear written expectations, a formal written warning, and has continued to fail to meet the standard can be grounds for termination. At-will employment means you technically can terminate for this reason, but documented process protects you from wrongful termination claims.
Do I need a written remote work policy? Yes, especially if you have more than one or two remote employees. A written remote work policy that covers availability expectations, communication standards, and performance expectations protects both you and your employees. It ensures everyone operates under the same rules and gives you a documented standard to reference in any performance conversation. See What Should Be in an Employee Handbook for what to include.
What if the responsiveness issue is really a performance issue? Then address the performance directly. Non-responsiveness is a symptom. If work isn't getting done, hold the employee accountable for the outcomes (missed deadlines, quality issues) rather than just the communication behavior. A Performance Improvement Plan with specific, measurable goals is the right tool when performance is the core issue.
The Right Tools for What Comes Next
If the conversation and written expectations don't resolve the issue, here's what you'll need:
Progressive Discipline Policy Template: A written policy that establishes your discipline process before you need it. Includes verbal warning, written warning, and final warning stages.
Performance Improvement Plan (PIP) Template: When remote performance is the underlying issue. Includes a Manager Guide, structured goal blocks with measurable criteria, a biweekly check-in log, and a final review section.
Both are editable Word documents, instant download, created by a SHRM-SCP certified HR professional.
Questions about this or other HR situations? Browse all resources or contact us.
