# data[].attributes.headline
Try to avoid breakouts followed by reporting back in plenary as this procedure mitigates against genuine discussion

# data[].attributes.subject
Try to avoid breakouts followed by reporting back in plenary as this procedure mitigates against genuine discussion

# data[].attributes.headline
Largely information sharing. Reserve discussion to Line Managing meetings; LM then acts as delegate, as it were, in Staff Meetings

# data[].attributes.subject
Largely information sharing. Reserve discussion to Line Managing meetings; LM then acts as delegate, as it were, in Staff Meetings

# data[].attributes.headline
Happy with either but it is nice to meet people face to face

# data[].attributes.subject
Happy with either but it is nice to meet people face to face

# data[].attributes.body
Can ELE colleagues make suggestions for topics covered in staff meetings? Does anyone want to?

# data[].attributes.body
If one meeting has a focus on the planning round, maybe group discussion on course recommendations. There could be an 'open' slot/ half a session where a colleague volunteers to share something that they are working on- particularly on larger projects like year-round pre-sessional, or presents a new course, summarises a course or course change that has been approved at Board of Studies. So a way of having more voices in the meetings. Some things may overlap with CPD though.

# data[].attributes.body
It depends upon the focus of the session but interactions might include open Q&A if documents have been shared beforehand, small group discussion and information sharing with an efficient feedback mechanism, or maybe brainstorming in groups when looking at the action plan for example.

# data[].attributes.body
Space for everyone to hear about and have a voice in upcoming projects, potential changes to e.g. large provision, and action plan. Also a way to build community as we work in different offices and at different times.

# data[].attributes.body
As we're moving back to being on-campus, in-person. Better for discussion and community building.

# data[].attributes.headline
If we have to have breakouts, then used sparingly and/or pre-planned groups rather than random - bringing together colleagues who perhaps don't routinely work together.

# data[].attributes.subject
If we have to have breakouts, then used sparingly and/or pre-planned groups rather than random - bringing together colleagues who perhaps don't routinely work together.

# data[].attributes.headline
More input from Heads of subject areas - what are they thinking and doing?

# data[].attributes.subject
More input from Heads of subject areas - what are they thinking and doing?

# data[].attributes.headline
Receive information with opportunities for comments or questions. Not breakouts and reporting back ... 

# data[].attributes.subject
Receive information with opportunities for comments or questions. Not breakouts and reporting back ... 

# data[].attributes.headline
Inform: to update members on what ELE (COL) is doing (what Heads are working on; what courses are being offered, etc) and is planing to do. As it's such a large audience, I would think more general - and mainly top-down - matters. 

# data[].attributes.subject
Inform: to update members on what ELE (COL) is doing (what Heads are working on; what courses are being offered, etc) and is planing to do. As it's such a large audience, I would think more general - and mainly top-down - matters. 

# data[].attributes.headline
Occasional pre or post meeting coffee/chat if online (to fulfill the early-arrivers' chat/walking-back-to-office chat we miss out on while still somewhat pandemicy

# data[].attributes.subject
Occasional pre or post meeting coffee/chat if online (to fulfill the early-arrivers' chat/walking-back-to-office chat we miss out on while still somewhat pandemicy

# data[].attributes.headline
With actual people, apart from those which are more informative in nature

# data[].attributes.subject
With actual people, apart from those which are more informative in nature

# data[].attributes.headline
Organisational planning, opportunity to give feedback and insights, chance to reflect on vision, purpose and values that underpin our work.  A space to collectively create ELE culture. 

# data[].attributes.subject
Organisational planning, opportunity to give feedback and insights, chance to reflect on vision, purpose and values that underpin our work.  A space to collectively create ELE culture. 

# data[].attributes.headline
Online works well - if we ever go back to a time when we are almost always back in PL, though, then F2F would make sense. (Maybe hybrid / F2F & recorded?) 

# data[].attributes.subject
Online works well - if we ever go back to a time when we are almost always back in PL, though, then F2F would make sense. (Maybe hybrid / F2F & recorded?) 

# data[].attributes.headline
Half an hour of top-down things, including gathering insights from us on the topic; half an hour where we break out into discussion groups so not plenary. Break-out rooms have themes of discussion and peers choose where to go and for how long. Feedback from discussion on padlet ???? 

# data[].attributes.subject
Half an hour of top-down things, including gathering insights from us on the topic; half an hour where we break out into discussion groups so not plenary. Break-out rooms have themes of discussion and peers choose where to go and for how long. Feedback from discussion on padlet ???? 

# data[].attributes.body
This might be controversial and not possible around people's schedules, but I feel they could be longer than 1hr, unless we increase the frequency. Given we now rarely see colleagues, a longer meeting would allow us to have some discussion time as opposed to only info sharing.

# data[].attributes.headline
Termly perhaps or at key moments (term starts and ends, before / after significant events)

# data[].attributes.subject
Termly perhaps or at key moments (term starts and ends, before / after significant events)

# data[].attributes.headline
I think the current frequency is fine. Easy enough to call "extraordinary" meetings if required.

# data[].attributes.subject
I think the current frequency is fine. Easy enough to call "extraordinary" meetings if required.

# data[].attributes.headline
To share information we all need to have; ask for clarification that may be useful to others too; catch up with colleagues; 

# data[].attributes.subject
To share information we all need to have; ask for clarification that may be useful to others too; catch up with colleagues; 

# data[].attributes.headline
I don't mind. A mix? Quite nice to touch base as a team, but at the same time F2F not really necessary.

# data[].attributes.subject
I don't mind. A mix? Quite nice to touch base as a team, but at the same time F2F not really necessary.

# data[].attributes.headline
information-sharing (top-down); peer to peer sharing (horizontal)about highs and lows of day in the life of an ELE Teaching Fellow (not CPD, as you say); a forum for collegiality

# data[].attributes.subject
information-sharing (top-down); peer to peer sharing (horizontal)about highs and lows of day in the life of an ELE Teaching Fellow (not CPD, as you say); a forum for collegiality

# data[].attributes.body
Face-to-face but online is OK