FIR & Complaint Drafting
"The FIR is the foundation — a weak foundation crumbles the entire case"
A well-drafted FIR triggers effective investigation, captures all offences, preserves evidence requirements, and withstands defence scrutiny. A poorly drafted FIR leads to discharge, acquittal, or quashing. Master the art of cyber crime FIR drafting.
FIR vs Private Complaint
FIR (First Information Report) under BNSS S.173 is information given to police about commission of a cognizable offence. Police must register and investigate without requiring court permission.
Private Complaint under BNSS S.200 is filed directly before Magistrate when: (a) offence is non-cognizable, (b) police refuses to register FIR, or (c) complainant prefers private prosecution.
| Aspect | FIR (S.173 BNSS) | Private Complaint (S.200 BNSS) |
|---|---|---|
| Filed With | Police (SHO of Police Station) | Magistrate (usually JMFC/MM) |
| Offence Type | Cognizable offences only | Both cognizable and non-cognizable |
| Investigation | Police investigates | Magistrate may order police investigation or inquiry |
| Arrest Power | Police can arrest without warrant | Bailable warrant after process issued |
| Use in Cyber Crime | Most cyber offences (IT Act, BNS fraud/cheating) | Defamation (BNS S.356), when FIR refused |
| Timeline | Immediate investigation | Process after Magistrate examines complaint |
1. Criminal Defamation: BNS S.356 defamation is non-cognizable — private complaint only route.
2. Police Refuses FIR: If police won't register FIR despite cognizable offence, file complaint before Magistrate who can direct FIR registration.
3. Cross-Complaint Strategy: When accused in one case wants to file counter-case, private complaint avoids delay of FIR route.
4. Quicker Process Sometimes: In some jurisdictions, Magistrate complaint proceeds faster than overburdened police investigation.
Essential Elements of Cyber Crime FIR
Every effective cyber crime FIR must contain these elements to trigger proper investigation:
- Full name, parentage, age, occupation
- Complete address with PIN code
- Mobile number and email address
- Relationship to victim (if filing on behalf)
- Authority to file (for corporate complaints — board resolution/authorization)
- Name and known details
- Phone numbers, email IDs, social media handles
- UPI IDs, bank account numbers (for financial fraud)
- IP addresses, device identifiers (if available)
- If unknown: "Unknown persons operating under [handle/ID]"
- Date and time of incident (or discovery)
- Exact sequence of events — chronological narrative
- Mode of commission (phishing link, fake app, direct hacking, etc.)
- Platform/medium used (WhatsApp, email, website, app name)
- Technical details: URLs, phone numbers, account details
- Financial loss — exact amount with transaction details
- Data compromised — type and sensitivity
- Reputational harm — nature and extent
- Emotional/psychological impact (for harassment cases)
- Business disruption — quantifiable impact
- IT Act sections (S.43, 66, 66C, 66D, 67, etc.)
- BNS sections (S.318 cheating, S.319 fraud, S.356 defamation)
- Special laws if applicable (POCSO, Copyright Act)
- Note: Include all potentially applicable sections
- Screenshots (with URL visible, timestamp)
- Bank/UPI transaction records
- Call records/SMS logs
- Email printouts with headers
- Social media posts/messages
- Any communication with accused
- Registration of FIR under specific sections
- Investigation and arrest of accused
- Seizure of devices/accounts
- Preservation notices to intermediaries
- Recovery of stolen money/data
Section Mapping for Common Cyber Crimes
Correct section selection determines: investigation scope, arrest powers, bail provisions, punishment range, and limitation period. Wrong sections can lead to discharge or quashing.
Pro Tip: Include all potentially applicable sections. Investigation can always drop inapplicable sections, but adding new sections later is procedurally complex.
| Crime Type | IT Act Sections | BNS Sections |
|---|---|---|
| Hacking/Unauthorized Access | S.43 (damage) + S.66 (hacking) | S.329 (criminal trespass) if physical + digital |
| Data Theft | S.43 + S.66 + S.72 (breach of confidentiality) | S.303 (theft), S.316 (criminal breach of trust) |
| Identity Theft | S.66C (identity theft) | S.319 (cheating by personation) |
| Phishing/Online Fraud | S.66D (cheating by personation using computer) | S.318 (cheating), S.319, S.336 (forgery) |
| Cyber Stalking | S.67 (if obscene content) | S.78 (stalking), S.351 (criminal intimidation) |
| Morphed Images | S.67/67A/67B (obscenity) | S.79 (word/gesture to insult woman), S.356 (defamation) |
| Online Defamation | — | S.356 (defamation) — non-cognizable |
| Ransomware | S.43 + S.66 + S.66F (cyber terrorism if critical) | S.308 (extortion), S.351 (criminal intimidation) |
| Banking Fraud | S.66C + S.66D | S.318, S.319, S.316 |
| CSAM (Child Abuse Material) | S.67B (child pornography) | POCSO Act provisions |
Most cyber crimes require combination of IT Act + BNS sections:
IT Act: Addresses the "cyber" aspect — unauthorized access, digital medium, computer manipulation
BNS: Addresses the traditional crime — cheating, theft, extortion, defamation
Example (Phishing Attack): S.43 + S.66 IT Act (unauthorized access, hacking) + S.66C (identity theft) + S.66D (cheating by personation) + BNS S.318 (cheating) + S.319 (cheating by personation)
Model FIR Templates
1. On [Date] at approximately [Time], I received a call/message from mobile number [Number] claiming to be from [Bank/Platform/Authority claimed].
2. The caller falsely represented that [false claim — KYC update required/reward pending/account blocked, etc.]
3. Under this false pretense, I was induced to [share OTP/click link/install app/transfer money]
4. As a result, an unauthorized transaction of Rs. [Amount in figures] (Rupees [Amount in words]) was made from my account.
5. Transaction Details:
- Date: [Transaction date]
- Amount: Rs. [Amount]
- Transaction ID/Reference: [ID]
- Debited from: [My Bank Name, A/c No.]
- Credited to: [Beneficiary UPI ID/Account if known]
6. Immediately upon realizing the fraud, I called 1930 cyber crime helpline and reported the incident. Complaint number: [1930 complaint number if any]
- Section 66C of IT Act, 2000 (Identity Theft)
- Section 66D of IT Act, 2000 (Cheating by personation using computer resource)
- Section 318 of BNS (Cheating)
- Section 319 of BNS (Cheating by personation)
- Section 61(2) read with Section 3 of BNS (Criminal conspiracy)
2. Screenshot of call log/message
3. Screenshot of UPI transaction
4. 1930 complaint acknowledgment (if any)
5. Any other communication with accused
1. Trace and arrest the accused persons
2. Freeze the beneficiary account(s)
3. Recover the defrauded amount
4. Seize electronic devices used in the crime
Date: [Date]
Signature of Complainant
[Name]
1. Be Chronological: Narrate events in sequence — helps police understand modus operandi.
2. Be Specific: Include exact dates, times, amounts, phone numbers, transaction IDs.
3. Be Technical: Include URLs, IP addresses, IMEI numbers, UPI IDs — these are investigation starting points.
4. Be Complete: Include all sections that might apply — can be reduced during investigation, hard to add later.
5. Annex Evidence: Attach everything you have — screenshots, statements, communications.
Common FIR Drafting Mistakes
1. Vague Description: "I was cheated online" — doesn't trigger specific investigation. Be detailed about what happened, how, when.
2. Missing Technical Details: Not mentioning phone numbers, UPI IDs, URLs — police has no starting point for investigation.
3. Wrong Sections: Filing under non-cognizable sections (like S.500 IPC defamation) when cognizable sections apply — loses arrest power.
4. Delayed Filing: Filing months after incident without explanation — raises credibility issues and evidence may be lost.
5. No Evidence Annexures: FIR without supporting documents — police may not take it seriously.
6. Contradictory Statements: Facts in FIR contradict later statements — destroys complainant credibility.
7. Over-Inclusion: Adding persons as accused without basis — can lead to malicious prosecution liability.
8. Missing Prayer: Not specifying what relief is sought — unclear what investigation should achieve.
Before submitting FIR, verify:
☑️ All dates and times are accurate and consistent
☑️ Transaction amounts match bank records exactly
☑️ All phone numbers, IDs are correctly typed
☑️ Screenshots are clear and show relevant information
☑️ Sections cover all aspects of the offence
☑️ Evidence annexures are numbered and referenced
☑️ Prayer specifically mentions investigation/arrest/recovery
☑️ Complainant has signed all pages
🎯 Key Takeaways — Part 4.2
- FIR (BNSS S.173) is for cognizable offences; Private Complaint (S.200) for non-cognizable or when FIR refused
- 7 essential FIR elements: complainant details, accused details, incident description, loss suffered, sections of law, evidence annexed, prayer
- Most cyber crimes need IT Act + BNS combination — IT Act for cyber aspect, BNS for traditional crime
- Include all potentially applicable sections — easier to drop than add later
- Be specific: exact dates, times, amounts, phone numbers, transaction IDs, URLs
- Always annex evidence: screenshots, bank statements, call logs, communications
- Call 1930 first for financial frauds — include complaint number in FIR
- Common mistakes: vague description, missing technical details, wrong sections, no evidence
- For defamation (BNS S.356) — non-cognizable, must use private complaint route
- Keep copy of FIR with acknowledgment — essential for all future proceedings