# data[].attributes.body
Establish sustainable team-building and training programmes during non-response periods

Long-term support from funders during non-response periods

# data[].attributes.body
Standardise incorporating response-driven work into criteria for doctoral theses and promotion

# data[].attributes.body
Promote leave-taking and respecting work hours

Clarify communication about processes and rewards across career stages

Integrate support roles into research teams

Standardise the onboarding of new team members

# data[].attributes.body
UKHSA has several HPRUs on pandemic preparedness including lshtm/imperial on modelling, Birmingham on panprep.

# data[].attributes.body
UKHSA is developing generic model for panprep covering 5 modes of transmission. There should be more standard uk models for diseases including aids, tb, syphilis, flu etc

# data[].attributes.body
NIHR should fund resilency to academic Centre’s to support response work.

Also, Wellcome could support.

It is important to work on resilency because development funding is going to decrease significantly in near term

# data[].attributes.headline
Who should decide what teams, and how they should be resourced given funding is finite?  

# data[].attributes.subject
Who should decide what teams, and how they should be resourced given funding is finite?  

# data[].attributes.body
At a global research community level I'm involved with a theme issue proposal for Proc R Soc B on disease modelling on the African Continent aimed at raising the profile of the modelling community in Africa - if you know or work with anyone based in Africa then send them my way!

# data[].attributes.body
Difficult to quantify impact of software packages. Not everything is packagable (e.g. bespoke cleaning scripts).

The "real currency" is publications but it is a) hard to convert all software into publication, b) software is poorly cited.

# data[].attributes.headline
On psychological support, can be differences in provision between staff and students (& what is offered by different institutions)

# data[].attributes.subject
On psychological support, can be differences in provision between staff and students (& what is offered by different institutions)

# data[].attributes.body
Staff may have access to Employee Assistance Programmes (EAPs)

Students may have a separate wellbeing support service.

# data[].attributes.body
We discussed different institutional approaches to 'bridging' after pre-faculty staff end date: 1) 'workforce model', where there is some departmental support to allow pool of staff between postdoc & faculty to react to incoming consultancy requests; 2) dept creates reactive teaching posts (but could instead have staff funded more predictably); 3) staff moving to other projects in the centre/department, which requires large volume of wider groups/projects and can limit reactivity to new response requests.

# data[].attributes.body
Traditionally, code pipeline development and application to a specific problem (e.g. outbreak scenarios) is heavily reliant on small number of individuals, who cannot easily handover in real-time (and hence take time off). The more of the code base that is predictable and commonly known (e.g. through training, documentation and interoperability with other common tasks), the easier this would be.

# data[].attributes.body
Even though response work is not always high profile, the senior staff should keep an eye on the future of the staff on their teams and what they needed for future career steps. Journal prestige is not always as important as having things lodged in the record.

# data[].attributes.body
Beyond our own teams within universities, I think it's worthwhile establishing best practices for recognising contributions and conducting knowledge-sharing programmes with local individuals on the ground. Ultimately, these are the people affected by many of our studied pathogens, and have knowledge of local factors (including the dynamical and observation processes).

# data[].attributes.headline
Juniper good for support on this in all areas

# data[].attributes.subject
Juniper good for support on this in all areas

# data[].attributes.body
Especially for smaller groups

# data[].attributes.body
Outside of response periods, they do periodic training of staff in the response tools that they have in house so that they are trained and ready to respond if needed.

# data[].attributes.body
Some people want to work a lot and it would be "wrong" to stop them. But if people need/want to working hours that MUST be respected.

# data[].attributes.headline
Prepared pipelines for pre-processing data, software best practices,...

# data[].attributes.subject
Prepared pipelines for pre-processing data, software best practices,...

# data[].attributes.body
I feel that several people did a lot of similar routine work simultaneously (e.g. data pre-processing). Having a clear pipeline prepared could save time at the beginning of an emergency.

# data[].attributes.body
Some of the turn-crank work, e.g. weekly reports, short term forecasts, would be automated from now on. Some of this was really where people got burnt out.

Go-Science/Spi-m could be taking a lead on this.

# data[].attributes.body
Groups such as admin staff, HR, those providing psychological support, etc should be able to be stepped up in line with the researchers

# data[].attributes.body
I hear tell that the next REF will have a stronger push on recognising outputs that are not papers. We as a community surely have done power to push this. Let's!!