# Analyzing Student Work Together (Workshop) > A ready-to-run PD workshop on using protocols to analyze student work in teams. Run-of-show, handout, follow-up. *A ready-to-run professional learning workshop from K12 Academics. Source page: https://pd.k12academics.com/analyzing-student-work-workshop.html* Some of the most powerful team PD is simply looking closely at student work together, with a protocol that keeps it focused and non-defensive. Analyzing student work surfaces what students actually understand, and what to teach next, better than scores alone. Looking closely at real student work together, with a structured protocol, surfaces what students actually understand and what to teach next, more richly than scores alone. ## Why it works Structured protocols for looking at student work, teams examining actual student responses together using a clear process, help teachers see what students genuinely understand, uncover misconceptions, calibrate expectations, and decide what to teach next. Research on this practice links it to improved instruction and teacher learning. The protocol matters: it keeps the conversation focused on the work and evidence rather than defensive or vague. **The research:** Research on looking at student work; protocols from the School Reform Initiative. ## The run-of-show ### Staff meeting (15 minutes) A fast introduction to plant one routine. **Goal:** everyone leaves with one thing to try. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | 0:00 | 3 min | Hook | When did you last look closely at student work with colleagues? Name it. | You are surfacing the practice gap. | | 0:03 | 5 min | Mini-teach | Protocol: describe, interpret, decide. One slide. | | | 0:08 | 5 min | Plan one | Describe one piece of work without judging it. Turn and talk. | | | 0:13 | 2 min | Commit | Each team commits to bringing work. | | ### PLC / team meeting (45 minutes) The standard version. **Goal:** every teacher leaves with something designed for a real upcoming lesson. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | 0:00 | 5 min | Hook | Scores vs looking at the actual work. What does each tell you? | Let them see the depth. | | 0:05 | 8 min | Mini-teach | The protocol and what to look for. | | | 0:13 | 12 min | See it in action | Run the protocol on real work together. | Describe before interpreting. | | 0:25 | 12 min | Design | Decide next instructional steps from the work. | Protect the full time. | | 0:37 | 5 min | Share | Compare interpretations; agree a next step. | Keep it evidence-based. | | 0:42 | 3 min | Commit + follow-up | Lock it in and set the next look. | | ### Half-day institute (~3 hours) A deep session for a PD day. **Goal:** built, practiced, and a rollout planned. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | Block 1 | 45 min | Experience + why | Scores vs work, then the research. | | | | 15 min | Break | | | | Block 2 | 60 min | Run protocols | Teams analyze common-task work with a protocol. | Group by course. | | Block 3 | 45 min | Practice | Decide and plan next steps from the work. | The protocol keeps it productive. | | Close | 15 min | Plan the rollout | Make it a routine; set the next look. | | ## The core activity: analyze student work with a protocol Teams leave with insights from the work and a next instructional step. - Bring a set of real student work to a common task. - Use a simple protocol to look closely together: describe, then interpret, then decide. - Surface what students understand and the misconceptions. - Decide what to teach next based on the evidence. ## Facilitator notes - Use a structured protocol; describe before interpreting. - Focus on evidence, and decide next steps. - Keep it non-defensive. ## Adapt it - **Elementary and secondary:** the same protocol approach. - **Teams:** bring common-task work. - **All settings:** describe, interpret, decide. ## Participant handout One page for every teacher. Print it, or save it as a PDF. ### Analyzing Student Work: look, then decide **Evidence over scores:** a protocol to describe, interpret, and decide what to teach next from real work. - The common task and student work: __________ - The protocol we use: __________ - What students understand and the misconceptions: __________ - What we will teach next: __________ - How we keep it evidence-focused: __________ ## Make it stick Work drives instruction: - Analyze work with a protocol. - Let it drive instruction. - Bring a next step from student work to the team. ## Common questions **How is this different from just grading?** Grading assigns a score; analyzing student work together digs into what the work reveals about understanding and misconceptions, with colleagues, to decide what to teach next. **Why use a protocol?** A structured protocol keeps the conversation focused on evidence in the work, not opinions or defensiveness, and ensures everyone looks closely. The structure is what makes it productive. **What do we look for?** What students actually understand, common misconceptions, the range of responses, and what the work tells you to do next instructionally. ## Go deeper - [The Learning Scientists](https://www.learningscientists.org) ## Build it into a bigger day - [Common Formative Assessments](https://pd.k12academics.com/common-formative-assessments-workshop.html) - [Data-Driven Instruction](https://pd.k12academics.com/data-driven-instruction-workshop.html) - [Facilitating Effective PLCs](https://pd.k12academics.com/facilitating-plcs-workshop.html) --- Full workshop page: https://pd.k12academics.com/analyzing-student-work-workshop.html All workshops: https://pd.k12academics.com/