Write the update once, not five times.
Write the update once and it reaches everybody who should see it: the client, the sponsor, the advisor, the mentor. Each of them gets a page of their own, and each of them can write straight back to you on it, in a thread nobody else on the list ever sees.
Write it once, send it to everybody who needs it
Write the update once and pick who should get it: the client, the sponsor, the mentor. It is yours until you send it, so nobody else in your organisation can read a draft, an administrator included. Sending is deliberate and one recipient at a time, and each delivery keeps its own result, sent or failed, so one that did not arrive shows up instead of hiding behind a single green tick.
A link, not an attachment
The report itself never travels by email. Each human gets a link of their own, with an end date, to a page holding the update, the files you attached, and any live documents you chose to show. Take a document out of your workspace and it leaves their page at the same moment.
Replies, in private threads
A human writes back on their own page. The reply is assigned to whoever that link was made for, never to a name they typed in. On your side, replies are grouped by human and marked when they are new, and no recipient ever sees another's thread.
A sent report stays sent
Editing a report humans already have would make your copy disagree with theirs. The platform refuses it, which is a real cost: a typo you spot after sending stays a typo. Write the next update instead.
Writing help that cannot send
An assistant can draft the update from your own project files, straight into the editor, and you can undo it in one step. It suggests a title, the period covered, and what to attach, and anything it does not know comes back as a marked gap for you to fill rather than a guess. It has no way to send: that stays yours.
See a report from draft to reply.