Memos, Notices & Emails: Formats, Uses & Best Practices

Key Definitions and Purposes

1. Memos (Memorandums)

A memo is a short, internal written communication used within an organization to convey information, instructions, or decisions. It follows a formal but concise structure and is typically used for:

• Internal announcements (e.g., policy changes, meeting schedules).
• Requests or approvals (e.g., leave applications, project updates).
• Record-keeping (e.g., minutes of meetings, action items).

Why use memos?

• Faster than emails for internal communication.
• Official record of decisions or instructions.
• Clear hierarchy (sender → recipient, often within the same organization).

---

2. Notices

A notice is a public or semi-public announcement used to inform a group (employees, customers, or the public) about an event, policy, or change. Unlike memos, notices can be:

• Internal (e.g., staff training schedules).
• External (e.g., hotel check-in procedures, flight delay announcements).

Key features:

• Brief and direct (no unnecessary details).
• Clear call to action (e.g., "Report by Friday").
• Visible placement (bulletin boards, digital screens, emails).

---

3. Emails

An email is a digital message sent between individuals or groups, both internally and externally. In business, emails serve multiple purposes:

• Formal correspondence (e.g., client inquiries, vendor communications).
• Quick updates (e.g., travel itinerary changes, team coordination).
• Document sharing (e.g., sending reports, brochures, or contracts).

Why emails dominate today?

• Instant delivery (unlike memos or notices, which may require printing/posting).
• Attachments and links for supporting documents.
• Searchable archives (unlike verbal communication).

---

Structures and Formats

1. Memo Structure

Use this standard format for professional memos:

Worked Example: Internal Leave Request Memo (Assume you work at a travel agency and need to request leave.)

TO: Mr. Sharma, HR Manager
FROM: Ramesh Adhikari, Marketing Executive
DATE: 2024-05-15
SUBJECT: Request for Leave from May 20–24

Dear Mr. Sharma,

I am writing to request leave from **May 20 to May 24** due to a family emergency. I will ensure all pending tasks are completed before my departure and will delegate responsibilities to [Colleague Name] in my absence.

Please approve at your earliest convenience.

Best regards,
Ramesh Adhikari

Why this works:

• Clear subject line (HR knows immediately what it’s about).
• Polite and professional tone (avoids sounding demanding).
• Actionable details (dates, backup plan).

---

2. Notice Structure

Notices are shorter and more direct. Use this template:

Worked Example: Hotel Notice for COVID-19 Protocols (Assume you manage a hotel in Kathmandu.)

NOTICE TO ALL GUESTS
DATE: 2024-05-10

Effective immediately, all guests must:
1. Show a **valid vaccination certificate** upon check-in.
2. Wear masks in **common areas** (lobby, restaurant).
3. Sanitize hands upon entry.

Failure to comply may result in denial of services.

Management
Hotel Everest View

Why this works:

• Bold headings for quick scanning.
• Numbered list for easy compliance.
• Consequences stated (encourages adherence).

---

3. Email Structure

Emails require a subject line, greeting, body, and closing. Use this template:

Worked Example: Email to a Tour Operator (Assume you’re coordinating a group tour to Pokhara.)

SUBJECT: Confirmation of Group Tour Booking – May 25, 2024

Dear Ms. Thapa,

I hope this email finds you well. We have **confirmed the booking** for our group of 20 participants for the **Pokhara Adventure Tour on May 25, 2024**. Attached is the signed contract and payment receipt.

Please let us know if any additional documents are required.

Best regards,
Anita Shrestha
Tour Coordinator
Sunrise Travels

Why this works:

• Descriptive subject line (helps recipient prioritize).
• Polite and concise (avoids unnecessary details).
• Attachment mentioned (saves recipient time).

---

Comparison Table: Memos vs. Notices vs. Emails

---

In the Real World

1. eSewa (Nepal) – Email & Notice Integration

eSewa uses automated emails and notices to inform users about:

• Transaction confirmations (email).
• Service updates (e.g., "New payment gateway available" – notice on their app/dashboard). How it works:
• Emails for receipts and alerts (e.g., "Your bill payment of Rs. 5,000 is confirmed").
• In-app notices for policy changes (e.g., "New KYC verification required").

2. Daraz (Nepal) – Internal Memos for Logistics

Daraz’s warehouse teams rely on daily memos to coordinate:

• Stock updates (e.g., "Shipment of 500 units of Himalayan Java arriving tomorrow").
• Delivery route changes (e.g., "Traffic delay on Ring Road; reroute to New Baneshwor"). Why memos?
• Faster than emails for large teams (e.g., 50+ warehouse staff).
• Physical copies can be pinned on boards for quick reference.

3. Nabil Bank – Email for Customer Service

Nabil Bank uses structured emails to:

• Acknowledge loan applications (e.g., "Your home loan request is under review").
• Notify customers of policy changes (e.g., "New interest rates effective June 1"). Real-world impact:
• Reduces call center load (customers check emails first).
• Legal compliance (emails serve as proof of communication).

---

Common Mistakes and How to Avoid Them

1. Memos

❌ Too vague (e.g., "We need to improve sales"). ✅ Fix: Be specific (e.g., "Increase online bookings by 15% via targeted Facebook ads by June 1").

❌ No call to action (e.g., "The meeting is tomorrow"). ✅ Fix: Add deadlines (e.g., "Submit your travel itinerary draft by May 18").

2. Notices

❌ Too long (e.g., a 5-paragraph notice about a new policy). ✅ Fix: Use bullet points (e.g., "New rules: 1. Mandatory ID check. 2. No refunds after 48 hours.").

❌ No urgency indicated (e.g., "Please submit your feedback"). ✅ Fix: Add deadlines (e.g., "Submit feedback by May 20 to qualify for the discount").

3. Emails

❌ No subject line (e.g., an email titled "Hi"). ✅ Fix: Use action-oriented subjects (e.g., "Urgent: Approval Needed for Event Budget").

❌ Attachments not mentioned (e.g., sending a contract without saying so). ✅ Fix: State attachments clearly (e.g., "Attached: Signed contract and payment schedule").

---

Case Study: How Himalayan Java Uses Notices and Emails

Scenario: Himalayan Java, a coffee chain in Nepal, needs to announce a new loyalty program to customers.

Step 1: Draft the Notice (For In-Store Display)

NOTICE TO ALL CUSTOMERS
DATE: 2024-05-12

Exciting News! Our **Himalayan Rewards Program** is live!
- Buy 9 coffees, get the 10th **FREE**.
- Scan your phone at checkout to earn points.
- Valid until **June 30, 2024**.

Visit any Himalayan Java outlet or download our app to join!

Management
Himalayan Java

Why this works:

• Eye-catching (bold text, clear benefits).
• Call to action (app download or in-store visit).

Step 2: Send an Email to Existing Customers

SUBJECT: Exclusive Offer – Join Himalayan Rewards Now!

Dear [Customer Name],

We’re thrilled to introduce our Himalayan Rewards Program! As a valued customer, you’re the first to know:

• 10th coffee FREE after 9 purchases.
• Double points for online orders.

👉 [Download the app here] or show this email at any outlet.

Happy sipping! The Himalayan Java Team

Why this works:

• Personalized (uses customer name).
• Urgency (exclusive offer for early adopters).

---

Exam Tip

What Examiners Look For

1. Correct Format

   • Memos: TO, FROM, DATE, SUBJECT, BODY.
   • Notices: HEADING, DATE, BODY, SIGNATURE.
   • Emails: Subject line, greeting, body, closing.

2. Professional Tone

   • Avoid slang (e.g., "Hey guys" → "Dear Team").
   • Use polite phrases (e.g., "Please find attached" instead of "Here’s the file").

3. Clarity and Conciseness

   • No fluff (e.g., "As per your request..." → "Please submit...").
   • Bullet points for lists (e.g., "Requirements: 1. ID proof. 2. Passport-sized photo.").

4. Real-World Application

   • Exams often ask for practical scenarios (e.g., "Draft a memo to your manager about a delayed tour").
   • Always assume a real audience (e.g., "TO: Hotel Manager" not "TO: Sir").

5. Proofreading

   • Check for:
     • Grammar (e.g., "Their" vs. "There").
     • Spelling (e.g., "accommodation" not "accomodation").
     • Tone (e.g., not too casual or too formal).

---

Common Exam Questions and How to Answer

---

Final Checklist Before Submitting

✅ Memo:

• Correct headings (TO, FROM, etc.).
• Professional tone.
• Specific and actionable.

✅ Notice:

• Bold headings and dates.
• Clear instructions or warnings.
• Visible call to action.

✅ Email:

• Descriptive subject line.
• Proper greeting and closing.
• Attachments mentioned if applicable.

---