Conversation cases

When a school office opens a case that needs review before recorded delivery, start by agreeing the case number, message date, organization and community. The case number identifies the work across review and delivery. Its revision identifies the version under decision. The operator prepares the record; the independent reviewer decides whether that version may proceed.

The operator enters a school conversation with its school community, owner and message date. The status board shows whether the case is still in preparation, awaiting review, decided or delivered. A revision identifies the exact version that the reviewer considered. The owner and reviewer can compare the current status with the revision and the supporting event detail before acting.

• Prepare. Give the case a number, dated context, organization, community and owner.
• Submit. Move the completed revision from Draft to Submitted for independent review.
• Trace. Compare the case status with its history, decision and delivery operation.

The owner checks the related event detail and evidence before submitting the case. The reviewer reads the same revision, its state history and any pending decision in School Conversations Workspace. The handoff is a change in responsibility, not simply a new label. Agree who can prepare, verify and decide before inviting users into the operating team.

Agree which organization owns the first pilot case and which active community definition applies. Name the operator who prepares it and the reviewer who makes the separate decision. Decide how the case number and source reference will be carried into event and evidence records. Confirm the information required before submission.

Use the status board to check that Draft work does not enter a delivery run. After submission, compare the visible case revision with the pending review decision. If a reviewer returns it, the operator must prepare a successor revision with the reason still available. A case marked Decided is not a confirmed delivery; the receipt has to be checked before the Delivered status is used.

Take a dated school conversation case awaiting review. Enter the source details and inspect the case in the workspace. Follow the related evidence into review, then compare the approved revision with the operation that carries it forward. A returned case goes back to the operator with a reason. If a delivered case needs correction, preserve the original run and decision, then prepare a successor revision. A colleague should be able to explain the final state from the stored case, decision, history and receipt without asking the original operator.

Rehearse a submitted case whose owner belongs to a different organization. Keep it out of review until the scope is corrected. Then return the case from review, amend the record and confirm that the earlier decision stays tied to its earlier revision. The case history should explain each transition.

• Conversation review inbox — Submitted cases with their owner, community and revision ready for independent review.
• My conversation cases — Cases assigned to the operator, including work still in Draft.

Follow this case through its process. Review roles before widening access.