Create a New Sub-Competency

Modified on Tue, 3 Sep, 2019 at 11:33 AM

  1. Log into LAAMP as a Publisher

  2. Open the Side Menu 

  3. Select “Sub-Competencies” 

  4. Select the “+ Add” button 

  5. Enter a Name (longer than 3 characters) for the Sub-Competency in the Name field 

  6. Select a Sub-Competency type from the list box 

  7. A Description and Notes may also be added, but are optional

  8. Enter an Expiry time frame in months - the expiry time frame must be greater than 0 and Save

  9. Select the “Add Location” button

  10. A “Find a Location” popup list will appear - in the popup, enter a Location name into the Search Box and press enter

  11. In the popup, select the Location 

  12. In the popup, select “OK”

  13. Select the “Chapter Name” field in the second column and type in a Name

  14. Select the “+” button next to the “Chapter Name” field to create a Chapter

  15. Select the newly created Chapter button

  16. Select the “Page Name” field in the third column and type in a Name

  17. Select the “+” button next to the “Page Name” field to create a Page

  18. Select the newly created Page button

  19. Select the “Instructions” field in the fourth column and enter an instruction for the page

  20. Select an “Evidence Type” from the List box - current supported evidence types are “Image”, “Video”, “Audio” and “Not Applicable”. 

  21. Select the number of Evidence required from the List box. LAAMP supports a minimum of 1 - 3 pieces of multimedia evidence per page

  22. Select the “Add Performance Criteria” button

  23. Select “Performance Criteria” field and enter a criteria

  24. Repeat steps 14 to 24 to complete Sub-Competency content

  25. Select the “Save as Draft” button in the top right corner 

The Sub-Competency will be saved in the system as a draft 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article