Your human checkpoint
A rubric earns its value when people can use it under time and pressure, not just when conditions are perfect. Reflection helps determine whether your language is specific enough to guide action without extra explanation. Sharing is how you test that clarity with real people. When a colleague in a different role can understand your row and follow the checkpoint, you know your rubric is ready to build consistency and trust across your team.
Your show and share prompt
Choose a row from your AI Use rubric that you think prevents the most responsibility drift in your setting. Share it alongside a brief rationale explaining why the category and checkpoint fit the task. Keep your share focused on decision logic. Avoid tool names—focus on what must stay human, what data is protected, and what gets verified before anyone relies on the output.
Role-based reflection questions
Select your role. Consider the reflection questions before you decide how and where to share your work.
For teachers
A colleague reviews your rubric and asks: "How will this actually help us when we are busy?" They want guidance that is clear, realistic, and consistent enough that multiple people can follow it the same way.
- Which student learning risk does your chosen row protect against most, and how does the checkpoint address it specifically?
- What is one sentence you would say to students to explain what AI may draft and what must remain their own work?
- What is one part of your row you might simplify so it's easier to follow during a busy week, without losing the accountability it provides?
For coaches
A colleague reviews your rubric and asks: "How will this actually help us when we are busy?" They want guidance that a team can actually follow consistently, not just in theory.
- What question would you ask a team to confirm that a checkpoint is specific and repeatable rather than just a general reminder to "review before sharing"?
- How would you respond if a teacher says, "I don't have time to verify"? What is one realistic checkpoint you would propose that takes two minutes or less?
- What pattern do you see in the rows your team would need first: classroom decisions, staff decisions, or communication decisions? What does that pattern tell you about where shared AI norms are most urgent?
For administrators
A colleague reviews your rubric and asks: "How will this actually help us when we are busy?" They want guidance they can point to when staff ask what is expected and why.
- What stakeholder trust concern does your chosen row address, and how does the privacy default reduce that specific risk before a session even starts?
- What is one place in a school workflow where this row should be required, not optional—and what would it take to make that expectation clear without it feeling like surveillance?
- What documentation expectation feels realistic and defensible if a decision is questioned later by a family, a board member, or a staff member?
Share your learning
Choose one option that fits your context. Keep your share focused on decision logic rather than specific tools or student details.
Share with a colleague
Share your chosen rubric row and invite your colleague to restate the category and checkpoint in their own words—without looking at your written version. What they say reveals whether your language is clear enough to guide action under pressure. Use what they say to refine one word or phrase before you consider the row finalized.
Share on a professional or social platform
Share one insight you gained about writing AI Use rubric language that keeps responsibility visible. Keep it general and avoid any student or staff details so your post models the same privacy-minded approach you built into your rubric. ISTE Connect, LinkedIn, Bluesky, and X are all places where educators are working through these same questions right now. A specific, honest observation about what makes a checkpoint usable carries more value than a general statement about AI responsibility.