Skip to main content
NDT Streamlined

Workforce development

Scoping a team learning request

Describe the audience and intended result before selecting content or delivery format.

A useful learning request begins with the work, not the course title. Describe who the participants are, what they currently do, and what should become clearer or more consistent after the engagement.

Record team size, roles, prior experience, interface language, technical language, location, schedule, accessibility needs, and any employer-controlled procedures or equipment that affect delivery.

Define how the organisation will recognise a useful result. That may involve participation, demonstrated practice, supervisor observation, or another approved measure; it should not be inferred by the website.

Technical content, prerequisites, assessment, translation, instructor authority, price, and completion wording remain separate approved records and decisions.

Four parts of a useful request

  • Audience

    Roles, experience, language, location, and number of participants.

  • Workplace need

    The task, decision, or communication that needs to improve.

  • Delivery context

    Timing, format, equipment, accessibility, and controlled source material.

  • Evidence of value

    The approved observation or record that will show whether the need was addressed.

Describe a team requirement

Use the corporate inquiry to capture the initial context.

Start a corporate inquiry