M.Tech Skill Enhancement – English & Communication
Study Notes (Exam‑oriented)
(Designed for M.Tech students preparing for written & oral communication exams in Skill‑Enhancement courses)
1. Overview
| Item | Why it matters | Exam format | Key focus |
|---|---|---|---|
| Technical Writing | Clarity & precision in research reports, proposals, patents | Multiple‑choice, fill‑in, essay | Tense, voice, structure |
| Business & Academic Emails | Professional outreach, networking | Short‑answer, role‑play | Tone, structure, etiquette |
| Oral Communication | Presenting research, defending projects | Oral exam, PowerPoint | Body language, pacing, visual aids |
| Listening & Feedback | Effective teamwork, peer review | Listening passages, reflective writing | Active listening, constructive critique |
Exam strategy tip:
Read the question carefully → Identify the type (grammar, composition, presentation) → Use the relevant “formula” below → Review for clarity and correctness.
2. Written Communication
2.1 Email & Correspondence
| Structure | Formula (set‑of‑steps) | Example (Business) |
|---|---|---|
| Header | To:, Cc:, Bcc:, Subject: |
To: Prof. R. Sharma |
| Opening | Dear <Title> <Surname>, |
Dear Dr. Sharma, |
| Purpose | One sentence stating objective | I am writing to request a meeting to discuss my thesis progress. |
| Body | 2-3 concise paragraphs | 1) Summary of issue 2) Proposed solution/ask |
| Closing | Sincerely,, Best regards, |
Sincerely, |
| Signature | Name, degree, department, contact | S. Patel, M.Tech. (Electrical), Dept. of EE, 9876543210 |
Tricky Points
| Issue | Rule | Exception |
|---|---|---|
| Tone | Formal vs. informal | Use “Dear” for formal, “Hi” for informal |
| Subject Line | Should be a concise summary | Avoid vague “Meeting” → use “Request for Thesis Meeting – 28‑Oct” |
| Attachment Mention | “Please find attached…” | Do not say “See attached” – it’s ambiguous |
2.2 Technical Reports
| Section | Purpose | Typical Content | Common Pitfalls |
|---|---|---|---|
| Title | First impression | Concise, descriptive | Avoid jargon |
| Abstract | One‑paragraph summary | Aim, methods, results | Over‑loading with detail |
| Introduction | Context & objectives | Literature review, gap | Repetition of abstract |
| Methodology | How work was done | Materials, procedures, equations | Lack of units & precision |
| Results | Data presentation | Tables, graphs, statistical tests | Mis‑labelled axes |
| Discussion | Interpretation | Comparison to literature | Over‑claiming |
| Conclusion | Take‑away | Summary, future work | Redundancy |
| References | Citation style | IEEE, APA | Inconsistent formatting |
| Appendices | Supplementary data | Raw data, code | Not referenced in text |
Formula for a robust report
- Purpose → Method → Result → Conclusion
- Claim + Evidence + Reason (CER) pattern in Discussion
2.3 Academic Writing (Essays & Papers)
| Writing Style | Key Features | Common Errors |
|---|---|---|
| Academic | Formal tone, passive voice acceptable, citations | Over‑use of passive → “It was found” instead of active “We found” |
| Technical | Precise language, minimal filler, focus on data | Use of colloquialisms (“like” “such as”) |
| Business | Persuasive, client‑centric, limited jargon | Ambiguous statements, vague metrics |
Grammar Checklist
| Rule | Sentence | Error |
|---|---|---|
| Subject‑Verb Agreement | The data *support* the hypothesis. |
supports (singular) |
| Tense Consistency | The study *revealed* a trend, and *it shows* it persists. |
revealed → shows (different |