# data[].attributes.headline
Where does FET/IAG collaboration already work well (or has worked well in the past)?

# data[].attributes.subject
Where does FET/IAG collaboration already work well (or has worked well in the past)?

# data[].attributes.headline
Practical ideas for how we can better work together to enhance our support for students. E.g.​How we communicate our combined offer to students​ / Info sharing between teams:​ What would be useful?​When?​How?

# data[].attributes.subject
Practical ideas for how we can better work together to enhance our support for students. E.g.​How we communicate our combined offer to students​ / Info sharing between teams:​ What would be useful?​When?​How?

# data[].attributes.headline
Where does FET/IAG collaboration already work well (or has worked well in the past)?

# data[].attributes.subject
Where does FET/IAG collaboration already work well (or has worked well in the past)?

# data[].attributes.body
- Events such as Green Careers Week which are open to all students but can benefit from some subject expertise.
- Confident at referring students to support from each other e.g. FET referring students for career guidance appointments
- Sharing information about "priority" schools and how the students in these schools can be supported

# data[].attributes.headline
Practical ideas for how we can better work together to enhance our support for students. E.g.​How we communicate our combined offer to students​ / Info sharing between teams:​ What would be useful?​When?​How?

# data[].attributes.subject
Practical ideas for how we can better work together to enhance our support for students. E.g.​How we communicate our combined offer to students​ / Info sharing between teams:​ What would be useful?​When?​How?

# data[].attributes.body
- Planning and sharing of programme information in advance of the start of term. Explaining why things are being done
- Informal "buddy" system to get to know each other and understand what the teams are working on
- Inclusion of programme specific resources on mycareer rather than individual school Blackboard sites

# data[].attributes.headline
Where does FET/IAG collaboration already work well (or has worked well in the past)?

# data[].attributes.subject
Where does FET/IAG collaboration already work well (or has worked well in the past)?

# data[].attributes.headline
Where does FET/IAG collaboration already work well (or has worked well in the past)?

# data[].attributes.subject
Where does FET/IAG collaboration already work well (or has worked well in the past)?

# data[].attributes.body
- For individual students, referring to appointments. You know you can point them to further support.
- joint IAG/FET meetings in the past (termly and focussed around topics and themes)
- Cross-over in working groups
- Recognition of where joint-working is and isn't necessary (no need to force when not needed)
- FoH can see School I&A appointments

# data[].attributes.headline
Practical ideas for how we can better work together to enhance our support for students. E.g.​How we communicate our combined offer to students​ / Info sharing between teams:​ What would be useful?​When?​How?

# data[].attributes.subject
Practical ideas for how we can better work together to enhance our support for students. E.g.​How we communicate our combined offer to students​ / Info sharing between teams:​ What would be useful?​When?​How?

# data[].attributes.headline
Practical ideas for how we can better work together to enhance our support for students. E.g.​How we communicate our combined offer to students​ / Info sharing between teams:​ What would be useful?​When?​How?

# data[].attributes.subject
Practical ideas for how we can better work together to enhance our support for students. E.g.​How we communicate our combined offer to students​ / Info sharing between teams:​ What would be useful?​When?​How?

# data[].attributes.body
- Can be hard to keep up with things through emails etc so face-to-face meetings / conversations important
- 'informal link' people between teams? Organically connection rather than always needing to make things formal. (fostering a culture?)
- Individuals going to each team meetings again?
- FoH team connecting with members of FET to be able to provide more specific sector knowledge. (and guidance team?)
e.g law students - linking with Jo
- 'mirror-mirroring' between Blackboard and website etc. Things linking both ways.
- Sharing simple means of what's on in each school.
- Some Consultants/Advisers having 'lead' sector/school areas? working with FET team
-

# data[].attributes.body
Good level of understanding/awareness across the two teams about the engagement points within School/Faculty. (Question: do members of the two teams know how to apply this understanding?)

# data[].attributes.body
- Service yearly planner to communicate to students
- Bringing together both team's planning processes. IAG more on a teaching block basis, FET on an annual EPA basis currently. Both teams should be informing each other's plans.
- Re-clarification of what each team's focus is about - over time there has been some overlap/duplication.
- Discussing student personas/student journey.
- Revisit gateway messages to make sure they are student centred, not just what we are trying to push.
- More representation of subjects on the central Careers Service website - avoid duplication on Blackboard of CS resources
- Can we personalise the CS website? e.g. type in student number and see what's available
- Badging and incentivising engagement (e.g. UpReach has good practice around this)
- Develop ways of communicating initiatives with each other. Often ad-hoc, or people are too busy to share. Need to develop a process for regular sharing, knowing how and when to share.

# data[].attributes.body
Worked well in the past: co-delivered Green Week event across faculties, with a focus on sustainability-related careers.

Works well now: signposting e.g. to guidance appointments.

# data[].attributes.body
Practical idea for info sharing: some kind of buddy system, where IAG team members are paired with FET colleagues, to promote both informal 'getting to know you' sessions over coffee and discussion about wider team initiatives, changes, working practices etc.