Architecture Portal

Continuing through another channel

The same agreement after a call.

Adrian Sutherland · Version 1.0 · · © 2005–2026

The proposed journey

CH-D1 (Cross-channel journey) follows the fictional learner from a cancellation message to a call. The first proposed trial is process-only and covers provider-run courses. The message refers to the existing case, and the case worker checks who is calling and what they may discuss before sharing protected details. Both routes use the same agreed meaning of a proposed alternative and an accepted resolution.

Event Information retained
Message sent Case reference, offer version and delivery state; sending alone establishes no agreement.
Learner calls Identity/authority checks appropriate to the discussion, existing offer and unanswered questions.
Learner agrees Agreed alternative, actor, time and the record required by the business rule.
Confirmation Accepted result and any remaining action, in an accessible form for the learner.

A later software option would let the case worker save an action on a mobile device while offline. CH-S1 (Pending and accepted actions) requires the interface to distinguish local saving from server acceptance. When the device reconnects, the case service checks the current case state and the caller’s authority. The security example governs access, while the systems contract governs the accepted result and repeat requests.

A proposed check

Start online, continue by phone, and then review the original message. Can the learner and worker establish the same current position? Repeat after a rule change and with a delayed notification. Retain discrepancies and their owners in the channel record. These checks have not been run.

About this edition

Refreshed for the September 2026 website update. This edition develops the earlier Architecture Portal and ASAF material; the fictional worked example was added in 2026.

Scope, limitations and next checks

Status and accountability

Read this page with its boundaries visible

Status

In development

Last reviewed

Intended users

  • Architects comparing and adapting their existing approach

Non-goals

  • Prescribing a mandatory method or claiming measured benefits

Limitations

  • Guidance illustrated by a fictional example; proposed designs and checks have not been implemented or run.

Next evidence sought

  • Review the guidance and try its records with a practising architect.