Free Resource by Mom's Grove

The 90-Second
Window

How I stopped asking teachers to remember what they saw, and what happened to 8 hours of paperwork when I did.

8 hrs Observation paperwork / week
45 min After one change
35 Teachers. Same school. Same children.
The Story

A Tuesday afternoon in March.

I was walking through the corridor when I saw Meera at her desk. She had just come out of a 20-minute classroom session. Now she was writing. I glanced at the clock. It was 4:47 PM.

At 5:31 PM, she was still writing.

Forty-four minutes of documentation for a twenty-minute observation. I pulled up a chair and asked her what she was doing. She said: "I'm trying to remember what Aryan did when he got the question wrong. I know there was something important. I just can't get it back."

She was reconstructing from memory. Not writing about what she saw. Writing about what she hoped she still remembered.

"The observation was alive for about 90 seconds after she left that classroom. By the time she sat down to write, it was already cold."

I have 35 teachers. Each one doing this. Every day.

The question I kept asking myself was not "why aren't my teachers documenting better?" It was something different. It was: why is documentation always the last thing that happens?

And more importantly: whose fault is that really?

What I Tried First

Three things I tried.
Three things that failed.

Attempt 01
Buy an observation app
Three teachers used it consistently. The rest opened it twice. An app does not solve the problem of when the note happens.
Attempt 02
Build better report templates
A better container does not help if the content inside it is still being reconstructed from a memory that no longer exists.
Attempt 03
Train teachers to write faster
Speed is not the issue. A teacher writing fast 44 minutes after an observation is still writing the wrong version of what they saw.
None of these touched the actual friction point.
The Turning Point
47 Minutes

I started timing the gap. From the moment a teacher left a classroom to the moment they sat down to document what they saw.

The average was 47 minutes. In that time: a parent question, another class, a staff meeting, water, a phone call, a forgotten lunch.

The observation that was alive, detailed, and emotionally present when it happened was a scattered summary by the time it reached paper.

The problem was never the writing. It was the wait.

If the note does not happen in the 90 seconds after the observation, a different note gets written. A reconstructed one. A guessed one.
The Free Resource

The solution was not a new tool.
It was a new moment.

We moved the note from desk to doorway. From memory to voice. The teacher does not write anything. They speak. Twenty seconds. Right after the observation. While the child is still visible in their mind.

Step 2 of 4  •  The Voice Prompt
What your teacher says aloud, immediately after observing
[Child code]. What I noticed: [what the child did or said]. The context was [what was happening in the class at that moment]. One thing I want to remember: [the specific detail that matters].
Part 1
Child Code
Not the child's name. A code. This keeps every observation DPDP-compliant when processed by any AI tool.
Part 2
The Observation
What actually happened. Behavior, response, action. Spoken in the moment, not reconstructed from memory.
Part 3
The Detail
One specific thing worth keeping. This becomes the basis of the end-of-term report for that child.
On privacy: This prompt uses a child code, never a name. The full DPDP-safe coding system, including how to build your school's code sheet, is in the complete guide. Without the code system, this prompt is incomplete.
One Month In

The numbers did not lie.

8-10 hrs
↓
45 min
Observation paperwork per week
3 days
↓
5 min
End-of-term report, per child
Memory
↓
Record
What observations are based on

Same depth. Same quality. Same 35 teachers. No new software. Zero cost.

What You Have vs. What's Left

The prompt is Step 2.
There are 4 steps total.

1
Build your school's child code system
Every child gets a unique code. No names in any AI tool. Stays DPDP-compliant. The guide includes the exact code structure and a ready-to-use school template.
🔒
2
You have this
The Voice Prompt
What the teacher says aloud immediately after observing. Twenty seconds. The note happens in the moment, not from memory.
3
The AI structuring step
Which AI tool we use, how we set it up, the exact instruction we give it, and how a teacher reviews and confirms the structured note in under 60 seconds.
🔒
4
The report that writes itself
How structured observations feed directly into end-of-term reports. The template, the flow, and how 3 full days of report writing became 5 minutes per child.
🔒

The voice prompt alone will not change your numbers. It is one piece of a connected system. Without Step 1 (the code system), the prompt is not privacy-safe. Without Steps 3 and 4, the spoken note remains an audio file. The full system is what creates the 45 minutes. The prompt is what makes the full system feel like nothing.

The Complete Guide

Every step. Every template. Every prompt.

The full 4-step system, including the DPDP child code method, the AI structuring step, and the report template. Immediate download.

Get the Full Guide →

One-time download  •  ₹199  •  topmate.io/adarsh_shaji

Used by Mom's Grove, Bengaluru
Built from 5 years of running a school with 35 teachers.
Every number in this guide is from our own data.