Pedagogical Documentation: What It Is, Real Examples, and How to Make It Part of Your Week

Walk into almost any licensed centre in Ontario and you'll find a documentation board. Photos of children at the water table. A few printed captions. Maybe a quote from a child in a speech bubble.
Now ask the educator who made it: "What did you learn about these children from this, and what did you change because of it?"
If the answer comes easily, that board is pedagogical documentation. If it doesn't, it's a display. Both can look identical from the hallway. The difference is entirely in the thinking behind it.
This guide is about that difference, and about how to make the thinking part fit into a week that's already full.
What Is Pedagogical Documentation?
Definition: Pedagogical documentation is the process of observing, recording, and interpreting children's experiences in order to understand how they think and learn, and then using that understanding to plan, reflect, and share with children, families, and colleagues. In Ontario, it is described in How Does Learning Happen? (HDLH), the province's pedagogy for the early years, as "more than recording events," and "a means to learning about how children think and learn."
HDLH describes several things pedagogical documentation does:
It's "a way of listening to children, helping us to learn about children during the course of their experiences."
It makes "children's learning and understanding of the world around them visible to the children themselves."
It moves "beyond simply an objective reporting of children's behaviour" to help educators find meaning.
It's "a process for educators to co-plan with children and with families."
It's "a means of sharing perspectives with parents and colleagues."
Put simply: an observation records what happened. Pedagogical documentation asks what it means and what you'll do next.
Observation vs. Documentation vs. Pedagogical Documentation
These three words get used interchangeably. They shouldn't be.
What it isExampleWhat's missingObservationNoticing and recording what a child did or said"Aiden stacked six blocks, knocked them down, and laughed."Meaning and next stepsDocumentationKeeping a record (notes, photos, work samples)A photo of the tower with the caption "Aiden built a tower!"Interpretation and responsePedagogical documentationRecording, interpreting, and acting on what you saw, often with children and families"Aiden repeated build-and-crash five times, predicting out loud when it would fall. He's testing cause and effect and balance. Tomorrow we'll add ramps and different-sized blocks, and ask his dad what he builds at home."Nothing. This one closes the loop.
If you're working on the first column (writing a clear, specific observation), start with our guide on how to write a developmental observation. This post picks up where that one ends.
The Four Moves of Pedagogical Documentation
Different frameworks describe the cycle differently. In practice, it comes down to four moves. You don't need to do all four in the moment, but you do need to get to all four eventually.
1. Notice. Something catches your attention: a question, a repeated behaviour, a new skill, a struggle. HDLH's view of children as "competent, capable of complex thinking, curious, and rich in potential" is the reason it's worth noticing.
2. Record. Write what you actually saw and heard, as specifically as you can. Direct quotes, actions, duration, who was involved. A photo or work sample can help, but it isn't required.
3. Interpret. Ask what this tells you. What is the child working on? Where does it sit on ELECT's continuum of development? Which of HDLH's four foundations (Belonging, Well-Being, Engagement, Expression) does it touch? What else might be going on? This is where a colleague's view or a family's view adds the most.
4. Respond and share. Change something: the environment, the materials, your interactions, next week's plan. Then share it. With the child ("I noticed you..."), with the family, with your team.
The fourth move is what makes documentation pedagogical. Without it, you have a very good record of a moment that didn't change anything.
Five Pedagogical Documentation Examples
These are illustrative examples written to show the full cycle across different ages and situations. Names are invented. Use them as models for structure, not as scripts.
Example 1: Infant (10 months), Expression and Belonging
Record: "During bottle time, Leila turned her head away from Sam (relief educator) three times and arched her back. When Priya (primary educator) came over and sat in the same chair, Leila relaxed, made eye contact, and fed for 8 minutes."
Interpret: Leila is communicating clearly about who she feels safe with. This is expression without words, and it tells us her attachment to her primary caregiver is strong. Belonging for an infant looks like consistent, responsive relationships.
Respond and share: Keep Priya as Leila's feeding caregiver where possible. When relief staff are needed, have them spend time near Leila during play first. Shared with Leila's mother at pickup: "Leila is really clear about who she's comfortable with. That's a healthy sign of a secure bond. We're making sure she has consistent people around her at feeding times."
Example 2: Toddler (2 years), Engagement
Record: "Over three mornings, Mateo spent 15 to 20 minutes at the sink filling cups and pouring water from one to the other. On the third day he lined up four cups by size and poured from largest to smallest, watching the overflow. Said 'too much!' each time it spilled."
Interpret: Mateo is exploring volume, quantity, and cause and effect, and he's starting to organize materials by size. "Too much!" shows he's predicting and labelling the outcome. He's deeply engaged and returning to the same inquiry over several days.
Respond and share: Move water exploration to the sensory table with funnels, measuring cups, and containers of different sizes. Add towels within his reach so he can manage the spills himself (supporting well-being and independence). Shared on the room's documentation board with photos of the cup lineup and the question "How much is too much?" Families were asked: "Does your child pour or fill things at home? Tell us what they like to fill."
Example 3: Preschool (4 years), Well-Being
Record: "At transition to outdoor time, Zara hid under the table for the third day this week. When an educator crouched down and said 'It's loud when everyone gets their coats at once,' Zara nodded. When offered to go first with one educator before the group, she came out and dressed herself."
Interpret: The transition itself, not going outside, seems to be the trigger. Noise and crowding at the cubbies appear to overwhelm her. She regulates well when the environment changes and her feeling is named. This is about self-regulation and well-being, not defiance.
Respond and share: Offer Zara (and any other child who wants it) a "first group" option for coats. Look at the whole room's transition: could the group be staggered? Shared with Zara's family in a private message focused on what's working, not on the hiding. For help wording messages like this, see our guide on writing a professional message to a parent about a difficult situation.
Example 4: Group (preschool room), Engagement and Expression
Record: "After a rainstorm, six children gathered around worms on the path. Questions recorded: 'Why do they come out when it rains?' 'Do they have eyes?' 'Where's his mom?' Jonah said, 'They're scared of drowning so they come up.' Two children wanted to bring them inside."
Interpret: The group has a shared inquiry. Children are forming theories (Jonah's drowning theory is a genuine hypothesis), asking questions, and expressing care for living things. This is a strong interest to follow for more than one day.
Respond and share: Add books on worms and soil, a magnifying station, and a "worm watch" spot outdoors where children can check daily. Revisit children's theories with them: "Jonah thinks they come up so they don't drown. What do you think?" Documentation panel at child height shows the children's questions in their own words, so they can see their thinking and add to it.
Example 5: Family-contributed (preschool, 3 years), Belonging
Record: "Amir's father shared that Amir has been 'cooking' at home using his grandmother's pots and talking about making rice like Grandma. In the dramatic play centre this week, Amir set the table for 'my family' and told a peer, 'You have to wait, the rice takes long time.'"
Interpret: Amir's play at the centre is drawing directly on family experiences and relationships. The family's insight helped us understand what we were seeing. This shows belonging (connection to family and culture) and expression (representing his world through pretend play).
Respond and share: Invite Amir's family to share a family recipe or photos of cooking at home. Add pots, utensils, and play foods that reflect the families in the room. Shared back with Amir's father: "Thank you for telling us about cooking with Grandma. We saw it in his play right away, and we'd love to bring more of it into the room."
This last example is the one most centres skip. HDLH notes the value of inviting families "to contribute to the documentation and share their own interpretations." Some of your best documentation will start with something a parent tells you at the door.
Common Formats: Learning Stories, Panels, Pedagogical Narration, and More
Pedagogical documentation isn't one format. These are the ones Ontario educators use most, and the names you'll see when you search.
Anecdotal observation (anecdotal record): A short, factual, dated account of a specific event. It's usually the raw material for documentation, not the finished product. On its own it covers the "record" step.
Running record: A detailed, continuous record of everything a child does over a set period (often 10 to 20 minutes). Useful for understanding a pattern or a concern in depth. Time-consuming, so use it selectively.
Learning stories: A narrative format that comes from New Zealand early childhood practice. Written to the child or family in warm, plain language, it usually includes what happened, what it means for the child's learning, and what might come next. Families tend to love them because they read like a story about their child, not a report.
Documentation panels: Visual displays (photos, children's words, work samples, educator interpretation) posted where children and families can see them. They make group inquiries visible. The interpretation is what makes them pedagogical. Without it, they're decoration.
Pedagogical narration: A term used mostly in British Columbia's early learning framework, describing a very similar process of documenting, reflecting on, and sharing children's learning. If you're searching for examples of pedagogical narration, the examples above apply. The process is closely aligned with how Ontario describes pedagogical documentation.
Individual portfolios: A collection of a child's documentation over time, often shared with families at intervals. Most useful when they show progression, not just a scrapbook of moments.
Digital logs: Dated observations and interpretations kept in software rather than binders. The advantage is search, consistency, and being able to see which children haven't been observed recently.
There's no single "right" format. What matters is that each piece gets through all four moves.
How to Make Pedagogical Documentation Sustainable in a Real Week
Every educator agrees documentation matters. The problem is time. Here's what actually helps.
Set a cadence, not an aspiration. "Document every child often" doesn't work. A specific, attendance-based number does. Many centres set an internal target based on how many days a child attends (for example, a few observations a month for part-time children, more for full-time). Root Skills uses 2 per month for 2-day and 3-day schedules and 4 per month for 5-day schedules, and shows who's met, partial, or behind.
Record in the moment, interpret later. Jot a few words in the moment ("Mateo, cups by size, 'too much!'"). Do the interpretation during nap or planning time, when you can think.
Interpret as a team. Ten minutes at a staff meeting, with each educator bringing one piece of documentation, does more than an hour of solo writing. Colleagues see things you don't.
Let documentation drive the plan. If next week's plan isn't influenced by this week's documentation, the cycle is broken. See how to plan an ELECT-aligned program from observations.
Protect children's privacy. Follow your centre's consent policy for photos, and think about where documentation is posted. Group panels in the room are different from an individual child's developmental concern, which belongs in a private conversation or file, not on a wall.
Make sure quiet children are seen. The children who are loud, struggling, or delightful get documented most. A simple tracker that shows who hasn't been observed in a while is the easiest fix for this.
Why This Matters for Your Program Statement
Under Section 46 of Ontario Regulation 137/15, every licensed centre's program statement has to be consistent with the Minister's policy statement on programming and pedagogy, which names HDLH. Among the approaches the program statement must describe is documenting and reviewing the impact of your program's strategies on children and their families.
Pedagogical documentation is how you actually do that. It's the evidence that your program statement isn't just words on a page. For a full walkthrough of HDLH and how it connects to your program statement, see our guide to How Does Learning Happen and the four foundations.
Where Root Skills Fits
Root Skills is built around the same four moves.
Notice and record: Log quick, dated observations per child. The monthly tracker shows each child's status against their observation target so no one slips through.
Interpret: Quick Guide takes one line about what you saw, plus the ELECT domain and age group, and gives back a developmentally grounded interpretation of what's happening. It's a starting point for your own thinking, not a replacement for it.
Respond: Quick Guide also suggests one or two concrete classroom actions, and your observations feed directly into the Weekly Plan, so next week's program responds to what children showed you this week.
Share: Quick Guide drafts a warm, plain-language message you can send the family the same day. Observations also roll up into ELECT-referenced portfolio notes per child.
See a child's behaviour, write one line, and get back something you can use in the classroom by lunch and send to the parent by pickup.
Try Root Skills free for 14 days, no credit card required. Start your free trial at rootskills.ca
Frequently Asked Questions
What is pedagogical documentation in early childhood education? Pedagogical documentation is the process of observing, recording, and interpreting children's experiences to understand how they think and learn, then using that understanding to plan and to share with children, families, and colleagues. Ontario's How Does Learning Happen? describes it as "more than recording events" and "a means to learning about how children think and learn."
What is the difference between observation and pedagogical documentation? An observation records what a child did or said. Pedagogical documentation goes further: it interprets what the observation means for the child's learning, leads to a change in the program, and is shared with children, families, or colleagues.
What are some examples of pedagogical documentation? Common examples include learning stories, documentation panels showing a group inquiry with children's own words, individual portfolios that show progression over time, and dated observations with an educator's interpretation and planned next steps. See the five worked examples above for the full cycle in action.
Is pedagogical documentation required in Ontario? Ontario licensed child care programs must have a program statement consistent with the Minister's policy statement on programming and pedagogy, which names How Does Learning Happen?. HDLH lists pedagogical documentation among its pedagogical approaches, and the program statement must describe how the program documents and reviews the impact of its strategies on children and families.
What is pedagogical narration? Pedagogical narration is the term used mainly in British Columbia's early learning framework for the process of documenting, reflecting on, and sharing children's learning. It is closely aligned with what Ontario calls pedagogical documentation.
What is a learning story? A learning story is a narrative form of documentation that originated in New Zealand early childhood practice. It describes a moment in warm, plain language, explains what it shows about the child's learning, and suggests what might come next. It's often written to the child or family.
Can photos alone count as pedagogical documentation? Not on their own. A photo is a record. It becomes pedagogical documentation when it's paired with interpretation (what it shows about the child's thinking) and leads to a response or a conversation.
The Bottom Line
The documentation board in the hallway isn't the point. The thinking behind it is. Notice, record, interpret, respond. When all four happen, you understand children better, your program fits them better, and families see their child the way you do.
Start small: one child, one moment, all four moves, this week.
Sources: Ontario Ministry of Education, How Does Learning Happen? Ontario's Pedagogy for the Early Years (2014; PDF), pp. 16 and 22 to 23 on pedagogical documentation; Child Care and Early Years Act, 2014 and Ontario Regulation 137/15, Section 46 (program statement). Worked examples in this post are illustrative and use invented names.