# OP-T02 — Handover and exceptions: completed example

Adrian Sutherland · Version 1.0 · Refreshed September 2026

© 2005–2026 Adrian Sutherland.
Source page: https://architectureportal.org/assets/organisation-process

Fictional teaching example. Proposed decisions and checks; actual results remain unknown.

## Trigger and result

OP-D1: transfer an active internal cancellation case when another person will perform the next action. The result is one accepted current assignment with enough context to continue.

## Information and acceptance

The offer references I1 and its current version, learner agreement, next action and unresolved matters. Receiver checks access, capacity and authority. Record accepting person, accepted version and effective transfer time; retain prior assignments. The response target is pending.

## Waiting and exceptions

The existing assignment remains current until the accepted transfer takes effect in the shared register. The receiver then becomes the current owner. The coordinator arranges cover for absent staff or queries and refers unresolved gaps to the service owner. If the case changed, the receiver checks the latest record and records that version. Conflicting attempts must be resolved before further action.

## Systems and delegated work

The trial uses a shared register and conversation. A later mobile action would remain provisional until accepted in the authoritative record. A cloud tool might route work; operational support must handle outage and reconciliation. In this example an AI summary cannot accept agreement or transfer ownership. Systems protocols and recovery are later design work.

## Checks and results

OP-V1 checks: no acceptance keeps the existing assignment; lack of access raises a query; unavailable owner triggers cover; a changed case requires current-version acceptance; conflicting receivers produce one accepted assignment; learner rejection prevents agreement to that alternative and resolution based on it.
All checks are unrun. Actual waiting time, failure rate, workload and correction effort are unknown.

## Methodology configuration

This may form part of a service procedure, case workflow or handover checklist. A process diagram shows waiting and acceptance; the role record names who can decide exceptions.

## History and open decisions

Version 1.0, September 2026. Linked to D1, R1, I1, OP-D1, OP-V1 and earlier V1/ID-V1. Set response targets, cover, access and reconciliation procedure before a real trial.