HCD.7:0 - Use This When

Use this pattern when a capability-development programme, Method, or practice set needs contributions from people, sources, tools, AI, an environment, or an organization, and the practitioner must establish what will actually be available. Begin with the concrete functions and their timing: explanation, task preparation, safe access, feedback, checking, independent assessment, specialist input, and fallback. Do not begin with a provider label or a total-hours budget.

The first useful result is an enabled development arrangement: each required contribution has an identified supplier, competent and authorized scope, access conditions, capacity at the required time, data and privacy boundary, human checks, fallback, and evidence of availability. If one of these values is missing, return the supported design and the exact unavailable contribution, timing, access condition, or provider result. A plausible design is not an enabled arrangement.

The practical gain is feasibility before participation. The practitioner can see whether feedback arrives before the next attempt, whether peak assessment demand fits the provider window, whether a peer contribution prepares rather than replaces competent assessment, and whether AI support leaves enough human time to check consequential output.

Do not use HCD.7 to create a missing provider capability, infer that a provider is competent from a job title, prove learning from access, or decide that a person is suitable for a class-level arrangement. Use HCD.8 when an exact unavailable contribution needs an obtain-or-build comparison and the preparation or operating test that the chosen route requires. Personal fit remains with the applicable demand, target, profile, programme, and participation decisions.