3.1 Technical Writing, Note-Making, Notice & Email Writing

Overview of Technical Writing

Technical writing is the form of written communication that conveys complex or specialised information to a specific audience in a clear, accurate, and useful form.

Definition and nature

Common textbook definitions:

• Sue Wickham: "Technical writing is the art and science of communicating technical information to a defined audience for a specific purpose."
• Mike Markel: "Technical communication is the process of finding, using, and sharing information that has practical value."

Nature of technical writing:

---

Basic Principles of Technical Writing

The principles below apply to every piece of technical writing — from a 100-word email to a 100-page dissertation.

Common exam question: "List the basic principles of technical writing." — Pick 7-8 principles with one-line explanations.

---

Styles of Technical Writing

A complete document often uses multiple styles — a research paper has descriptive (methods), analytical (results), and persuasive (conclusion) sections.

---

Note-Making

Note-making is the skill of summarising information from a longer source (lecture, book, video, meeting) into a concise written record for future reference.

Why note-making matters

• Aids understanding (active engagement vs passive listening)
• Permanent record (you forget 80% of what you hear within 24 hours)
• Searchable reference (review before exams, meetings)
• Builds writing skill (forces you to summarise)

Standard Note-Making Format

A widely-taught format for academic note-making:

                                      TITLE
                                       │
                                       │
   ┌───────────────────────────────────┼─────────────────────────────────┐
   │                                                                     │
   │   1. Main heading                                                  │
   │      1.1 Sub-heading                                                │
   │           1.1.1 Sub-sub-heading                                     │
   │           ・ Point 1                                                 │
   │           ・ Point 2                                                 │
   │                                                                     │
   │   2. Main heading                                                   │
   │      2.1 Sub-heading                                                │
   │                                                                     │
   └─────────────────────────────────────────────────────────────────────┘

   Abbreviations Key:
     • mgmt  = management
     • org   = organisation
     • etc.

Sample Note (on Communication chapter)

                       COMMUNICATION

   1. Definition
      1.1 Comm = sharing info to create understanding
      1.2 Latin "communis" = common
      1.3 Two-way process (sender ↔ receiver)

   2. Process elements
      2.1 Sender, Encoding, Message, Channel,
           Decoding, Receiver, Feedback
      2.2 Plus: Noise (8th element)

   3. Types
      3.1 Verbal vs Non-verbal
      3.2 Formal vs Informal
      3.3 General vs Technical
      3.4 Oral vs Written

   4. Barriers
      4.1 Physical (noise, distance)
      4.2 Language (jargon, accent)
      4.3 Psychological (bias, anxiety)
      4.4 Cultural (norms differ)

   5. Seven Cs
      Clear, Concise, Concrete, Correct,
      Coherent, Complete, Courteous

   Abbreviations:
     • Comm = communication
     • Info = information

Note-making techniques

---

Notice Writing

A notice is a brief, formal written announcement displayed on a board or circulated, intended for a defined audience (students, employees, members).

Characteristics

• Short — typically 50 words
• Formal — neutral tone
• Time-bound — relevant for a specific date / event
• Audience-specific — clearly addressed
• Verifiable — signed and dated by an authority

Standard Notice Format

                                NOTICE

                          [Organisation Name]
                          [Date: 28 May 2026]

   Subject: [One-line description of the notice]

   This is to inform all [target audience] that [event / instruction
   / announcement]. [Date, time, venue]. [Action required, if any].

   For any queries, contact [name / department / contact].

                                              [Signature]
                                              [Name]
                                              [Designation]

Sample Notice

                                NOTICE

                          XYZ College
                          Date: 28 May 2026

   Subject: Annual Inter-College Coding Contest

   All students are informed that the Annual
   Inter-College Coding Contest will be held on Saturday, 14 June 2026,
   from 10:00 AM to 1:00 PM in the Main Auditorium.

   Interested students must register with the Coding Club by 10 June
   2026. Registration is free. Top three winners will receive cash
   prizes and certificates.

   For details, contact Mr Rohit Jangra (Coding Club President) at
   coding.club@xyzcollege.edu.

                                            Priya Sharma
                                            Convener — Coding Club

Common types of notices

---

Email Writing

Email is the most-used business communication tool today. Despite the rise of Slack and Teams, email remains the primary channel for formal external communication and on-record internal messages.

Anatomy of a business email

   From:       priya@abc.com
   To:         rohan@xyz.com
   Cc:         manager@xyz.com
   Bcc:        records@abc.com
   Subject:    Sprint Review Postponed to 28 May, 3:00 PM

   Dear Rohan,

   I hope this email finds you well.

   [Body — purpose, details, action]

   Looking forward to your response.

   Regards,
   Priya Sharma
   Project Manager, ABC Technologies
   +91 98765 43210 | priya@abc.com

Standard sections

Subject line — make it count

The subject line is what decides whether your email is opened or ignored. Make it specific and outcome-oriented.

Email structure — the BLUF principle

Bottom Line Up Front — state your purpose / request in the first sentence. Don't bury it in paragraph three.

Bad opening:

"I hope you are doing well. I wanted to reach out to follow up on something we discussed last Friday, which is related to a topic I think might be of interest..."

Good opening:

"Could you please approve the revised SOW (attached) by EOD Wednesday? The client is waiting on our sign-off to start work."

Sample formal business email

Subject: Request for Quotation — Office Furniture for 20 Workstations Dear Mr Sharma, I am writing on behalf of XYZ Solutions to request a quotation for the supply and installation of office furniture for our new branch in Gurugram. Requirement: - 20 standard workstations (desk + ergonomic chair) - 2 meeting tables (10-seater each) - 1 receptionist desk - Delivery + installation at Sector 44, Gurugram Timeline: Delivery and installation to be completed by 30 June 2026. Kindly share your detailed quotation including unit prices, total cost (excl. GST), warranty terms, and earliest delivery date, by 10 June 2026. Please feel free to call me at +91 98765 43210 for any clarifications. Looking forward to your response. Regards, Priya Sharma Operations Manager, XYZ Solutions Pvt Ltd priya@xyz.com | +91 98765 43210

Email etiquette — do's and don'ts

When NOT to use email

• Highly emotional / sensitive topic — talk in person or call
• Complex argument that needs back-and-forth — meet or call
• One-line acknowledgement to a one-line message — use chat
• Information already in a shared dashboard / doc — link instead

---

Modern email tools

---

Study deep

1. The subject line is the email. Most professionals receive 50-100 emails a day; they decide what to open in 2 seconds. A vague subject = your email gets skipped. A specific subject = it gets read.

1. BLUF saves everyone's time. Burying your request in paragraph three means the reader has to read everything to figure out what you need. Lead with the ask.

1. Email is on-record forever. Companies retain emails for years. Don't write what you wouldn't want screenshotted. Don't say in email what should be said in person.

1. Notice writing is a 5-minute skill that earns marks. It's a guaranteed exam question and the format is fixed. Memorise the structure once and reproduce it.

1. Note-making is the skill no one teaches but everyone needs. Strong students take active notes — they translate the speaker's words into their own. Passive note-takers (just copying slides) learn far less.

Key Terms — Lesson 3.1

The terms below cover technical writing fundamentals plus the four short written forms — note-making, notice, email — that every Unit-III PYQ expects.

Technical Writing — The discipline of writing technical, scientific, or business content for a specified audience with clarity, accuracy, and purpose. Distinct from creative writing in that it prioritises information transfer over self-expression. Tested by whether the reader can take the right action after reading.

Principles of Technical Writing — The set of guidelines that distinguish good technical writing: clarity, conciseness, accuracy, audience awareness, structure, objectivity, simplicity, completeness, consistency, action-orientation. Every PYQ on "principles of technical writing" expects 8–10 of these.

Audience Analysis — The step before drafting where the writer identifies who will read the document — their role, expertise, expectations, time pressure, and what they need to do next. Audience-blind writing is the single largest cause of failed technical documents.

Pre-Writing / Planning Stage — The first phase of the technical-writing process: define purpose, identify audience, gather information, outline structure. Skilled writers spend significant effort here; novice writers rush straight to drafting.

Drafting Stage — The middle phase of technical writing: write a complete first draft following the outline, focused on getting content down rather than perfecting wording. Editing happens later.

Revising / Editing Stage — The final phase: revise content for clarity and completeness, edit sentences for concision and grammar, proofread for typos and formatting. Revising is where mediocre drafts become strong documents.

Note-Making — The practice of producing structured, abbreviated personal notes from a source (lecture, book, meeting, video) for future recall. Differs from verbatim transcription by selecting, condensing, and re-organising the material into your own structure.

Note-Making Format — The canonical structure: title at top, source and date, heading-based hierarchy (Roman numerals for sections, capital letters for sub-sections, numbers for points), consistent abbreviations, summary at the end. Allows quick scanning weeks later.

Cornell Note-Making System — A widely-taught note format with the page divided into three zones: a narrow cue column on the left (questions, keywords), a wide notes column on the right (main content), and a summary strip at the bottom (key takeaways). Designed at Cornell University, 1950s.

Abbreviations and Symbols (Note-Making) — Standard shortcuts for faster note-taking: & (and), w/ (with), w/o (without), → (leads to), = (is, equals), e.g. (for example), i.e. (that is), vs (versus), + (positive), − (negative), discipline-specific shortcuts. Build a personal key.

Notice — A short, formal written announcement displayed publicly to inform a specified audience about an event, change, or requirement. Found on company noticeboards, college boards, government offices, residential associations. Used in academic exams to test brief formal-writing skills.

Notice Format — The canonical exam-ready structure: organisation name at top centre, bold heading NOTICE, date on the left, subject as a heading, 3–5 sentence body (what / when / where / who / how), issuer's signature with name and designation. ~50 words target.

Email — Asynchronous electronic mail — the workhorse of professional written communication. A modern professional sends 30–100 emails per working day; mastering email structure compounds dramatically.

Subject Line — The first 50–60 characters of an email — what the recipient sees in their inbox list. A specific, action-oriented subject ("Sprint Review moved to Wed 3 PM") dramatically increases the chance of being read. Vague subjects ("Update", "Quick question") get ignored.

BLUF (Bottom Line Up Front) — A modern email-writing convention popularised in US military and business contexts: state the main request or conclusion in the first 1–2 sentences, then provide context and details. Saves the reader from reading the whole email to extract the ask.

To / Cc / Bcc — Three email recipient fields with distinct meanings. To is the primary recipient expected to act. Cc (carbon copy) is for awareness, no action required. Bcc (blind carbon copy) is hidden from other recipients — used for confidential awareness; should be used sparingly.

Reply All vs Reply — Two response options that cause endless email-pain when misused. Reply All sends to everyone on the thread; Reply only to the original sender. Default: choose Reply unless everyone needs the response.

Email Etiquette — Norms for professional email: clear subject, proper greeting, concise body, professional sign-off, signature with title and contact, proofreading, reasonable response time, judicious Cc / Bcc, no all-caps shouting, no chain-forwarding.

Email Signature — A standardised block at the end of every email containing the sender's name, title, organisation, contact details. Modern signatures may include disclaimers (legal), social links (LinkedIn), brand logo. Set once in your email client; auto-appended thereafter.

Memo (Memorandum) — An internal written communication within an organisation — formal, short (typically 1 page), and structured. Used for policy announcements, brief reports, action directives. The pre-email era's email; still used in regulated industries and government.

Subject (in Notice / Memo / Email) — The one-line description that appears prominently below the heading. Specifies exactly what the document is about. Strong subject = strong skim-readability.

Salutation / Greeting — The opening line of a letter or email. "Dear Mr Sharma," for formal; "Hi Rohan," for semi-formal; "Hello team," for group emails. Choose by audience and relationship.

Sign-off / Complimentary Close — The closing line before the signature. "Sincerely" / "Yours faithfully" for very formal; "Regards" / "Best regards" for standard business; "Thanks" / "Cheers" for friendly. Indian convention historically favoured "Yours faithfully"; modern Indian business email increasingly uses "Regards".

Body Paragraphs Structure — A practical pattern for the body of an email or short letter: paragraph 1 sets context and the ask, paragraph 2 provides supporting detail, paragraph 3 specifies next steps and timing. Keep each paragraph short (2–4 sentences).

Attachment Etiquette — When attaching files: reference the attachment in the body ("see attached invoice"), use clear file names (Invoice_XYZ_May2026.pdf, not scan001.pdf), verify the attachment is actually attached before sending (Gmail's auto-warning saves countless embarrassments).

Forward / FW — Sharing an email thread with someone not originally included. Best practice: add a brief explanation at the top ("Forwarding for your awareness — Priya's update on the migration"), don't blindly forward sensitive content.

Email Threading — Most email clients group related messages (a reply chain) into a single thread. Helps preserve context but can make threads unwieldy after many replies. Modern practice: rename the subject if the topic shifts substantially, or start a new thread.

Out-of-Office (OOO) Auto-Reply — An automated email sent in response to incoming mail when the user is unavailable. Should state: dates of absence, alternate contact, expected return. Set whenever you'll be unavailable for more than half a day.

---

Common exam question: "Define technical writing. Discuss its principles." — Definition + 8-10 principles with one-line explanations.

Common exam question: "Write a notice on [topic — e.g. annual function, library closure, code club registration]." — Use the standard format; 50 words; date, sign-off included.

Common exam question: "Write a formal email to [scenario — request quotation, apology to client, leave application, project status update]." — Use BLUF; clear subject; greeting, body, sign-off; ≤ 200 words.

Common exam question: "What is note-making? Discuss its importance and techniques." — Define; benefits (active engagement, permanence, search, writing practice); show standard format with abbreviations key.

Self-check

Recall the writing fundamentals and the three short forms — answer, then check.

1. Whose definition calls technical writing "the art and science of communicating technical information to a defined audience for a specific purpose"? (Sue Wickham)
2. What does BLUF stand for in email writing? (Bottom Line Up Front)
3. What is the difference between Cc and Bcc? (Cc is visible to all recipients, for awareness; Bcc is hidden from the other recipients)
4. Name three note-making techniques. (linear/outline, Cornell method, mind mapping, charting, sentence method, boxing — any three)
5. What is the typical word target for a notice? (about 50 words)
6. Name three styles of technical writing. (descriptive, instructional, persuasive, analytical, expository, narrative — any three)