Stakeholder Database Sample Clauses
Stakeholder Database. In summary • Working group stakeholders (WGS). As part of the co-design initiative, COACCH worked with around 40 stakeholders who were involved in the co-design of the project. These organisations were invited to join the working groups, attending four working group meetings during the project (months 6, 24, 36, 42). The aim was to develop the design and research focus, then continue to provide advice to ensure the research stays relevant to the needs and interests of stakeholders. • Deep engagement stakeholders (DES). From this larger group, around 10 organisations were offered the opportunity to be involved more closely in the project. These so-called ‘deep engagement stakeholders’ benefit from more targeted-research and co-production (within the boundaries of the project), helping to guide case study analysis to provide insights of direct relevance. This focused on practice orientated research, with a bilateral programme of detailed co-design, co-production and co-dissemination. This was anticipated to involve approximately at least one additional bilateral meeting a year (in addition to the workshop) to co-design and co-produce a deep engagement case study, to help ensure the relevance and user-orientation of the research, and to discuss the synthesis material and outputs from the work.
Stakeholder Database. Creation of two main types of stakeholder: WGS and DES. • Identification of other individuals of interest for dissemination purposes. • While it is possible to identify a group of representative stakeholders, maintaining and holding onto a balanced and representative group is something that needs to be actively monitored and managed. • Much greater success was found - in terms of collaboration and use of the COACCH results - when a deep engagement process was followed. • However, the distinction between types of stakeholders (‘working group’ or ‘deep engagement’) may cause unnecessary confusion as well as leading to heterogenous experiences of project engagement (i.e. for those not selected). • For a truly ‘representative’ group, it is important to target specific people as well as an organisation. Engaging with multiple people from an organisation can increase the extent and impact of knowledge co-production as well as minimising the risk of stakeholder ‘bottlenecks’ or drop-out.
Stakeholder Database xlsx format)
Stakeholder Database. Consultant shall create and maintain a database that includes stakeholder groups and interested parties. The database will be updated as the project progresses and will track individuals and groups who express interest in the project. The database will be used to send project updates and notification of engagement opportunities. Update the stakeholder database weekly, or as stakeholders are received, and will average one- hour per week for nine months. • Stakeholders and partnering agencies may include, ODOT, BNSF, Cascades East Transit, City of Bend Accessibility Advisory Board (COBAAC), Neighborhood Associations, adjacent developments, businesses and residential owners, the Transportation Bond Oversight Committee (TBOC), and other interested and/or affected parties.
Stakeholder Database. Update the stakeholder database at regular intervals and provide to RCTC upon request.
Stakeholder Database. Engineer will develop a database mailing/email list of key community leaders, including multi-cultural, faith-based, environmental business and other leaders, as well as organizations and groups that may be affected by field investigations, proposed pipeline routes, or other aspects of TAP. This is also known as a stakeholder database and it will be in a format acceptable to the City that can be manipulated and sortable to maximize its effectiveness as a tool for contacting stakeholders and other interested parties throughout the course of the project. It will include by way of example ▇▇▇▇▇▇ Bridge residents, off-road bicycling club, equestrian clubs, and others who might be impacted by field investigations on District land, parks, and golf courses along the recharge/recovery route.
Stakeholder Database. Consultant shall create a stakeholder database that includes key agencies, residents, property owners, schools, and businesses. This database shall include stakeholder name and contact information, as well as the preferred method of contact and potential key concerns and/or areas of Project interest.
Stakeholder Database. To develop the overall process for the co-production process. A co-production pathway/roadmap will be completed in advance of the first workshop, to set out the proposed process, goals and outcomes. • To identify roles and responsibilities. Based on the proposal, it is proposed that PWA and Ecologic Institute act as the boundary agents for the overall co- production process and that each stakeholder is assigned a ‘relationship manager’ from across the consortium. Additional roles will be discussed and agreed at the first workshop. • To identify potential user needs and decisions. This has been progressed through the development of a stakeholder template, completed for all stakeholders (in Deliverable 1.1). Further user needs will be discussed at the first workshop and key decisions will be identified through the Deep Engagement Stakeholder meetings.