Chapter 8: Report Writing and Business Proposals
Reports and proposals are among the most important business documents. Reports provide structured information for decision-making, while proposals present solutions and pitch ideas for approval. This chapter covers planning, writing, and presenting both document types.
8.1 Understanding Business Reports
Definition: A business report is a structured, factual document communicating information about a specific business situation, presenting analysis, and often including conclusions and recommendations.
Types of Reports
| Type | Length | Format | Nepal Example |
|---|---|---|---|
| Memo Report | 1-2 pages | Informal, To/From/Subject | Internal memo on new leave policy |
| Letter Report | 1-5 pages | Business letter format | Audit findings from CA firm |
| Short Formal | 5-15 pages | Structured with headings | Annual marketing performance report |
| Long Formal | 15-100+ pages | Full formal structure | Nepal Investment Board sector analysis |
| Annual Report | 50-200 pages | Comprehensive with financials | Nabil Bank's annual report to shareholders |
Report Purposes
| Purpose | Description | Example |
|---|---|---|
| Informational | Present facts without analysis | Monthly sales report to branch manager |
| Analytical | Analyze data, provide interpretations | Market analysis for product launch in Terai |
| Persuasive | Recommend a course of action | Report recommending digital transformation |
| Compliance | Fulfill regulatory requirements | NRB-mandated quarterly bank report |
| Feasibility | Assess project viability | Study for new hotel in Pokhara |
8.2 Structure of a Formal Report
| Section | Part | Content | Tips |
|---|---|---|---|
| Prefatory | Title Page | Report title, author, date, recipient | Specific title, not just "Report" |
| Letter of Transmittal | Formal letter presenting report | State purpose, scope, acknowledgments | |
| Table of Contents | Headings with page numbers | Up to 3 levels; use dot leaders | |
| Executive Summary | Condensed version (10% of total) | Write LAST; include findings and recommendations | |
| Body | Introduction | Background, purpose, scope, methodology | State what report covers AND doesn't cover |
| Findings | Data, analysis, discussion | Use headings, tables, charts | |
| Conclusions | What findings mean | Each supported by data in findings | |
| Recommendations | Specific suggested actions | Number them; make actionable | |
| Supplementary | References | Sources cited | Consistent citation style (APA) |
| Appendices | Supporting documents, raw data | Label A, B, C; reference in body |
8.3 Writing an Executive Summary
The executive summary is often the only section senior decision-makers read. It must be a self-contained miniature of the entire report.
Components
| Component | Content | Length | Tips |
|---|---|---|---|
| Purpose | Why the report was written | 1-2 sentences | "This report examines..." |
| Key Findings | Most important data points | 3-5 sentences | Include specific numbers |
| Conclusions | What findings mean | 2-3 sentences | Link directly to findings |
| Recommendations | Suggested actions | 2-4 sentences | Be specific and actionable |
Sample Executive Summary
Customer Satisfaction Survey — Himalayan General Insurance
This report presents findings from a survey of 500 policyholders across five cities during January-February 2026. Overall satisfaction stands at 68%, down from 74%. Claim settlement scored lowest (52%) with 45-day average delays against promised 15 days. Policy purchase scored highest (82%). Customers aged 25-35 showed highest dissatisfaction regarding digital services.
Declining satisfaction is driven by claim delays and inadequate digital services. Recommendations: (1) Implement automated claim processing to reduce time to 10 days (NPR 2.5 crore investment, NPR 80 lakh annual savings); (2) Launch mobile app by Q3 2026; (3) Establish dedicated feedback team with 48-hour response commitment. Projected to increase satisfaction to 80% within 12 months.
8.4 Business Proposals
Types
| Type | Initiated By | Nepal Example |
|---|---|---|
| Solicited | Response to RFP | IT firm responding to government e-governance RFP |
| Unsolicited | Proposer identifies opportunity | Consulting firm proposing efficiency audit to bank |
| Internal | Within organization | HR proposing training program to management |
| Grant | To funding agencies | NGO proposing women's empowerment to UN Women |
Proposal Structure
| Section | Content | Persuasion Strategy |
|---|---|---|
| Executive Summary | Overview of problem, solution, benefits, cost | Make reader want to read full proposal |
| Problem Statement | Detailed description of need | Show deep understanding of pain points |
| Proposed Solution | What you will do and how | Be specific; show methodology |
| Timeline | Milestones and delivery dates | Realistic planning with contingency |
| Budget | Detailed cost breakdown | Show value for money |
| Team/Qualifications | Profiles and track record | Build credibility with past successes |
8.5 Report Writing Process
| Stage | Activities | Time | Pitfall |
|---|---|---|---|
| Planning | Define purpose, audience, scope; create outline | 20% | Skipping to writing immediately |
| Researching | Collect primary and secondary data | 30% | Relying solely on internet |
| Organizing | Analyze data, identify patterns | 15% | Presenting data without analysis |
| Writing | Draft body first, then intro and summary | 25% | Writing exec summary first |
| Revising | Proofread, check logic, get peer review | 10% | Submitting first draft |
Writing Style
Objectivity — "The data indicates..." not "I think..." Conciseness — "because" not "due to the fact that." Precision — "Revenue increased 12.5% in Q3" not "significantly." Formal Tone — no contractions. Active Voice — "The committee recommends..." is clearer.
8.6 Common Mistakes
| Mistake | Problem | Correction |
|---|---|---|
| Vague Recommendations | "Improve customer service" | "Hire 5 reps by July; implement 24-hour response policy" |
| Unsupported Conclusions | Conclusions not backed by data | Every conclusion must trace to findings |
| Information Overload | Including every data point | Relevant data only; extras in appendices |
| Biased Language | "Amazing team achieved incredible results" | "Team exceeded targets by 18%" |
8.7 Case Study: Nepal Infrastructure Bank ADB Proposal
Goal: Secure NPR 500 crore ADB credit line, competing against 3 banks.
Strategy: Researched ADB priorities. Problem statement highlighted Nepal's infrastructure gap (35% roads paved, 40% unreliable electricity). Proposed specific sectors with NPR 1,200 crore pipeline.
Differentiators: Environmental/social framework aligned with ADB safeguard policies; 30% gender-responsive lending; quarterly reporting metrics; three pilot project feasibility reports; staff with ADB experience.
Result: Selected as primary partner, full NPR 500 crore. Evaluators cited clarity, ADB alignment, and detailed implementation plan as decisive factors.
Practice Questions
Short Answer:
1. Differentiate informational and analytical reports with examples.
2. What are components of a formal report? Explain prefatory parts.
3. How does an executive summary differ from introduction?
4. Explain solicited vs unsolicited proposals.
5. Describe the five-stage report writing process.
Long Answer:
6. Write an executive summary for a report on declining hotel occupancy in Nepal with recommendations. (15 marks)
7. Explain complete proposal structure. How does a proposal differ from a report? (15 marks)
8. "Good reports are rewritten." Discuss revision importance and common mistakes. (15 marks)
9. Draft a feasibility report outline for a Nepal e-commerce business. (15 marks)
10. Prepare a brief internal proposal for staff training at a Nepali bank. (15 marks)
Exam Tips: ✓ Know difference: reports (objective) vs proposals (persuasive) ✓ Follow exact structural format ✓ Practice writing executive summaries ✓ Mention five-stage process ✓ Nepal examples (NRB, NEPSE, ADB)