Communication events

When a school office has several dated observations for one conversation case, start by agreeing the event sequence, source record and outcome. A child event belongs to one parent case. The operator records its sequence, observation date and source record so the reviewer can assess it in context. An event outcome documents that observation; it does not decide the whole case.

The operator adds each communication event under the correct school conversation. Sequence and source record identify the observation, while the event date and description give reviewers the context they need. A colleague can compare the observation with its source reference and the parent case before changing the outcome.

• Link. Attach every observation to its parent conversation and retain the source record identifier.
• Assess. Record Pending, Accepted or Rejected for each event, with a reason for rejection.
• Correct. Keep the original observation visible while the operator repairs the case detail.

Pending and rejected outcomes remain visible. A rejected event carries its decision reason, so an operator can correct the case before asking for another review. 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 what counts as a separate event for the pilot community. The operator needs a consistent sequence, observation date and source record identifier; otherwise two observations can be mistaken for the same one. Decide when an event is Accepted and what explanation a Rejected event needs. The reviewer uses that explanation when assessing the case revision.

Take a case with a pending event and a second event linked to the same parent. Check their source identifiers, dates and order before review. If the second event is rejected, record the reason and have the operator correct the underlying detail. The event list should still show which observation prompted the correction.

Take a case with several dated observations from the school office. 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. The event record is evidence about the case; its outcome alone does not establish that the school conversation was delivered. The parent case and delivery operation retain that state. 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 rejected observation with a decision reason, then correct its parent case. Check that the source record and event outcome still point to the observation originally assessed. A later case decision must refer to the corrected revision; changing the event alone must not make an earlier approval current.

• Pending event outcomes — Events awaiting an outcome, with the parent case and source reference beside each observation.
• Rejected event outcomes — Rejected observations and their decision reasons for operator correction.

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