Business Correspondence And Report Writing By Rc Sharma And Krishna Mohan

What This Book Actually Covers

Business Correspondence and Report Writing by RC Sharma and Krishna Mohan is one of those textbooks you will see recommended across almost every Indian university business program. It covers the mechanics of writing business letters, memos, emails, reports, proposals, and case studies. The approach is practical rather than theoretical. You get templates, formats, and exercises meant for students who need to produce professional documents under time pressure. The book is widely available through major online retailers and university bookshops. Check platforms like Amazon India, Flipkart, or your campus bookstore. You may also find older editions at lower prices on used book sites. Newer editions tend to update email and digital communication sections, which matters because the format of modern business correspondence has shifted since the first print run. The content breaks into two main parts. The first part deals with correspondence. That includes formal letters, job application letters, inquiry and order letters, complaint letters, claim letters, and cover letters. The second part focuses on report writing. You will find chapters on types of reports, structure and layout, data presentation, and the mechanics of drafting different report formats.

Each chapter usually ends with exercises. These are not filler. They mirror real assignments you might get in a course or actual workplace tasks. The exercises include drafting letters based on scenarios, rewriting poorly written messages, and structuring short reports from given data.

What Works Well About This Textbook

The clearest strength is the format library. If you have never written a formal complaint letter or needed to structure a progress report, the book gives you a straightforward template to follow. The examples are simple and repetitive by design. That repetition is useful when you are learning. You practice until the structure becomes automatic. The language is plain. There is no unnecessary academic padding. That makes it easier to use as a quick reference rather than a cover-to-cover read. I have had students flip directly to the report chapter during exam prep because they already knew the correspondence section cold.

Where the Book Falls Short

The biggest limitation is the treatment of digital communication. Earlier editions treat email as an afterthought. Even in updated versions, the coverage does not match how most business correspondence actually happens today. Slack messages, internal documentation tools, and asynchronous written communication are barely mentioned. If you rely solely on this book for email writing, you will miss nuances around tone, threading, and audience awareness in digital spaces. Another gap is the treatment of international business correspondence. The examples lean heavily toward Indian business contexts. Formats, conventions, and tone expectations vary across regions. If you are working with clients or partners in North America, Europe, or Southeast Asia, you will need to adapt what the book teaches. The exercises sometimes feel detached from real workplace stakes. In a class, a poorly written report gets a grade. In a company, it can delay a decision or damage a relationship. The book does not push hard enough on that consequence mapping. You can fill that gap by treating each exercise like it has an actual recipient who will react negatively if you mess it up.

How to Use This Book Effectively

Do not read it passively. Work through the exercises and then revise your answers against the model responses. The model answers are not always perfect, but they show you the expected structure. Compare your version side by side with theirs. Mark where you added unnecessary words, missed a required component, or used the wrong tone. Focus especially on the report writing section. That is where most students struggle. The book explains the difference between informational and analytical reports well. Pay attention to how each type requires a different executive summary approach. Informational reports summarize facts. Analytical reports summarize conclusions and recommendations. Mixing those up in an actual workplace document is a common mistake. Practice rewriting bad examples. The book provides some intentionally poor drafts. Fixing them teaches you more than writing from scratch. You start recognizing structural flaws quickly. Redundancy, vague language, missing context, and incorrect formatting become visible to you faster.

A Specific Problem I Ran Into and How I Fixed It

I was reviewing a student's assignment where they followed the book's complaint letter template perfectly but addressed the letter to a generic customer service department instead of a specific recipient or title. The book's example used a generic placeholder, and the student copied that format without questioning it. In real business practice, routing a complaint through a generic department delays response time significantly. The workaround was simple. I had them research the company's organizational structure online, identify the relevant department head or grievance officer, and address the letter directly. That single change improved the letter's effectiveness in practice. It also taught them that templates are starting points, not final instructions. Always verify the recipient before sending.

Counter-Intuitive Points Beginners Miss

One thing most learners overlook is that brevity in business correspondence is not about using fewer words blindly. It is about removing ambiguity. A shorter letter that leaves out key context is worse than a longer one that includes it. The book emphasizes conciseness, but it does not always make clear that conciseness and completeness are different goals. You need both. Another overlooked point is the role of the subject line. Beginners treat it as decorative. In actual business environments, the subject line determines whether your message gets opened, filed, or ignored. The book mentions subject lines but does not drill into their strategic importance. A good subject line states the purpose, the reference number if applicable, and the required action. That alone can cut response time by half in routine correspondence.

When This Book Is Not Enough

If you need to write technical reports, data-heavy business proposals, or documents for regulatory compliance, this textbook will only take you so far. It covers general report formats adequately but does not go deep into technical documentation standards, visual data presentation beyond basic tables, or industry-specific reporting frameworks. For those cases, you will need supplementary material. Consider pairing this book with resources on business data visualization, technical writing handbooks, or industry-specific communication guides. The foundation from Sharma and Krishna Mohan is solid. The gaps appear when your work moves beyond standard correspondence and report types into specialized domains. The book remains a useful reference for students and early-career professionals who need to learn the core formats. It will not make you an expert in business communication on its own. But used correctly alongside real-world practice and supplemental reading, it builds a functional base that most people in office roles will need at some point.