CB.11:4.5 - Transfer through receiving use

Provide the chosen receiver with the contributions their work requires. This can include explanations, tools, access, contact with a qualified practitioner and a way to obtain corrections. Preserve the conditions under which a method or resource can be used; the recipient needs to recognise when it is unsuitable.

Have the receiver perform the next consequential work under the new conditions. For an organiser, that could be preparing and running a meeting, responding to an access problem and returning its result. For an independent user, it could be finding the guide, applying the relevant instruction and reaching its maintained correction route.

Observe the gap that the attempt reveals. A missed permission calls for an access decision; an uninterpretable method calls for explanation or learning; a defective method calls for its actual development through ME or the domain practice. Repair the gap and try the affected receiving use again. Keep other usable contributions available.

For a platform move, obtain the applicable export, hosting and access conditions, then inspect the transferred content and a real receiving task. Navigation, links, search, contribution permissions and private material can behave differently. The practical test concerns the functions people rely on, not just the number of files copied.

Finish the departing contributor’s responsibility at the agreed boundary. State which work has transferred, what remains unsupported and who has accepted any remaining handover. If the new arrangement cannot carry an essential promise, tell its users and reduce or stop that promise before declaring transfer complete.