Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-21 13:53:25 UTC · snapshot created 2026-11-21 13:55:03 UTC · last check 2026-11-21 14:20:20 UTC

MKT.2:4.4 - Obtain a supply answer before relying on the promise

Establish what the responsible supplier can provide and under what conditions. Use its existing answer where it suffices. If the contribution or a condition is unclear, ask the supplier about the missing point. Relevant conditions include configuration, capability, staffing, time, access, dependencies and support. Separate a planned improvement from an available contribution. Include preparation and continuing support when comparing feasible versions.

For each important promise, follow the required contribution to a responsible provider or to an explicit gap. Resolve incompatible timings, shared scarce resources and conflicting claims made to different roles. A technically possible service can still be unavailable in the proposed window. Return an unsupported part for engineering, operational or organisational work, or reduce the proposal to a supported part.

The supply answer constrains both the offer and its positioning. If only batch processing is supported, “continuous” must disappear from the current promise. If an operator must inspect every output, the offer must leave that work visible.