If part of a group project or meeting moves into a private conversation, bring back only the information the whole group needs to act. Confirm what may be shared, distinguish an agreed decision from a suggestion, and give the group a short update that identifies the next step without repeating personal remarks. A private conversation is not permission to publish everything said in it.
The practical method is permission, decision, action. Ask the people in the private exchange which outcome can be reported; state the decision’s actual status; then tell the larger group who needs to do what. If nothing has been agreed or cannot appropriately be shared, say that there is no confirmed group decision yet. This protects both privacy and participation.
The real problem: two audiences now have different information
A group of five may share a project channel, while two members discuss an issue separately. The smaller conversation can be useful: someone may explain a personal constraint, describe a sensitive difficulty or simply check a detail. But the other three people can be left wondering whether the plan changed. If one participant forwards the full private exchange, they may reveal more than anyone intended.
The opposite error is silence. If a deadline, task or shared choice has genuinely changed, keeping the result inside the side chat can prevent others from acting. The solution is not to ban private conversations. It is to produce the smallest accurate update that lets the whole group move forward.
Did You Know? A meeting summary is an act of selection
A useful summary does not repeat every sentence. It selects relevant points and preserves uncertainty, disagreement and decisions. The British Council’s Managing meetings guidance encourages clarification, checking agreement and recording action points. That supports concise public updates, but it does not authorise revealing private personal information.
There is also a linguistic distinction between said and agreed. “We discussed postponing” reports a conversation; “We agreed to postpone” reports a decision. They are not interchangeable. A side discussion among two people does not automatically grant them the authority to decide for five.
Step 1: identify the public information need
Before drafting anything, ask three questions: Which shared decision is waiting? What facts does every participant need to continue? What information belongs only to the smaller group or the person who disclosed it? For a presentation project, the public need might be the revised slide order. The private detail might be the reason one member requested fewer speaking lines.
Write a temporary two-column note: “Necessary for the project” and “Not necessary for the project.” A project update might name the revised task allocation without disclosing a family situation, health explanation or interpersonal frustration. Keep the second column out of public messages. If disclosure is required for safety, use the appropriate responsible route rather than a group chat.
Step 2: confirm what the other speaker permits you to report
A practical sentence is: “I think the group needs an update. May I say that we proposed swapping the slide order, without sharing the reason you mentioned?” This request specifies the information, audience and limit. If the other speaker says no, discuss a non-identifying alternative or arrange for the affected person to speak for themselves. Silence is not a positive answer.
Permission to report a final task change is not permission to quote private comments. Nor does it make a decision binding on the whole group. For a sensitive issue, ask whether the speaker would prefer to write the group update themselves. This is the same respect for story ownership explained in eduKate’s lesson on retelling someone else’s personal story, applied to a shared project result.
Step 3: label the decision status accurately
Use one of three statuses. Proposal: “Two of us discussed switching the speaking order; this still needs the group’s agreement.” Agreed group decision: “All five confirmed the new speaking order.” Pending confirmation: “We need to confirm whether the final slide can move earlier.” Do not upgrade “sounds reasonable” into “everyone approved.”
Also distinguish two people’s authority from the whole group’s authority. A team lead may be authorised to assign tasks; classmates may need to agree together; a teacher may retain approval of submission arrangements. The right wording depends on the situation. Never imply authorisation that you have not verified.
Step 4: report action, not private explanation
A concise update can follow a three-sentence pattern. “The proposed change is to move the introduction before the experiment.” “We have not yet agreed on this as a group.” “Please reply with any practical concern by our next planning meeting.” The words tell people what has changed, what remains open and what participation is needed.
Compare this with: “Ben said he is nervous and thinks Jo is being difficult, so we decided to change everything.” That message mixes personal feelings, an unfair characterisation and a claim of group authority. Even if some words were spoken privately, the public update has no reason to include them.
Worked dialogue: Secondary school project
Fictional demonstration. Aisha: “I told you privately that I cannot present the opening. Please don’t explain why to the group.” Ryan: “Understood. Can I say we are proposing a new order without mentioning your circumstances?” Aisha: “Yes, but it isn’t final.” Ryan, in the project chat: “A new speaking order has been suggested. Shall we check whether everyone is comfortable with Aisha taking the diagram section and Ryan opening?”
Notice that the update neither invents a reason nor treats agreement between two classmates as the whole team’s decision. If the rest of the group accepts, someone can record the confirmed order. If they do not, the group can discuss alternatives without turning the private reason into an argument.
Worked dialogue: an adult workplace handover
Fictional demonstration. Supervisor: “I’ve checked privately with the technician. The current task may need a later handover.” Assistant: “What is safe to tell the morning shift?” Supervisor: “Tell them that the equipment check is pending and I will confirm the handover. Don’t relay an unverified diagnosis.” Assistant, in the work channel: “The check is still pending. Please do not mark the handover complete; the supervisor will confirm the status.”
This version communicates what the next team must do without exaggerating certainty. If there is an urgent safety problem, follow the actual organisation’s escalation process rather than relying only on a conversational summary.
Worked dialogue: family and community planning
Fictional demonstration. Two relatives discuss a family dinner while one mentions a personal difficulty. One asks: “Can I tell everyone that Saturday no longer works, without giving your personal explanation?” After consent, the family message says: “Saturday is no longer suitable. Could everyone indicate whether Sunday afternoon works?” The family receives a practical question, not private details.
At a volunteer event, the same principle might produce “We are seeking another person for registration between two and three” rather than “So-and-so has a family problem.” Respectful communication can be precise without being intrusive.
Register: how to phrase the public update
For friends, “Quick update: we’ve discussed a possible swap, not decided yet” is natural. For a school project, “The revised order is a proposal pending team agreement” is clearer. For a workplace, “Following a separate discussion, the confirmed operational change is …; no other tasks are affected” may be appropriate. Avoid legalistic language for a simple class chat, and avoid casual guesswork for consequential work.
Cambridge Grammar Today describes polite wording as showing respect and moderating force; see Politeness. A respectful update is usually brief, explicit and non-judgmental. It need not announce that it is protecting a secret.
Common mistakes and how to repair them
Forwarding the screenshot: Ask whether a summary is enough; do not expose private context by default. Saying “we decided” when two people only discussed: Change the wording to “we proposed.” Hiding a genuine change: Name the shared consequence and next action. Using vague phrases like “things happened”: State the operational information that the group actually needs.
Giving the loudest two people the final say: Check authority and invite the relevant decision-makers. Pressing for the private explanation: Ask what task information is needed instead. If someone refuses to share their reasons, that does not mean their practical constraint should be ignored.
A diagnostic before you press Send
Test your message: Does it distinguish an idea from an authorised decision? Does it disclose anyone’s personal situation without permission? Could an absent member tell what action is needed? Does it suggest consensus where none exists? If the answer to the second or fourth question is yes, revise before sending.
For a quick classroom practice, rewrite “Jo and I sorted it out” into three versions: (1) a proposal needing approval, (2) a genuinely approved decision, and (3) a private conversation with no group action. The three versions should sound different because their evidential status is different.
Retrieval practice and four-week transfer
Without looking back, recite the three checks: permission, decision, action. Then write one two-sentence update in each context: a class presentation with an unconfirmed swap, an equipment check still pending and a family event moving dates. In every case, remove irrelevant personal explanation and preserve what is not yet known.
During week one, practise writing a public-safe summary of a fictional private discussion. During week two, ask permission before quoting a real non-sensitive comment. In week three, have classmates distinguish “we suggested” from “we agreed.” In week four, practise an update in which no public result can yet be shared and check whether the group understands what remains pending.
Guidance for students, parents and teachers
Students should avoid turning classmates’ private messages into public evidence of who was right. Parents can model asking about intended recipients and suitable detail before sharing family information. Teachers can tell group leaders what kind of project status belongs in the shared channel and what should be handled privately, while remaining attentive to legitimate safeguarding concerns.
For the separate listener-side problem of restoring a shared understanding after a multilingual side exchange, see eduKate’s shared-summary lesson. The skill here is different: someone who participated in a private discussion must decide exactly what is appropriate to bring back.
Frequently asked questions
Must I share every group decision? Share what the relevant people need, through the appropriate channel, subject to privacy and authority. What if I cannot obtain permission? Do not repeat private material; ask how to communicate the task consequence safely. What if a person claims a group decision was already made? Ask who agreed and where it was confirmed. Can I mention that a private discussion happened? Usually it is enough to state the current proposal or task status without naming private participants.
Evidence and sources
This lesson’s discussion of meeting summaries and action points draws on British Council LearnEnglish: Managing meetings, Making a decision and Cambridge Grammar Today: Say or tell?. All dialogues are original fictional teaching illustrations, not recorded outcomes.