weekly status update
a regular meeting to share progress, problems, and plans
Example: During the weekly status update, each person gave a short report.
Intermediate listeningWeekly status meetingDuration 00:02:43
English Listening Practice (Intermediate) - Monday Status Update: Website, Sales, and Support
In this weekly status update meeting, Maya (the team leader) checks in with Jordan, Priya, and Luis. They discuss a website redesign, sales outreach, and customer support issues. You will hear specific numbers, including 18 support tickets, 12 client emails, and a goal of 30 demo sign-ups. They also mention a Tuesday 3:00 p.m. deadline, a Thursday 10:30 a.m. training session, and a Friday 4:00 p.m. check-in. Listen for what each person finished, what is blocking them, and what they plan to do next, including who will follow up with the vendor and what needs approval.
Topic focus: A team leader runs a weekly status update meeting with three employees to review progress, blockers, and next steps.
Audio
1) Listen once for the main idea. 2) Answer questions. 3) Study the transcript.
Questions
Answer each question based on the audio. Use Practice Mode to test yourself without the transcript.
0 of 8 answered0%
Transcript
Study Mode shows the full transcript. Practice Mode hides it.
Tap a timestamp to jump to that point in the audio
Transcript hidden. Switch to Study Mode when you want to check details.
Maya
Good morning, everyone. It’s Monday, March 4th, and it’s 9:05 AM. Let’s do our
.065 Maya: weekly status update... We’ll go person by person: progress, blockers, and next
.195 Maya: steps.
.971 Jordan: Sounds good, Maya.
.782 Maya: Jordan, start us off. How’s the website redesign?
.068 Jordan: I finished the new homepage layout on Friday. And... the main blocker is the
.969 Jordan: vendor’s slow response on the image licenses. Without that, I can’t publish
.805 Jordan: the final version.
.981 Maya: What’s your next step?
.488 Jordan: Um... I’ll follow up with the vendor by noon today, and I’ll prepare a draft so
.669 Jordan: we can review copy. I also need a quick sign-off from you on the new button
.584 Jordan: color.
.983 Maya: Okay. I can approve that after this meeting. Priya, your turn—sales.
.020 Priya: Last week I sent 12 client emails and booked 4 calls. Our goal is 30 demo
.644 Priya: sign-ups this month. One risk is that two leads asked for case studies we don’t
.737 Priya: have in a final format.
.534 Maya: What do you need?
.577 Priya: A short case-study-PDF by Tuesday at 3:00 PM, even if it’s a simple version. My
.262 Priya: next step is to draft it and ask Jordan for one screenshot.
.233 Maya: Great! Luis, support updates?
.462 Luis: We closed 18 tickets. The backlog is down, but there’s an escalation from a
.743 Luis: hospital client in Denver. They reported login timeouts at 7:40 a.m. Saturday.
.279 Maya: Any blockers?
.301 Luis: Yes, I need engineering to confirm the server logs. My next step is to join the
.769 Luis: incident review at 11:00 a.m. and send a summary.
.750 Maya: Thanks. Quick recap: Jordan, follow up with the vendor and send the draft.
.824 Maya: Priya, draft the case-study. Luis, handle the escalation and incident review.
.106 Maya: Also, we’ll do a brief training session Thursday at 10:30 a.m. on the new ticket
.703 Maya: tags. And we’ll have a check-in Friday at 4:00 p.m. to confirm we’re on track.
.159 Jordan: Maya, should I include the new pricing banner in the draft?
.267 Maya: Not yet. Keep it out until finance confirms the numbers.
.354 Jordan: If finance delays, can we still hit 30 demo sign-ups?
.044 Priya: Yes, but we’ll need faster follow-ups. Let’s keep the cadence: respond to leads
.691 Priya: within one business day.
.428 Jordan: Got it. I’ll add that reminder to our support notes.
.004 Maya: Perfect. Please post your updates in the channel right after you're done.
Vocabulary
Key terms from this listening practice with meanings and examples.
blocker
something that prevents work from moving forward
Example: A missing file can be a blocker for finishing the report.
follow up with the vendor
contact the supplier again to get information or action
Example: She will follow up with the vendor to confirm the delivery date.
sign-off
official approval to proceed
Example: We need your sign-off before we publish the new page.
risk
a possible problem that could happen
Example: A risk is that the client may cancel if we are late.
case study PDF
a document describing a project or customer success story
Example: He attached a case study PDF to show results.
backlog
unfinished work that is waiting to be done
Example: The backlog grew when the team was short-staffed.
incident review
a meeting to analyze a problem event and decide next actions
Example: After the outage, they held an incident review to prevent it happening again.
Learning tips
Apply these focused strategies to get more value from the audio and questions.
- Listen for meeting structure words like “start us off,” “your turn,” and “quick recap” to predict what will come next.
- Write down numbers and times as you hear them, then connect each one to the person who said it.
- Notice action phrases such as “next step” and “follow up” to understand responsibilities and deadlines.
Post-listening questions
Use these reflection prompts to summarize what you heard and practice speaking or writing.
- 1
In your workplace or school, what information would you share in a weekly status update?
- 2
What are some polite ways to ask for sign-off when you need approval quickly?
- 3
How would you handle a blocker caused by a vendor’s slow response?
- 4
What steps would you take after an escalation from an important client?