Objective. Students will analyze a complete child portfolio data set, identify developmental strengths and needs, and write a written instructional response addressing at least two identified needs.
This lesson, its worked examples and its practice questions has not yet been verified by a licensed professional in the field or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
Collecting observation notes, work samples, and developmental checklists is only the first step. The real purpose of assessment in early childhood education is to improve outcomes for each child. When you analyze a portfolio systematically and then plan instruction based on what the data actually shows, you are practicing evidence-based teaching — a core expectation in both the CDA credential and state childcare licensing standards.
This lesson walks you through the full cycle: summarizing portfolio data, identifying strengths and needs, and writing a clear instructional response.
Before you can plan anything, you need an organized picture of what the data says. The Data Summary Form structures that picture into three columns: what the child does well (strengths), where the child needs support (areas for growth), and what evidence supports each claim.
Identifying strengths means looking for patterns of consistent, age-appropriate performance across multiple observations or work samples. One lucky day does not make a strength; two or more independent pieces of evidence do.
Identifying needs means looking for patterns where performance falls below typical developmental expectations or below the child's own previous level. Again, a single off day is not a need; a recurring gap documented across time and settings is.
Citing evidence sources is non-negotiable. Every claim on the form must name the source: a running record from a specific date, a work sample labeled by domain, a developmental checklist item, or a family interview note. Vague statements such as "the child struggles with language" are not acceptable — "Anecdotal record 3/14: child used single words only during free play; checklist item 2.3 not yet met" is acceptable.
This habit of evidence citation protects children from biased conclusions and protects you professionally. It also directly mirrors what CDA assessors look for in a portfolio and what licensing inspectors expect in program documentation.
The IIR is a one-page planning document that translates your data summary into concrete teaching action. A well-written IIR includes four components:
1. The identified need and its evidence base. State the need clearly and reference the specific evidence that revealed it.
2. Two planned learning experiences. Each experience must be described specifically enough that another teacher could carry it out. Name the activity, the setting (small group, center time, outdoor play), and the approximate duration.
3. Materials required. List every material by name. Vague entries like "art supplies" are not sufficient; "large paintbrushes, three colors of washable tempera paint, 12-by-18-inch paper" is sufficient.
4. A measurement plan. Explain exactly how you will know whether the child is making progress. Will you use a tally sheet, a follow-up checklist item, a dated work sample, or a brief running record? Name the tool and when you will collect data.
Your IIR must also connect each planned experience to at least one early learning standard from your state framework. Standards connections show that your instruction is developmentally grounded, not arbitrary.
The most common error in writing an IIR is planning activities that are enjoyable but do not directly address the identified need. Test every planned experience with this question: How does this specific activity build the specific skill the data showed is lacking? If you cannot answer that question in one or two sentences, the activity may not be the right fit.
For example, if the data shows a child has limited fine-motor control evidenced by difficulty using scissors, a sand-writing tray builds hand strength and finger isolation — a direct connection. A dramatic-play activity might be wonderful for that child's social development but does not address fine-motor need. Plan accordingly.
Sharing your IIR in a triad and receiving structured feedback is not just a classroom exercise — it mirrors professional practice. Early childhood educators regularly collaborate with colleagues, special education staff, and families to review plans and catch gaps in thinking.
When you give peer feedback, use the protocol card: name one specific strength (not just "good job") and one specific improvement tied to a rubric category. When you receive feedback, listen for patterns. If two peers independently flag the same weakness, the data point is reliable.
Revise your IIR before submission. A revised document that shows you responded to feedback demonstrates the reflective practice that is central to the CDA competency standards.
Even with fictional portfolios, practice the habits you will use with real children. In professional settings, child assessment records are confidential. They must be stored securely, shared only with authorized individuals (families and direct caregivers), and never left accessible to unauthorized persons. This is both an ethical obligation and a legal requirement under applicable privacy standards. When you write about a real child's needs, use professional, strengths-based language — deficit framing can harm families and is inconsistent with best practice in early childhood education.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.