We rely heavily on the legacy 'scores templates' function to record (for instance) tutor feedback and mock exam scores.

Each of our course types tends to have the same scores requirements, but when adding a new course template to an existing course type, we have to create a new scores template from scratch or duplicate an existing course template. Setting-up scores templates from scratch has lead to errors, eg if someone doesn't match the label conventions of scores templates already setup, ew delegate fields are created in the report tool and lead to holes in our data. Duplicating an existing course template has lead to other errors, where various fields have not been changed to match the parameters of the new course.

You also can't report on scores templates beyond the delegate table, so you can only identify these problems when something goes wrong and you realise you're missing some delegate data.

Also, we cannot automatically pull mock data back into ADM from our LMS, because the legacy scores templates don't appear to be available for API. 

Suggestions:
* Allow creation of scores templates centrally, independently of course templates, then select the relevant scores template within the course template from a selection

* Allow Scores fields to be accessible via API, so results can be pulled-back into ADM from an LMS

* Allow scores templates fields to be reportable via a 'Course' report, so that any incorrect fields can be identified and corrected before student data is input at the event level

---

I would instead use Learner Fields if they were not universal/site wide fields, as I believe they are available to the API.

'Courses' across different qualifications can be structured very differently and our scores templates are built with that in-mind eg varying amounts of mock score fields, tutor feedback is not always required and more.

As LFs are universal, every course/event would have fields which are inappropriate, potentially leading to data entry issues - too much choice!

Suggestion:
* Allow Learner Fields to be created centrally, but then the fields available for each event to be customisable, say at the course type or course template level