3.3 Report Writing

What is a Report?

A report is a structured, factual document that presents information about a specific subject — research findings, an investigation, a project's progress, an incident, a recommendation — to a defined audience for a specific purpose.

Definition

C.A. Brown: "A report is a communication from someone who has information to someone who wants to use that information."

J.M. Barwa: "A report is a formal document, usually prepared for a specific purpose, addressed to a particular audience, and used as a basis for decision-making."

Characteristics of a good report

---

Importance of Reports

---

Categories / Types of Reports

There are several recognised classifications. The most-used:

By function

By formality

By frequency

By audience

Common business / academic report types

---

Elements of a Formal Report

A formal long report has a standard structure. The IPU-style answer must include all major sections in order.

┌─────────────────────────────────────┐
│       FRONT MATTER                  │
│  - Cover page                       │
│  - Title page                       │
│  - Letter of transmittal            │
│  - Acknowledgements                 │
│  - Table of contents                │
│  - List of figures / tables         │
│  - Abstract / Executive summary     │
├─────────────────────────────────────┤
│       MAIN BODY                     │
│  - Introduction                     │
│  - Methodology                      │
│  - Findings / Discussion            │
│  - Conclusions                      │
│  - Recommendations                  │
├─────────────────────────────────────┤
│       BACK MATTER                   │
│  - References / Bibliography        │
│  - Appendices                       │
│  - Glossary (if needed)             │
│  - Index (long reports only)        │
└─────────────────────────────────────┘

Detailed breakdown

---

Short / Informal Report — Memo Format

For short reports (1-3 pages), the memo format is used:

                            MEMO REPORT

  To:        [Recipient]
  From:      [Author]
  Date:      [Date]
  Subject:   [Specific subject line]

  1. Introduction
     [1-2 sentences on purpose and scope]

  2. Findings / Discussion
     [Main content in 2-4 short sections]

  3. Conclusion
     [Key takeaway]

  4. Recommendation
     [What to do next]

No front matter or back matter for short reports — just the body.

---

Style and Formatting

Language

• Formal but readable — third person ("It was observed..." or first person plural "We observed..." depending on style guide)
• Active voice preferred where possible — "The team tested X" not "X was tested"
• Past tense for completed work, present for general statements
• Avoid emotional / subjective language
• Define acronyms on first use

Formatting

Numbering tables and figures

Table 1: Sample distribution by age group
Table 2: Response time comparison (in seconds)

Figure 1: Project timeline (Gantt chart)
Figure 2: System architecture diagram

---

Step-by-Step Process — Writing a Report

---

Sample Executive Summary (one of the most important sections)

EXECUTIVE SUMMARY

This report investigates the high attrition rate (32%) in the
Engineering department of ABC Technologies during FY 2025-26.

The study analysed exit-interview data from 87 departing employees,
internal HR records, and benchmark data from three peer organisations.

Three primary causes of attrition emerged:

  1. Compensation gap of 12-18% versus market median (cited by 64%)
  2. Lack of clear career-progression paths (cited by 51%)
  3. Limited learning opportunities for emerging technologies (44%)

The report recommends three immediate interventions:

  1. Compensation revision aligned to 75th percentile of market data
  2. Formal career-progression framework with quarterly reviews
  3. Quarterly learning budget of ₹50,000 per engineer

Estimated investment: ₹2.1 crore in Year 1.
Projected attrition reduction: from 32% to ~18% within 12 months,
saving an estimated ₹4.8 crore in recruitment + ramp-up costs.

Detailed methodology, findings, and implementation plan follow.

The executive summary is the report. Senior readers often only read this. Write it last — after you know everything you want to say.

---

Sample Short Report (Memo Style)

                          MEMO REPORT

  To:        Mr Anil Sharma, Head of Operations
  From:      Priya Sharma, Project Manager
  Date:      28 May 2026
  Subject:   Status Report — Project Phoenix as of 28 May 2026

  ─────────────────────────────────────────────────────────────

  1. INTRODUCTION

  This report provides the bi-weekly status update for Project Phoenix
  for the period 14-28 May 2026.

  2. PROGRESS AGAINST PLAN

  The project is currently on track. Sprint 7 concluded on schedule.

  - Sprint 7 stories: 18 planned, 18 completed (100%)
  - Quality: 0 critical defects in production
  - Customer demo: scheduled for 5 June (on plan)

  3. KEY ACCOMPLISHMENTS

   - Login flow with OTP integration completed and deployed
   - Dashboard analytics module 80% complete
   - Pair-programming reduced defect rate by 40% vs Sprint 6

  4. CHALLENGES

   - Staging deployment taking 2 days (target: 1 day) — investigating
   - Testing environment crashes on Mondays — IT engaged

  5. PLAN FOR NEXT SPRINT (1-14 June)

   - Payment gateway integration (Team A)
   - Notification system (Team B)
   - Performance testing (joint)

  6. RECOMMENDATIONS

   - Allocate one DevOps engineer to fix the staging-deploy issue
   - Escalate Monday crashes to IT for permanent resolution

  Detailed sprint report attached.

  ─────────────────────────────────────────────────────────────

  Priya Sharma
  Project Manager, ABC Technologies

---

Common Mistakes in Report Writing

---

Modern Trends

---

Study deep

1. The reader decides whether to read. If your executive summary doesn't grab attention in 30 seconds, the rest may go unread. Front-load the value.

1. Structure beats content. A well-structured report with average content is more useful than a poorly-structured report with great content. Structure makes content findable.

1. Every paragraph should have a purpose. If you can delete a paragraph without losing meaning, delete it.

1. Reports are political. Conclusions reflect on people, decisions, and budgets. Choose language carefully — "challenges" not "failures"; "opportunities" not "gaps". Without compromising honesty, manage tone.

1. Templates save time. Most companies have a report template — use it. Consistency makes filing, retrieval, and comparison easier.

Key Terms — Lesson 3.3

The terms below cover report-writing vocabulary — every PYQ on reports expects fluent use.

Report — A structured written document that presents information, analysis, findings, or recommendations about a specific subject, event, or situation. Different from a letter (which addresses a specific person) and an email (which is conversational); a report is standalone, referenceable, and on-record.

Formal Report — A long, structured report (typically 10+ pages) with all front matter, body, and back matter sections — cover, title page, abstract, acknowledgements, table of contents, list of figures/tables, executive summary, introduction, methodology, findings, analysis, conclusion, recommendations, references, appendices. Used for academic, regulatory, and board-level reporting.

Informal Report — A short report (1–5 pages) in memo or letter style — header, brief introduction, body, conclusion. Used for routine internal updates. Skips most of the front and back matter of a formal report.

Informational Report — A report that shares facts and updates without analysis or recommendations. Examples: sales summary, attendance report, system uptime report. The reader's job is to understand, not to act.

Analytical Report — A report that analyses data and draws conclusions — finds patterns, root causes, comparisons. Adds value beyond raw facts by interpreting them.

Research Report — A formal report documenting research findings — methodology, data, results, discussion, conclusions. Follows academic conventions (IMRaD structure, citation style). Detailed in Lesson 3.4.

Recommendation / Decision Report — A report that presents a problem, evaluates options, and recommends a course of action. Common in management consulting and policy work. Structure: situation → analysis → options → recommendation.

Progress / Status Report — A periodic report tracking a project's status — what was planned, what was achieved, what is pending, what is blocking. Often follows a fixed template; sent weekly or monthly during projects.

Project Report — An umbrella term for any report on a project — feasibility, progress, completion. In academic settings, "project report" specifically refers to the final report submitted as part of a course requirement (BCA Final Year Project, etc.).

Title Page — The first page of a formal report containing title, author(s), affiliation, date, document number, version. Often includes a logo and the recipient's name. The first "professional impression" of the document.

Abstract / Executive Summary — A concise standalone summary of the entire report — purpose, methods, key findings, main conclusions. Abstract is academic (150–250 words); executive summary is business (1–2 pages). Written last but placed near the front. The most-read section of any report.

Table of Contents (ToC) — A list of all major sections with page numbers, generated from the report's headings. Lets the reader find specific information without reading sequentially. Generated automatically by modern word processors.

List of Figures / List of Tables — Front-matter sections that list every figure and table in the document with caption and page number. Like a ToC but for visuals. Useful for reports with many visualisations.

Introduction — The opening section of the report's body. Establishes context (background, why this report exists), scope (what is and is not covered), objective (what the report aims to achieve), structure (how the rest of the report is organised).

Methodology / Methods Section — A section describing how the work was conducted — data sources, sampling, instruments, analytical techniques, assumptions, limitations. Lets readers judge the rigour and replicability of the findings.

Findings / Results — A section presenting what was discovered, ideally without interpretation. Pure facts: tables, graphs, key numbers. The "raw output" of the work.

Analysis / Discussion — A section interpreting the findings — what patterns mean, how they connect, what was unexpected, how results compare with prior work. The intellectual core of an analytical report.

Conclusion — A section summing up the report's findings and analysis — what it all means in the bigger picture. Distinct from recommendations: conclusion is "what is the truth"; recommendations are "what should be done next".

Recommendation — Specific, actionable proposals for action based on the report's findings — what should be done, by whom, by when, with what resources. Phrased as imperatives ("Allocate one DevOps engineer to fix...") rather than vague suggestions.

References / Bibliography — A list of sources cited in the report — books, papers, articles, websites, internal documents. Allows readers to verify claims and explore further. Follows a specific citation style (APA, MLA, Chicago, IEEE). Differences: References lists only cited works; Bibliography may include uncited background reading.

Appendix / Appendices — Supporting material placed after the references — detailed tables, full questionnaires, raw data, lengthy code. Removed from the main flow to keep the body readable, but accessible to anyone who wants more detail.

IMRaD Structure — The classical scientific-paper structure: Introduction → Methods → Results → and Discussion. Standard for research papers and academic reports. Lets readers familiar with the format navigate any paper quickly.

Footnote / Endnote — Short clarifying notes placed at the bottom of a page (footnote) or at the end of a section/chapter (endnote). Used for citations in some styles (Chicago) or for explanatory asides that would interrupt the main flow.

Citation Style — A standardised format for citing sources. Common ones: APA (American Psychological Association — psychology, social sciences), MLA (Modern Language Association — humanities), Chicago/Turabian (history, publishing), IEEE (engineering, computer science), Vancouver (medical). Choose one and apply it consistently.

Plagiarism — Presenting someone else's work or ideas as your own without proper attribution. Forms include copy-paste from source, paraphrasing without citation, using AI-generated text without disclosure, recycling your own prior work without acknowledgement (self-plagiarism). Most academic and journalistic codes treat plagiarism as career-ending.

Plagiarism Checker — Software (Turnitin, iThenticate, Grammarly Plagiarism, Copyscape) that scans a document against billions of online and database sources and reports similarity percentages. Used by universities, journals, and conferences. Most institutions accept ~15% similarity as fair use.

Cover Letter / Transmittal Letter — A brief letter accompanying a formal report, addressed to the recipient. Explains the purpose of the report and what action (if any) is requested. Like a handshake before handing over a document.

Glossary — A list of specialised terms and their definitions included in the report's back matter. Helps readers not fluent in the subject matter. Modern technical reports increasingly include glossaries.

Visual Aid in Reports — Tables, charts, graphs, infographics, photographs, maps — used to convey data and concepts more efficiently than text. Each visual gets a number, caption, and reference in the body ("see Figure 3"). Powerful but must be relevant — gratuitous visuals reduce credibility.

One-Page Report / One-Pager — A modern executive-friendly format that distils any report into a single page with key visuals, headlines, and recommendations. Forces ruthless prioritisation; increasingly mandatory for senior consumption.

---

Common exam question (very high frequency): "Explain the elements of a formal report." — List all front matter, body, and back matter sections (15 sections in order); one-line description of each.

Common exam question: "Differentiate formal and informal reports." — Tabulate: formal = long, structured, all elements; informal = short, memo-style, body-only.

Common exam question: "Discuss the types / categories of reports." — Functional types (informational, analytical, research, recommendation); other classifications (by formality, frequency, audience).

Common exam question: "Write a status / progress report on [scenario]." — Use memo format; sections: intro, progress, accomplishments, challenges, plan, recommendations.

Worked Example — A Correct Formal-Report Skeleton

Task: a student plans a formal project report with only this outline — fix it against the lesson's elements.

"1. Introduction 2. Body 3. Conclusion"

Diagnosis: it has no front matter (no title page, table of contents, or executive summary), no back matter (no references or appendices), and it collapses methodology, findings, and recommendations into one vague "Body". A formal report must carry all major sections in order.

Revision (correct skeleton):

Front matter: cover page → title page → letter of transmittal → acknowledgements → table of contents → list of figures/tables → abstract/executive summary Main body: introduction → methodology → findings/discussion → conclusions → recommendations Back matter: references/bibliography → appendices → glossary

Why it works: it follows the lesson's three-block structure — front matter, main body, back matter — and separates conclusions (what is true) from recommendations (what to do next), the distinction graders look for.

Self-check

Recall the report's structure and types — answer, then check.

1. Name the three blocks of a formal report's structure. (front matter, main body, back matter)
2. What is the difference between a report's conclusion and its recommendations? (the conclusion states what is true / what the findings mean; recommendations state what should be done next)
3. Name the four functional types of report. (informational, analytical, research, recommendation)
4. When should the executive summary be written, and why does it matter? (written last, after you know everything; senior readers often read only it)
5. What does IMRaD stand for? (Introduction, Methods, Results, and Discussion)
6. Which format is used for a short / informal report? (memo format — To/From/Date/Subject header, then a short body)