CUST.2:4.4 - Choose disposition on separate axes

Decide first whether the difference should be accepted at all. A useful customer result may still be unavailable under actual capacity, rights or professional conditions. A smaller result or later date can be preferable to an unsupported exception.

Then distinguish three choices:

• What remains local and what, if anything, should become shared?
• What realizes and provides the contribution: configuration, code, hardware, procedure, training, assisted service or a partner?
• What is actually promised, to whom, for how long and with which support?

These choices can coexist. A common adapter does not remove a local operating change; a repeatable service can include specialist help; a partner can deliver either a common or bespoke contribution. They are not rungs of a maturity ladder.

For a candidate common change, identify the property or operation expected to transfer and the difference that could defeat it. Send that question to CUST.3 with the recovered cases and their limits. For a known permitted variation, send the actual fit question to CUST.4. For an unresolved causal or transfer question, ask CUST.5 for a discriminating answer. Do not use a route label as that answer.