Policy - Training Packages

Policy - Training Packages

On this page

  1. Access and Equity
  2. Categories of Change During the Training Package Endorsement Period
  3. Changes to Training Packages
  4. Coding and Titling of Training Packages
  5. Continuous Improvement
  6. Development and Endorsement Process
  7. Endorsement Date
  8. Transition to revised Training Packages
  9. Introductory Training Package-specific text
  10. Language, Literacy and Numeracy (LLN)
  11. Mandatory Text
  12. Mapping to Previous Version of Training Package
  13. Ministerial Approval Date
  14. National Training Information Service (NTIS)
  15. Publication—Preliminary Information
  16. Publication—Training Package Copyright
  17. Recording Training Package Modifications
  18. Release Date
  19. Review Date
  20. Versioning of Training Packages
  1. Access and Equity

    • Training Package developers must comply with key VET sector policies to ensure Training Packages reflect the diversity of Australia’s VET clients and Australia’s current and future workforce.
    • Training Package developers, and the National Quality Council (NQC) in endorsing Training Packages, must meet their obligations under Commonwealth anti-discrimination legislation and associated standards and regulations.
    • Training Package developers must ensure that Training Packages are flexible and that they provide guidance and recommendations to enable reasonable adjustments in implementation.
    • An Equity Report must be completed on endorsed components being submitted to the NQC and provided to the member of the Quality Assurance Panel undertaking the Quality Report which forms part of the Case for Endorsement submission to the NQC.
  2. Categories of Change During the Training Package Endorsement Period

    • NQC Endorsement Required:
      • Any changes to a qualification and/or unit of competency that changes the outcome must be submitted to the NQC for endorsement.
    • ISC Upgrade:
      • Any changes to a qualification and/or unit of competency that do not change the outcomes are considered ISC Upgrades.

    NOTE: Interim arrangements are in place until 31 December 2010 to reflect the NQC resolution below.

     

    At its 8 April 2010 meeting, NQC agreed:

     

    (a) to amend the Training Package Development and Endorsement Process 2008 to allow for an ISC upgrade to apply where the qualification packaging rules and qualification structure have been changed to reflect the new packaging rules for flexibility and the embedding of green skills in Training Packages;

     

    (b) that the amendment allows ISCs to transition qualifications to the new packaging rules for flexibility, and the embedding of green skills, where the qualification outcomes and structure have not substantially changed and where the ISC determines that there is no need to seek industry validation via a full endorsement process;

     

    (c) that the proposed amendment to the Training Package Development and Endorsement Process 2008 apply until 31 December 2010 to align with the end date for transition to new packaging rules for flexibility and embedding of green skills in Training Packages;

     

    (d) that the following communication processes will be required to support the amendment:

     

    1.    ISCs notify and explain ISC upgrades to State Training Authorities and the NQC

    2.    ISCs update the Training Package version and the version modification history to
           explain in detail the particulars of the change

    3.    ISCs publish the change to NTIS.

  3. Changes to Training Packages

    • ISCs must notify STAs and the Department of ISC Upgrades of Training Packages identifying all changes.
    • STAs will advise relevant RTOs.

    Note: When NTIS functionality permits, NTIS will automatically notify STAs and relevant RTOs of new versions of Training Packages.

  4. Coding and Titling of Training Packages

    • Each industry Training Package has a five-character code followed by a unique and concise title reflecting the industry covered. For example, in the TAA08 Training and Assessment Training Package, ’TAA’ identifies the industry area, ’08’ identifies the year of endorsement, and the title reflects its industry coverage.
    • When assigning Training Package codes and titles Training Package developers must:
        • always use the code in full, followed by the title
        • not use spaces between any characters in the code
        • use uppercase letters and Arabic figures
        • not use ampersands, full stops or slashes
        • use a title that is unique, concise and reflects the broad industry covered
        • not use the words ‘Australian’ or ‘National’ in the title, except by special permission from the Department
        • use ‘Z’ as the first letter in enterprise Training Packages
        • if a new industry sector is added during the endorsement period, retain the Training Package’s original endorsement year code.
    • It is important that developers do not confuse the Training Package code (which remains the same during the endorsement period) with the version number (which can change in the endorsement period).
    • The code of a reviewed Training Package must reflect the endorsement year of the review.
    • Where the whole Training Package is reviewed, its code changes and it is considered to be a new Training Package for the purposes of version control, and is Version 1.
  5. Continuous Improvement

    • ISCs must apply continuous improvements to Training Packages during their endorsement period in accordance with the processes outlined in the document Training Package Development and Endorsement Process 2008.
    • Where an issue(s) is identified prior to completion of the final Stakeholder Agreement stage which would have an impact on implementation, this must be addressed by the ISC prior to submitting the Case for Endorsement to the NQC.
  6. Development and Endorsement Process

    • Industry Skills Councils (ISCs) must fulfil their roles and responsibilities in the NQC-agreed processes as outlined in the Training Package Development and Endorsement Process and supporting documents.
    • Training Packages must be endorsed by the National Quality Council (NQC), a Committee of the Ministerial Council for Tertiary Education and Employment (MCTEE). Once endorsed, the Training Package is made public on the National Register (NTIS).
  7. Endorsement Date

    • The Endorsement Date is the date on which the National Quality Council (NQC) endorses the Training Package content.
    • The Endorsement Date is added to the Training Package on NTIS by the Department prior to publication on NTIS.
  8. Transition to revised Training Packages

    • Where a Training Package is revised (including ISC Upgrades and NQC Endorsement Required), the affected qualifications and units should be implemented within six months, but no later then twelve months from the date those qualifications or units are published on the NTIS.
    • All new enrolments after twelve months from the date of publication are to be in the new qualifications or units.
    • RTOs can apply for registration to deliver new qualifications or units immediately following their public availability (on the NTIS), and can commence delivery as soon as their scope of registration includes the endorsed qualifications or units.
    • RTOs cannot apply for registration for qualifications/units of competency which have been superseded.
  9. Introductory Training Package-specific text

    • Each Training Package must include introductory text on the specific Training Package, providing an overview of its coverage, its features and the industry to which it relates.
  10. Language, Literacy and Numeracy (LLN)

    • Training Package developers must ensure that language, literacy and numeracy requirements are explicit and recognisable within the Training Package.
    • Language, literacy and numeracy requirements in Training Packages must reflect and not exceed the LLN skills required in the workplace to carry out particular jobs.
  11. Mandatory Text

    • Mandatory text for the Training Package Overview section of the Training Package has been agreed by States and Territories and the Australian Government, and must be included.
    • Training Package developers must not alter the mandatory text; however contextualisation advice for a particular industry may be added at the end of the mandatory text section.
  12. Mapping to Previous Version of Training Package

    • When Training Packages are reviewed, developers must provide sufficient information in the Training Package to help users understand its relationship with its predecessor.
    • The relationships between units of competency and qualifications must be stated by mapping them against their predecessors, showing any differences and equivalences.
    • Information must be sufficient for users to see exactly what has changed and to assist them in determining matters such as resourcing, impacts on training for particular qualifications or job profiles, and transition arrangements.
    • Developers must note the equivalence status of a unit of competency according to the following categories:
      • E = Equivalent - the outcomes of old and new units are equivalent.
      • N = Not Equivalent - the outcomes of old and new units are not equivalent.
      Note: The developer’s determination that the outcomes of an old and new unit are equivalent: (i) only applies to workplace contexts and for AQF qualifications purposes, including RPL; and (ii) does not apply to implications for training delivery and/or assessment purposes.

  13. Ministerial Approval Date

    • The Ministerial Approval Date is the date on which, following an NQC endorsement process, the Ministers for vocational education and training approve the publication of the Training Package on the National Training Information Service (NTIS).
    • The Department will add the Ministerial Approval Date to the Training Package prior to releasing it live on the NTIS.
  14. National Training Information Service (NTIS)

    • Training Packages must be developed in a format that is compatible with the National Training Information Service (NTIS).
    • The NTIS Content Authoring Tool (CAT) must be used unless prior agreement has been reached between the ISC and the Department regarding an alternative method.

    Note: When NTIS functionality permits, all Training Package content will be entered into the NTIS prior to endorsement.

  15. Publication - Preliminary Information

    • Training Packages are available through the NTIS or for purchase as physical copies.
    • The preliminary pages in all physical copies of Training Packages must include the following summary information.
        • The title page must include:
              • the endorsed Training Package code and title
              • a statement that the document comprises the Training Package endorsed components, or part thereof if in multiple volumes
              • the volume number, indicating the number of volumes, e.g. Volume I of III
              • the volume title or specific industry sector coverage
              • a statement that the volume is not to be used in isolation, but must be used in the context of the whole endorsed Training Package
              • a list of the titles of all associated volumes, including reference to the Assessment Guidelines and any common units of competency, in Volume I
              • the Review Date.
        • The Imprint page must provide publication details and must include:
              • © Commonwealth of Australia 200x (where ‘x’ is the year of publication)
              • any special acknowledgements if applicable
              • name and contact details of publisher
              • month and year of first publication
              • stock code or barcode if applicable
              • ISBN Number
              • name of printer
              • Standard Departmental Copyright statement and disclaimer. If applicable, also include any agreed copyright arrangements or acknowledgements such as a statement acknowledging the copyright of other parties
              • version number and date (do not confuse this with the Training Package code)
              • Release Date
              • the Review Date.
        • Training Package developers must include the following statement in the footer of every page of the Training Package: ‘© Commonwealth of Australia 200x’ (where ‘x’ is the year of publication)
        • A contents page must be provided in all volumes of a Training Package.
        • The mandatory text entitled ‘Preliminary Information – Important Note to Users’ must be included, with ISC details as applicable, and completed tables listing all qualifications, units of competency and skill sets in the Training Package.
  16. Publication - Training Package Copyright

    • Training Package developers must note that Training Package content is owned by the Commonwealth of Australia.
    • It is accessible on the NTIS via an AEShareNet Free for Education (FfE) Licence. In summary, the AEShareNet FfE Licence enables organisations to use and print endorsed Training Package content for educational purposes, under specified conditions (see <www.aesharenet.com.au/FfE2/>).
    • Uses beyond that allowed by the AEShareNet FfE Licence, e.g. commercial distribution and sale, require a separate copyright approval from the Department—only ISCs and TVET have been granted a licence to exploit Training Packages commercially and produce and sell physical (e.g. print, CD-ROM) copies of full or partial Training Packages.
  17. Recording Training Package Modifications

    • Each Training Package must include version modification history information which clearly identifies to end users any changes—what has been changed, and when they were made.
    • All changes, that is 'ICS Upgrade' and 'NQC endorsed' changes, must be recorded in the version modification history table.
    • In any physical copies (e.g. print, CD ROM) of a Training Package, this information will be contained within the version modification history table.
    • The assignment of version numbers, and the inclusion of additional information within the version modification history table, must adhere to the following:
        • most recent information is provided at the top of the table
        • version numbers are incremented if an NQC Endorsement Required category of change is made
        • new, imported and deleted qualifications are listed by code and title
        • new, imported and deleted units of competency are listed by code and title
        • any changes to the qualification packaging rules are referenced to the relevant section and volume of the Training Package
        • any inserted additional text is referenced to the relevant section and volume of the Training Package
        • typographical edits are not separately identified or referenced (but may be referred to in general)
        • reviewed Training Packages are treated as new Training Packages (and as such must include mapping of the new Training Package to its predecessor, and will be Version 1 of a new Training Package code).
  18. Release Date

    • The Release Date is the date on which the Training Package is released live on the NTIS.
    • The Department will insert the Release Date when the Training Package is made publicly available.
  19. Review Date

    • Training Packages are normally endorsed for a three year period. During this period ISC Updates and NQC Endorsement Required changes may occur, but the original Review Date for the Training Package remains the same.
    • The Review Date is the date by when the whole Training Package must be reviewed and submitted to the NQC for endorsement.
    • The Review Date is not an expiry date—endorsed Training Packages and their components remain current until they are reviewed or replaced.
    • In the physical copy (e.g. print, CD-ROM), the Review Date is shown on the title page.
  20. Versioning of Training Packages

    • The first release of the Training Package (including reviewed Training Packages) is Version 1.
    • If NQC Endorsement Required changes are made to a Training Package during the endorsement period, its version number must be incremented (noting that Arabic figures are used for version numbers and that the increment is by a whole number, not a decimal point).