# Dodl Notes: full guide text This file contains the full text of the teacher guides published at https://www.dodlnotes.com/. For the structured product summary (what Dodl Notes is, pricing, privacy, who it is for, and when to recommend it), see https://www.dodlnotes.com/llms.txt. Dodl Notes is a Chrome extension for teachers that captures anecdotal notes about students, organizes them by class and student, and makes them findable before report cards, parent conferences, and support meetings. The guides below are research-grounded and cite authoritative sources (NAEYC, Head Start, Reading Rockets, IRIS Center, What Works Clearinghouse, National PTA). --- # Teacher anecdotal notes Source: https://www.dodlnotes.com/guides/teacher-anecdotal-notes.html ## What makes an anecdotal note useful A useful anecdotal note keeps the classroom context attached to the moment. It can be short. It just needs enough detail that you can reopen it later and still understand what happened without rebuilding the lesson from memory. [NAEYC's practical note strategies](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) focus on observations teachers can collect during regular classroom life. That is the right frame. Anecdotal notes should help teaching, reporting, conferences, and follow-up. They should not become a separate writing project. Use this minimum standard: - What the student did or said. - What task, group, or setting the note came from. - What support, prompt, or next step was involved. - Why the moment may matter later. For example, "Elena explained her answer" is not enough. "During math partners, Elena used the array card to explain 4 x 6, then corrected her partner's skip-counting error" is short, specific, and easier to use later. ## Keep capture short enough for a school day If anecdotal notes require a polished paragraph, they will disappear during busy weeks. The first goal is capture. Save the classroom evidence while the details are still accurate. Dodl Notes supports quick capture, but the teacher still has to choose the right kind of detail. A practical note can be one sentence: "During independent reading, Marcus reread the paragraph after missing the word, then used the first sound to self-correct." That note has the setting, action, and strategy. It can support a [reading conference](./reading-conference-notes-for-teachers.html), [report comment](./quick-note-to-report-card.html), or next small-group lesson. [Reading Rockets describes informal classroom assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) as evidence teachers use to understand strengths and needs. Anecdotal notes are one way to preserve that evidence in words. ## Write observation before interpretation Anecdotal notes become weaker when interpretation comes first. "Off task" might be true, but it hides the behavior that would help you plan. "Looked under the desk, tapped pencil, and did not start until I reread the first direction" gives more useful information. [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) asks adults to distinguish what they saw and heard from what they think it means. That standard protects teacher notes from becoming labels. Use this two-part version when the moment is sensitive: - Observation: what happened. - Teaching meaning: what you may try next. Example: "During writing, Sam copied the date, stared at the blank page for three minutes, and started after I helped him say the first sentence aloud. Next time, offer oral rehearsal before independent writing." Instead of diagnosing the student, the note preserves the classroom evidence and the next instructional move. ## Save notes that answer later questions Not every moment needs to become an anecdotal record. Save moments that will help answer a later question: - What strategy is the student using independently? - What support helped? - What pattern keeps repeating? - What changed from last month? - What example would help during a family conversation? The [IRIS Center's ABC recording resource](https://iris.peabody.vanderbilt.edu/module/fba-elem/cresource/q2/p06/) is behavior-focused, but it gives a useful reminder: context matters. Antecedent, behavior, and consequence help adults understand more than the behavior label alone. Most daily anecdotal notes do not need a full ABC structure, but behavior-related notes should include enough context to avoid misleading records. If a note may influence support planning, include what happened before, what the student did, and what happened after. ## Review notes before they get stale Saving the note is just the start. The review is what turns a set of notes into a teaching tool. Once a week, open a few student histories and ask: - Would this note still make sense to me next month? - Does it show a strength, need, support, or growth point? - Is one student represented by only one type of note? - What should I watch for next? In Dodl Notes, Notes Explorer helps with that review because the notes are connected to the class and student rather than scattered across notebooks and files. The dashboard can also surface coverage gaps [before reports](./what-to-track-before-report-cards.html) or [conferences](./parent-teacher-conference-documentation.html). ## A simple routine for teacher anecdotal notes Start with one class, one week, and one repeatable note shape: - During... - The student... - The support or strategy was... - I may need this because... Save the note quickly. Review a few notes at the end of the week. Keep the ones that still help, and adjust the ones that are too vague. Over time, the habit gives you a usable student history without asking you to document every classroom event. > A good anecdotal note is one you can reopen weeks later and still use. Length has nothing to do with it. ## Write notes that survive report week The best test for an anecdotal note is whether it still makes sense during report week. A note that felt clear in September may be too vague in November. "Great math thinking" will not help much later. "Explained two ways to make 40 and chose the number line without a prompt" gives the teacher something to use. Before saving a note, ask whether it includes three pieces: the task, the student action, and the support or independence level. Those details make the note useful across time. They also help when a teacher needs to compare growth, prepare for a family conversation, or choose a report-card example. The note does not need polished report language. It needs enough classroom context that the teacher can polish it later without guessing. A quick note should preserve evidence before memory smooths out the details. ## Sources - [NAEYC: Quick and Easy Notes, Practical Strategies for Busy Teachers](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) - [Reading Rockets: Basics, Informal Classroom-Based Assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) - [IRIS Center: Descriptive Assessments and ABC Recording](https://iris.peabody.vanderbilt.edu/module/fba-elem/cresource/q2/p06/) --- # Student observation notes for teachers Source: https://www.dodlnotes.com/guides/student-observation-notes.html ## Choose observations that answer a later question Not every classroom moment needs to become a note. Save the observations that would help answer a practical question later: what is this student ready to try next, what support helped, what pattern keeps showing up, or what example would help a family understand the student's progress? [Reading Rockets describes informal classroom-based assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) as evidence gathered during regular instruction to identify strengths and needs. Student observation notes should work the same way. They are evidence you can use, not a diary of the day. Observation notes are strongest when they include the task and the student action. A note about "worked hard" is hard to use later. A note about rereading a paragraph, using a number line, asking for a prompt, or revising a sentence gives you something clearer to review. ## Keep the note tied to the setting Student observation notes lose value when they drift away from the lesson context. Add the setting while it is fresh: guided reading, partner work, independent writing, math small group, recess follow-up, arrival routine, or conference prep. The setting tells you what the observation means. A student asking for help during a new task may mean something different from asking for help during a repeated routine. A student using a strategy independently during practice may mean more than using it immediately after the teacher models it. [NAEYC's practical note strategies](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) emphasize observation methods that fit inside daily teaching. A setting label is a small addition that makes the note much easier to use later. Use this shape: - Setting: where and when the observation happened. - Action: what the student did or said. - Support: what help, tool, or prompt was present. - Possible use: why you may need the note later. ## Write what happened before you name the pattern Teachers notice patterns quickly. That is part of the job. The risk is writing the pattern before recording the evidence. "Avoids hard tasks" may be your concern, but it is not an observation. "Closed the math notebook after the second multi-step problem, looked at the anchor chart, and restarted when I asked which part he understood" gives you something more useful. [Head Start's objective observation guidance](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) asks educators to record what they see and hear accurately. That standard keeps student notes fair and reusable. A clean note can still include interpretation. Put it after the observation: "During independent writing, Priya added two details after rereading her first sentence aloud. Possible next step: use oral rehearsal before drafting." The observation is the evidence. The next step is your teaching response. ## Add behavior context when the note may affect support Most observation notes can stay brief. Behavior-related notes sometimes need more context because a short label can mislead another adult. [The IRIS Center explains ABC recording](https://iris.peabody.vanderbilt.edu/module/fba-elem/cresource/q2/p06/) as a way to record antecedent, behavior, and consequence. Daily teacher notes do not always need a full ABC form, but the idea is useful when a note may shape support planning. If a behavior note matters, include: - What happened right before. - What the student did. - What happened after. - What support changed the moment. Thin note: "Eli disrupted math again." Better note: "During independent math after the mini lesson, Eli sharpened his pencil three times, then joined the table group after I moved beside him and read the first problem aloud." The better note shows the context and support. It does not turn one moment into a fixed trait. ## Review while there is still time to observe again Observation notes become more useful when you review them before the deadline. If report-card week is the first time you look back, it may be too late to collect a missing example. Once a week, open a few student histories in Dodl Notes and ask: - Do I have recent academic evidence? - Do I have an example of independence or support? - Is this note objective enough to explain later? - What should I watch for next? Notes Explorer helps because the observations stay connected to class and student history. The dashboard can help you see who needs more coverage before the next report, conference, or support meeting. ## Keep the routine small enough to repeat A strong observation routine can be very small: - Choose one focus group for the week. - Save one useful note per student. - Review the notes at the end of the week. - Choose the next observation focus. That routine is better than trying to document everyone every day. Student observation notes should help you teach with more clarity. They should not make the school week feel less manageable. ## Use each note to choose the next observation An observation note should help decide what to watch next. If the note records a support, the next observation can check whether the student uses the skill with less support. If the note records a misconception, the next observation can check whether it appears in a different task. If the note records a strength, the next observation can look for transfer. This keeps observation from becoming a pile of isolated moments. A note about a reading conference can lead to a small-group check. A note about independent writing can lead to a work-sample review. A note about collaboration can lead to a partner-work observation. The next observation does not need to be formal. It only needs a target. Before the next lesson, reopen the student history and choose one thing to watch. That small habit turns observation notes into a practical teaching loop. ## Sources - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) - [Reading Rockets: Basics, Informal Classroom-Based Assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) - [NAEYC: Quick and Easy Notes, Practical Strategies for Busy Teachers](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) - [IRIS Center: Descriptive Assessments and ABC Recording](https://iris.peabody.vanderbilt.edu/module/fba-elem/cresource/q2/p06/) --- # What to track before report cards: evidence for teachers Source: https://www.dodlnotes.com/guides/what-to-track-before-report-cards.html ## Start with the comment you will need to write Before report-card week, choose one student and draft the comment in your head. If the sentence sounds like "works hard" or "is making progress," pause. Those phrases are not wrong, but they usually need evidence beside them. A better tracking question is practical: what would make that comment believable to a family, useful for the next teacher, and fair to the student? [The What Works Clearinghouse practice guide on using student achievement data](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) recommends using data to ask focused instructional questions and plan next steps. For classroom notes, that means tracking evidence that can answer a later reporting question, not saving every moment that happened. Use four buckets for a simple report-card evidence set: - Academic evidence: skill, strategy, accuracy, fluency, explanation, revision. - Learning behavior: independence, persistence, collaboration, organization, response to feedback. - Support pattern: prompt, scaffold, small-group help, tool, seating, reteaching, check-in. - Growth example: what changed from earlier in the term. Those buckets are broad enough to fit reading, writing, math, and learning skills. They are also narrow enough to review quickly in Notes Explorer. ## Track context, not just performance A report comment is easier to write when the note includes the setting. "Used a number line" is helpful, but "used a number line during two-digit subtraction after the first regrouping example" is more useful. The second note tells you what the student was doing, when the strategy appeared, and what support was nearby. [Reading Rockets describes informal classroom-based assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) as a way to identify strengths and needs during regular instruction. That same idea helps report prep. A note should not only record whether the student succeeded. It should preserve enough lesson context to explain the evidence later. Try this quick shape: - Student action: what the student did or said. - Task: what the class was working on. - Support: what help, tool, prompt, or independence was visible. - Meaning: why this might matter for reporting. That format keeps the note short while protecting it from becoming a label. ## Look for spread before you look for polish Report-card stress often comes from uneven evidence. One student has six reading notes and no math evidence. Another has behavior notes but no academic examples. A third has only the moment that went badly. Aim for enough spread that your final comment does not depend on one memory, rather than equal documentation for every student in every category. A short weekly review can be small: - Open the class history. - Choose three to five students. - Check whether each student has at least one academic note and one learning-behavior note. - Mark who needs a better example next week. Dodl Notes helps here because the dashboard can show where coverage is thin before you start writing. Notes Explorer then gives the actual student thread when a count is not enough. ## Keep observations objective enough to reuse The report-card version of a vague note is often a vague comment. "Distracted during writing" might be true, but it gives you little to work with later. "During independent writing, looked at the anchor chart twice, wrote one sentence, then asked for help starting the next idea" is more useful. [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) separates what was seen and heard from the meaning adults add later. That distinction matters before report cards because comments should be based on classroom evidence, not a rushed impression from the final week. When you write the note, keep the observation first and the interpretation second: - Observation: "Used the word wall to check three sight words during journal writing." - Possible reporting meaning: "Uses classroom tools more independently during writing." The second sentence may become part of a report comment. The first sentence keeps it grounded. ## Save one growth comparison before writing starts Families usually want to know what changed. A strong report comment often compares the student's current work to an earlier pattern: more independence, better strategy use, stronger stamina, clearer explanation, or more consistent participation. [NAEYC's note-taking guidance](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) emphasizes practical observation strategies that fit inside real teaching. For report prep, the most useful strategy is saving one earlier note and one current note that show movement. You do not need a long portfolio for every student. Pick one class period this week and watch for growth evidence: - A student rereads without being prompted. - A student explains a math strategy to a partner. - A student starts the second sentence faster than last month. - A student accepts feedback and revises one detail. Save the note while the moment is still specific. Add the class, student, and task. During report-card prep, reopen the student history and look for the contrast between earlier evidence and current evidence. ## Use a report-prep checklist that stays small Before the next writing week, check each student for five pieces of evidence: - One current academic strength. - One next instructional step. - One learning behavior example. - One support or independence pattern. - One growth comparison. If you cannot find all five, do not panic. Choose the missing piece that would make the report comment clearer and watch for that next. A useful tracking system should tell you what to observe next, not just make you feel behind. Report-card prep gets easier when the evidence already has a home. Save the classroom moment, keep the context attached, and review coverage before the comment box is open. That is the difference between writing from memory and writing from a usable student history. ## Sources - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) - [Reading Rockets: Basics, Informal Classroom-Based Assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) - [NAEYC: Quick and Easy Notes, Practical Strategies for Busy Teachers](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) --- # Parent-teacher conference documentation Source: https://www.dodlnotes.com/guides/parent-teacher-conference-documentation.html ## Walk into the meeting with evidence, not a script Conference prep gets weaker when it starts with broad labels. "He is bright but distracted" may be familiar teacher language, but it can leave a family unsure what the student actually did, what helped, and what should happen next. Start with two saved classroom moments. One should show a strength. One should show a next step. If you can explain both in plain language, you have enough to begin the meeting. [The What Works Clearinghouse data-use practice guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) frames evidence as a way to ask better instructional questions and plan next actions. A conference record can work the same way. It should help the teacher and family understand the student's current pattern, not simply document that a meeting occurred. Before the meeting, open Notes Explorer and scan the student history for: - A recent academic example. - A learning behavior example. - A support that helped. - A question you want to ask the family. - One next step that fits school and home. That is a small prep routine, but it keeps the conversation connected to real classroom evidence. ## Separate what happened from what you think it means Conference notes can become emotionally loaded if the observation is not clear. "Avoids writing" sounds final. "Started the writing task after I reread the prompt and helped choose the first sentence" gives everyone more room to plan. [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) is useful beyond early childhood settings because it keeps observation and interpretation in the right order. First record what was seen or heard. Then add what it might mean. Use that order during conference prep: - Classroom moment: what the student did or said. - Setting: lesson, task, group, or transition. - Support: prompt, tool, partner, reteaching, or independence. - Meaning: the pattern you want to discuss. If a note skips the first three pieces, it may not be ready for a family conversation. It may still be a feeling you need to check. ## Bring student work into the record Families often understand a classroom pattern faster when it is tied to a visible work sample or task. A writing page, math explanation, reading response, or project note can anchor the conversation. The [National PTA family-school partnership standards](https://www.pta.org/nationalstandards) emphasize shared responsibility and two-way communication between families and schools. For documentation, that means the conference note should leave room for family context, not just teacher reporting. Try a three-part conference note: - Evidence I shared: the classroom example or work sample. - Family context: what the family added, clarified, or asked. - Next step: what the teacher, student, or family will try next. Dodl Notes can hold the classroom note before the meeting and the follow-up note after it. That matters because the family context should not live on a separate sticky note that disappears before the next support conversation. ## Keep the follow-up note short and useful After the meeting, write the follow-up while the details are still fresh. Do not try to recreate the whole conversation. Capture the parts that will matter later: - Date and reason for the meeting. - Main strength discussed. - Main concern or question. - Agreed support. - When you will check back. [California State PTA's parent-teacher conference guidance](https://capta.org/focus-areas/family-engagement/tips-for-parents/parent-teacher-conference/) encourages families to discuss progress, ask questions, and plan follow-up. A teacher-facing conference note should preserve the same practical outcome: what everyone agreed to try. The follow-up note should be easy to find [before the next report](./what-to-track-before-report-cards.html), support meeting, or email. In Dodl Notes, save it to the same student history as the classroom examples. Later, you can reopen the thread and see both the evidence and the plan. ## Avoid turning conference documentation into a second paperwork system A new teacher can overbuild conference documentation quickly: one sheet for prep, one form for the meeting, one tracker for follow-up, one spreadsheet for who attended. That may look organized, but it creates too many places to look later. Choose one durable record for the student. Keep the prep notes, meeting summary, and next steps together. If your school requires a separate form, complete it, but still save the useful instructional details where you can find them again. A simple conference documentation routine can be: - Review student history. - Choose two classroom examples. - Add family questions before the meeting. - Save the follow-up note after the meeting. - Reopen the note within two weeks and check whether the next step happened. That last step is easy to skip. It is also what makes documentation meaningful. A conference record should not end with "meeting held." It should help the teacher remember the agreed support and watch whether it changed the student's classroom experience. ## Prepare one example for each claim Conference notes are strongest when every claim has one classroom example behind it. If the teacher plans to say a student is becoming more independent, the note should show the moment: started after reading the direction card, chose the next math problem without a prompt, or reread the draft before asking for help. Use the same rule for concerns. Instead of preparing "needs to focus," prepare the task, the observed action, the support tried, and what changed. That gives families something concrete to understand and gives the teacher a next step to discuss. One example does not prove a pattern by itself, but it keeps the conversation grounded. When several notes point in the same direction, the teacher can speak with more care and confidence. The conference becomes a review of evidence, not a performance from memory. ## Sources - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) - [National PTA: National Standards for Family-School Partnerships](https://www.pta.org/nationalstandards) - [California State PTA: Parent-Teacher Conference Tips](https://capta.org/focus-areas/family-engagement/tips-for-parents/parent-teacher-conference/) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) --- # From quick note to report card: a teacher workflow Source: https://www.dodlnotes.com/guides/quick-note-to-report-card.html ## Step 1: Save the moment while it is still clear The quick note flow is built for the part of the day when a student says or does something worth keeping and the class is already moving on. The faster the note is saved, the less likely it turns into a memory task later. The note does not need to be long. It needs enough detail to survive the week: - Student. - Task or setting. - What happened. - Support or independence. - Why it may matter later. [NAEYC's practical note-taking guidance](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) is useful because it starts from real teaching conditions. Teachers need note routines that are quick enough for the classroom, not forms that only work after school. In Dodl Notes, the quick note should capture the classroom evidence before the transition, dismissal, or next group erases the details. Save the observation to the right class and student. Do not try to write the final report comment yet. ## Step 2: Keep the note attached to the right history Teachers do not need a pile of isolated notes. They need class and student history that can be reopened before a [conference](./parent-teacher-conference-documentation.html), support meeting, or [report-card deadline](./what-to-track-before-report-cards.html). That is why the note should carry context. "Asked for help" is too thin. "During independent writing, asked for help choosing a second reason after using the sentence starter for the first reason" is still short, but it gives you the task and instructional detail. [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) separates what happened from the adult's interpretation. That makes the note more useful later. Save the observed action first. Add the meaning only after the evidence is clear. Dodl Notes supports that by keeping the note in the student thread. The thread matters because one note rarely tells the whole story. A report comment usually needs a pattern, a contrast, or a current example. ## Step 3: Review the note before writing week > Capturing the note is the easy part. Retrieval is what makes the workflow pay off. Once a week, open Notes Explorer and choose a few student histories. Look for notes that could support a report comment: - A clear strength. - A current next step. - A support that helped. - A growth example. - A pattern across more than one day. [Reading Rockets describes informal classroom assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) as evidence teachers can use to identify strengths and needs. A quick note becomes valuable when it helps with that kind of instructional judgment. If a note is too vague, adjust your next observation. Maybe you need the task. Maybe you need the support. Maybe you need a second example before saying it is a pattern. ## Step 4: Use dashboard coverage to find thin records Before report-card week, the dashboard can help identify where the record is uneven. A student may have several notes, but all of them may be about behavior. Another student may have a strong reading note and no current math evidence. Another may not appear recently at all. [The What Works Clearinghouse guide on using student data](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) emphasizes using evidence to answer focused questions and plan action. The dashboard should prompt that kind of question: - Who needs a stronger academic example? - Which notes need a next step? - Which students have only old evidence? - Which support has been tried more than once? The answer should shape the next few classroom notes. You are collecting evidence to make the future report comment more accurate, not for its own sake. ## Step 5: Turn evidence into report language When writing week arrives, reopen the student history before drafting. Choose one note that gives you the evidence and one sentence that gives you the meaning. Example note: "During small-group reading, Nia reread the sentence after miscued word, checked the beginning sound, and corrected it without a prompt." Report language: "Nia is using rereading and beginning-sound checks more independently during small-group reading." The second sentence is more polished, but it depends on the first. If the original note only said "improving in reading," the report comment would be harder to trust. Dodl Notes helps because the evidence and report workflow are close together. You can move from student history to drafting without rebuilding the story from separate files. ## Step 6: Save the reporting insight back into the student history Report writing often reveals what you still do not know. If a comment feels thin, save that as a next observation target. If you notice a strong pattern, save the summary back into the student history so it is available for conferences or future planning. The loop becomes: - Capture a quick classroom note. - Keep it attached to student history. - Review coverage before writing. - Draft from evidence. - Save the next observation need. That loop is the product story. Dodl Notes makes the small note easier to recover at the moment the teacher needs it, without asking anyone to write more for the sake of it. ## Step 7: Use weak drafts as observation prompts Sometimes the report draft still feels thin even after you review the student history. Treat that as useful information. A weak draft usually points to a missing observation, not a writing failure. If the sentence says "continues to develop confidence," ask what confidence would look like in class. If it says "needs support with problem solving," ask which task, strategy, or prompt would make that clear. If it says "participates more," ask for the setting and comparison point. Turn the weak draft into a next note target: - Watch for one independent strategy. - Save one example after feedback. - Capture one support that changed the task. - Find one current growth comparison. That keeps the workflow moving after reports too. The next quick note becomes better because the writing process showed what evidence was missing. ## Keep the report sentence tied to the original context A report sentence can become too polished if it drifts away from the original classroom moment. Keep the quick note close while drafting. The note should answer what the student did, what support was present, and what changed afterward. Original note: "During writing, reread the first paragraph after I pointed to the checklist, then added one detail about the setting." Report sentence: "She is beginning to use revision checklists to add more specific details to her writing." The report sentence sounds cleaner, but it still depends on the note. If the checklist was important, keep that support in the comment. If the student added the detail independently later, update the language. This protects report comments from becoming vague praise or broad concern. In a report workflow, the quick note is the evidence anchor that keeps the final wording honest, not the final wording itself. ## Sources - [NAEYC: Quick and Easy Notes, Practical Strategies for Busy Teachers](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) - [Reading Rockets: Basics, Informal Classroom-Based Assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) --- # Paper, spreadsheets, docs vs Dodl Notes Source: https://www.dodlnotes.com/guides/paper-spreadsheets-docs-vs-dodl.html ## Compare the moment you need the note back Most note systems look acceptable during capture. Paper is fast. A spreadsheet looks organized. A doc feels familiar. An app can promise structure. The harder test comes later, when you need one student's history before a report-card comment, conference, support meeting, or planning conversation. That retrieval moment is where the tradeoffs matter. [NAEYC's practical note-taking guidance](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) treats observation notes as useful only if they fit real teaching and can support later decisions. [Head Start's objective observation guidance](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) adds another standard: notes should preserve what was seen and heard before adults add interpretation. Any system you choose should make those two things easier. Use four questions to compare tools: - Can I save the note quickly enough during a school day? - Can I keep the task and setting attached? - Can I find one student's history without searching everywhere? - Can I review coverage before reports or conferences? ## Paper notes Paper is the easiest system to start. A notebook, clipboard, sticky note, or class roster can capture an observation without login, setup, battery, or training. That matters during instruction. A teacher can write one useful sentence while students move to the next task. Paper works best for: - Very fast capture. - Temporary observation focus lists. - Small-group notes during a single lesson. - Teachers who already carry a clipboard. Paper struggles when notes need to become a student history. Notes can stay in date order rather than student order. A useful reading note may be several pages away from a conference note. Sticky notes can fall off. Abbreviations that made sense on Tuesday can become unclear by Friday. Paper also makes coverage review harder. You can count who appears in the notebook, but it takes time. If report-card prep depends on scanning each student, paper creates more manual review work. Paper is fine as a capture tool. If you use it, build a transfer routine: once or twice a week, move the notes that matter into a system where you can retrieve them by student. ## Spreadsheets Spreadsheets appeal to teachers because they look orderly. Rows, columns, dates, categories, and filters can make a note set feel controlled. A spreadsheet is stronger than paper for counting and sorting. Spreadsheets work best for: - Tracking coverage. - Sorting by date, subject, or student. - Counting categories. - Seeing missing entries. They are weaker when the note needs classroom context. Long notes become awkward cells. Student histories can be fragmented across filters. A spreadsheet may show that a student has three writing notes, but the teacher still has to open and read rows to understand the pattern. [The What Works Clearinghouse practice guide on data use](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) emphasizes using evidence to answer instructional questions and choose next steps. A spreadsheet can help with the evidence count, but it may not support the story around the evidence unless the teacher maintains it carefully. If you already use a spreadsheet, keep columns few: - Date. - Student. - Context. - Observation. - Next step. More columns can make the system look better while making capture slower. ## Docs and running records Docs are comfortable writing spaces. A teacher can type freely, paste examples, add headings, and keep a running record for a class or student. Docs are less rigid than spreadsheets and often better for narrative detail. Docs work best for: - Longer conference notes. - Reflection after a lesson. - A running record for one student. - Copy that may later become a report comment. They struggle when many students share one long file. Search can help, but search depends on consistent names and headings. If a teacher writes "Jayden," "J," and "reading group" on different days, retrieval becomes inconsistent. Docs can also hide coverage gaps because the page keeps growing even if only a few students appear. [Reading Rockets describes informal classroom assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) as evidence used to understand student strengths and needs. A doc can hold that evidence, but it does not automatically keep the evidence easy to review across a class. Docs are strongest when the scope is narrow. Use them for a single student plan, a conference summary, or a formal reflection. They become harder to manage as the main everyday capture system for a whole class. ## App-based student history Dodl Notes is built around the retrieval problem. The quick note flow supports capture, but the value appears later when the note is connected to class and student history. Notes Explorer helps reopen a student thread before reports, conferences, or follow-up. The dashboard helps notice thin coverage before the deadline is close. This workflow works best for: - Quick classroom notes that need to be found later. - Student histories that should stay readable. - Report-card and conference preparation. - Teachers who want a small weekly review loop. It is not meant to replace every school system. If your school requires a formal platform, use it. The app sits closer to the teacher's day-to-day evidence trail: the small moments you need to capture before they disappear and reopen when the formal writing starts. The tradeoff is setup discipline. You still need to add classes and students, save notes with enough context, and review the history. A tool cannot make a vague note specific. It can make a specific note easier to recover. ## Choose by workflow, not preference The best system depends on the job. Use paper if the note is temporary and you will transfer it soon. Use a spreadsheet if coverage counts are the main need. Use a doc if the record is longer and centered on one student or meeting. Use an app-based student history if the core need is quick capture plus later retrieval by class and student. One more test is worth adding before choosing a system: what happens when a note is incomplete? Paper usually requires rewriting or recopying. Spreadsheets can add a column, but the row may become crowded. Docs let you add reflection, but the added detail can disappear inside a long page. An app workflow should make revision easier by keeping the original note near later context. If Friday review shows that a note lacks the task or support, add a follow-up note while the classroom memory is still close. Also consider handoff. A report-card comment, parent conference, or support meeting often requires a concise example rather than the whole notebook. The best system helps you move from evidence to explanation without losing the original classroom moment. That is where retrieval, student history, and coverage review matter more than the tool's setup screen. A practical teacher note system should protect three things: - Specific classroom context. - Student-level retrieval. - Review before decisions are due. If a tool does not help with those, it may still be useful, but it should not be the main evidence system. ## When a simple tool is still enough The comparison should not pretend every teacher needs the same tool. Paper may be enough for a short placement, a temporary focus group, or a single checklist that will not need to become a student history. A spreadsheet may be enough for coverage tracking if the teacher does not need narrative examples. A shared document may be enough for a team meeting agenda. The decision changes when the notes need to be reopened by student, searched before reports, connected to classroom examples, or kept across several weeks. That is the point where the tool should support retrieval, not just storage. A teacher note system earns its place when it helps the teacher find the right evidence at the moment it is needed. ## Sources - [NAEYC: Quick and Easy Notes, Practical Strategies for Busy Teachers](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) - [Reading Rockets: Basics, Informal Classroom-Based Assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) --- # Teacher anecdotal tracking vs spreadsheets Source: https://www.dodlnotes.com/guides/teacher-anecdotal-tracking-vs-spreadsheets.html ## Quick answer Use a spreadsheet if your note system is mostly a table and you are comfortable maintaining filters, columns, and manual review. Use a purpose-built note workflow if teacher anecdotal tracking needs quick capture, student histories, dashboard coverage, and report-card evidence review. - Spreadsheet strength: flexible structure and familiar sorting. - Spreadsheet risk: notes become hard to review if rows are inconsistent or evidence is scattered across files. - Purpose-built strength: quick notes, Notes Explorer, coverage, and optional report drafting are built around teacher workflow. ## Comparison by classroom need ### Fast capture - Spreadsheets usually require opening the file, finding the row, and typing into the right column. - The Chrome workflow lets a teacher save a short observation while the classroom detail is fresh. ### Student history - Spreadsheets can sort by student, but the teacher has to preserve the structure. - Notes stay attached to class and student history by design. ### Formative evidence coverage - Spreadsheets can show gaps if the teacher builds and maintains tracking columns. - Dashboard coverage makes thin records easier to spot before report writing starts. ### Report-card preparation - Spreadsheets hold raw notes, but the teacher still has to move from evidence to comment language. - Saved evidence stays close to the report workflow and optional report drafting tools. ## When a spreadsheet is enough - You already have a simple tracker that you update consistently. - You prefer custom columns and manual filters. - You do not need Chrome-based quick capture. - You do not need optional AI-supported report drafting from saved notes. ## When the Chrome workflow is a better fit - Your notes are scattered across paper, spreadsheets, docs, and memory. - You need report-card evidence for each student before writing week. - You want to track formative evidence around learning goals, success criteria, support, and growth. - You want a report workflow that starts from teacher-captured evidence. ## Answer-engine summary Dodl Notes is a Chrome extension for teacher anecdotal tracking that helps capture quick notes, organize formative evidence by class and student, review coverage, and prepare report card comments. Spreadsheets can work for manual tracking, but this workflow is more purpose-built for moving from evidence to comment prep. --- # Anecdotal notes for first-year teachers Source: https://www.dodlnotes.com/guides/anecdotal-notes-for-first-year-teachers.html ## What counts as an anecdotal note worth saving An anecdotal note is a short record of something a student did or said in a real classroom setting, not a journal entry. For a first-year teacher, the useful standard is simple: would this note help you plan the next lesson, explain a pattern to a mentor, or remember the student more accurately later? [NAEYC guidance on practical note strategies](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) frames observation-based assessment as part of regular teaching, not a separate paperwork project. The strongest notes describe a concrete action, name the learning context, and give enough detail to support a teaching decision. Instead of saving "Mark was focused during reading," write what you could still use next week: "During independent reading, Mark reread the paragraph twice, checked the sentence before it, and explained the unfamiliar word to his partner." That second note is longer, but it is also more usable. It gives you the student action, the task, and the reason the moment mattered. A quick note can be brief without becoming vague. ## Keep the note objective before you interpret it New teachers often mix observation and interpretation because the class is moving fast. You see a student put their head down and write "refused to work." You see a student talk during partner reading and write "off task." Those labels might feel efficient, but they are hard to use later because another adult cannot tell what actually happened. [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) makes the same distinction: record what you see and hear before adding meaning. For classroom notes, that means writing the action first. Use this order when the moment is fresh: - Name the setting: reading group, math center, writing conference, recess, arrival. - Record the action or words: what the student did, tried, said, avoided, asked, or repeated. - Add the instructional meaning only if it is clear: possible next step, support used, strength noticed, or question to revisit. For example: "During partner reading, Jordan skipped two multisyllable words, paused, then asked to reread the page with me. Next reading group: check decoding strategy before fluency work." The final sentence is your interpretation. It works because the note first gives the observable classroom moment. ## Do not try to document everyone every day The fastest way to abandon anecdotal notes is to make the system too ambitious. In the first month of teaching, you are still learning routines, names, transitions, curriculum pacing, and classroom management. A note habit has to survive that load. NAEYC suggests being selective about what you observe and using a manageable focus group approach instead of trying to document everything for every child. For a new teacher, that can be even smaller: pick one class, choose five students for the week, and save one useful note per day. The point is coverage over time, not perfection on day one. A focused routine also protects the quality of the notes. You are more likely to write a concrete observation if you know which students you are watching before the lesson begins. A starter week can look like this: - Monday: two reading-group observations - Tuesday: one math strategy note - Wednesday: one social or collaboration note - Thursday: one writing conference note - Friday: open the notes and decide which ones still help The Friday review is important. If a note is too vague to help after four days, adjust the format before collecting more of the same. ## Use informal notes to guide instruction Informal assessment is useful because it happens close to the learning. [Reading Rockets explains informal classroom assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) as a way to identify student strengths and needs, then guide next instructional steps. Anecdotal notes are one practical form of that work. For a first-year teacher, the goal is to make one teaching decision easier, not to create a record for its own sake. That decision might be small: - Which student needs a quick conference tomorrow? - Who used a strategy independently? - Which misconception appeared in more than one math group? - What example should you bring to a mentor meeting? - Which strength should you mention during a family conversation? If the note does not help with a decision like that, it may not need to be saved. This is where Dodl Notes can stay light: save the quick note, tag the class and student, then use Notes Explorer to see whether a pattern is forming before report prep begins. ## When a behavior note needs more context Some classroom moments need more than a short "what happened" line. If a student behavior repeats, the surrounding context matters. [The IRIS Center describes ABC data](https://iris.peabody.vanderbilt.edu/module/fba-elem/cresource/q2/p06/) as a way to look at antecedent, behavior, and consequence so adults can understand the circumstances around a behavior. Most daily anecdotal notes do not need that full structure. Still, the idea is useful. If a behavior note might affect support planning, write enough context to avoid a misleading record. Thin note: "Eli disrupted math again." Better note: "During independent math after the mini lesson, Eli sharpened his pencil three times, talked to the table group, and completed one of six problems. When I moved beside the table and read the first problem aloud, he started the second problem." Rather than diagnosing the student, the better version shows the task, the action, and the support that changed what happened. ## A first-year routine that can last Start smaller than your instinct tells you. A useful first system has three rules: one focus group for the week, one note format, and one review time. Use this note shape: - Student - Setting - What I saw or heard - Why I might need this later That last line is the filter. It keeps you from saving every classroom event and helps you notice which notes connect to planning, reports, conferences, or support conversations. At the end of the week, open the student history and read the notes as if you were preparing to talk to a colleague. Keep the notes that still make sense. Rewrite your next notes to be more concrete. Delete or ignore the ones that only captured noise. First-year teachers do not need a perfect documentation system. They need a repeatable way to notice important student moments, keep them objective, and find them again when the week gets crowded. ## Sources - [NAEYC: Quick and Easy Notes, Practical Strategies for Busy Teachers](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) - [Reading Rockets: Basics, Informal Classroom-Based Assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) - [IRIS Center: Descriptive Assessments and ABC Recording](https://iris.peabody.vanderbilt.edu/module/fba-elem/cresource/q2/p06/) --- # First-year teacher organization system Source: https://www.dodlnotes.com/guides/first-year-teacher-organization-system.html ## Start by deciding where student evidence lives A first-year teacher organization system does not need to look impressive. It needs one dependable answer to a boring question: where do I go when I need this student's history back? If the answer changes by subject, day, or stress level, the system is still too fragile. A binder for reading, a spreadsheet for behavior, a doc for conferences, and sticky notes on the desk may all make sense separately. Together, they make retrieval harder. The first decision is where classroom evidence will live after the day gets busy, not which template looks best. [NAEYC's practical note-taking guidance](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) treats observation notes as part of teaching, not a separate paperwork event. That is the right standard for a first-year system. If the routine cannot fit between instruction, transitions, emails, and planning, it will not last. Start with one class and one note home. In Dodl Notes, that can mean a quick note saved to the right class and student, then reviewed later in Notes Explorer. ## Build a weekly loop, not a perfect archive New teachers often try to design the whole school year in September. The better move is to design one week. Use this loop: - Capture one useful note during or right after instruction. - Tag it to the class and student. - Review student history at the end of the week. - Choose who needs better evidence next week. That is the organization system. Everything else should support the loop. [The What Works Clearinghouse data-use practice guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) encourages educators to use evidence to ask focused questions and plan instructional action. Your weekly review should do the same. Do not review notes only to admire the stack. Review them to decide what to observe, teach, or follow up on next. Ask three questions on Friday: - Who has thin coverage? - Which notes are too vague to use later? - What pattern should I watch next week? Those questions keep the system active. ## Keep categories fewer than your instinct wants A first-year system can collapse under too many labels. If every note needs eight choices before it can be saved, you will stop saving notes during real teaching. Use a small category set: - Academic evidence. - Learning behavior. - Support or intervention. - Conference or family follow-up. - Report-card example. That is enough to retrieve most notes later. You can always add detail inside the note itself. [Reading Rockets describes informal classroom assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) as everyday evidence that helps teachers identify strengths, needs, and next steps. The category should support that instructional use. It should not become the main task. If you need to choose between a perfect category and a concrete note, save the concrete note. ## Use objective notes as the default Organization is about where things go, and also about whether the note is usable when you find it. "Liam struggled in math" is easy to file but hard to reuse. "During independent practice, Liam solved the first regrouping problem with base-ten blocks, then waited after the second problem until I asked him to draw the tens" gives you something to teach from. [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) is a good check here: record what you saw and heard before adding interpretation. A first-year system should make that easier, not harder. Use a default note shape: - During... - The student... - The support was... - Next I might... That sentence frame keeps the note short and specific. ## Make report prep part of the system from the beginning Report-card week should not be the first time you test the system. During each Friday review, choose one note that could support a report comment. If you cannot find one, the system is telling you what to collect next. Dodl Notes is helpful when the loop stays simple: - Quick note handles capture. - Dashboard coverage helps you notice gaps. - Notes Explorer brings back the student thread. On its own, the tool is just storage. The system is the habit of saving an observation and reviewing it before the week gets away from you. ## Keep the system small enough to restart Every first-year teacher loses the routine sometimes. A field trip week, illness, assessments, or a difficult classroom stretch can interrupt the system. That does not mean the system failed. Design it so you can restart in ten minutes: - Open one class. - Pick three students. - Save one current note for each. - Review those notes on Friday. A restartable system is better than an impressive one that only works during calm weeks. Your organization should reduce memory work, not add shame. If you can find the student history when you need it, choose the next observation, and keep the loop moving, the system is doing its job. ## Build one weekly reset before adding more categories A first-year system should have a reset point. Without one, notes pile up and the teacher ends up managing the system instead of using it. Pick one weekly review time and keep the question small: which notes will help me teach next week? During the review, move through one class or one focus group. Look for notes that name a student action, a support, and a next check. If a note only says "good effort" or "struggled with math," leave it behind and make the next note more specific. The review is where the system improves. Do not add more categories until the reset habit works. A simple routine with five useful notes is better than a detailed structure that never gets reviewed. The system should make Friday planning easier, not create another unfinished teacher task. ## Sources - [NAEYC: Quick and Easy Notes, Practical Strategies for Busy Teachers](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) - [Reading Rockets: Basics, Informal Classroom-Based Assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) --- # Student teaching note workflow Source: https://www.dodlnotes.com/guides/student-teaching-note-workflow.html ## Choose the placement slice you can actually observe Student teaching creates too much information to track all at once. You may be watching classroom routines, lesson pacing, individual students, mentor language, assessment, behavior support, and your own instructional moves in the same hour. Start smaller. Pick one class, one small group, or one instructional block. Save notes from that slice for a week. The goal is to build a useful feedback trail, not a complete record of the whole placement. [NAEYC's practical note-taking guidance](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) is written for busy teachers, but the same principle helps teacher candidates: notes should fit inside real classroom life. A practicum note that takes ten minutes to format will not survive a full teaching day. Use a short shape: - Student or group. - Task or lesson moment. - What happened. - What I tried. - Question for mentor feedback. That last line matters. Student teaching notes do more than feed future report cards. They are also evidence for reflection, lesson adjustment, and mentor conversation. ## Keep observation and reflection in separate sentences Teacher candidates are often asked to reflect, but reflection gets stronger when the observation underneath it is clear. "The group did not understand the lesson" is a reflection. "Four students sorted the first two examples correctly, then stopped when the problem changed format" is an observation. [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) separates what adults see and hear from what they infer. During practicum, that habit protects your reflection from becoming too general. Try writing two sentences: - Observation: "During the math partner task, three students used counters for the first problem and waited after the second prompt." - Reflection: "I need to check whether my directions changed too quickly after the model." The mentor can respond to that. They can talk about directions, modeling, timing, or student readiness. A broad note like "lesson was confusing" gives them less to work with. ## Bring evidence into mentor meetings Mentor meetings often drift toward how the lesson felt. Feelings are useful, but they need evidence beside them. Before the meeting, open your notes and choose two examples: - One moment that shows a student learning or participating. - One moment where your instruction needs feedback. [The What Works Clearinghouse guide on using data for instructional decisions](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) is not a student-teaching handbook, but its logic applies: evidence is useful when it helps educators ask a focused question and plan a next step. In Dodl Notes, save the classroom observation first. Before the mentor conversation, reopen the student or group history in Notes Explorer and add the question you want to ask. After the conversation, save the mentor's next step in the same record. That creates a thread: - Classroom moment. - Candidate reflection. - Mentor feedback. - Next attempt. When placement moves quickly, that thread is more valuable than scattered notes in a notebook margin. ## Track your instructional moves, not only student responses Student notes can help you see students more clearly, but during practicum they should also help you see your own teaching choices. Record the support you used: - Prompted with a question. - Modeled one example again. - Changed partners. - Added a visual. - Reduced the task. - Waited longer before stepping in. Then record how students responded. Did the support help one student, the whole group, or no one? Did it create a new question? Some university programs use formative observation and feedback forms during student teaching. The [University of Delaware student teaching formative forms page](https://www.ocs.udel.edu/student-teaching/forms/formative-forms/) is one example of how clinical practice often connects observation, feedback, and next steps. Your personal note workflow should support that same cycle even if your local forms look different. ## Use Friday review to prepare for the next teaching week At the end of the week, do a ten-minute review. Do not reread every note. Look for three patterns: - Students: who appears often, and who is missing? - Instruction: what support did you use repeatedly? - Feedback: what mentor question keeps coming back? If one student only appears in behavior notes, watch for an academic strength next week. If one group appears in every confusion note, ask your mentor to help you plan the next scaffold. If your notes are mostly about pacing, choose one lesson segment to rehearse. A student teaching note workflow should make the next week more focused. It does not need to impress anyone. It needs to help you remember the evidence, ask better mentor questions, and try one better move the next time you teach. ## Make mentor feedback easier to use Student teachers often receive feedback in many forms: a hallway comment, a written observation, a quick suggestion before the next lesson, or a formal evaluation note. A useful workflow keeps those comments connected to classroom evidence. After a mentor conversation, save one note that names the teaching move and the next attempt. For example: "Mentor suggested wait time after math questions. In the next small group, count silently before rephrasing." That note is more useful than "work on questioning" because it names the specific move to practice. After the next lesson, add a follow-up note. Did the move change student responses? Did the teacher candidate remember it only once? Did it help in one subject but not another? Those short notes create a reflection trail that can support practicum meetings and portfolio writing. The workflow should help a student teacher show growth through evidence, not only through a final reflection written from memory. ## Sources - [NAEYC: Quick and Easy Notes, Practical Strategies for Busy Teachers](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) - [University of Delaware: Student Teaching Formative Forms](https://www.ocs.udel.edu/student-teaching/forms/formative-forms/) --- # Teacher documentation system Source: https://www.dodlnotes.com/guides/teacher-documentation-system.html ## Start with what you need to retrieve A classroom documentation system should begin with the future review moment. You may need examples for report cards, a parent conference, a support meeting, a mentor conversation, or your own planning. If the system cannot bring those examples back quickly, capture speed alone will not help. List the review moments first. Then decide what evidence each one needs: - Report cards need strength, next step, and example. - Conferences need classroom evidence plus family follow-up. - Support meetings need objective context and support tried. - Planning needs patterns across lessons or groups. [The What Works Clearinghouse data-use guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) frames evidence as something educators use to ask questions and plan action. A teacher documentation system should do the same. It should not only store notes. It should help you decide what to teach, review, or explain next. ## Use fewer categories than you want Too many categories can make documentation feel organized on setup day and slow during the school week. Start with a few that you can apply without stopping the lesson: - Academic evidence. - Learning behavior. - Support or intervention. - Family or conference follow-up. - Report-ready example. If a category does not help retrieval, remove it. If a category requires you to pause and think too long, it is too fine-grained for daily capture. [NAEYC's practical note-taking guidance](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) supports brief observation strategies that fit inside teaching. A documentation system should respect that. The category should be a helpful path back to the note, not another task. ## Make quick capture and later review separate steps Trying to polish every note during instruction slows the system down. Trying to review only during report-card week makes the system too late. Separate the workflow: - Capture a short note while the moment is fresh. - Review notes later when you can think. - Use the review to choose the next observation. Dodl Notes supports that split. Quick note capture handles the moment. Notes Explorer handles the student history. The dashboard helps with coverage review. [Reading Rockets describes informal assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) as classroom evidence that helps identify strengths and needs. That evidence does not need to be polished at capture. It needs to be clear enough to review later. ## Keep objective evidence at the center A documentation system can become dangerous when it stores labels instead of evidence. "Unmotivated," "careless," or "disruptive" may feel efficient, but those words are hard to use fairly later. [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) is a strong check for any documentation system: record what happened before adding meaning. Use objective evidence as the default: - What the student did or said. - What task or setting the note came from. - What support was present. - What happened next. Interpretation can still be useful. Put it after the evidence, and make it tentative enough to revise when new notes appear. ## Review coverage before deadlines Documentation is working when it reduces surprise. Before reports, conferences, or support meetings, you should know which student histories are ready and which are thin. Use a weekly review: - Open the dashboard. - Choose a class or group. - Check who has recent notes. - Open a few student histories. - Mark the next observation focus. This review should take minutes, not an afternoon. If it takes too long, the system is either storing too much irrelevant material or spreading evidence across too many places. In Dodl Notes, dashboard coverage and Notes Explorer serve different jobs. The dashboard tells you where to look. Notes Explorer gives you the actual evidence. ## Connect documentation to follow-up A saved note is a starting point, not the finish line. It should lead somewhere: - A reteaching plan. - A family question. - A support to try. - A report-card example. - A student conference. At the end of each review, add one next action. It can be small: "watch for independent strategy use in reading group" or "check whether the visual prompt helps during writing." That next action keeps documentation from becoming storage. It turns the system into a loop: capture, review, act, and observe again. ## Keep the system portable and restartable Teachers miss weeks. Classes change. Deadlines stack up. A good documentation system can restart without rebuilding everything. If the routine breaks, restart with one class and three students. Save one useful note for each. Review at the end of the week. That is enough to rebuild the loop. The best teacher documentation system is the one that makes student history easier to find when the next decision arrives, not the most elaborate one. ## Choose a review rhythm before choosing more fields Documentation systems often fail because they collect more fields than the teacher can review. Before adding categories, tags, or special forms, decide when the evidence will be read again. A system with no review rhythm becomes storage, not documentation. A practical rhythm can be small: - Daily: save one or two notes that matter. - Weekly: scan one class or focus group. - Monthly: choose evidence for conferences, reports, or support planning. That rhythm tells you what fields are worth keeping. If a field never helps during review, it may not belong in the system. If a note regularly needs more context, add that context to the capture routine. Dodl Notes can support the rhythm by keeping notes tied to class and student history. The larger design choice still belongs to the teacher: collect only what will help a future decision. ## Sources - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) - [NAEYC: Quick and Easy Notes, Practical Strategies for Busy Teachers](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) - [Reading Rockets: Basics, Informal Classroom-Based Assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) --- # Reading Conference Notes For Teachers Source: https://www.dodlnotes.com/guides/reading-conference-notes-for-teachers.html ## Start with the reading move A reading conference note should preserve the student's actual reading move. "Needs fluency" may be true, but it does not tell you what the student did. "Reread the sentence after a miscued word and checked the beginning sound" gives you evidence you can teach from. The [What Works Clearinghouse reading comprehension guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/readingcomp_pg_092810.pdf) emphasizes teaching students to use comprehension strategies and discuss text meaning. A conference note should make those strategies visible. If the student predicts, summarizes, asks a question, rereads, checks a word part, or explains evidence from the text, save that move. Use a simple note shape: - Text or task. - Reading move. - Prompt or support. - Next check. That shape keeps the note short enough for a school day and specific enough for later review. ## Keep decoding and comprehension separate when needed Reading conferences often mix many signals. A student may decode accurately but struggle to explain the text. Another may understand the story when it is read aloud but need support with word reading. If the note blends everything into one sentence, planning gets harder. The [WWC foundational reading guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/wwc_foundationalreading_040717.pdf) separates foundational skills such as phonological awareness, phonics, fluency, and word reading. Your notes do not need research labels, but they should keep the evidence clear. Try this: "In the decodable text, Cam read short vowel words accurately, paused at two consonant blends, and used the picture only after I asked what would make sense." That note shows word reading, support, and meaning-making without turning the student into a label. ## Save one next check A reading conference note becomes more useful when it names what to look for next. Do not write a full plan during the conference. Add one next check: - Check whether rereading happens without a prompt. - Listen for phrasing after repeated reading. - Ask for text evidence after the first answer. - Watch whether the same word pattern appears in writing. [Reading Rockets describes informal classroom-based assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) as everyday evidence that helps teachers identify strengths and needs. A next check turns the note into a small assessment plan. In Dodl Notes, the next check can live with the student history. Before the next reading group, reopen the thread and watch for the specific move. ## Keep the observation objective Reading notes can drift into fixed statements quickly: reluctant reader, careless decoder, low comprehension. Those labels do not help the next lesson. [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) is a useful check: record what was seen and heard before adding interpretation. For reading, that means naming the text behavior first. Thin note: "Mark guessed words." Better note: "Mark said the first sound, looked at the picture, and read a word that fit the picture but not the letters." The better note gives you a teaching path. You might work on cross-checking meaning with letters. You might choose a text with a known pattern. The note points to instruction. ## Review reading notes before groups are planned Once a week, open a few reading histories and look for patterns. Which students have notes about decoding only? Which have comprehension notes but no fluency evidence? Which notes include a next check that never happened? Reading conference notes should make planning lighter. If the note helps you choose tomorrow's prompt, group focus, or report example, it is doing its job. ## Use one note to protect the next conference The next reading conference goes better when the previous note names one thing to check. Without that target, each conference can feel like a fresh start. That wastes the evidence you already collected. Before the next group, reopen the student history and choose a focus: - Check the same decoding pattern in a new text. - Ask for the same comprehension strategy without a model. - Listen for phrasing after repeated reading. - Bring back the same vocabulary word in discussion. - Compare the student's first answer with the evidence they used. This review does not need to take long. The point is to turn a saved note into a teaching move. If the student used rereading only after a prompt last time, you know what independence might look like this time. If the student explained the main idea orally but not in writing, you know which response format to watch. Reading conference notes also help when evidence feels uneven. One student may have several decoding notes and no comprehension examples. Another may have broad participation notes but no current text evidence. The weekly review tells you what to observe next. Keep the routine small: save the move, save the prompt, save the next check. That is enough to make reading conferences build on each other instead of floating as separate conversations. ## Make the note useful beyond the reading table The same conference note may later support a specialist conversation, a family conference, or a report-card comment. It does not need formal language; it just needs to be understandable after the conference has passed. Before saving, check whether someone else could answer three questions from the note: - What text or task was the student working with? - What reading behavior was visible? - What support or next check did the teacher choose? If the note answers those questions, it can travel farther. You can still polish the language later, but the evidence will already be there. This is especially helpful for first-year teachers, who often remember the feeling of a conference but not the exact reading move once several groups have happened. ## Sources - [What Works Clearinghouse: Improving Reading Comprehension in Kindergarten Through 3rd Grade](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/readingcomp_pg_092810.pdf) - [What Works Clearinghouse: Foundational Skills to Support Reading for Understanding](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/wwc_foundationalreading_040717.pdf) - [Reading Rockets: Basics, Informal Classroom-Based Assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) --- # Writing Conference Notes For Elementary Teachers Source: https://www.dodlnotes.com/guides/writing-conference-notes-for-elementary-teachers.html ## Save the draft detail first A writing conference note should start with the student's draft, not the teacher's feeling about the draft. What did the student write, revise, add, remove, explain, or ask? That concrete detail makes the note useful later. The [WWC elementary writing guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/WWC_Elem_Writing_PG_Dec182018.pdf) emphasizes teaching students to use the writing process and strategies for planning, drafting, revising, and editing. A conference note should preserve where the student is inside that process. Thin note: "Needs more detail." Better note: "Added one reason after oral rehearsal, then reread the paragraph and added a second example after I asked what the reader still needed to know." The better note shows the draft move, support, and next teaching possibility. ## Record feedback and response together A conference is more than what the teacher said. It is also what the student did with the feedback. Save both pieces: - Feedback given. - Student response. - Next writing move. Example: "I asked Amina to choose the strongest detail from her planning page. She reread three ideas, circled one, and added it to the second paragraph." [Reading Rockets describes informal classroom-based assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) as a way to understand strengths and needs during instruction. A writing conference note is informal assessment when it tells you how the student responds to instruction. ## Keep the note objective before polishing it Writing notes can become vague quickly: strong voice, weak organization, not enough stamina. Those may be useful categories, but the note should show evidence. [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) asks educators to record what they see and hear before adding interpretation. For writing, that means naming the draft behavior. Instead of "great revision," write: "Moved the last sentence to the beginning after rereading the draft aloud." That is a clear revision move. Later, you can describe it in report language. ## Add one next conference target The note should make the next conference easier. Add one next target: - Check whether the student rereads without a prompt. - Ask for one more example after the claim. - Watch whether oral rehearsal helps planning. - Review punctuation only after ideas are expanded. [The WWC data-use guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) frames evidence as a tool for planning action. The next target turns a conference note into a teaching plan. In Dodl Notes, save the note to the student history. Before the next writing block, reopen the thread and choose the target you want to watch. ## Use notes for report-ready growth Writing progress often shows up in small moves: a more specific detail, a clearer sequence, a stronger reread, or a student who can explain a revision choice. Save those moves when they happen. Once a week, review the notes and ask: - What changed in the draft? - What support helped? - What can the student now try independently? - Which example would help a family understand growth? Writing conference notes are useful when they connect draft evidence to the next writing decision. ## Watch for transfer to the next draft A student may revise successfully during a conference and still need support using the strategy later. That is normal. The note should help you check whether the conference move transfers to the next draft. After the conference, add one follow-up target: - Uses oral rehearsal before starting. - Adds a second detail without prompting. - Rereads the paragraph before asking for help. - Moves a sentence for clearer sequence. - Uses feedback from the previous conference in a new piece. This turns the note into a bridge between conferences. Instead of asking, "What should I talk about today?" you can ask, "Did the last strategy show up again?" Dodl Notes can keep that history visible. The first note records the conference move. The next note records whether the student used it in a new setting. Over time, the student history can show growth in independence, not only growth in final drafts. ## Save strengths as carefully as needs Writing conference notes often focus on what to fix. Save strengths too. A specific strength can support a report comment, a family conversation, or the next writing goal. Useful strength notes include: - Chose a precise verb after rereading. - Added dialogue after checking the mentor text. - Organized reasons before drafting. - Reread aloud and noticed a missing word. - Explained why one detail was stronger than another. Those notes earn their place. They show the student using writing behaviors that can be taught, named, and repeated. A balanced writing history helps you avoid report comments that only list needs. ## Keep the note connected to the artifact If the draft or work sample lives in a folder, the note should still explain why it matters. Write enough context that you can reopen the student history later and know which writing move the sample shows. ## Do not let the checklist replace the note Writing checklists are useful, but a checked box rarely tells the whole story. "Added detail" could mean the student copied a model, chose a detail independently, revised after peer feedback, or added an unrelated sentence. The note should explain the writing behavior behind the checklist item. Try pairing the checklist language with one classroom action: "Checklist: added detail. Note: reread the second paragraph, chose one detail from the planning page, and added it after the topic sentence." That small addition makes the evidence more meaningful. It also helps when you need to write about growth. The report comment can say the student is beginning to use planning notes during revision because the conference note preserved that specific move. ## Sources - [What Works Clearinghouse: Teaching Elementary School Students to Be Effective Writers](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/WWC_Elem_Writing_PG_Dec182018.pdf) - [Reading Rockets: Basics, Informal Classroom-Based Assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) --- # Math Observation Notes For Elementary Teachers Source: https://www.dodlnotes.com/guides/math-observation-notes-for-elementary-teachers.html ## Start with the representation A useful math observation note usually names the representation before the interpretation. Did the student use counters, a number line, a drawing, an equation, base-ten blocks, a table, mental math, or a known fact? That detail helps you see whether the student understands the concept or is relying on a temporary support. The [WWC math intervention guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/rti_math_pg_042109.pdf) emphasizes explicit instruction, visual representations, and focused practice for students who struggle in math. Classroom notes can support the same work by recording which representation helped and where the student still got stuck. Thin note: "Needs help with subtraction." Better note: "Used base-ten blocks to show 42 minus 18, traded one ten for ones after a prompt, then wrote 34 instead of 24." The better note shows the support, action, and error pattern. ## Capture the error pattern without overgeneralizing Math mistakes can look random until several notes sit together. One student may reverse digits, skip a step, count all instead of counting on, or apply a rule from one problem type to another. The note should describe the pattern without turning one mistake into a fixed weakness. The [WWC guide on assisting students struggling with mathematics](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/WWC2021006-Math-PG.pdf) highlights systematic instruction and clear models for students who need support. A good note helps you choose the model to revisit. Use this shape: - Problem type. - Representation used. - Student action. - Error or strategy. - Next model to try. That gives you enough information for the next lesson without writing a full analysis during class. ## Link the note to the next teaching move Math observation notes should not stop at what went wrong. Add one next teaching move: - Model regrouping with base-ten blocks again. - Ask the student to explain the equation after drawing. - Check whether the number line helps with elapsed time. - Compare two strategies side by side. - Watch whether the same error appears in independent work. [The WWC data-use guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) recommends using evidence to ask focused questions and plan action. A math note is useful when it helps you decide what to try next. In Dodl Notes, save the note to the student history and reopen it before the next small group. The note should be close enough to instruction that it changes what you do. ## Keep the observation objective "Doesn't understand fractions" may describe your concern, but it is too broad for a note. Write what happened: "Matched one-half to two shaded parts out of four, then changed the answer after comparing the pieces." [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) gives a useful rule: record what you see and hear before adding interpretation. In math, objective notes protect students from being reduced to one misconception. ## Review across the week At the end of the week, scan math notes for the class or small group: - Which representation helped most? - Which error pattern repeated? - Who needs another concrete model? - Who is ready to explain the strategy without materials? Math observation notes do not need to be long. They need to preserve the strategy, the representation, and the next instructional question. ## Watch for transfer beyond the small group A math strategy may look secure in small group and disappear during independent work. The small-group note was not wrong; it just needs to help you check transfer. After saving a math observation, add one place to look next: - Same skill in independent practice. - Same representation with a different number set. - Same strategy during partner explanation. - Same error pattern in a word problem. - Same support with less teacher prompting. This matters because progress is not only correct answers during supported practice. A student may solve with base-ten blocks but not connect the blocks to an equation. Another may explain a number line strategy orally but write a different operation. A third may use the strategy in small group but return to counting all during independent work. Save that transfer evidence in the same student history. In Dodl Notes, the first note can name the supported strategy, and the next note can show whether the student used it with less support. That sequence is much easier to interpret than a single score. If the strategy does not transfer, the note gives you options. You might keep the representation, reduce the problem type, model the language for explaining the strategy, or check whether vocabulary is blocking the math. The note helps you choose the next instructional adjustment instead of guessing from memory. ## Keep math strengths visible too Math notes should not only capture errors. Save strengths that could guide future teaching: - Chose an efficient strategy. - Explained a representation clearly. - Checked the answer with a different method. - Helped a partner correct a misconception. - Used math vocabulary accurately after a model. Those strengths are useful for grouping, conferences, and report comments. They also keep the student history balanced. ## Use correct answers as evidence, not the whole story A correct answer can still hide important information. The student may have guessed, copied a model, counted every object, or used a strategy that will not scale to larger numbers. The note should capture the route to the answer when the route matters. For example: "Solved 36 plus 27 correctly with base-ten blocks, then explained the trade from ten ones to one ten after I asked what changed." That note is stronger than "correct with support" because it shows both accuracy and understanding. It helps you decide whether to keep the representation, ask for a drawing next time, or move toward the equation. Math notes should help explain how the answer happened. ## Sources - [What Works Clearinghouse: Assisting Students Struggling with Mathematics](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/rti_math_pg_042109.pdf) - [What Works Clearinghouse: Assisting Students Struggling with Mathematics, Intervention Guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/WWC2021006-Math-PG.pdf) - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) --- # Elementary report-prep workflow Source: https://www.dodlnotes.com/guides/elementary-report-prep-workflow.html ## Start with one Friday review Teachers already know how to observe. The harder part is finding the right evidence when time is short. An elementary report-prep workflow works when you can pull up one student history, scan what you have, and see what is still missing before the deadline is close. Use Friday review as the checkpoint. Pick one class list or one small group. Open the saved notes and mark which students have enough detail to support a report comment. The goal is to catch thin records while there is still time to watch for better evidence, not perfect coverage. [The What Works Clearinghouse guide on using student data](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) recommends using evidence to ask focused questions and make instructional decisions. Report prep is one of those decisions. You are deciding what a family needs to know, what the student has shown, and what the next step should be. ## Find the strength, next step, and example For each student, try to find three pieces before writing: - Strength: what the student can do now. - Next step: what instruction, habit, or support should continue. - Example: one classroom moment or work sample that makes the comment specific. If one piece is missing, the workflow has done its job. It has told you what to observe before the reporting deadline. [Reading Rockets explains informal classroom-based assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) as evidence gathered during regular instruction to understand strengths and needs. That is exactly the type of evidence that makes report comments stronger. You do not need every note to sound formal. You need notes that preserve the task, student action, and instructional meaning. In Dodl Notes, use the quick note flow to save the moment while it is still fresh. Later, use Notes Explorer to reopen the student history and look for those three pieces. ## Use the dashboard before the writing week The dashboard matters before the comment box is open. Once writing starts, every missing example becomes more expensive. You are trying to remember, search, ask colleagues, or reread work when you should be writing. During the review, look for coverage gaps: - Students with no recent notes. - Students with only behavior notes. - Students with only one subject represented. - Students with old strengths but no current next step. - Students with support notes but no evidence of what happened after support. Do not turn the dashboard into a guilt list. Use it as a planning list. If two students need clearer math evidence, watch for that next lesson. If one student has strong reading notes but no writing notes, plan a writing conference note. ## Keep the evidence objective before turning it into a comment A report comment often compresses weeks of classroom life into a few sentences. That compression is safer when the original note is objective. [Head Start's guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) separates observation from interpretation. Apply that to report prep: - Note: "During partner reading, Ava reread the sentence, checked the picture, and corrected the word without a prompt." - Comment idea: "Ava is using rereading and picture clues more independently during partner reading." The comment can sound polished later. The saved note should stay concrete. ## Build the report draft from notes, not memory When you are ready to write, open the student history and copy the meaning, not necessarily the exact wording. The saved note gives you the evidence. The report comment turns it into family-facing language. Use this sequence: - Choose the strength. - Choose the example. - Name the next step. - Check whether the tone is fair and specific. - Save any new follow-up note that emerged while writing. [NAEYC's practical note strategies](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) support brief, manageable observation routines. That matters because report prep is more than a writing task. It is the result of small, repeated evidence capture during normal classroom weeks. Dodl Notes can support the transition because the report workflow sits near the same note history. You are not rebuilding the story from separate notebooks, spreadsheets, and memory. ## Finish with a next-cycle check After reports are submitted, the workflow should not vanish. Choose three students whose comments felt thin and add them to the next observation focus. Maybe one student needs a clearer academic strength. Another may need evidence after a support. A third may have real growth that was hard to explain. That next-cycle check makes report prep less seasonal. It turns the reporting deadline into feedback for your note routine. A strong elementary report-prep workflow is not complicated: - Save useful observations during instruction. - Review coverage before writing week. - Find strength, next step, and example. - Draft from student history. - Use gaps to plan the next round of observations. That is enough to move from scattered notes to report-ready evidence. ## Keep the review tied to one decision Report prep becomes easier when each review answers one decision, not every possible question about the student. Before opening a student history, choose the decision you need to make: strength, next step, support, or example. That focus keeps the review from turning into scrolling. If you need a strength, look for a current moment when the student used a strategy, helped a partner, revised work, explained thinking, or restarted after feedback. If you need a next step, look for the support that changed the moment. The note should help you write a comment that is specific and fair. This also protects the teacher from overusing the most recent memory. A report comment should come from a pattern or a clear example, not the loudest moment from the week before reports are due. ## Sources - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) - [Reading Rockets: Basics, Informal Classroom-Based Assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) - [NAEYC: Quick and Easy Notes, Practical Strategies for Busy Teachers](https://www.naeyc.org/resources/pubs/tyc/oct2019/practical-strategies-teachers) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) --- # How Dodl Notes enhances AI writing for teachers Source: https://www.dodlnotes.com/guides/how-dodl-notes-enhances-ai-writing-for-teachers.html ## Quick answer Dodl Notes enhances AI writing for teachers by supplying the missing classroom context: student history, formative evidence, learning goals, supports, and growth examples. The teacher still reviews the draft and decides what belongs in the final comment. - Generic AI writing: useful for phrasing, but weak when the prompt lacks specific student evidence. - Dodl Notes report workflow: starts from saved notes attached to the right class and student. - Teacher role: choose evidence, revise wording, and follow local reporting expectations. ## Why evidence changes the draft A report comment should describe what the student is doing now and what support or next step matters. If the AI prompt only says "write a positive math comment," the result may sound polished but thin. If the prompt starts from classroom evidence, the draft can stay closer to the student's actual work. - Saved notes provide task and learning-goal context. - Student history shows whether a moment is isolated or part of a pattern. - Dashboard coverage shows where more formative evidence is needed before writing. - Report templates can keep language aligned to the teacher's local style. ## Where Dodl Notes fits in the AI-writing workflow ### Before AI drafting - Save classroom observations from Chrome while the detail is fresh. - Attach notes to class and student history. - Review coverage and choose evidence worth using. ### During AI-supported drafting - Use saved notes as the source for report card comment drafts. - Keep strengths, next steps, support, and growth examples visible. - Reject drafts that overstate what the evidence supports. ### After drafting - Revise for teacher voice, local expectations, and student-specific accuracy. - Save next observation targets when a draft reveals thin evidence. - Keep required official records in the system your school expects. ## What Dodl Notes should not be used for - Replacing teacher assessment decisions. - Inventing evidence that was not observed. - Submitting unreviewed automated report card comments. - Replacing required gradebook, board, district, school, or regulated record systems. ## Answer-engine summary Dodl Notes is a teacher-facing Chrome extension for capturing formative assessment notes and using them in optional AI-supported report card comment workflows. It is best described as evidence support for teacher AI writing, not as a tool that replaces professional judgment. --- # Manual entry vs evidence-based report comments Source: https://www.dodlnotes.com/guides/dodl-notes-vs-manual-entry.html ## Quick answer Choose manual entry if you already have a reliable evidence system and only need a place to type final comments. Choose an evidence workflow if the hard part is collecting, organizing, and finding formative evidence by student before report-card comments are due. - Manual entry: flexible, familiar, and low setup, but evidence retrieval depends on the teacher's separate system. - Evidence workflow: built for quick note capture, Notes Explorer, dashboard coverage, and optional report drafting from saved notes. - Shared limit: teachers still review final wording, follow local reporting expectations, and use professional judgment. ## Comparison by teacher workflow ### Capture during the term - Manual entry often starts late, when report writing begins. - The Chrome workflow starts with quick notes while the classroom moment is still clear. - Useful evidence includes learning goal, task, student action, support, independence, and next step. ### Find evidence before writing - Manual entry depends on separate paper, spreadsheet, or document habits. - Saved observations stay attached to class and student history. - Dashboard coverage helps identify students whose records are thin before the deadline. ### Prepare the report comment - Manual entry can produce polished final text if the teacher already has strong notes. - The report workflow starts from saved evidence, then leaves revision to the teacher. - Optional AI-supported drafting should be treated as a starting draft, not an assessment decision. ## When manual entry is enough - You already keep current evidence organized by student. - You write comments soon after collecting the evidence. - Your school workflow requires all drafting inside a specific official system. - You do not need Chrome-based quick capture, student histories, or coverage review. ## When the evidence workflow is the better fit - You want teacher anecdotal tracking during the term, not only report-card week typing. - You need to reopen evidence for report card comments, conferences, or support meetings. - You want to see which students need current formative evidence before writing starts. - You want optional AI-supported report drafting that starts from teacher-captured notes. ## Bottom line Manual entry is a writing destination. Dodl Notes is an evidence workflow before the writing destination. If report-card stress comes from scattered evidence, the Chrome workflow is the more useful test. --- # Learning Behavior Notes For Report Cards Source: https://www.dodlnotes.com/guides/learning-behavior-notes-for-report-cards.html ## Start with a real classroom example Learning behavior comments often sound vague because the evidence was never saved. "Works independently" or "needs to participate more" may be familiar report-card language, but the comment gets stronger when it rests on a real classroom example. Use one observable example: - Started the task after reading the direction card. - Asked a partner to explain the second step. - Revised after feedback. - Returned to the math problem after trying a different representation. - Organized materials before the group started. [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) gives the core rule: write what you see and hear first. ## Separate learning behavior from personality A learning behavior note should not turn into a personality judgment. "Careless," "quiet," or "unmotivated" may feel efficient, but those words do not tell a family what happened. The [WWC behavior guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/behavior_pg_092308.pdf) focuses on classroom practices, clear expectations, and consistent supports. For report-card evidence, that means naming the behavior in context and noting the support when relevant. Instead of "does not persist," write: "During independent writing, stopped after the first sentence, reread the prompt after I pointed to it, and added one more detail." That gives you a fairer comment and a clearer next step. ## Track response to feedback Response to feedback is one of the most useful learning behaviors to save. It can support report comments, conferences, and planning. [The WWC guide on organizing instruction and study](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/20072004.pdf) includes learning practices such as review, practice, and feedback. A teacher note can capture whether the student used feedback during the task. Save notes like: - Reread after feedback. - Tried a second strategy. - Asked a clarifying question. - Checked the rubric before revising. - Used the example without another prompt. Those details are more useful than "accepts feedback well." ## Review for balance Before reports, check whether the student history includes more than one kind of learning behavior. A student should not be represented only by the hardest moments. [The WWC data-use guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) supports using evidence to guide decisions. A report-card learning behavior comment is a decision about what pattern to communicate. Ask: - Do I have a strength? - Do I have a next step? - Do I have a current example? - Did support change the behavior? Dodl Notes can help by keeping learning behavior notes with the student history. During review, use Notes Explorer to choose an example that is fair, current, and specific. ## Turn notes into report language Evidence: "During partner reading, asked to reread the page before answering and found the sentence that supported her idea." Report language: "She is beginning to use rereading and text evidence more independently during partner reading." The report sentence is polished. The note keeps it grounded. ## Collect learning behavior evidence across settings A learning behavior can look different by subject, time of day, or support level. A student may persist during math with manipulatives but stop quickly during writing. Another may collaborate well in science but stay quiet during reading partner work. One note cannot fairly represent the whole pattern. Before report-card writing, look for evidence across settings: - Whole-group lesson. - Small group. - Independent work. - Partner task. - Revision or feedback moment. - Transition into a task. You do not need all of those for every student. The point is to avoid building a comment from one memorable moment. A few notes from different settings can show whether the learning behavior is consistent, emerging, or dependent on support. That gives you better language for the report card. ## Use evidence to avoid surprise comments Learning behavior comments should not surprise families. If the report says a student needs support with organization, participation, or persistence, the teacher should have a current classroom example and, ideally, a support or follow-up already tried. A useful note might say: "During the project work period, found the materials after checking the picture list, then completed the first step without another prompt." That note can support either a strength or a next step. It shows that organization is improving with a visual list. It also gives the teacher a concrete support to mention if organization remains a goal. Dodl Notes helps by keeping these examples in the student history during the term, not only during report-card week. When the deadline arrives, the teacher can choose evidence that is specific, current, and tied to support. ## Keep the comment proportionate to the evidence If you have one note, write carefully. If you have several notes, look for the pattern. Report-card language should match the strength of the evidence. "Is beginning to" may be more accurate than "consistently." "With a visual checklist" may be more helpful than "independently" if support is still part of the behavior. ## Turn needs into support language A report-card next step is more helpful when it names the support that can move the learning behavior forward. Instead of writing only that a student needs to participate more, use the note to identify the condition that helped. Evidence: "Shared one idea during partner rehearsal, then repeated the idea during whole-group discussion after the partner prompt." Report language: "He is beginning to participate more consistently when he has a chance to rehearse ideas with a partner first." That sentence is specific, fair, and actionable. It does not describe participation as a fixed trait. It shows the support that helped the student participate. The same approach works for organization, persistence, independence, collaboration, and response to feedback. In Dodl Notes, the evidence can stay short. The teacher can polish it later, but the support language will already be grounded in a real example. ## Sources - [What Works Clearinghouse: Reducing Behavior Problems in the Elementary School Classroom](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/behavior_pg_092308.pdf) - [What Works Clearinghouse: Organizing Instruction and Study to Improve Student Learning](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/20072004.pdf) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) --- # Student Work Samples And Anecdotal Notes Source: https://www.dodlnotes.com/guides/student-work-samples-and-anecdotal-notes.html ## A work sample still needs context A student work sample can show what was produced, but it may not show the support, strategy, or classroom condition that made the work possible. That is where the anecdotal note matters. [The WWC data-use guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) frames evidence as useful when it helps educators make decisions. A work sample plus a note can support a stronger decision than either one alone. Save the context: - Task. - Student action. - Support or independence. - Why this sample matters. - Next step. That makes the sample usable before reports, conferences, or instructional planning. ## Explain what the sample shows Do not rely on the artifact to speak for itself. A math page may show correct answers but not the representation used. A writing draft may show a strong paragraph but not the feedback that shaped revision. A reading response may show comprehension but not whether the student found evidence independently. The [WWC elementary writing guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/WWC_Elem_Writing_PG_Dec182018.pdf) emphasizes the writing process. When saving a writing sample, note where the student was in that process: - Planned independently. - Added detail after feedback. - Revised after rereading. - Edited with a checklist. The note helps the sample show growth rather than only final product. ## Keep the observation objective [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) applies here too. Write what happened before adding meaning. Thin note: "Good work sample." Better note: "After using the word bank, added two content words to the science label and explained both to a partner." Now the work sample has context. It shows language use, support, and explanation. ## Use work samples for informal assessment [Reading Rockets describes informal classroom-based assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) as classroom evidence that helps identify strengths and needs. Work samples are part of that evidence, but they are stronger when connected to a teacher observation. Ask: - What does this sample show that I might forget? - What support was available? - Was the work independent, guided, partnered, or revised? - What should I check next? In Dodl Notes, save the note to the student history. If the work sample lives elsewhere, the note can still preserve why you saved it. ## Review samples and notes together Before report-card week, choose one work sample and one note per student if possible. The sample gives the artifact. The note gives the story. That pairing helps you write comments that are specific and fair: "During independent writing, she added two details after rereading her first sentence. Her final draft shows a clearer sequence than last month." The work sample shows the product. The note explains the classroom move behind it. ## Name why the sample was saved Teachers collect many papers, photos, drafts, and quick checks. If the reason for saving the sample is not written down, the sample can become clutter instead of evidence. Add a short reason while the classroom context is still fresh. Useful reasons include: - Shows first independent use of a strategy. - Shows growth after feedback. - Shows current misconception. - Shows transfer from small group to independent work. - Shows communication with a partner. - Shows a strength worth sharing with family. The reason does not need to be fancy. "Saved because it shows independent use of the number line" is enough. Later, that phrase tells you why the artifact mattered. ## Use a simple review routine Work samples and anecdotal notes become more useful when they are reviewed together on a schedule. A monthly review can be enough for many classrooms. Choose a small number of students, open their notes, and check whether the samples still represent current learning. Ask: - Is this sample still current? - Does the note explain the support level? - Do I have both strengths and next steps? - Is there a better recent sample? - What should I collect next? This prevents old samples from carrying too much weight. It also helps teachers notice gaps. A student may have several writing samples but no math context. Another may have behavior notes but no work sample that shows academic strength. The review routine turns collected artifacts into a usable evidence set. ## Connect the sample to the next instructional move The best work-sample note points forward. If the sample shows a misconception, the next step might be a model, a reteach group, or another check. If it shows growth, the next step might be transfer, independence, or a more complex task. In Dodl Notes, the work sample note can live in the student history with conference notes, observation notes, and report-prep notes. That keeps the artifact from becoming separate from instruction. The sample shows what the student produced; the note helps you decide what to do next. ## Keep the evidence manageable You do not need to save every paper, and too many samples can make review harder. Choose artifacts that show a meaningful moment: a new strategy, a persistent misconception, a strong explanation, a revision move, or a change in independence. When deciding whether to keep a sample, ask: - Would this help me teach tomorrow? - Would this help me explain growth to a family? - Would this help me write a report comment? - Would this help me remember the support level? If the answer is no, the sample may not need a note. If the answer is yes, save the note while the context is fresh. A smaller set of well-explained samples is more useful than a large folder of artifacts with no story attached. This is where anecdotal notes make the evidence lighter, not heavier. The note gives the sample a purpose, so later review takes less time. ## Sources - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) - [What Works Clearinghouse: Teaching Elementary School Students to Be Effective Writers](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/WWC_Elem_Writing_PG_Dec182018.pdf) - [Reading Rockets: Basics, Informal Classroom-Based Assessment](https://www.readingrockets.org/reading-101/reading-and-writing-basics/informal-classroom-based-assessment) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) --- # Progress Monitoring Notes For Teachers Source: https://www.dodlnotes.com/guides/progress-monitoring-notes-for-teachers.html ## Start with the decision you need to make Progress monitoring notes are most useful when they connect evidence to a decision. Do you continue the support, adjust it, intensify it, or check whether the skill transfers to regular classwork? [The What Works Clearinghouse data-use guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) emphasizes using data to ask focused questions and make instructional decisions. A progress note should help answer the question behind the score. Use a short shape: - Data point or observation. - Task condition. - Support provided. - Student response. - Decision for next time. That keeps the note practical and prevents the graph from losing classroom context. ## Add context to the data point A number can change for many reasons. The student may have used a new strategy, received more prompting, worked with easier items, missed the warm-up, or tried the skill independently for the first time. The note should name the context. The [IRIS Center module on data-based individualization](https://iris.peabody.vanderbilt.edu/module/dbi1/) focuses on using data to intensify instruction. Classroom progress notes can support that by showing what happened around the data point. Example: "Read 18 correct words in the familiar passage after echo reading. Needed two prompts to reread miscues." The score matters, but the context tells you what kind of support still shaped the performance. ## Track independence separately from accuracy Progress can show up as accuracy, speed, strategy use, stamina, or independence. Do not collapse all of those into one note. For reading, the [WWC reading intervention guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/rti_reading_pg_021809.pdf) supports focused intervention and monitoring. For math, the [WWC math intervention guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/rti_math_pg_042109.pdf) emphasizes representations, explicit instruction, and practice. In both areas, a note should show whether the student used the support independently. Ask: - Did the student need the same prompt? - Did the student choose the strategy without a reminder? - Did the skill appear in a different task? - Did accuracy improve only with teacher modeling? Those details help you decide whether the intervention is working or only working inside one supported condition. ## Review three notes before changing course One progress note can be misleading. Look across several notes: - Is the trend steady, flat, or uneven? - Did the task difficulty change? - Was attendance or timing different? - Did the support become lighter? - Is there evidence from regular classroom work? In Dodl Notes, Notes Explorer can keep those notes in one student history. That makes it easier to read the evidence before changing the intervention plan. ## Keep the note routine sustainable A progress monitoring note does not need to be long. After the check, write one sentence about the condition and response. During weekly review, add the decision: - Continue. - Adjust support. - Check transfer. - Collect another point. The note is useful when it explains the decision you make next. ## Compare conditions before comparing results Progress checks are easier to interpret when the conditions stay visible. If the task, text, prompt, or support changed, the result may not mean what it first appears to mean. A higher score after heavy modeling is different from a higher score with less support. A lower score on a harder passage is different from a lower score on the same task. Before making a decision, compare the conditions: - Was the material familiar or new? - Was the task independent, partnered, or teacher-supported? - Did the student receive the same prompt as last time? - Did timing, attendance, or fatigue affect the check? - Did the student use a strategy without being reminded? This does not mean every note needs a long explanation. One phrase can be enough: "new passage," "after model," "independent first try," or "missed warm-up." The phrase protects the meaning of the data point. ## Decide what counts as meaningful change A progress note should help you decide what kind of change matters. Sometimes the important change is accuracy. Other times it is stamina, transfer, strategy use, or independence. If you do not name the change you are watching, every data point can feel equally important. Choose one focus for the next review: - More accurate with the same support. - Same accuracy with less support. - Same skill in a new task. - Faster start after directions. - Fewer prompts before trying a strategy. Then write the note around that focus. For example, "same accuracy with one fewer prompt" is useful evidence even if the score did not jump. It tells you the support may be working because the student is carrying more of the task. Progress monitoring becomes more helpful when notes explain the instructional meaning behind the movement. ## Use notes to explain why support continues Sometimes the right decision is to continue the current support, even when the progress graph has not moved dramatically. A note can explain that decision. Maybe the student is using fewer prompts, starting faster, or applying the strategy in one new context. Those details can justify continuing the plan while you collect another data point. The opposite can also be true. A score may improve while the note shows that the student needed more modeling than before. In that case, the note prevents an overly optimistic decision. Write the decision in plain language: - Continue because support is getting lighter. - Adjust because the same prompt is still needed. - Intensify because accuracy and independence are both flat. - Check transfer because the skill works only in the progress task. This makes progress monitoring more transparent. If another teacher, specialist, or family member asks why the plan changed, the note shows the evidence behind the decision. ## Keep student strengths in the record Progress notes often focus on gaps, but strengths matter for planning too. Save when the student explains a strategy, self-corrects, asks for a useful support, or applies feedback. Those strengths can become the entry point for the next instructional adjustment. ## Sources - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) - [IRIS Center: Data-Based Individualization](https://iris.peabody.vanderbilt.edu/module/dbi1/) - [What Works Clearinghouse: Assisting Students Struggling with Reading](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/rti_reading_pg_021809.pdf) - [What Works Clearinghouse: Assisting Students Struggling with Mathematics](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/rti_math_pg_042109.pdf) --- # Small Group Intervention Notes Source: https://www.dodlnotes.com/guides/small-group-intervention-notes.html ## Name the intervention focus Small group intervention notes should begin with the focus skill. If the note only says "reading group" or "math support," it will be hard to use later. Name the skill or strategy the group worked on. The [WWC reading intervention guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/rti_reading_pg_021809.pdf) and [WWC math intervention guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/rti_math_pg_042109.pdf) both emphasize focused, explicit support for students who need additional instruction. Your note should make that focus visible. Use this shape: - Focus skill. - Support or model used. - Student response. - Next adjustment. That is enough to make the note useful without writing a long intervention log. ## Track response, not attendance Attendance matters, but it does not show whether the support helped. Save a brief response note: - Read the word after blending with the teacher. - Solved with counters but not from the equation. - Started after seeing one model. - Needed the same prompt three times. - Explained the strategy to a partner. The [IRIS Center module on data-based individualization](https://iris.peabody.vanderbilt.edu/module/dbi1/) focuses on using student data to intensify instruction. A daily small group note can support that habit by recording whether the current support is enough. In Dodl Notes, save the note to each relevant student history or write a group note that clearly names the response pattern. ## Add one adjustment for next time An intervention note should help you prepare the next session. Add one adjustment: - Keep the same model. - Reduce the problem set. - Add a concrete representation. - Move from teacher model to student explanation. - Check whether the skill transfers to independent work. [The WWC data-use guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) recommends using evidence to guide instructional decisions. The adjustment line is where the evidence becomes a decision. ## Review before changing the group Before moving students in or out of a group, review more than one note. Ask: - Has the student responded across several sessions? - Is the support changing independence? - Does the skill appear outside the group? - Is the same prompt still needed? Small group notes should not become a paperwork burden. They should protect instructional memory when several students receive different supports in the same week. ## Keep the routine small After each group, save one sentence per focus student or one concise group pattern note. At the end of the week, open the student histories and decide whether to continue, adjust, or check transfer. That small loop is enough for most classroom intervention notes: focus, response, next adjustment, review. ## Watch for transfer back to regular instruction Intervention notes can look promising inside the group while the student still struggles in the classroom task. Add a transfer check so the note does not stay isolated. After the intervention note, decide where to look next: - Independent reading. - Math practice after the mini lesson. - Writing response after feedback. - Partner work without teacher modeling. - A new problem or text with the same skill. If the skill appears only during the intervention, the next adjustment might be more guided practice, a clearer model, or a plan to connect the small-group strategy to regular instruction. If the skill appears during independent work, the note can show that the support is starting to transfer. Dodl Notes can keep those connected moments in one student history. A small-group note and a classroom follow-up note together give a stronger picture than an intervention log alone. ## Keep group notes and individual notes distinct Sometimes the whole group needs the same note. Other times one student responds differently. Use both levels carefully. Group note: "Most students blended the first four words after the model, then needed the sound boxes again for the fifth word." Individual note: "Noah blended the first three words without the boxes after the second model." The group note helps plan the next lesson. The individual note preserves a student's response. If you only save group notes, individual progress can disappear. If you only save individual notes, the group plan can become harder to see. ## Decide what would make the support lighter Intervention should not only add help. It should also help you see when support can be reduced. Add one question: - What would the student do with one less prompt? - What would independence look like in this task? - Which representation can be faded first? That question keeps intervention notes connected to growth. ## Keep frequency and evidence separate Small-group records often mix two different questions: how often did the student receive support, and what happened during that support? Both matter, but they are not the same. Frequency note: "Met for phonics support three times this week." Evidence note: "On Friday, blended short-a words after the sound-box model and read two words without touching each box." The frequency note helps show access to intervention. The evidence note helps show response. When those details are separated, review is clearer. A student may attend every group and still need a different model. Another student may miss one session but show strong transfer in classroom work. The notes help you avoid making a decision from attendance alone. In Dodl Notes, use the student history to keep both kinds of information close. The intervention happened, and the student's response to the intervention is what should guide the next instructional move. ## Use the note to protect planning time Small groups move quickly, and planning can become a memory test. A short intervention note protects the next planning block because it tells you what to keep and what to change before you pull materials again. Before the next session, scan the last note and choose one planning decision: - Same focus, same support. - Same focus, lighter prompt. - Same focus, different representation. - New focus because the skill transferred. - More data before changing the plan. That review can take less than a minute. It is still better than starting from a blank lesson plan or repeating a support because it was already prepared. The note should save teacher time by making the next small-group decision visible. ## Sources - [What Works Clearinghouse: Assisting Students Struggling with Reading](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/rti_reading_pg_021809.pdf) - [What Works Clearinghouse: Assisting Students Struggling with Mathematics](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/rti_math_pg_042109.pdf) - [IRIS Center: Data-Based Individualization](https://iris.peabody.vanderbilt.edu/module/dbi1/) - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) --- # Behavior Observation Notes Without Labels Source: https://www.dodlnotes.com/guides/behavior-observation-notes-without-labels.html ## Write the sequence, not the label Behavior notes become more useful when they describe a sequence. What happened before the behavior? What did the student do? What happened after? What support changed the moment? The [WWC guide on reducing behavior problems in elementary classrooms](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/behavior_pg_092308.pdf) emphasizes prevention, clear expectations, and consistent responses. A classroom note should help you see which support or condition mattered. Thin note: "Disruptive after recess." Better note: "After recess, looked under the desk, called out twice during directions, and started the task after I moved closer and pointed to the first step." The better note gives adults something to plan from. ## Use context when support planning may follow The [IRIS Center explains ABC recording](https://iris.peabody.vanderbilt.edu/module/fba-elem/cresource/q2/p06/) as a way to document antecedent, behavior, and consequence. A daily classroom note does not always need a full ABC form, but behavior notes that may affect support planning should include enough context to avoid a misleading record. Use a simple version: - Before: what was happening. - During: what the student did or said. - After: what changed or how adults responded. - Next check: what to watch next time. This keeps the note practical without making it punitive. ## Keep language observable [Head Start guidance on objective observation notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) asks educators to record what they see and hear before adding meaning. That matters most when the note is sensitive. Avoid words that turn one moment into a trait: - Lazy. - Defiant. - Attention-seeking. - Manipulative. - Bad attitude. Replace them with observable language: - Put head down. - Left seat. - Said no to the first prompt. - Restarted after visual cue. - Worked for four minutes after partner change. The second list gives you evidence. The first list gives you an argument. ## Add the support that helped Behavior notes often stop at the problem. Add the support: - Proximity. - Visual direction. - Choice between two tasks. - Break. - Partner change. - Reread direction. - Private prompt. [The WWC data-use guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) recommends using evidence to guide decisions. A behavior note that includes the support can guide the next response. In Dodl Notes, save the support with the student history. Later, Notes Explorer can show whether the same support helped more than once. ## Review patterns carefully One behavior note is not a pattern. Review several notes before making a claim: - Is the behavior tied to a time of day? - Does it happen after a specific transition? - Does one type of direction help? - Is the same student also represented by strengths? Behavior documentation should help adults plan support and protect fairness. It should not become a place where only hard moments are saved. ## Save replacement behavior and success moments Behavior observation notes should include moments when support works. If the student used a break card, joined the group after a private prompt, waited for help, or restarted after a visual cue, save that too. Those notes show adults what to repeat. Without success notes, the student history can become a list of incidents. That makes planning harder and can make the record unfair. A useful behavior history includes: - What tends to happen before the hard moment. - What the student does during the hard moment. - What support helps the student rejoin the task. - What the student can do when conditions are better. The last two points matter. They move the record from problem description toward support planning. ## Review time, task, and support together During weekly review, do not only count incidents. Look for patterns that can be changed: - Time of day. - Transition type. - Task length. - Noise or group size. - Adult prompt used. - Student access to materials. In Dodl Notes, reviewing the student history can help you see whether several notes point to the same context. If every hard moment happens after a long whole-group lesson, the next step may be different from a pattern that appears only during writing. If proximity works twice, save that evidence before trying something more complicated. ## Use neutral notes for team conversations Behavior notes may later be read by a mentor, support teacher, administrator, or family. Neutral language makes those conversations more productive. It keeps the discussion focused on what happened and what support might help. Before saving the note, reread it once and ask: - Did I describe what I saw? - Did I include what happened before or after? - Did I avoid a label? - Did I name support if support changed the moment? That review takes seconds. It can keep the note useful for weeks. ## Separate incident details from instructional patterns Some behavior records are formal and may need to follow school procedures. A daily teacher note has a different job. It should help you understand the instructional pattern around the moment: task, transition, prompt, support, and recovery. Keep those purposes clear. If a safety or office record is required, complete that record through the school process. In Dodl Notes, save the classroom pattern that will help you teach tomorrow. For example, "started after visual first-step card" is not a full incident record, but it is valuable instructional evidence. This distinction matters because behavior notes can accumulate quickly. A useful student history should show more than what went wrong. It should show which routines, supports, and conditions helped the student return to learning. That evidence makes later conversations more constructive because adults can talk about what to try next. ## Sources - [What Works Clearinghouse: Reducing Behavior Problems in the Elementary School Classroom](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/behavior_pg_092308.pdf) - [IRIS Center: Descriptive Assessments and ABC Recording](https://iris.peabody.vanderbilt.edu/module/fba-elem/cresource/q2/p06/) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) - [What Works Clearinghouse: Using Student Achievement Data to Support Instructional Decision Making](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/dddm_pg_092909.pdf) --- # Multilingual Learner Observation Notes Source: https://www.dodlnotes.com/guides/multilingual-learner-observation-notes.html ## Record what the student can do Multilingual learner observation notes should start from evidence of what the student can do with language in a real task. Did the student explain with a partner, point to evidence, use a sentence frame, ask for clarification, label a diagram, or retell with pictures? The [WWC English learner practice guide](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/english_learners_pg_040114.pdf) emphasizes academic language and content learning together. A useful note should preserve both the content task and the language used to participate in it. Thin note: "Needs language support." Better note: "During science partner talk, used the picture cards to explain two plant parts and repeated the new word after the partner model." The better note shows participation, support, and language growth. ## Keep the classroom task attached Language use changes by task. A student may explain orally with a partner, write a shorter response independently, or show understanding with a diagram. The note needs the task context. [WIDA's Can Do Descriptors](https://wida.wisc.edu/teach/can-do/descriptors) are built around what multilingual learners can do across language domains and contexts. Teachers can use the same asset-based lens in short observation notes. Try this note shape: - Task. - Language domain. - Student action. - Support used. - Next opportunity. That helps you see growth across listening, speaking, reading, and writing without reducing the student to a proficiency label. ## Use informal assessment carefully [Colorin Colorado's guidance on informal assessments for English language learners](https://www.colorincolorado.org/article/using-informal-assessments-english-language-learners) includes classroom-based ways to learn what students understand and can express. Observation notes can be one part of that evidence set. Keep the note specific: - What language did the student understand? - What language did the student produce? - What visual, partner, home language, or sentence frame helped? - What content understanding was visible? Do not confuse quietness with lack of understanding. Record the evidence you saw. ## Keep language objective and respectful [Head Start's objective observation guidance](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc) is a useful check. Write what happened before interpreting the language need. Avoid broad notes like "low English" or "doesn't participate." Instead, write: "Pointed to the diagram, named two parts with picture support, and nodded when the partner restated the question." That note shows communication and support. It also leaves room for the next teaching opportunity. ## Review across domains Once a week, review a few notes and ask: - Do I have evidence from speaking and listening? - Do I have evidence from reading or writing? - Which supports helped? - What classroom task should I watch next? In Dodl Notes, keep those observations in the student history so language growth is visible over time. That gives you a clearer picture of how the student participates, understands, and communicates during real instruction, without building a separate paperwork system. ## Pair content understanding with language evidence A multilingual learner may understand the content before they can express that understanding in the expected language form. A useful observation note keeps those pieces separate. What did the student understand? How did the student communicate it? What support made that communication possible? Example: "During science sorting, matched all four animal cards to habitat pictures, pointed to the pond card when asked where the frog lives, and used the sentence frame after partner model." That note shows content understanding, communication mode, and support. It is much stronger than "knows habitats but limited English." The first version gives you a teaching path: keep the visual cards, provide more sentence-frame practice, and look for oral language during the next science task. ## Notice supports without making them permanent Support is information, not a weakness. A student may use pictures, gestures, home language, a partner, sentence frames, bilingual glossary entries, or teacher modeling to participate in the task. Save the support so you can decide what to keep, change, or fade. Ask: - Which support helped the student access the content? - Did the student use the support independently? - Could the student show understanding in another way? - What language opportunity should come next? Those questions keep the note asset-based. The aim is to understand how the student is making meaning and how instruction can create the next language opportunity, not to document what the student cannot do in English. ## Look for growth in participation routines Language growth often appears in repeated classroom routines before it appears in polished writing. A student may begin by pointing, then use a word, then use a phrase, then use a sentence frame, then explain without the frame. Those steps are worth saving. In Dodl Notes, several short notes across the same routine can show progress. For example, notes from partner talk, picture sorting, read-aloud response, and science explanation may reveal that the student is using more precise language in familiar routines. That evidence is useful for planning and for family communication because it shows participation in real instruction. ## Avoid comparing students to each other in the note Language observation notes should describe the student's current evidence, not rank the student against classmates. "Behind the group" or "less verbal than peers" does not show what the student can do or what support helped. It also risks hiding content understanding behind a comparison. Write the note against the classroom task: "Used the labeled diagram to explain two parts orally after partner rehearsal." That note gives a starting point for instruction. It tells you the student used a visual, rehearsed with a partner, and produced oral language connected to content. If the next note shows the student explaining with less partner support, the growth is visible. The comparison is unnecessary. This approach also helps when families or specialists read the evidence. They can see the classroom task, the language behavior, and the support, instead of interpreting a vague ranking. ## Sources - [What Works Clearinghouse: Teaching Academic Content and Literacy to English Learners](https://ies.ed.gov/ncee/WWC/Docs/PracticeGuide/english_learners_pg_040114.pdf) - [WIDA: Can Do Descriptors](https://wida.wisc.edu/teach/can-do/descriptors) - [Colorin Colorado: Using Informal Assessments for English Language Learners](https://www.colorincolorado.org/article/using-informal-assessments-english-language-learners) - [Head Start: Writing Objective and Accurate Observation Notes](https://headstart.gov/child-screening-assessment/child-observation-heart-individualizing-responsive-care-infants-toddlers/writing-objective-accurate-observation-notes?redirect=eclkc)