Terminology Customisation

Every training organisation is unique. While some use standard VET terms like "Units" and "Competency," others delivering internal professional development might prefer "Modules" and "Completion".

Terminology Customisation lets you rename the core structural and outcome labels across the platform to match your organisation's context — without changing any of the underlying logic or compliance behaviour.

What's Covered in This ArticleArticle Summary

This article outlines how to modify system labels to match your delivery model.

Structural Labels

You can replace the default names for the two primary structural elements in Nimbu.

Default Term Common Alternatives
Course Qualification, Program, Workshop, Certificate.
Unit Module, Subject, Topic, Competency.

Pro-Tip: If none of the preset options suit your organisation, you can type a custom label directly into the field.

Custom Labels for Results

For many RTOs, the language of "Competency" is vital for compliance; however, for non-accredited or internal training, you may wish to use softer or more generic terms.

  • Competent (C): You can rename this to "Passed," "Complete," or "Successful".
  • Not Yet Competent (NYC): You can rename this to "Unsuccessful," "Requires More Work," or "Incomplete".

While you change the visual label, the underlying logic remains unchanged. AVETMISS reporting for Accredited courses will still use the correct national standards regardless of the label displayed in the platform.

Where Terminology Appears

Once updated, custom labels are applied globally across the platform.

  • Navigation Sidebar: The Courses registry will update to reflect your chosen term (e.g. "Programs").
  • Student Dashboard: Students will see their progress through "Learning Modules" instead of "Units," or whichever term you have set.
  • Class Management: Trainers will mark students using your custom outcome labels (e.g. "Passed" instead of "Competent").
  • AVETMISS Exports: Custom terminology is reflected in AVETMISS data exports, ensuring your reporting language is consistent with your platform.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us