The best way to handle an email that needs input from several people is to give every person one named question, one deadline, and one owner who collects the answers. Put those three things in the first message, number the questions, and move the work to a shared document once the thread passes about three rounds of replies.
You've probably seen the alternative. Someone sends a thread to eight people with "thoughts?" at the bottom. Two people reply to the sender, one replies all with a half-answer, and three assume someone else will handle it. By day four the thread has 23 messages, nobody is sure which version of the plan is current, and you've read it more than once without replying.
Why group threads stall
The usual fixes treat this as a politeness problem. People try "reply all" etiquette, a stern note asking everyone to be concise, or a follow-up that says "just bumping this." These feel productive for a day or two.
They fail because the problem is structural. When a message goes to eight people with an open question, each recipient reasonably concludes that someone else is better placed to answer. Nobody is being lazy. The email gave no one a specific job.
The other common fix is to wait and see who responds. That puts you in the role of unpaid referee, scrolling a growing thread to work out who agreed with whom. It also hides the one thing you need to know, which is who still hasn't answered.
The approach that works: one owner, named questions, a visible deadline
This is a template you can use the next time you send a group email. It takes about five minutes longer than "thoughts?" and saves days.
1. Name the owner in the first line. Open with something like: "I'm collecting input on the Q4 vendor decision and will make the final call on Friday." Everyone now knows who is gathering answers and where the decision lands.
2. Split the ask into numbered points, one per person. Don't write "Can everyone weigh in on pricing, timeline, and risks?" Write:
- Priya: does the proposed timeline fit your team's capacity?
- Marcus: are the pricing terms acceptable to finance?
- Dana: any legal concerns with the contract language?
Numbers matter because people can reply "2: yes, with one condition" and stay on topic. They also make the thread easier to read later.
3. Put the deadline in the email body, with a default. Write "Please reply by Thursday, 3pm. If I haven't heard from you, I'll proceed with option A." A default turns silence into a decision instead of a stall.
4. Use To for people who must answer and CC for people who only need to know. Say so explicitly: "Those on CC, no action needed." This is the single easiest way to shrink the number of people who feel obligated to respond.
5. Keep the replies in one place. Ask people to answer on the thread, not in side messages. When answers arrive, the owner posts a short roundup so everyone sees the current state. If you're joining late, our guide to summarizing a long email thread you're CC'd on covers how to catch up quickly.
If you want help with the busywork, Email Triage can surface which threads are waiting on you and draft a first-pass reply to each numbered question. You still decide what to send. If you'd like to see how it handles a thread like this, you can Try Email Triage Free.
When email isn't the right place
Email is good for collecting short answers. It's bad for negotiating between them. If people are replying to each other's replies, or you're on your third version of an attachment, the thread has outgrown the format.
At that point, move to a shared document with comment threads, or a project tool with named assignees. Then send one last email linking to it and say the thread is closed. This pairs well with the advice in how to stop losing project emails in the inbox void.
If the discussion is turning into a scheduling problem, check whether you need a meeting at all. We looked at that in why email threads keep turning into meetings.
Edge cases and adjustments
Naming a default and a deadline assumes you have the authority to make the call. If you're a peer, soften it: "Unless I hear otherwise, I'll assume we're going with A." If you're asking senior people, a hard deadline can land badly, so give them a date and tell them why it matters.
This system also assumes people can respond asynchronously. In a customer-facing role, or during an incident, the right answer is a quick call or a chat channel, not a carefully numbered email.
Finally, some groups simply won't follow the structure. That's fine. You can still do your part by replying with the numbered format yourself, and eventually others copy it. Sustainable beats perfect here.
One thing to do today
Find the one open thread right now where you're waiting on three or more people. Send a single short reply to it that does three things: names the people you still need, states what you need from each in one line, and gives a deadline with a default.
That's it. Don't rebuild your whole process. One clear nudge on one stalled thread will probably get you answers faster than another week of waiting, and it gives you a template for the next one.