# data[].attributes.body
this needs to be supported by the University

# data[].attributes.body
Move DAB documentation to one drive.

# data[].attributes.body
Need to time and motion study to monitor the amount of time it takes us to produce - 18 depts 3 x per year

# data[].attributes.body
Needs to be updated for 2020/21 - one-sheet version much easier to use & follow as a step-by-step process

# data[].attributes.body
All paperwork & email communications need updating in good time each year, as it occurs too late currently for communications to be sent out

# data[].attributes.body
The template was very late coming out (about 3 days before deadline date).  This needs to be available a lot sooner.

# data[].attributes.body
More emphasis could be made on the fact that Module Leaders are responsible for checking their module marks once the reports are made available and the importance of doing so. To try and make sure any errors are picked up prior to the DAB

# data[].attributes.headline
Problems with new EE's accessing SharePoint

# data[].attributes.subject
Problems with new EE's accessing SharePoint

# data[].attributes.body
As part of the initial communication that goes out to EE's with the DAB dates, we could ask them to try and access the SharePoint where we upload reports. That way if they do have any access issues, we have plenty of time to resolve them rather than them reporting issues days before the DAB when the reports have been released.

# data[].attributes.body
Rather than having it on one sheet could we have pre, during & post DAB sections of the checklist and make it more clear

# data[].attributes.body
Fairly quick and easy to set up. Didn't take much time at all.

# data[].attributes.body
Needs to be more clear, or their training about the process. They always seem to stumble over the IT side of the process. i.e. logging in, links not working etc.

# data[].attributes.body
When you store a page of marks, it doesn't go to the next page, there used to be an option of store and next page. Also when you click store, it goes back to the top and you have to scroll down to click next page. Can there be a next page section at the top

# data[].attributes.body
Agreeing modules in vista is by page. Would be so much better if you could do the whole module in one click (like SITs)

# data[].attributes.body
The amounts of reports we need to check before marks inputting, MRA, RESD and RRAA. You always end up missing something as they are updated continuously

# data[].attributes.body
Is a great idea and works if up to date

# data[].attributes.body
Can be time consuming chasing EE's for absence pro-formas. Are these needed or would an email from the EE confirming they've checked the reports be sufficient?

# data[].attributes.body
Really useful for checking marks, particularly when working alone from home.

# data[].attributes.body
These shouldn't be scheduled during school holidays - staff are on leave.

# data[].attributes.body
Need a report which shows which marks/modules have not yet been agreed.

# data[].attributes.body
Course leaders unclear as to what certain marks mean i.e. refers been read out as fails, and RD’s CR’s not being understood. Maybe going back to having the old tables of mark outcome combinations we had in the past would be useful. These could also go out with mark requests and then again when we confirm that all module reports have been uploaded. We’d still have queries at the DAB’s but it might cut down on them.

# data[].attributes.body
| Although not our process CMR meetings were a great way to review information prior to the DAB

# data[].attributes.body
A precise simple tick list in the order of which you do each process - perhaps all the the links and info could be on a sepreate tab		

# data[].attributes.body
A precise simple tick list in the order of which you do each process - perhaps all the the links and info could be on a separate tab

# data[].attributes.body
Change to way CLs present data at DABs.  Framework was developed by Leop and CIPs rather than reading student marks.
Comparisons between previous years marks and this year and what improvements they are intending to make to courses

# data[].attributes.body
Briefings to academic staff (part of CMRs or separate briefings) to explain how reports work, what the data means and what they need to present at the DAB.

# data[].attributes.body
Organisation is key – the earlier correspondence e-mails are sent to ML, CL and EE the better.
All e-mails reminders for marks deadlines essential.

Not all CAs send out in timely manner.

# data[].attributes.body
Repeated issues with academics not meeting marks deadlines, not checking for CR submissions so marks are missed.

# data[].attributes.body
Having to re-input marks that have already been inputted by academics in gradecentre. Isn't this a waste of resource?

Checking marks - no checking marks report for P/F modules. More room for human error.

# data[].attributes.body
It is very useful but it is quite long and complex so it is sometimes difficult to find out where you are up to.

# data[].attributes.body
Difficult to create the marks checklist.

# data[].attributes.body
Academics need to be made accountable if their marks are late as it causes more work for us.  How can we make sure they meet the deadlines? Could we make sure the academics use the academic calendar when setting their assessment deadlines to ensure their marking will be done on time.

# data[].attributes.body
Can we make the format we need the marks from academics clearer. Takes time going back to them if we don't have the correct info.

# data[].attributes.body
Could we download the marks from GC instead of asking academics to provide them?

# data[].attributes.body
Refreshing immediately

# data[].attributes.body
Could there be a better way of doing this. Spend a lot of time filling this in / counting what marks we are missing. Could we use it in a better way?

# data[].attributes.body
Could we do this differently so academics are just contacted for their marks and not all cc'd into a long email.  (Could we use mail merge).  We could then use the space at the bottom of the email where the module list normally is, to show an example of the format we want the marks in.

# data[].attributes.body
When we are notified of changes prior to the DAB (from the CMR or RoR) we tried to update these before the DAB. It would have been easier to just mention these at the DAB and sort the records out after / have someone sorting them out while the DAB was taking place.

# data[].attributes.body
Easier with a print out version of the reports.

# data[].attributes.body
We feel that the team work really well together in a coordinated way to meet deadlines and get processing done.

# data[].attributes.body
Reports worked well, the extra refreshes are really useful and much quicker. Reports also worked well from home

# data[].attributes.body
This went well and the instructions we had about combining reports and preparing documents were really helpful.
In the DAB reports were easier to view and easier to listen to what people were saying.

# data[].attributes.body
Worked well and really useful

# data[].attributes.body
Would be good to have everything in one place, now seem to have some things on SP and some on N drive

# data[].attributes.body
This process needs firming up so we are clear on who is responsible for chasing late marks

# data[].attributes.body
o   Cross-department module confusion – whose responsibility is marks request/marks inputting?  Also clarification around MRA, CR etc needed.

# data[].attributes.body
o   At DAB time being able to share information/plan can be more difficult now that we are all working from home – regular team online huddles and/or specific MS Teams DAB chat group may be good.

# data[].attributes.body
Please keep forever

# data[].attributes.body
Could this be added to the checklist so that the team managing the DAB have pre-agreed methods of communication for during the DAB. Can get messy and hard to make contact when we have jabber, in zoom chat, WhatsApp...and whatever else

# data[].attributes.headline
The external examiner database is much improved

# data[].attributes.subject
The external examiner database is much improved

# data[].attributes.headline
DAB paperwork - the merging of DAB reports is really good for the smooth running of the DAB

# data[].attributes.subject
DAB paperwork - the merging of DAB reports is really good for the smooth running of the DAB

# data[].attributes.headline
APEL - We must be given access to add APEL in bulk. Having to APEL all L3 and L4 modules was very time consuming.

# data[].attributes.subject
APEL - We must be given access to add APEL in bulk. Having to APEL all L3 and L4 modules was very time consuming.

# data[].attributes.headline
Results release - There are a lot of historical codes when linking module/course codes. These need cleaning up. 

# data[].attributes.subject
Results release - There are a lot of historical codes when linking module/course codes. These need cleaning up. 

# data[].attributes.headline
DAB paperwork - the preparation of the Agenda was delayed due to late additions due to COVID processing

# data[].attributes.subject
DAB paperwork - the preparation of the Agenda was delayed due to late additions due to COVID processing

# data[].attributes.headline
Merging of reports - can all admin staff have access to the software required to do this. It makes the DAB run much smoother,

# data[].attributes.subject
Merging of reports - can all admin staff have access to the software required to do this. It makes the DAB run much smoother,

# data[].attributes.headline
Issues with minor modifications - There was a lot of misunderstanding between academics/quality team/SITS which needed to be ironed out before the exam boards 

# data[].attributes.subject
Issues with minor modifications - There was a lot of misunderstanding between academics/quality team/SITS which needed to be ironed out before the exam boards 

# data[].attributes.body
o   AQS External examiner lists are not up-to-date on curriculum view – could AQS do a DQ check to pick up missing externals?

# data[].attributes.body
Doesn't work for non standard courses and PG. Staff end up having to double check the report and manually add most modules. Time consuming and easy for things to get missed.

# data[].attributes.headline
Trailing students - very labour intensive to ensure these students were completing the correct work so academics could provide the correct marks.

# data[].attributes.subject
Trailing students - very labour intensive to ensure these students were completing the correct work so academics could provide the correct marks.

# data[].attributes.headline
XN overriding an approved RRAA is frustrating. very labour intensive and also needing to check the MRA's and no-detriment students.

# data[].attributes.subject
XN overriding an approved RRAA is frustrating. very labour intensive and also needing to check the MRA's and no-detriment students.

# data[].attributes.headline
PG auto progression - why are some PG course not set up for this? Can be confusing on the reports.

# data[].attributes.subject
PG auto progression - why are some PG course not set up for this? Can be confusing on the reports.

# data[].attributes.headline
No Detriment process - If this is to be used again it needs relooking at as processing the records and recording info was very clunky.

# data[].attributes.subject
No Detriment process - If this is to be used again it needs relooking at as processing the records and recording info was very clunky.