Writing Process: Stages, Techniques & Business Applications

TAKEAWAYS

• The writing process is a cyclical model (pre-writing → drafting → revising → editing → proofreading) that ensures clarity, purpose, and professionalism in business documents.
• Prewriting (brainstorming, outlining, research) is critical to avoid vague or disorganized content—common pitfalls in Nepali business letters.
• Drafting requires structure (e.g., direct vs. indirect approaches in emails) and tone adaptation (formal for NTC reports, concise for Pathao delivery notes).
• Revising focuses on logic, flow, and audience needs (e.g., revising a Khalti transaction failure email to sound empathetic yet solution-oriented).
• Editing/proofreading eliminates errors that undermine credibility (e.g., typos in a NEPSE stock analysis report).
• Digital tools (Grammarly, Hemingway Editor) and collaborative platforms (Google Docs) streamline the process for remote teams (e.g., Daraz’s global customer service teams).

The Writing Process: A Cyclical Model

Business writing is not linear—it’s an iterative cycle where each stage refines the previous one. Below is the 5-stage model with real-world applications:

graph TD
    A["Pre-writing"] --> B["Drafting"]
    B --> C["Revising"]
    C --> D["Editing"]
    D --> E["Proofreading"]
    E -->|"Feedback"| A

1. Pre-writing: Planning Your Message

Definition: Research, brainstorming, and structuring ideas before drafting. Skipping this leads to disorganized emails (e.g., a Daraz customer service agent replying to a complaint without key details).

Key Steps:

• Purpose: Define the goal (inform, persuade, request, or solve). Example: A Nabil Bank loan officer’s email to a client must persuade while providing clear terms.
• Audience: Adapt tone and complexity. A technical report for NTC needs jargon; a WhatsApp message to a Pathao driver must be ultra-concise.
• Research: Gather facts (e.g., citing NEPSE stock trends in an investment pitch).
• Outlining: Use hierarchical structures (see below) to avoid rambling.

Visual: Hierarchical Outline for a Business Proposal

Worked Example: Drafting a Complaint Email to Daraz Scenario: Your order (ID: #DZ12345) arrived damaged. Write the pre-writing plan:

• Purpose: Request a refund/replacement politely but firmly.
• Audience: Daraz customer service (professional, not emotional).
• Key Details: Order ID, photos of damage, expected resolution timeline.
• Tone: Indirect approach (buffer → problem → solution → call to action).

2. Drafting: Turning Ideas into Structure

Definition: Writing the first version using the pre-writing plan. Focus on content, not perfection.

Structures for Business Writing:

Tone Adaptation:

• Formal: "We regret to inform you that..." (NTC letter).
• Semi-formal: "Hi [Name], thanks for reaching out! Here’s the update..." (Daraz email).
• Informal: "Your order’s on the way! 🚚" (Pathao delivery update).

Worked Example: Direct vs. Indirect Email for a Loan Request Scenario: You’re applying for a loan from Nabil Bank.

3. Revising: Refining Logic and Flow

Definition: Evaluating the clarity, coherence, and effectiveness of the draft. Ask:

• Does each paragraph support the main idea?
• Is the tone consistent (e.g., empathetic in a Khalti refund email)?
• Are there logical gaps (e.g., missing steps in a Pathao delivery route plan)?

Techniques:

• Read aloud: Catches awkward phrasing.
• Peer review: Have a colleague (e.g., a classmate) check for audience relevance.
• Checklists:
  • Is the purpose clear in the first sentence?
  • Are transitions smooth (e.g., "Furthermore," "In contrast")?
  • Does the closing match the opening (e.g., "Thank you for your time" → "Looking forward to your reply").

Worked Example: Revising a Traffic Congestion Report for NTC Original Draft (Problematic): "Kathmandu traffic is bad. People waste time. Roads are narrow. Buses are old."

Revised Version (Clear & Action-Oriented): "Kathmandu’s traffic congestion costs the city an estimated ₹2 billion annually in lost productivity, according to a 2023 NTC study. Key issues include:

• Narrow roads (e.g., Thapathali to Koteshwor route) with insufficient lanes for the 1.2 million daily vehicles.
• Outdated public transport fleets (average bus age: 15 years), contributing to 40% of emissions. Recommendations:

1. Widen critical routes (e.g., Ring Road) by 2025.
2. Introduce electric buses in high-density corridors (e.g., New Baneshwor to Chabahil)."

4. Editing: Polishing Language and Style

Definition: Fixing grammar, word choice, and conciseness. Tools like Grammarly or Hemingway Editor help here.

Common Editing Mistakes in Nepali Business Writing:

Worked Example: Editing a Pathao Driver’s Delivery Note Original (Informal/Unclear): "Yo, the package is at your place. It’s in the blue bag. U can pick it anytime. Let me know if u need help."

Edited (Professional): "Dear [Customer Name], Your order (#P12345) has been delivered and is safely placed in the blue bag at [address]. You may collect it at your convenience. Should you require assistance, please call me at [phone number] or reply to this message. Best regards, [Your Name] Pathao Driver"

5. Proofreading: The Final Check

Definition: Spotting typos, formatting errors, and inconsistencies. Use:

• Tools: Grammarly, ProWritingAid.
• Manual Checks:
  • Read backwards (sentence by sentence) to catch typos.
  • Check numbers/dates (e.g., ₹50,000 vs. ₹5,00,000).
  • Verify attachments (e.g., a NEPSE report with missing charts).

Real-World Impact:

• A single typo in a Nabil Bank loan agreement could lead to legal disputes.
• A misplaced decimal in a Daraz invoice might cause customer distrust.

## In the Real World

1. Nabil Bank’s Loan Agreements
   • Idea Used: Structured drafting + legal proofreading.
   • How: Loans are drafted in clear, jargon-free language (e.g., "EMI" explained as "monthly installment") to avoid confusion. The bank uses multi-stage reviews (legal team → compliance → customer service) to ensure accuracy.

2. Daraz’s Customer Service Emails

   • Idea Used: Indirect approach + tone adaptation.
   • How: When resolving complaints (e.g., delayed orders), Daraz uses:
     • Buffer: "We sincerely apologize for the inconvenience."
     • Problem: "Your order #DZ12345 was delayed due to a warehouse issue."
     • Solution: "We’ve expedited shipping, and you’ll receive it by [date]."
   • Result: Higher customer satisfaction scores.

3. NTC’s Public Notices

   • Idea Used: Formal structure + hierarchical outlines.
   • How: Notices follow a block format with:
     • Header: "Notice No. [X]/2024" (official tone).
     • Body: Clear steps (e.g., "All vehicles must carry a pollution certificate by [date]").
     • Footer: Contact details for queries.
   • Why It Works: Reduces ambiguity in legal/compliance communication.

## Case Study: How Himalayan Java Uses the Writing Process

Scenario: Himalayan Java wants to launch a digital marketing campaign but lacks an online presence. Their social media manager follows the writing process to create a proposal for the CEO:

1. Pre-writing:

   • Purpose: Secure budget for SEO and ads.
   • Audience: CEO (data-driven, prefers concise points).
   • Research: Competitor analysis (Daraz’s ad spend, local café trends).

2. Drafting:

   • Structure:
     • Intro: "To align with our 2024 growth target of 20% online sales, we propose a 3-month digital marketing campaign."
     • Body: Bullet-pointed strategy (see outline below).
     • Closing: "Initial investment: ₹2,00,000; projected ROI: 35%."

3. Revising:

   • Added ROI calculations (CEO’s priority).
   • Removed jargon (e.g., replaced "CTR" with "click-through rate").

4. Editing:

   • Shortened paragraphs; used bold for key stats.

5. Proofreading:

   • Checked currency formatting (₹ vs. Rs.) and CEO’s preferred font (Arial).

Final Proposal Outline:

Outcome: The CEO approved the proposal, citing its clarity and data-driven approach.

## Exam Tip

How This Unit is Tested in PU Exams:

1. Short Questions (5–10 marks):

   • Define pre-writing, editing, or proofreading.
   • Example: "Differentiate between drafting and revising in business writing." → Use a comparison table (see above).

2. Long Questions (15–25 marks):

   • Scenario-based: "You are the HR manager of Nabil Bank. Draft an email to employees announcing a new leave policy. Follow the writing process steps."
     • Marks Breakdown:
       • Pre-writing plan (5 marks).
       • Draft (10 marks: structure, tone, clarity).
       • Revision notes (5 marks: logic, flow).
       • Edited version (5 marks: grammar, conciseness).

3. Case Studies (20–30 marks):

   • "Analyze how Daraz could improve its customer complaint emails using the writing process."
     • Expected Answer:
       • Pre-writing: Audience (frustrated customers) → empathetic tone.
       • Drafting: Indirect approach + clear action steps.
       • Revising: Add FAQs (e.g., "Will I get a refund or replacement?").
       • Editing: Remove passive voice (e.g., "Your issue is being resolved" → "We will resolve your issue by [date]").

4. Visuals (5–10 marks):

   • Draw the writing process cycle (like the Mermaid diagram above) and label each stage.
   • Tip: Always color-code stages (e.g., pre-writing = blue, drafting = green).

Common Mistakes to Avoid:

• Ignoring the audience: Writing a formal letter to a Pathao driver.
• Skipping pre-writing: Starting with a draft without research (e.g., a NEPSE report without data).
• Over-editing: Changing the original message while polishing (e.g., making a Khalti refund email sound too robotic).

Pro Tip for Full Marks:

• Use real examples (e.g., "Like Nabil Bank’s loan emails...").
• Show the process (e.g., "First, I would brainstorm key points...").
• Format answers clearly (bullet points for steps, tables for comparisons).