# data[].attributes.headline
more intuitive to leave grades and / or feedback without a digital submission

# data[].attributes.subject
more intuitive to leave grades and / or feedback without a digital submission

# data[].attributes.headline
Academic staff time: to provide feedback, engage with dialogic feedback processes, time to innovate 

# data[].attributes.subject
Academic staff time: to provide feedback, engage with dialogic feedback processes, time to innovate 

# data[].attributes.headline
Anonymity and desire of staff to mark on paper

# data[].attributes.subject
Anonymity and desire of staff to mark on paper

# data[].attributes.headline
Grading, consistency, quality and feedback

# data[].attributes.subject
Grading, consistency, quality and feedback

# data[].attributes.body
Bb Total column

# data[].attributes.body
Not all unis enable crocodoc because of data security

# data[].attributes.body
monitoring engagement with feedback- how do we measure how students are engaging with feedback

# data[].attributes.body
need for quite spaces to provide audio/video feedback

# data[].attributes.headline
*Why can't we overwrite a submission? *Email receipt needed to reassure students *Show late submissions in views other than needs grading *Save draft option is confusing. Can we hide – or rename? *UI of submission page horrible. The most important feature (for us) is also the smallest (for rubric). *Can we report on when grades / feedback is submitted? *Can we report on when grades / feedback is released? *Why can't we release feedback only (for assignments)? *Can we see when / if a student has accessed feedback? *Can students comment on their feedback? *Multiple markers for each assignment. *Non standard character types – essential. *Admin control of student notifications. 

# data[].attributes.subject
*Why can't we overwrite a submission? *Email receipt needed to reassure students *Show late submissions in views other than needs grading *Save draft option is confusing. Can we hide – or rename? *UI of submission page horrible. The most important feature (for us) is also the smallest (for rubric). *Can we report on when grades / feedback is submitted? *Can we report on when grades / feedback is released? *Why can't we release feedback only (for assignments)? *Can we see when / if a student has accessed feedback? *Can students comment on their feedback? *Multiple markers for each assignment. *Non standard character types – essential. *Admin control of student notifications. 

# data[].attributes.body
Keeping track
Double marking
Access by external examiners
Justification of decisions
Resistance by markers
Small group assignments

# data[].attributes.body
Not currently using BB for submission as use Turnitin - and this functionality is not integrated with the BB assignment submission system

# data[].attributes.body
still some resistance to online submission and marking from staff

# data[].attributes.body
The documentation isn't clear enough to allow a developer to develop building blocks easily

# data[].attributes.body
Late approvals
Moderation
External examiners
Data retention

# data[].attributes.body
over assessment

# data[].attributes.body
What you said.... plus...
* Dealing with extensions and abnormal submission processes
* Supporting university policies (such as anonymity, double blind marking)
* Support moderation processes
* Learning objectives - correctness, assessment needs to be aligned, but if they aren't right....
* Supporting students through the assessment process (ie noticing if they don't submit, providing receipts, reminders/notifications)
* Exam board prep - getting what you need for exam boards easily (combining assessment artefacts?)
* Making sure users have correct permissions to do what they need but no more.
* Retention dashboard & analytics: measuring engagement - are we making sensible decisions based on the data? i.e student engagement checks based on how much of videos of lectures they've watched. How do you tie these bits of data together? Just because it is possible... should we do it?  Can we work out if a student is disengaging? Looking at trends.
* Support for good admin processes like bulk upload of feedback, lists of who hasn't submitted
* Clear interface for marking - so it's clear that marking has been saved.
* Good integration with external tools like Turnitin, linking with other bits of Learn too.
* Getting picture of whole student
* Supporting big classes - multiple markers, prompting markers, marking notifications, etc