Incidents

A disruption record links the affected service and asset to an assigned person. Service Operator acknowledges it with the actual acknowledgment time, then keeps the investigation in ordered updates. Recovery and final closure are separate decisions.

The service, asset and assignee establish where the response starts. Record the time acknowledgment actually happened; a later edit time is not a substitute. Keep each investigation update with its author and occurrence time so a receiving operator can reconstruct the response.

• Ownership. Service Operator assigns the responder and follows the case through closure.
• Evidence. Compare priority, service, asset, assignee and actual response times.
• Follow-through. Keep each dated update with its author and incident.

Agree how priority is chosen, who owns the response and when an update is required. Each note needs an author and occurrence time. A status change without chronology leaves the next operator unable to reconstruct the response.

Rehearse an ordinary record and an exception with the people who will use this area. Check the linked owner or service before changing a status. If the outside information changes, compare it with the original request before the next handoff.

Open a case for a service interruption. Confirm the linked asset and assignee, record the actual acknowledgment time, and add an authored update. After recovery, check the resolution time and the handoff before the record is Closed.

Have the receiving operator repeat the check using the linked records. Review a mismatched owner, value or date with the decision owner before applying the same handling to more work.

For an exception, use an incident that was acknowledged after its opening but entered later. The Service Operator should record when acknowledgment actually happened, not when the form was saved. The assigned person and affected service must remain clear to the next responder. During investigation, add an update with its author and occurrence time when the condition changes. A resolved status follows recovery; closure follows a separate review of the chronology. If the disruption returns, the receiving operator should be able to read the earlier updates and understand which asset and service were affected.

The assignee should see that distinction before taking over the case.

• Service incident queue — Open, acknowledged and investigating incidents with priority and assignee.
• My incident assignments — The operator’s assigned incidents and their current status.

Follow the incident response handoff and review the data model before migrating records.