Of all the procedural promises the Protection of Children from Sexual Offences Act, 2012 makes to a child victim, none is as concrete — or as routinely breached — as Section 35. It commands that the child's evidence be recorded within thirty days of the Special Court taking cognizance, and that the trial itself be wrapped up, as far as possible, within one year. Behind these two numbers lies a settled legislative anxiety: that a young witness's memory fades, that repeated court visits re-traumatise, and that justice delayed in a child sexual abuse case is very often justice defeated. This chapter unpacks the text of Section 35, the difference between its two limbs, the consequences (and non-consequences) of breaching the deadlines, and the rich body of High Court and Supreme Court authority that has grown around it.

The bare provision: what Section 35 actually says

Section 35 of the POCSO Act, captioned "Period for recording of evidence of child and disposal of case", has two sub-sections. Sub-section (1) provides that the evidence of the child shall be recorded within a period of thirty days of the Special Court taking cognizance of the offence, and that reasons for delay, if any, shall be recorded by the Special Court. Sub-section (2) provides that the Special Court shall complete the trial, as far as possible, within a period of one year from the date of taking cognizance of the offence.

Two textual features deserve immediate notice. First, the trigger for both clocks is not the date of the FIR, nor the date of the chargesheet, but the date the Special Court takes cognizance — a precise judicial act under the Code of Criminal Procedure (now the BNSS). Second, the two limbs are worded differently in their stringency: sub-section (1) carries an apparently unconditional "shall … within thirty days," softened only by the duty to record reasons for delay, whereas sub-section (2) is expressly qualified by the phrase "as far as possible." That drafting asymmetry has driven most of the litigation on whether Section 35 is mandatory or directory, examined below.

Section 35 does not stand alone. It is the timekeeping companion to the child-friendly trial machinery in Section 33 and the protective safeguards of Sections 36 and 37, and it must be read with the definitions in the definitions chapter — particularly the meaning of "child" and "Special Court."

Two clocks, not one: the 30-day and the one-year limbs distinguished

It is a common examination error to conflate the two sub-sections. They protect different interests and run for different durations. Sub-section (1) is about the child's testimony: the law wants the deposition captured while the memory is fresh and before the child is exposed to the wear of repeated adjournments. Sub-section (2) is about overall disposal: it sets an outer limit of one year for the entire trial, recognising that examination of other witnesses, forensic evidence and arguments will take time.

The practical consequence is that a Special Court can be in full compliance with one limb and breach of the other. A court that records the victim's evidence on day twenty but takes eighteen months to deliver judgment has honoured sub-section (1) and breached sub-section (2). Conversely — though rarer — a court could conclude the trial within a year while still having recorded the child's evidence on, say, day fifty. The thirty-day limb is the sharper of the two precisely because the harm it guards against, memory decay and tutoring, is irreversible once it sets in.

The Bombay High Court drew this distinction out vividly in Atul Gorakhnath Ambale v. State of Maharashtra (2022 SCC OnLine Bom 873), where Mohite Dere, J. stressed that "the younger the child/victim, the earlier the recording" of evidence must be, and that strict adherence to sub-section (1) is non-negotiable in spirit even if the one-year disposal target proves elastic in practice.

When does the clock start? Cognizance, not chargesheet

Because both deadlines run from "the date of taking cognizance," identifying that date is the first analytical step. Cognizance is the moment a Magistrate or Special Court applies its judicial mind to the offence on a police report or complaint — it is an act of the court, distinct from registration of the FIR or filing of the chargesheet by the police. The thirty days therefore do not begin to run while the investigation is ongoing; they begin only once the matter is judicially seised.

This has an important corollary. Delays in investigation, in filing the chargesheet, or in obtaining forensic and medical reports do not, by themselves, eat into the Section 35(1) window, because that window has not yet opened. The pre-cognizance phase is governed instead by the investigation and chargesheet timelines, and by the default-bail jurisprudence under Section 167 CrPC / Section 187 BNSS — a regime entirely separate from Section 35. Conflating the two is a frequent source of error, and as we will see, courts have firmly held that a breach of Section 35 is not a route to statutory default bail.

It also means the Special Court's own diligence is what Section 35 polices. Once cognizance is taken, the responsibility for honouring the thirty-day limb rests squarely on the trial court's listing and case-management, not on the prosecution's investigative pace.

The object behind the deadline: protecting memory and dignity

The rationale for Section 35 is not mere docket-management. Courts have repeatedly located its object in child welfare. The purpose, as the Karnataka High Court put it in Hanumantha Mogaveera v. State of Karnataka, is to ensure that the victim child is "secured from the trauma of the trial at the earliest, so that she or he could be rehabilitated and reintegrated into society at the earliest." Speed here is therapeutic, not merely administrative.

There is also an evidentiary dimension. A child's recollection is more fragile and more suggestible than an adult's, and the longer the gap between the incident and the deposition, the greater the risk both of genuine forgetting and of tutoring by interested adults. The Supreme Court's caution in State of M.P. v. Ramesh, (2011) 4 SCC 786 — that a child witness is "susceptible to tutoring" and the evidence must be scrutinised with care — is the flip side of the same coin: the sooner the evidence is recorded, the less time there is for the testimony to be contaminated. Section 35(1) is thus simultaneously a shield for the child and a safeguard for the integrity of the record.

This protective logic connects Section 35 to the gravity of the underlying offences it serves — the penetrative sexual assault and aggravated penetrative sexual assault provisions — where the stakes for both child and accused are at their highest and a reliable, early record matters most.

Mandatory or directory? The central interpretive question

The most litigated question on Section 35 is whether its time limits are mandatory (so that breach produces some legal consequence) or merely directory (so that breach is an irregularity to be explained but not penalised). The settled judicial view leans strongly towards directory, particularly as regards consequences for the accused.

The textual clues point this way. Sub-section (2)'s "as far as possible" is the classic legislative formula for a directory timeline. Sub-section (1), though worded as an unqualified "shall," itself contemplates the possibility of delay by requiring the court to record reasons for delay — a provision that would be incoherent if the thirty-day limit were absolute and breach were fatal. A statute that simultaneously says "do X within thirty days" and "if you don't, write down why" is plainly anticipating, and tolerating, non-compliance in deserving cases.

Courts have therefore treated Section 35 as imposing a strong, justiciable duty of expedition on the Special Court — one whose breach invites administrative scrutiny and judicial direction — rather than a self-executing sanction that automatically benefits the accused or vitiates the trial. The distinction matters enormously in practice, as the next two sections show.

Breach of Section 35 does not entitle the accused to bail

The single most important practical proposition about Section 35 is negative: non-compliance with its time limits does not create a right to bail in the accused. This was authoritatively settled by a larger bench of the Karnataka High Court in Hanumantha Mogaveera v. State of Karnataka (decided in April 2021, with the detailed judgment pronounced in May 2021). The reference arose because a single judge doubted whether an accused became entitled to release if the child's evidence was not recorded within thirty days or the trial not completed within a year.

The larger bench answered emphatically in the negative. It held that if the evidence of the child is not recorded within thirty days, or if the trial is not completed within one year from cognizance, that breach cannot lead to the accused being released on bail. Section 35, being part of a special enactment enacted for the protection of children, must prevail over the general bail provisions of the CrPC where the two are inconsistent. The deadline exists to protect the child, and it would be perverse to convert the State's or the court's failure to meet it into a benefit for the accused.

The court drew a sharp line between Section 35 and the genuine default-bail regime under Section 167(2) CrPC. Default bail is triggered by failure to file a chargesheet within the prescribed investigation period — a pre-cognizance event with an express statutory consequence. Section 35 operates post-cognizance and contains no comparable "and therefore bail" clause. The two simply do not overlap, and a delay in recording the child's evidence is not a default within the meaning of Section 167.

The same bench also clarified that a statement recorded under Section 164 CrPC is not a substitute for, and does not amount to, the recording of the child's evidence under Section 35 — the former is a pre-trial statement, the latter is substantive evidence taken during trial and subject to cross-examination.

Breach does not vitiate the trial or warrant acquittal

If breach of Section 35 does not free the accused on bail, neither does it taint the eventual conviction. An accused cannot argue that because his trial overran the one-year limit, or because the child's evidence was recorded on day forty rather than day thirty, the proceedings stand vitiated and he is entitled to acquittal. Treating the time limits as directory carries this logical consequence: delay is an irregularity to be explained on the record under the "reasons for delay" clause, not an illegality that unravels the trial.

This is consistent with the general principle that procedural time limits framed for the protection of a victim or for the orderly conduct of proceedings are not to be read so as to defeat the very object they serve. To hold otherwise would mean that a Special Court's congestion or an unavoidable adjournment could hand an acquittal to a person facing grave charges of child sexual abuse — an absurd outcome that no court has endorsed. The remedy for delay lies in administrative direction, judicial monitoring and, where warranted, action against the responsible officers, not in the collapse of the prosecution.

What breach does do is shift a burden of explanation onto the court and expose systemic failure to higher-court scrutiny, which is exactly how the supervisory jurisprudence discussed below has developed.

Supreme Court supervision: the "Alarming Rise" proceedings

The most consequential enforcement of POCSO timelines has come not through individual appeals but through the Supreme Court's suo motu writ proceedings titled In Re: Alarming Rise in the Number of Reported Child Rape Incidents, registered in 2019. Treating the chronic under-enforcement of the Act's deadlines as a systemic problem, the Court issued a series of directions designed to give Section 35 real bite.

Among the measures, the Court directed the creation of dedicated POCSO Special Courts — to be set up in every district where more than 100 such cases were pending — funded by the Union, with child-friendly infrastructure, special public prosecutors and support staff, and ordered that these be operationalised within a defined window. It directed that chargesheets be filed within the mandatory investigation period and that trials be completed within the timeframe contemplated by the Act. The thrust of the proceedings was to translate Section 35's paper deadline into institutional capacity, recognising that courts cannot record evidence within thirty days if there are too few courts and too many cases.

These proceedings illustrate the directory-but-enforced character of Section 35: the Court did not pretend the deadline was self-executing, but it refused to let chronic breach become acceptable, instead building the machinery — and the monitoring — to make compliance feasible.

High Court directions: the Bombay template

High Courts exercising supervisory jurisdiction over their subordinate judiciary have issued detailed practice directions to operationalise Section 35. The leading example is Atul Gorakhnath Ambale v. State of Maharashtra (2022 SCC OnLine Bom 873), where the Bombay High Court, while dealing with a bail application, used the occasion to lay down a code of conduct for Special Courts trying POCSO cases.

The directions included: recording the victim's deposition as expeditiously as possible in conformity with Section 35; conducting examination-in-chief and cross-examination preferably on the same day to spare the child repeat appearances; minimising the number of times the child is brought to court; restricting adjournments during the child's examination and recording reasons whenever an adjournment is unavoidable; ensuring child-friendly in-camera proceedings; ensuring the presence of a parent or trusted person under Section 37; and following the Supreme Court's directions in this field. The court emphasised that the younger the victim, the more urgent the recording, lest the passage of time erode the memory of the incident.

The Bombay template demonstrates how Section 35 is enforced in practice — through institutional discipline imposed from above, not through consequences visited on the prosecution from below.

Section 35 cannot be read in isolation from Section 33, which governs the procedure and powers of the Special Court. Section 33(5) directs the Special Court to ensure that the child is not called repeatedly to testify, and Section 33(7) bars aggressive, scandalous, indecent or confusing questioning. Together with Section 35's thirty-day limb, these provisions form an integrated scheme: record the child's evidence early, record it once, and shield the child while doing so.

Courts have enforced the no-repeated-recall principle with vigour. The Kerala High Court, for instance, has held under Section 33(5) that a child witness cannot be recalled to fill up a lacuna or omission in the defence's evidence — the protection against repeated testimony is for the child's benefit and cannot be turned into a tactical tool. The recent insistence by the Delhi High Court that minor victims should not be summoned repeatedly, even for bail hearings, reflects the same protective philosophy radiating outward from Sections 33 and 35.

The practical synthesis is this: an early, single, well-protected recording under Section 35(1), conducted within the Section 33 safeguards, serves the child, the truth-finding function and the accused's fair-trial interest simultaneously.

Why early recording matters: child-witness reliability

The evidentiary case for the thirty-day rule rests on settled law about how courts assess child testimony. In State of M.P. v. Ramesh, (2011) 4 SCC 786, the Supreme Court synthesised the authorities and held that the evidence of a child witness must be evaluated carefully and with caution, because a child is susceptible to tutoring; that the deposition may require corroboration; but that where the testimony inspires the confidence of the court and is free of embellishment, it may be acted upon. The Court added that the trial court's assessment of the child's demeanour and maturity is entitled to deference, an appellate court interfering only where the record shows the child was wrongly treated as reliable.

Every one of these propositions argues for speed. Corroboration is easier to secure while physical and forensic evidence is fresh; the risk of tutoring grows with every passing week; and the trial judge's first-hand impression of the child's demeanour is most valuable when taken before the child has been coached or worn down. Section 35(1) operationalises the evidentiary wisdom of Ramesh by minimising the interval in which contamination can occur. A deposition recorded within thirty days is, all else equal, a more reliable deposition.

Whose evidence, and in which court: scope of the section

Section 35 governs the recording of "the evidence of the child" by "the Special Court." Two scope questions follow. First, the protected witness is the child victim or child witness as defined under the Act — and the meaning of "child" is strictly chronological. In Eera v. State (NCT of Delhi), (2017) 15 SCC 133, the Supreme Court held that "age" in the POCSO Act means biological age, not mental age, declining to extend the Act's child-friendly machinery (including Section 35's timeline) to an adult with the mental age of a child, however sympathetic the facts. The thirty-day protection therefore attaches by reference to biological age below eighteen, as elaborated in the definitions chapter.

Second, the duty falls on the Special Court — the designated court of session trying POCSO offences. Because Section 35 is a feature of the special trial forum, it applies to the full range of offences triable there, from sexual assault through the aggravated forms, and not merely to a sub-set of cases. For the institutional architecture of these courts and the broader scheme, see the introduction to the POCSO Act and the hub at POCSO Act notes.

Practical and examination takeaways

For the judiciary aspirant, Section 35 condenses into a handful of high-yield propositions. First, the two limbs: child's evidence in thirty days (sub-section 1), trial in one year "as far as possible" (sub-section 2), both running from cognizance. Second, the character of the deadlines: directory rather than mandatory, with a duty to record reasons for delay built into the text itself. Third, the consequences of breach: no default bail (Karnataka HC, Hanumantha Mogaveera) and no acquittal or vitiation of trial; the remedy is administrative and supervisory, not a windfall for the accused.

Fourth, the enforcement architecture: Supreme Court monitoring in the Alarming Rise suo motu proceedings, dedicated courts and infrastructure, and High Court practice directions such as those in Atul Gorakhnath Ambale. Fifth, the companion provisions: Section 33(5)'s bar on repeated recall and Section 33(7)'s protective questioning rules, which make a single early recording both possible and humane. Sixth, the evidentiary rationale drawn from State of M.P. v. Ramesh: early recording preserves reliability and reduces the window for tutoring.

Hold those six threads together and the section is fully exam-ready: a child-protective timeline, robust in purpose but flexible in consequence, enforced from the top down rather than weaponised from the defence bench.

Frequently asked questions

From what date does the thirty-day period under Section 35(1) begin to run?

From the date the Special Court takes cognizance of the offence — a judicial act distinct from the FIR or the chargesheet. The thirty days do not run during investigation; they open only once the court is judicially seised of the matter, and the same date triggers the one-year trial limit under Section 35(2).

Is the thirty-day limit in Section 35 mandatory or directory?

It is treated as directory rather than absolute. Sub-section (2) is expressly qualified by "as far as possible," and even sub-section (1) requires the court to record reasons for any delay — a provision that would be meaningless if breach were fatal. Courts therefore read Section 35 as a strong duty of expedition on the Special Court, not a self-executing sanction.

Can an accused get default bail if the child's evidence is not recorded within thirty days?

No. In Hanumantha Mogaveera v. State of Karnataka (2021) a larger bench of the Karnataka High Court held that non-compliance with Section 35's time limits does not entitle the accused to release on bail. Default bail under Section 167(2) CrPC turns on failure to file a chargesheet in the investigation period — a separate, pre-cognizance regime that has no application to Section 35.

Does a delayed trial under Section 35 result in acquittal or vitiate the proceedings?

No. Because the time limits are directory, breach is an irregularity to be explained on the record, not an illegality that unravels the trial. Converting the court's congestion into an acquittal for a person facing grave child-abuse charges would defeat the very object of the provision, so the remedy is administrative direction and judicial monitoring rather than collapse of the prosecution.

Is a statement recorded under Section 164 CrPC the same as recording evidence under Section 35?

No. As clarified in Hanumantha Mogaveera, a Section 164 CrPC statement is a pre-trial statement, whereas Section 35 contemplates the substantive evidence of the child recorded during trial and tested by cross-examination. A Section 164 statement does not satisfy or substitute the Section 35 requirement.

How have the higher courts enforced Section 35 in practice?

Through supervisory action rather than consequences on the accused. The Supreme Court's suo motu proceedings In Re: Alarming Rise in the Number of Reported Child Rape Incidents (2019) directed dedicated POCSO courts and child-friendly infrastructure, and the Bombay High Court in Atul Gorakhnath Ambale v. State of Maharashtra (2022) issued detailed practice directions for expeditious, single-sitting recording of the child's evidence.