Quick Reference: BNSS Timelines for Mobile Forensics

• 60 days — bail clock for offences punishable up to 10 years (Section 187(3))

• 90 days — bail clock for offences punishable with death, life imprisonment, or 10+ years (Section 187(3))

• 40 / 60 days — outer limit for police custody requests within the larger window (Section 187(2))

• 2 months — investigation cap for specified sexual offences under BNS Section 64–71 and POCSO Section 4, 6, 8, 10 (Section 193(2))

• 48 hours — maximum time from forensic sample collection to FSL receipt, drawing from the Section 51 medical/DNA framework (Section 193)

• State-notified — forensic expert at scene plus videography for offences carrying 7+ years, where the state has notified the provision (Section 176(3))

• Mandatory — sequence of custody for electronic devices in the final report (Section 193(3)(i))

• Mandatory — Section 63(4)(c) BSA certificate for electronic evidence in court

  
  

The way most lab heads I know absorbed the new criminal codes was in two passes. First pass: read the headlines, note that BNS replaces IPC, BNSS replaces CrPC, BSA replaces the Evidence Act, move on. Second pass, which happened months later and usually after a trial court reminded somebody, was a much closer reading. That second pass is where the surprises live, and most of them are about timelines.

For mobile forensics, the surprises are concentrated in three sections of BNSS. None mentions mobile forensics by name, which is part of why labs missed them on first reading.

The 60/90 Day Clock — Section 187 and Section 193

Under the old CrPC, Section 167 set a 60 or 90 day cap on how long an arrested person could be held without a chargesheet, depending on whether the offence carried up to ten years or longer. BNSS Section 187 retains that custody framework with one wrinkle worth knowing. Police custody can now be requested intermittently within the first 40 days for offences punishable up to ten years, or the first 60 days for offences carrying death, life, or ten or more years, instead of only within the first 15 days as under Section 167.

Section 193, the BNSS counterpart to the old Section 173, does not itself set the 60/90 day investigation deadline most lawyers cite. Section 193(1) only says investigation shall be completed "without unnecessary delay." The 60/90 day clock everyone refers to actually lives in Section 187(3), and the Karnataka High Court has held expressly that the investigation-deadline reading "belongs exclusively to Section 187." What Section 193 does add is a hard two-month investigation cap for specified sexual offences against women and children: BNS Section 64 to 71 (the rape and aggravated-sex-offence chapter) and POCSO Section 4, 6, 8 and 10, measured from the date the information was recorded.

In practice, Section 187 sets the bail clock and Section 193 sets the procedural discipline. Together they create the 60/90 day pressure on the investigation that mobile forensics now has to fit inside. The Madras High Court, Madurai Bench, in December 2025 issued directions requiring strict adherence to Section 193 timelines, including written reasons in the case diary for any delay. Other state high courts have signalled they will follow.

For an investigating officer working a chargesheet that depends on mobile evidence, the math is uncomfortable. A typical Indian phone, full of modern apps, takes anywhere from a few hours to a few days to acquire properly. Decoding what came off the phone — UPI traffic, regional messaging apps, deleted artifacts, locally cached app data — adds more days. Writing a defensible report that survives Section 63 BSA scrutiny adds more.

By the time the IO is at the seizure point, the 90-day clock is already running. Whatever happens with the phone after that — courier, queue, parser, report — happens inside that window.

The 48-Hour Sample Rule — Section 193

Section 193 contains a quieter line that lab heads have started flagging in internal SOPs.

Forensic samples must reach the concerned forensic science laboratory with dispatch, and in any case not later than 48 hours from the time of collection.

This is one sentence in the bare act, drawing its language from the Section 51 medical-examination and DNA-sample framework. Operationally, it is an SOP rewrite for every regional police station that sits more than a half-day's drive from the nearest FSL. It also raises a question about mobile devices specifically that the section does not answer cleanly: is a seized phone a "forensic sample" in the Section 193 sense, or does the 48-hour clock apply only to biological and physical traces?

Most lab heads have started reading it inclusively. If a phone is being sent for forensic examination, they want the chain-of-custody record to show transit within 48 hours, even if formal extraction will not begin for a week. The reasoning is simple. If defence counsel wants to attack the integrity of the evidence at trial, the easiest line of attack is the gap between seizure and lab receipt. Closing that gap is cheap insurance.

Practically, that means a regional unit needs a courier path, a documented hand-off, and a receiving officer at the lab who can sign and timestamp on arrival. If your tier-2 unit still sends phones to the state FSL whenever someone happens to be driving down that week, that practice has a shelf life now. Defence counsel will get to the gap before you do.

Forensic Expert at the Scene — Section 176(3)

Section 176(3) is the headline change for forensic capacity in India. For any offence punishable with imprisonment of seven years or more, the officer in charge of the police station must cause a forensic expert to visit the crime scene to collect forensic evidence. The collection process must be videographed on a mobile phone or another electronic device.

The bare act gives state governments up to five years to notify Section 176(3) into force in their jurisdictions. Some states have already notified; others have not, citing lab capacity. Either way, lab heads should plan as though Section 176(3) will be operative in their state inside this window. Designing SOPs now is cheaper than rewriting them after a notification lands.

There is a capacity problem, and a tooling problem, and the capacity one gets all the attention. India has 7 Central Forensic Science Laboratories under DFSS, with an 8th approved at Samba, about 32 State FSLs, and roughly 97 Regional FSLs as of late 2024, against several thousand police stations falling under Section 176(3). The arithmetic is not subtle. Most states are now discussing field forensic units, mobile forensic vans, or partner arrangements with private labs. That is a state-government conversation, not a tooling one.

The tooling side gets less airtime, and it is the one defence counsel will reach first. The Section 176(3) videography is not loose footage. To survive a Section 63 BSA challenge, it has to be acquired in a way that supports a hash, a timestamp trail, and a custody record. The phone the Section 176(3) video is shot on is itself an evidentiary device for the duration of that recording. Was it hashed? Was it preserved? Was the shot edited?

If your forensic expert is shooting Section 176(3) video on a personal phone with no preservation discipline, you have just generated evidence with a Section 63(4)(c) BSA certificate problem.

Sequence of Custody for Electronic Devices

Section 193 contains another line worth noting, because it codifies something most labs were doing informally and now must do in writing.

The final report submitted to the Magistrate must include the sequence of custody in cases involving electronic devices, and similar discipline applies to DNA evidence under the connected provisions.

Sequence of custody is not a dated chain-of-custody form on top of an envelope. It is a narrative trail: who handled the device, when it was sealed, when it was opened, who hashed it, what tool version was used, what the post-acquisition hash was, who carried the report. Every Magistrate now sees this as part of the chargesheet bundle.

In practice, the labs that do this well have already shifted to digital chain-of-custody systems where every action against an exhibit is logged with a user identity, a timestamp, and a hash. The labs working off paper forms and handwritten registers will find Section 193 a slow grind, especially when the chargesheet bundle expands and the Magistrate starts asking specific questions about gaps in the timeline.

What This Adds Up To

A senior Indian IO running a seven-years-plus offence today is being asked to:

1. Get a forensic expert to the scene with videography, with the videography itself being defensible evidence (Section 176(3), in a notified state).

2. Move the device into the custody chain and into lab transit within 48 hours (Section 193).

3. Acquire and decode the device in time to feed a 90-day chargesheet (Section 187, Section 193(1)), even when the phone is full of regional apps the lab's parser stack has not seen yet.

4. Reproduce the entire custody narrative in writing inside the chargesheet (Section 193(3)(i)).

For a single high-priority case, all of this is doable with a focused team. The challenge for FSLs and state police is what happens when fifty cases of this profile are running concurrently across a state, and the lab queue is already two months deep before anything new lands.

Mobile forensic tooling cannot solve the capacity problem on its own, but it determines a large fraction of the answer. What tooling can actually move is acquisition time, decode coverage on regional apps, and how fast a new parser ships when a lab opens a phone with something the tool does not know yet. Each of these now has a date attached: the chargesheet date, the 48-hour dispatch line, the bail clock at 60 or 90 days.

For a long time, mobile forensics speed was the thing a vendor pitched and a lab head quietly accepted whatever the existing tool gave them. After BNSS, speed is not a feature. It is a compliance dimension. The labs that adjust their workflow and tool selection to that early will have an easier two years than the ones still treating acquisition time as a nice-to-have.

The 60-day clock has always existed for the accused. It now also exists for the investigation.

Secfore builds mobile forensic tooling in India for Indian investigation timelines. If you are rewriting your FSL's BNSS-aligned SOPs and want to compare notes on acquisition latency, decode coverage, or chain-of-custody logging, write to us. We would rather have the conversation early than after the chargesheet date.