What is a professional learning community and how does it differ from a department meeting?

A PLC is a collaborative team that focuses specifically on improving student learning through examining evidence together. It differs from a department meeting in its focus: department meetings handle logistics, scheduling, and administrative tasks. PLCs focus on four questions: What do we want students to learn? How will we know if they learned it? What will we do when they do not learn it? What will we do when they already know it? The collaborative examination of student data and the instructional decisions that follow are what define a PLC.

What should a PLC newsletter communicate to staff?

It should describe the current PLC cycle focus, share any data patterns that have emerged from recent collaborative analysis, communicate any instructional agreements the team has reached, note upcoming PLC meeting dates, and celebrate specific instances of collaborative professional learning. A PLC newsletter that only reminds staff of meeting times is not communicating the value of the practice.

How do you build a PLC culture that focuses on learning rather than compliance?

A PLC newsletter that communicates the work of PLCs as a compliance obligation, requiring participation, produces compliance. A newsletter that shares what a PLC team figured out together, describes the instructional change they made based on data, and reports what happened to student outcomes builds authentic professional learning culture. Lead with the outcomes of collaborative learning, not the attendance requirements.

What protocols should a PLC use in its meetings, and how should the newsletter describe them?

The four key PLC activities are: reviewing common assessment data to identify learning gaps, determining which students need additional support, identifying which instructional strategies were most effective, and planning the next instructional steps together. The newsletter should describe the protocol used in each of these activities briefly, so staff who are new to PLC work understand what to expect in their meetings.

How does Daystage support professional learning community newsletters?

Daystage lets school PLC coordinators send newsletters with embedded data summaries, meeting agendas, and shared instructional agreements. The platform allows PLC newsletters to be sent to specific team distributions, so fourth grade PLC members receive content relevant to their grade level rather than a school-wide communication that includes irrelevant grade-level data.

Professional Learning Community Newsletter

A professional learning community is only as strong as the quality of collaborative conversation it generates. A newsletter that communicates the PLC's work, celebrates its learning, and keeps members oriented to the team's goals between meetings builds the culture that makes PLCs productive rather than performative.

Anchor every newsletter issue in one of the four PLC questions

The four critical questions of a PLC give every newsletter a natural organizing framework. Each issue can focus on one: what did our recent common assessment tell us about what students have learned? Which students need additional support and how are we providing it? Which of our instructional strategies produced the strongest student outcomes? What are we planning for students who are ready to extend? Rotating through these questions ensures the newsletter covers the full scope of the collaborative work rather than defaulting to the logistics of the next meeting.

Share data patterns without naming individual classrooms

A PLC newsletter can report on team-level data patterns without creating comparisons that damage professional relationships. "Three of five classes showed a significant gap in fraction division, while conceptual understanding of fraction equivalence was strong across all classes" is useful information that drives instructional planning without creating a competitive dynamic. Report aggregate patterns, not individual classroom rankings.

Communicate the instructional agreements the team reached

One of the most valuable outputs of an effective PLC meeting is a shared instructional decision: all team members will use the same academic vocabulary for this concept. The whole team will provide a reteach opportunity in week three for students who did not pass the common formative assessment. The team agrees to try a specific discussion protocol in the next unit and compare results. Documenting these agreements in the newsletter creates a record of collective professional commitments that the team can reference and revisit.

Feature a small-group instructional example from a team member

When one PLC member tries a small-group reteach approach that produces measurable results, sharing that experience in the newsletter creates a practical resource for the whole team. A brief description of the approach, what students who needed reteaching were working on, and what the data showed afterward gives other team members a specific strategy to try. This kind of peer-to-peer professional sharing is what distinguishes a high-functioning PLC from a group of teachers who meet and discuss without shared learning.

Describe the intervention and extension plan clearly

The PLC response to data should always include a plan for both students who need additional support and students who have already demonstrated mastery. A newsletter that only describes the intervention plan implies that the team's job ends when struggling students are identified. The extension plan is equally important: students who already know the material should not sit through reteach lessons. Describing both plans in the newsletter communicates a complete picture of how the team is using data to serve all learners.

Include the upcoming meeting agenda and protocol

A brief preview of the next PLC meeting, including what data will be reviewed, what protocol the team will use, and what decisions need to be made, helps team members come prepared. Meetings where everyone arrives having reviewed the relevant data and ready to engage with a specific protocol are consistently more productive than meetings where the first 20 minutes involve orienting to the data and deciding what to discuss. The newsletter does the pre-meeting preparation work.

Celebrate collaborative learning, not just outcomes

A PLC newsletter that only reports data and instructional decisions misses the relationship dimension of professional collaboration. A brief sentence acknowledging a particularly productive discussion, a moment when the team changed direction based on evidence, or a risk one teacher took in sharing honest data about what was not working in their classroom reinforces the collaborative norm that makes PLC culture possible. Professional learning communities need their collaborative behaviors celebrated as much as their academic outcomes.

Connect PLC work to the school improvement plan

PLCs that operate independently of the school's formal improvement goals produce learning that is not connected to the school's priorities. A newsletter that regularly references the specific improvement goal the team's PLC work is contributing to keeps the collaborative effort aligned with the school's direction. That alignment also helps administrators understand the value of protecting PLC time when competing demands arise.

Professional Learning Community Newsletter: Collaborative Growth