It's always worth thinking about what you're actually asking for, and why.
As a busy geek, my gut-reaction to "status update" requests (even if I have the self control not to say so) is "if you people stopped bugging me for status updates, planning meetings, review meetings, "catch-ups" and the rest, I might actually have time to do stuff!".
"Status update" requests often fall into one of three categories:
- Thinly-veiled nags. (I asked you to do X, I've not seen evidence it's been done yet, and I don't trust that you're on the case)
- Back-covering. (Y assured me X was happening and going smoothly, so it's not my fault it's all gone pear-shaped)
- Managers are expected to provide reports to their boss weekly/periodically on their projects (possibly a variant of 2).
If it's not just a nag, terse "status update" requests often imply that there isn't a good ongoing dialog and human- or professional-interest in the project being enquired after.
If it is a nag, don't pretend it isn't. Try:
I'm sure you're busy, but have you had a chance to do X? We need it by Y because/it's holding up progress on Z. Is there anything I can do to help you achieve X?
If it's a genuine catch up, try:
Please can you spare a moment to write a couple of sentences to let me know how X is going. Give me a phone call if you think that'd be a better way to keep me informed.
Show that you're actually paying attention with:
Previously you mentioned you had a few concerns about X; how's that going/has that all been resolved now?
Previously you were anticipating some great results from ... ; how did that go?
Indicate the level of detail you're seeking. But consider whether a scheduled periodic phone-call/Teams-chat would be more interactive and give a deeper understanding of the progress.