1.2Write, reply, forward & attachments
The essentials in 30 seconds
- “Reply all” only if ALL should read: otherwise, “Reply”.
- BCC for external group shipments: reflex of politeness AND GDPR compliance.
- Share a link rather than an attachment: lightweight, up-to-date, co-editable.
Nassim’s thread — Write, reply, forward & attachments
Nassim responds to a call for tenders. It must write a clear message, reply to all the correct recipients, forward a thread with its context and attach files without version errors.
Continuation of the common thread: a digital services SME in Algiers structures its exchanges.
1. Understand
The heart of the job: writing and responding. Beyond the obvious (New message, Reply, Forward), three skills make the professional: the correct use of To / Cc / BCC (BCC for external group sendings - a GDPR reflex), a clear object which says the expected action, and above all sharing by link rather than by heavy attachment.
You will master “Reply” vs “Reply all” (the number 1 source of useless emails), attach a file OR share a OneDrive link (co-editing possible, zero weight), and good writing reflexes – subject, conciseness, only one subject per email.
2. Key points
“Reply all” only if ALL should read: otherwise, “Reply”.
BCC for external group shipments: reflex of politeness AND GDPR compliance.
Share a link rather than an attachment: lightweight, up-to-date, co-editable.
A clear object = a named action: it conditions the response (and the classification).
🔎 Concrete example — Real life example — Write, reply, forward & attachments
New message: write a clear action object (“[To be validated] T3 budget – desired return Tuesday”).
Inform To (the decision-makers) and Cc (for info) wisely; to send to several external parties, switch to Bcc.
Instead of attaching a large file: Insert → Link → a OneDrive/SharePoint file — set the right (read or modify).
On a thread received by 8 people: practice choosing “Reply” (to the sender alone) when the other 7 do not need your response.
Emails that are clear, light, and respectful of other people's inboxes — the mark of the professional.
Section vocabulary
- To / Cc / Bcc
- To = recipients expected to act; Cc = for information; BCC = blind copy (external bulk mailings: protects addresses).
Simple example: Nassim uses “To / Cc / Bcc” in his daily life to write, reply, forward & attachments.
What it is not: Confusing “To / Cc / Bcc” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
- Reply all
- Replies to the sender AND all recipients: Use only if EVERYONE really needs to read — the major source of box pollution.
Simple example: Nassim uses “Reply All” in his daily life to write, reply, forward & attachments.
What it is not: Confusing “Reply all” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
- Attachment vs link
- The attachment weighs down and freezes a copy; the OneDrive/SharePoint link remains light, up to date and co-editable – the modern reflex.
Simple example: Nassim uses “Attachment vs link” in his daily life to write, respond, forward & attachments.
What it is not: Confusing “Attachment vs. link” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
- Effective object
- An object that announces the action: “[Action required] Validate quote before Friday” rather than “Info”.
Simple example: Nassim uses “Effective Object” in his daily life to write, respond, forward & attachments.
What it is not: Confusing “effective object” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
- Read receipt
- The option (use sparingly) that notifies when the email is read — often perceived as intrusive.
Simple example: Nassim uses “Read receipt” in his daily life to write, respond, forward & attachments.
What it is not: Confusing “read receipt” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
In practice — A well-constructed professional email
- New message: write a clear action object (“[To be validated] T3 budget – desired return Tuesday”).
- Inform To (the decision-makers) and Cc (for info) wisely; to send to several external parties, switch to Bcc.
- Instead of attaching a large file: Insert → Link → a OneDrive/SharePoint file — set the right (read or modify).
- On a thread received by 8 people: practice choosing “Reply” (to the sender alone) when the other 7 do not need your response.
Ready-to-Speak Script — Write, Reply, Forward & Attachments (25 sec)
“Write an email, reply/forward, manage Cc/Bcc, and attach files (or OneDrive links). I rely on this key point: “reply to all” only if everyone must read: otherwise, “reply”.”
Short formulation, to be adapted to the recipient and the context.
Copy and paste template — “Write, reply, forward & attachments” checklist
CHECKLIST — Write, reply, forward & attachments
1. “Reply all” only if ALL should read: otherwise, “Reply”.
2. BCC for external group shipments: reflex of politeness AND GDPR compliance.
3. Share a link rather than an attachment: lightweight, up-to-date, co-editable.
4. A clear object = a named action: it conditions the response (and the classification).
EXPECTED RESULT: Emails that are clear, light and respectful of other people's inboxes — the mark of the professional.
Express version
“Reply all” only if ALL should read: otherwise, “Reply”.
As a team
BCC for external group shipments: reflex of politeness AND GDPR compliance.
Point of vigilance
Share a link rather than an attachment: lightweight, up-to-date, co-editable.
Control before distribution
Emails that are clear, light, and respectful of other people's inboxes — the mark of the professional.
✓ Best practices
- “Reply all” only if ALL should read: otherwise, “Reply”.
- BCC for external group shipments: reflex of politeness AND GDPR compliance.
- Share a link rather than an attachment: lightweight, up-to-date, co-editable.
✗ Common pitfalls
- Process “Write, reply, forward & attachments” by intuition without checking the context.
- Multiply channels and notifications for the same subject.
- Send or share without rereading recipients and rights.
Key takeaways
- “Reply all” only if ALL should read: otherwise, “Reply”.
- BCC for external group shipments: reflex of politeness AND GDPR compliance.
- Share a link rather than an attachment: lightweight, up-to-date, co-editable.
- A clear object = a named action: it conditions the response (and the classification).
48 hour challenge — apply tomorrow
Put “A well-constructed professional email” into practice in a real case of Nassim’s SME: New message: write a clear action object (“[To be validated] T3 budget – desired return Tuesday”). Time it for 20 minutes and note what has changed.
- I can explain and apply: “Reply All” only if ALL must read: otherwise, “Reply”.
- I can explain and apply: BCC for external group shipments: reflex of politeness AND GDPR compliance.
- I can explain and apply: Share a link rather than an attachment: lightweight, up-to-date, co-editable.
Frequently asked questions
When should you put someone in Cc rather than To?
To: the people from whom you expect an action or response. In Cc: those who must be kept informed without requesting them. Too many people in A dilutes responsibility (“someone will take care of it” = no one).
The OneDrive link does not open for my external recipient: why?
The right to share does not include external ones: when creating the link, choose “Specific people” with their address, or “Any person with the link” if the organization's policy allows it. For sensitive data, we remain cautious (see Cybersecurity).
What key point should I apply for “Write, reply, forward & attachments”?