Employee Not Responding to Emails: What to Agree First

An employee not responding to emails can leave a decision or handoff waiting. Start with one request that affected the work. Find out what happened to it, then agree what response is needed, when it is realistic and what to do if the answer is not ready.

Employee not responding to emails: start with one request

Choose a specific example: the budget question sent on Tuesday, the missing approval or the handover that could not continue. Separate the time you sent it from the time you needed the input. A message asking for "thoughts when you get a chance" does not tell someone that a colleague will be waiting for a decision at noon.

Ask: "I was waiting for your answer on the supplier quote, and the order could not move. Can we look at the request together? What happened after it arrived?" This is an illustrative opening. Leave room for the employee to correct your account, including whether another person owned the decision or the email arrived while they were unavailable.

You might find an unclear ask, too many places to check, a missing input, conflicting priorities or an agreed focus period. An email may also have been missed despite a clear expectation. The explanation should determine the next action. Do not choose a personality label before hearing it.

If the wider responsibility is disputed, use the responsibility check before adding a reply deadline. A quick acknowledgement will not resolve a decision nobody has authority to make.

Make the expected urgency explicit

In the final experiment, 852 full-time US employees considered hypothetical emails. A note clarifying non-urgency aligned response expectations outside working hours. It did not test whether employees answered real requests faster, and its direct effects on perceived stress were not statistically significant.

That finding supports a modest practice: put the expectation into the message. "For your next working day; I need your decision by Thursday afternoon" gives the recipient more information than an evening timestamp. The study does not explain why a particular employee has not answered an in-hours request.

If a request cannot wait until the person is next available, identify the authorized cover or existing urgent route. Sending it to more inboxes does not create availability. Do not make an ordinary email urgent by following it with repeated pings or a message to a private number.

Agree what kind of reply the work needs

1. 01

   Name the response

   An acknowledgement confirms that the request has been seen and says who will handle it. An answer supplies the information or decision needed. Approval requires the relevant authority, and completed work requires the actual output. Specify which one you need; a brief "seen" can leave the real task untouched.

2. 02

   Fit the time to the work

   Agree a specific time for the needed response within existing working availability. Ask what information and effort the answer requires. If it conflicts with another commitment, make a priority decision or change the request. Avoid imposing the same response time on every role and every message.

3. 03

   Choose one working route

   Use the channel people already check for this type of request. Put the ask, owner and needed time together, with a link to the relevant work. Reserve any urgent route for its agreed purpose, and make cover explicit for times when the recipient will be unavailable.

4. 04

   Say when the answer is not ready

   Agree how the employee will report a missing input, timing conflict or decision outside their authority before the work is left waiting. Name who can resolve the blocker or authorize the fallback. Silence is not approval, acceptance of a deadline or permission to act.

Only require acknowledgement where the work needs it. A general FYI does not need a second task confirming that it was read. If you have to request a status update on every email, inspect how the team routes work and which messages actually require a decision.

When the needed answer will not fit alongside existing commitments, make an explicit workload trade-off. Adding a short reply can be reasonable; adding the analysis behind it may require other work to move.

Acas guidance on setting objectives says they should reflect the employee's usual tasks and workload, be achievable and have a reasonable time frame. Apply that principle to the actual role. This guidance does not set a universal email response time.

Turn the agreement into a usable request

Consider this hypothetical example. A manager needs a supplier recommendation before approving an order on Wednesday. The employee is available during the agreed Tuesday working hours and on Wednesday morning. Both confirm that a Wednesday morning answer is feasible if the current comparison task takes priority. For this request, they agree a Tuesday noon acknowledgement and a Wednesday 10am answer. These times illustrate an agreement; they are not recommended deadlines for every team.

The manager writes: "Please recommend supplier A or B for this order. Acknowledge by noon today and send the recommendation with the price comparison by 10am Wednesday. If a price is missing or that timing no longer works, tell me what is blocked in the acknowledgement. I will resolve the priority or ask the operations lead to arrange cover. Do not place the order without my approval."

The employee replies before noon: "I own the comparison. Supplier B has not confirmed the delivery charge, so I cannot recommend a choice yet. I will check with them this afternoon. If it is still missing at 4pm, I will let you know so you can decide the next step." The manager now knows who owns the work, what is missing and when another decision may be needed.

If the delivery charge remains unavailable, the manager still has to act on the status: obtain the missing information, change the order timing or use an authorized alternative. An acknowledgement cannot make the underlying constraint disappear. If noon passes without a reply, follow the agreed work route and cover arrangement; do not infer that the employee approved the order.

Write the agreement where both people can find it. Keep the request, response expectations, relevant blocker, owner and follow-up point. There is no need to copy a private inbox or record personal explanations to maintain a working agreement.

Current communication preferences in Coop Profile can help you ask which working route and format are useful now. Confirm them with the person. A profile does not set their working hours, authorize a decision or decide the required response time.

When the agreed reply still does not arrive

Tell the employee that you will review the next few requests of this kind together. Use comparable work that needs an answer; do not turn every message into a responsiveness score. Check whether the acknowledgement named ownership or a blocker, whether the answer arrived by the agreed point and whether the next step actually proceeded.

When answers arrive in time but you keep chasing sooner, change your own follow-up habit. Timely acknowledgements followed by late decisions call for a check of missing information or authority. A timing conflict that keeps recurring calls for a priority, capacity or cover review.

When people cannot resolve the blocker within the agreement, connect this to an early escalation route so the next person hears before their work stalls. Make sure someone receives the escalation and owns the response.

If an employee repeatedly does not respond to emails, discuss the missed requests. First check that the expectation was clear, feasible and understood, and that the agreed support was provided. If those conditions hold and the misses continue, use the company's normal performance process. Check for new information before deciding what happens next, and get qualified support when a formal decision requires it. Reply speed on its own does not establish commitment or overall performance.

Keep the agreement only as detailed as the handoff needs, and revise it with the people doing the work.