Pedagogical documentation is the practice of recording children's learning through photographs, transcripts of their talk, notes and their own work, and then interpreting and revisiting that record together with colleagues, children and families. It comes from the municipal preschools of Reggio Emilia in Italy. Its purpose is not to prove what children achieved but to make their thinking visible, so that teachers can understand it, respond to it and plan the next step of a project.
Documentation is often confused with the attractive wall displays found in many preschools, or with the files of evidence that schools keep for inspection. It overlaps with both but is something different. This article explains what pedagogical documentation is, where the idea comes from, the steps teachers follow, and how a bilingual preschool can make it work without drowning in photographs. It complements the articles in this category on observation notes and learning stories, which focus on individual children; documentation is often about a group and its shared thinking.
Where the idea comes from
The preschools and infant-toddler centres of Reggio Emilia, a city in northern Italy, grew after the Second World War from a community effort led in large part by the educator Loris Malaguzzi. Over decades their teachers developed a way of working in which careful recording of children's activity became central to teaching itself. Visitors from around the world saw the results in exhibitions such as The Hundred Languages of Children, and the practice spread.
Two later publications shaped how documentation is understood in English. Making Learning Visible: Children as Individual and Group Learners, published in 2001 by Project Zero at the Harvard Graduate School of Education together with Reggio Children, studied how documentation supports group learning. Carlina Rinaldi, a close colleague of Malaguzzi, described the underlying attitude as a pedagogy of listening in In Dialogue with Reggio Emilia. In Beyond Quality in Early Childhood Education and Care, Gunilla Dahlberg, Peter Moss and Alan Pence drew a clear line between pedagogical documentation, which is open and interpretive, and child observation in the narrower sense of measuring children against fixed expectations.
A teacher does not need to work in a Reggio-inspired school to use documentation. Many curricula, including Global Nexus, borrow the practice because it fits project-based learning so well.
Documentation, display and record keeping compared
The three are often mixed up, and much of the frustration teachers feel about documentation comes from treating it as one of the other two.
| Display | Record keeping | Pedagogical documentation | |
|---|---|---|---|
| Main purpose | Make the room attractive and show finished work | Keep evidence of progress for each child | Understand and extend children's thinking |
| Typical content | Finished paintings, decorations | Notes, checklists, samples filed by child | Photographs of process, children's words, drafts, teacher questions |
| When it is made | After the activity | Continuously | During the project, while it is still unfolding |
| Who reads it | Visitors, families | Teachers, leaders | Teachers, children and families, together |
| What happens next | Usually nothing | Feeds reports | Changes what the teacher offers tomorrow |
In practice the same photograph can serve all three. What makes it documentation is what the adults do with it: whether they study it, discuss it, show it to the children and ask what they were thinking, and whether the conversation changes the plan.
The documentation cycle, step by step
Teams describe the cycle in slightly different ways, but most include the same steps. In a busy preschool, the cycle might turn once or twice a week during an active project.
- Start with a question. Before recording anything, the team decides what they want to understand. How are the children explaining why the plants on the windowsill grow faster than those in the corner? A focused question prevents the camera from recording everything and nothing.
- Record the process. Teachers take photographs of children at work, not just of results, write down what children say, collect drafts and failed attempts, and sometimes make short audio recordings of group talk.
- Interpret together. At a team meeting, teachers lay out the material and discuss it. What theories are the children testing? What surprised us? Where do they disagree? Different adults will read the same moment differently, and that disagreement is useful.
- Revisit with the children. Teachers show the children a few photographs or read back their words and ask them to explain. Children often add explanations, correct the teacher or take the project in a new direction.
- Make it public. A panel, a book or a digital story shares the thinking with families and other classes. It shows the path of an idea, not only its end point.
- Plan the next step. The team decides what to offer next: a new material, a provocation, a visit, a question to put to the group.
Steps four and five are the ones most often skipped, and they are what distinguish documentation from simple record keeping. Without revisiting, the children are only subjects of the documentation; with it, they become participants in reflecting on their own learning.
What good documentation looks like
A good documentation panel or book tells the story of an idea. It begins with the question or event that started the project, shows how children's theories developed, includes their words in their own voice, shows the turning points and ends with where the group is now. It contains fewer photographs than people expect and more text than a display, and the text explains rather than decorates.
Children's words are the heart of it. A transcript of four children arguing about whether the moon follows the car is far more revealing than a photograph of them looking out of the window. Teachers who are new to documentation often find that the most valuable skill is simply writing down exactly what children say, without tidying it up.
In a bilingual classroom those words will be in two languages, and sometimes in both at once. Documentation should keep them that way, with translation alongside, so that families who read only one language can follow and so that the panel itself shows bilingual thinking in action.
Good documentation is also honest about failure. A bridge that collapsed three times before it held is a better story than one that worked the first time, and it shows children that mistakes are part of learning rather than something to hide.
Questions that help a team interpret documentation
The interpretation meeting is where documentation either becomes useful or stays a pile of photographs. Teams that work well usually return to a small set of questions, and try to answer them from the evidence on the table rather than from general impressions.
- What were the children trying to find out or do, in their own terms rather than ours?
- What theories or explanations did they offer, and how did those change over the days?
- Where did children disagree, and how did they handle the disagreement?
- What surprised us, and what does the surprise tell us about our own assumptions?
- Which children were most involved, and which were on the edges? What might draw them in?
- Which language did children use for which purpose, and did one language carry ideas the other did not yet carry?
- What is the smallest change we could make tomorrow to push the inquiry further?
The last question keeps the discussion practical. A meeting that produces one well-chosen provocation, for example offering a torch and a cardboard box to children who are arguing about shadows, has done its job. Long meetings that end with no change to the plan are a sign that the team is admiring documentation rather than using it.
Documentation with the youngest children
Documentation is often associated with four- and five-year-olds working on long projects, but it is just as valuable with babies and toddlers. With the youngest children the material is different: fewer words, more photographs of gestures, gaze and movement, and careful notes about how a child explores a basket of objects or responds to another child. A sequence of photographs showing a fourteen-month-old working out how to post a ball through a tube over several days can tell a teacher a great deal about her persistence and problem solving.
For infants and toddlers, revisiting looks different too. Children may simply point at photographs of themselves, smile or reach for the object they see, and that response is itself information. Families of the youngest children often value documentation more than anyone, because so much of their child's day is otherwise invisible to them.
Teachers working with the youngest children also need to be especially careful about the line between documenting and interrupting. A baby deeply absorbed in exploring a wooden spoon does not need an adult leaning in with a camera. Short, quiet records taken from a respectful distance, and photographs that show hands and objects rather than faces, usually capture what matters without disturbing the child's concentration.
Making documentation manageable
Documentation has a reputation for consuming teachers' evenings. Much of that comes from trying to document everything, beautifully, all the time. A more sustainable approach is to document one project at a time in depth, keep the rest of the record-keeping light, and accept that a handwritten panel with good thinking on it is more useful than a polished one made in a hurry.
Co-teaching makes it easier. In a bilingual classroom, one teacher can lead the activity while the other photographs and writes down what children say, and they can share interpretation at the weekly planning meeting. Schools can help by protecting that meeting, by providing a simple shared folder structure for photographs, and by agreeing who prints and arranges material.
There are practical points too. Photographs should be taken and stored on school devices under a clear privacy policy, and families should know how images are used. In a tropical city, paper panels near open windows fade and curl quickly, so laminating key pages or keeping a documentation book on a shelf may last longer than a wall.
Above all, documentation should never become a performance for visitors. If the team notices that panels are being made mainly to impress families on open days, it is worth stepping back and asking which documentation actually changed what happened in the classroom.
Documentation in the Global Nexus curriculum
Global Nexus uses pedagogical documentation mainly around its weekly projects and monthly themes, where it helps teachers follow a group's thinking from one day to the next. A project on how rain collects in the school garden, for instance, might produce photographs of children's first predictions, their drawings of where the water goes, transcripts of their debates in Vietnamese and English, and a short book the class reads back together at the end of the month.
Documentation sits alongside individual records rather than replacing them. When a documentation panel shows one child explaining an idea particularly clearly, that moment can also become an observation note in her file or the seed of a learning story. In this way group documentation feeds individual assessment, while keeping the focus on shared learning.
The curriculum keeps the same rule here as everywhere else: documentation never compares children or ranks contributions. It shows how a group's thinking grew, with each child's voice part of the story.
Câu hỏi thường gặp
Is pedagogical documentation only for Reggio Emilia schools?
No. It began in Reggio Emilia, but schools following many different curricula use it, especially those that work with projects. What matters is the cycle of recording, interpreting, revisiting with children and planning, not the label.
How is documentation different from a learning story?
A learning story usually focuses on one child and one significant episode, written for the child and family. Documentation often follows a group's thinking across a project and is used by teachers and children to reflect and plan.
Do teachers need special equipment for documentation?
No. A school camera or tablet, paper, a printer and time to talk are enough. Simple audio recording helps when capturing group discussions. Clear rules about storing children's images matter more than expensive tools.
How do young children take part in revisiting documentation?
Teachers show a few photographs or read back what children said and ask open questions such as what were you thinking here. Even two-year-olds respond to photographs of themselves, and older preschoolers often add explanations or new ideas.
Should documentation be shared with families?
Yes. Panels, books and digital stories help families understand how their children think and what a project involved. Sharing should follow the school's privacy policy, and families should know how photographs of their children are used.
How much time does documentation take each week?
It depends on the depth of the project. Teams that document one project at a time, divide roles between co-teachers and use planning meetings for interpretation usually find it manageable within normal working hours.