# BP-V02 (Accepted handover)

Adrian Sutherland · Version 1.0 · September 2026

© 2005–2026 Adrian Sutherland.

Refreshed for the September 2026 website update.

Licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Keep the [edition note](https://architectureportal.org/downloads/blueprint/1.0/edition.md) with adaptations.

- Question: An accepted transfer with a lost reply.
- Design state: SOFT-01 (Later software option)
- Level: Logical
- Design: Proposed; unimplemented
- Scope: Accepting an offered internal case transfer
- ASAF aspects: Process, Structure, Information, Security, Systems
- View page: /blueprint/accepted-handover
- Editable source: accepted-handover.mmd
- Export: accepted-handover.svg

## Reading the view

A receiving member of staff requests acceptance through the staff client. The case service checks authority and current state, then commits assignment, offer, receipt and pending notification together. The response is lost. A repeat uses the same operation and inputs. Current permission is checked before the retained result is returned, without another assignment. Notifications follow the commit independently. Booking confirmation is separate.

## Key

- Read downwards. Columns identify participants; solid arrows show requests or actions.
- Dashed arrows show results. A crossed arrow marks a lost response. Notes state conditions.

## Linked records

- [R1 (Continuous ownership) · continuous ownership](/business-architecture/worked-example#business-intent)
- [OP-D1 (Accepted-transfer procedure) · process handover](/organisation-process/worked-example)
- [SI-C01 (Transfer acceptance contract) · acceptance contract](/systems/worked-example#the-acceptance-contract)
- [SI-V1 (Interface checks) · proposed checks](/systems/worked-example#proposed-checks)

The view page supplies the decisions, open choices and checks. The object
reference supplies each identifier's meaning and source.