When someone says “keep me posted”, agree what change should trigger an update, who will send it, and how the information should arrive. The phrase asks for continuing information but does not automatically establish a reporting schedule. A useful reply is: “Of course. Would you like an update when the date is confirmed, if a problem arises, or at our Friday check-in?”
That one question prevents two opposite mistakes: sending a stream of messages that do not help, and staying silent while a change affects somebody else’s decision. You are not refusing to communicate. You are turning an open-ended request into a reliable agreement about information.
What does “keep me posted” actually mean?
The Cambridge Dictionary explains the idiom as keeping someone informed about what is happening, particularly when circumstances change. It does not define the expression as “message every hour”, “copy me into every email”, or “make a promise that nothing will go wrong”. Those extra expectations must be negotiated in the particular conversation.
The language mechanism is a standing request. Instead of asking for one answer now, the listener asks for future information when it exists. Both parties must decide what counts as relevant news. The same sentence may refer to a medical appointment, a class project, a delivery or a community activity, but the useful updates differ.
Distinguish the request from a single question such as “What time is the meeting?” That question normally has a specific answer. “Keep me posted” has a moving subject, a possible series of messages and an unclear end point. A practical repair is therefore not simply repeating the sentence; it is specifying the conditions under which a message becomes worthwhile.
Did you know? “Nothing has changed” can be useful information—but not always
Imagine waiting for permission to book transport. A short, agreed checkpoint saying “No decision yet; next check tomorrow” may be useful because it tells you not to act. In a less urgent school activity, a daily “still no news” could distract more than it helps. The value of an update depends on what the reader needs to decide, not merely on how many messages are sent.
This is a practical observation about communication, not a claim that one frequency has been scientifically proved best for everyone. Ask what decision the receiver is waiting to make, then design the update around that need.
The trigger–owner–channel–checkpoint method
- Trigger: Name the event that changes the plan: a decision, delay, new result, safety issue or confirmed arrangement.
- Owner: Identify who can provide reliable information, rather than expecting everyone in a group to report rumours.
- Channel: Choose how the update will arrive—brief message, email, phone call or class notice—and match privacy to the situation.
- Checkpoint: If nothing happens, agree whether a brief status message is needed and when the request should end.
A concise natural form is: “I’ll message you when the teacher approves our final topic. If we haven’t heard by Thursday, I’ll tell you that we’re still waiting.” It offers a specific trigger and a checkpoint without inventing an outcome. An adult-life version might be: “I’ll send the confirmed quotation by email when the supplier replies; I’ll phone you if the delivery date changes.”
The checkpoint is not an invented deadline for someone else’s decision. It is a promise about your own communication that you can realistically keep. If you cannot promise even that, state the limit: “I’ll update you if I receive an official notice; I may not know when it will arrive.”
Worked dialogue 1: a Primary-school group project
Fictional demonstration. Aisha: “Can you keep me posted about the Science model?” Jun: “Sure. Which changes do you need to know about?” Aisha: “If the teacher approves our materials or changes the submission plan.” Jun: “I can tell you after class on those days. If nothing changes, we’ll check together on Thursday.”
Aisha does not need every sketch and casual suggestion. She needs information that affects what she must bring or build. Jun clarifies the school task without making Aisha feel demanding. Neither child is said to have improved a real score; the exchange is an invented practice example.
Worked dialogue 2: a parent waiting for a repair
Fictional demonstration. Parent: “Please keep me posted about the leaking tap.” Older sibling: “Do you want a message each time I call someone, or when we have an appointment?” Parent: “Tell me as soon as a repair time is confirmed, and immediately if the leak gets worse.” Sibling: “Understood. I’ll send the time once confirmed; meanwhile the water is turned off.”
Here the repair trigger is not academic progress but a household consequence. A worsening leak matters more than a routine administrative call. The exchange also shows why a communication plan does not replace practical safety action; a serious immediate hazard needs action, not merely an update.
Worked dialogue 3: a workplace delivery
Fictional demonstration. Manager: “Keep me posted on the revised presentation.” Colleague: “Would a draft-ready note and any change to the client’s deadline be most useful?” Manager: “Yes. No need to copy me on every edit.” Colleague: “I’ll send the draft link when it’s ready and flag any risk to the deadline. I’ll mark questions that still need approval.”
A colleague who sends every minor change creates unnecessary reading. One who silently assumes approval may create a different problem. The conversation distinguishes status information from a request for decision-making authority. Related lesson: clarifying whether copying someone into email means action or awareness.
Worked dialogue 4: adult plans across different schedules
Fictional demonstration. Farah: “Keep me posted if the community event moves.” Dev: “I’ll notify you when the organiser posts a new venue or date. Is a group message okay?” Farah: “Yes, but call if it’s cancelled on the day.” Dev: “Agreed. I’ll link the official announcement so nobody relies on an old screenshot.”
The original source matters: a tentative chat message is not the same as a confirmed notice. An update should identify whether the information is proposed, verified or superseded. This is the same discipline as naming which earlier instruction a new plan replaces, but here the central job is negotiating the notification itself.
Tone and register: one intention, several suitable sentences
With a classmate, “I’ll text if anything changes” may be enough after the group has agreed what “anything” covers. With a teacher, “I can send a short update when the results are available, and a note if there is a delay” is clearer. In a formal team email, write: “I will notify you when the approval status changes; if it remains pending on Friday, I will send a brief status update.”
Avoid using “I’ll keep you posted” as an automatic polite ending when you have no way to obtain the information. Say instead, “I don’t have access to the final decision, but the coordinator can confirm it.” Politeness works better with accurate responsibility than with a reassurance nobody can fulfil.
Three misconceptions to correct
- Misconception 1: The phrase requires constant messaging. It requests relevant information, but frequency depends on the situation.
- Misconception 2: Every update must contain good news. A truthful delay or unknown result can be important if the recipient needs to adjust.
- Misconception 3: Everyone who sees a discussion is now responsible for updates. A named owner prevents messages from being both duplicated and forgotten.
Diagnostic questions before you agree
Ask yourself: What could change the other person’s next action? Which facts do I personally know or have authority to confirm? Will they need a response or simply awareness? Is a fixed check-in better than event-by-event alerts? Do privacy or safeguarding rules restrict who may be told? If you cannot answer those questions, make a narrow offer instead of a broad promise.
For a school activity, the teacher may retain responsibility for official dates and changes; a pupil should not present an unconfirmed peer rumour as a teacher’s instruction. For health or confidential family information, ask permission about the audience before forwarding details.
Retrieval practice: say the repair without looking
Cover the examples and complete these prompts aloud. A friend says, “Keep me posted about the rehearsal.” Name one useful trigger. A colleague says, “Keep me posted on the draft.” Name the recipient’s possible decision. A relative says, “Keep me posted about Saturday.” Ask for the channel and the circumstances that would justify calling rather than texting.
Now write a four-part reply using trigger, owner, channel and checkpoint. Check that every promise concerns something you can actually do. Compare your answer with this model: “I will message you when the room is confirmed. I will check the official notice, send the update in our group chat and follow up on Thursday if it is still pending.”
A four-week transfer plan
- Week 1: Notice three uses of “keep me posted” and record what the listener actually needs to know.
- Week 2: Practise asking for a trigger and a preferred channel in two fictional scenarios.
- Week 3: In one real low-stakes task, agree a responsible person and checkpoint before sending messages.
- Week 4: Review whether updates arrived when they could influence a decision; adjust the rule without blaming anyone.
Guidance for students, parents and teachers
Students can learn a simple sentence frame: “I will tell you when ___ happens, by ___.” Parents can explain why a useful update differs from constant reassurance, and model how to say “I don’t know yet.” Teachers can give group projects an update owner and clearly distinguish a class announcement from a pupil’s suggested arrangement.
The British Council’s guidance on enquiries provides useful models for clear questions. Its active-listening lesson also emphasises responding to what a listener actually needs. Neither source provides a universal update frequency; that is why the participants must make their own practical agreement.
Frequently asked questions
Does “keep me posted” mean “reply immediately”? Not by itself. A time-sensitive situation may require rapid notice; agree that expectation explicitly.
What if nothing has changed? Use the checkpoint you agreed. If none was set and the matter is still important, one brief honest status message may be useful.
Can I ask someone not to send every update? Yes. Thank them, identify the event you care about and give a workable rule, such as “Only let me know when the booking is confirmed or the date changes.”
What if I am not authorised to share details? State that limit and direct the person to the appropriate authorised source; do not disclose protected information to appear helpful.
What makes this a conversation repair skill? It replaces a vague standing request with a shared expectation about which information matters, who can provide it, how it arrives and what remains undecided.