5 collocation exercises on asynchronous team communication.
0 / 5 completed
1 / 5
In a remote team, you regularly ___ an update.
You write an update — a written status post keeping the team informed asynchronously. Write collocates with update, note and summary. Pen off, compose up and draft out are not idiomatic. Writing clear updates is core to async work: it lets colleagues across time zones stay aligned without meetings, so a good update is concise, specific and states next steps.
2 / 5
To bring a colleague into a conversation, you ___ them ___.
You loop someone in — adding them to a thread or conversation so they are aware and can contribute. The phrasal verb loop in is standard workplace vocabulary (also keep someone in the loop). Wrap up, pull off and draw out mean different things. Looping in the right people early prevents surprises and avoids the frustration of someone discovering a relevant decision too late.
3 / 5
If you get no reply, you ___ on the message.
You follow up — sending a polite reminder when a message has gone unanswered. The phrasal verb follow up collocates with on a message, email or request. Chase off, ping up and nudge out are not idiomatic (though chase and nudge exist alone informally). Following up keeps work moving without being pushy, especially across async teams where replies can naturally take time.
4 / 5
To highlight a potential problem early, you ___ a risk.
You flag a risk — proactively drawing attention to something that could go wrong. Flag collocates with risk, issue and concern (you also raise a risk). Wave off, raise up and mark out are not the standard collocation. Flagging risks early gives the team time to plan mitigations; surfacing concerns in writing also creates a record that the risk was known and discussed.
5 / 5
After a long discussion, it helps to ___ the thread.
You summarise the thread — condensing a long conversation into key points and decisions. Summarise (US: summarize) collocates with thread, discussion and findings. Sum off, recap up and wrap out are not idiomatic (though recap works alone). Summarising a thread saves everyone re-reading dozens of messages and captures the outcome, which is especially valuable for those joining the conversation late.