Stakeholder Engagement And Communications Plan

2y ago
54 Views
2 Downloads
666.32 KB
18 Pages
Last View : 19d ago
Last Download : 2m ago
Upload by : Mollie Blount
Transcription

UniDoc ProjectStakeholder Engagement andCommunications PlanAuthor:Version:Shane Geisler3.5

UniDoc Project – Stakeholder Engagement and Communications Management Plan1 Table of Contents1Table of Contents2Communications Purpose41.12Communications Objectives4Information Needs52.1Key challenges and opportunities5Communication History63Key messages64Recommended Communication Methods84.1Decide what needs to be communicated94.2Establish a regular email communication timeline105Evaluation106Appendices116.1Appendix A – Stakeholder Identification (Group)116.2Appendix B – Key Stakeholder Identification (reference Stakeholder Matrix)126.3Appendix C – Email Templates13M E M O13SUBJECT13UniDoc – Implementing an Electronic Document and Records ManagementSystem13TO13FROM13Division of Information13DATE1315 July 2011136.5Appendix D – Project Communications Accountabilities15Appendix D – Communications Schedule167Document Control177.1Revision History177.2Distribution177.3Approvals18Page 2

UniDoc Project – Stakeholder Engagement and Communications Management Plan7.4Page 3Contact Details18

UniDoc Project – Stakeholder Engagement and Communications Management PlanCommunications PurposeThe UniDoc Stakeholder Engagement and Communications Plan (CP) aims to support project successthrough efficient communication to a range of internal and external project stakeholders. The CPestablishes a formal framework for the creation and delivery of key project communications via the belowapproach: The type of communication;The frequency of communication;Media Type;Presenter; &The intended audience of the communication.1.1 Communications ObjectivesClear and convenient communication will be critical to the success of the UniDoc implementation.Stakeholders occupying the categories of Executives, Management, Support Personnel and interestedparties will have been identified. The objective of the communication plan is to ensure appropriatecommunication takes place with these parties.KeyStakeholderCommunication Objective- Understand the status of the migration at a very detailed level.Project SteeringCommittee (PSC)- Understand how and when to get their organisations to support the change- Are excited advocates for the change- Set expectations regarding the challenges of the migrationProjectManagementGroup (PMG)- Understanding of the broader context of the project- Knowledge of dependencies and interdependencies- Progress and assistance required to Project Manager to coordinate various parts of the project- Understand the status of the migration at a detailed level.OVC, CollegeHeads, ServiceDivision Directors,other Directors,General Managers- Understand the impact to their portfolio/area- Understand what tasks need to be completed and assigned in order to prepare for the migration- Are active engaged in making the move successful- Are excited advocates- Communicate shared information with their portfolios/Managers/Associate DirectorsSpecifiedPersonnel (ITManagers etc),College/DivisionSupportResources, HelpDesk Personnel- Consistently understand what is being done and when so that the message is the same no matterwhat communication point is used.- Understand where to go for education and training- Are excited advocates- Are vested in the change- Know what will happen and when it will take place- Know the steps that they need to complete for a successful transitionProfessional Staff- Are educated about the change and understand how to get training and support- Are excited for the change and see it in a positive light.Page 4

UniDoc Project – Stakeholder Engagement and Communications Management PlanAn outline of the identified stakeholder groups within the UniDoc Project is detailed at Appendix A.2 Information Needs2.1 Key challenges and opportunitiesThe establishment of the UniDoc environment at the University presents a number of challengesand opportunities. Key opportunities include: Increased information management efficiency;Increased positive end user experience through the correct search and delivery of relevantdocuments on demand;Reduced corporate risk;Increased compliance with relevant legislative obligations.In order to maintain stakeholder focus, commitment and morale throughout the project is imperative.The Stakeholder Engagement and Communications Plan seeks to promote these opportunitiesregularly through the delivery of key messages by the Project Executive and Project CommunicationsOfficer, and the ongoing support of embedded Project Champions within Colleges and Divisions.Some of the key challenges are outlined in the table below, together with recommendedcommunications responses to address the challenges if they arise.ChallengesCommunications response(s)·Tight project timelines which, unless managedeffectively, could impact the breadth ofconsultation and quality of outputs····Potential stakeholder confusion about the Projectapproach, scope and / or the nominated projectsolution·····Potential stakeholder dissatisfaction about the opportunities toprovide communication input and influence the the way they are ·communicated·Page 5Directly share with stakeholders the project timelinesand explain the constraints the Project Team is workingunder, as well as communicating the timeline on theProject Team website and project newsletterIdentify and promote opportunities for stakeholders tobe involvedTailor consultation processes where possible to ensurestakeholders have an opportunity to engage ie if there isonly a short period to provide feedback, proactivelyengage with the stakeholder rather than waiting for aresponseClear and agreed messages about the project and keydecisions communicated both formally and informallyCreation of a simple fact sheet/chart which illustrates theproject approach and nominated solution andopportunities to provide inputReiterate the approach at any consultation forumUtilise existing communications forums to convey keymessages (e.g. existing regulator newsletters, links toProject Team website, workshops)Key opportunities for input and decisions advised viamonthly newsletters and Project Team websiteClear and agreed key messages about the project andopportunities to provide input and feedbackDevelopment of a simple fact sheet/chart which illustratesthe process and opportunities to provide inputReiterate the project process at any consultation forumEnsure that all input by stakeholders is appropriatelyaddressed in a timely manner

UniDoc Project – Stakeholder Engagement and Communications Management PlanPotential anxiety among staff about the change··Consistent, regular message to all staffDevelopment of a Change Management Plan in closeconsultation with current Division Heads as required·Clear and agreed messages about the project andfunctional design elements communicated bothformally and informallyStrong leadership by the Project Executive andProject Team membersStrong stakeholder engagement andcommunication processes to ensure stakeholdersare taken on the reform journeyClearly demonstrate the risks and drawbacks ofremaining in the current stateClearly articulate the ‘big picture’ goal and that theproject is working for and the benefits of a best- ‐practiceapproachManaging staff expectations about the software capability··Lack of stakeholder buy in for the proposed solution··Communication HistoryIn 2011, five update memos were sent from July to November to a key stakeholder list including College Heads,General Managers and Directors. These can be found on Alliance. An example of the first memo is below.A website was also launched in May 2011 which was made redundant in August of 2012 when it was replaced withwebpages inline with all projects. This url is information.anu.edu.au/unidocUpdates also featured in the Information Services newsletter, in August 2011 (launch of project details), June 2012(announcing Red Rock as successful vendor), and September 2012 (project update).3 Key messagesAn agreed set of key messages is critical to ensuring consistent communication about the project.These overarching messages should be shared with all project partners, to ensure all partners arespeaking with one voice when communicating externally. These key messages will also becommunicated on the project webpages.What is the UniDoc Project?The UniDoc Project is an Electronic Documents Records Management System Implementation Project.Why are we doing the UniDoc Project? Increased information management efficiency;Increased positive end user experience through the effective search and delivery of relevantdocuments on demand;Reduced corporate risk;Increased compliance with relevant legislative obligations.How will the UniDoc System Function?Non-Technical Description The UniDoc system will utilise a proven EDRMS framework from the Oracle Software Suite. Thesolution will provide three levels of access: User, Super User and Records Manager. All UniDocusers will be able to access the system via a web based user interface or through windowsexplorer. The UniDoc system will allow users to drag and drop files into the UniDoc repository,assign metadata to each document, email documents to colleagues, perform repository widecontent searches (limited by access) and develop document approval workflows.Page 6

UniDoc Project – Stakeholder Engagement and Communications Management PlanTechnical Description The UniDoc system will deploy four Oracle software components, WebCentre Content: CoreCapabilities, WebCentre Content: WCM (Site Studio), WebCentre Content: Records and a scaledOracle Database. The UniDoc solution will be accessible via web based user interface thatprovides full user functionality or via windows explorer view which will offer limited functionality.Functionally, the WebCentre Content: WCM (Site Studio), will store all of the uploaded files andis responsible for the administration of the documentation uploaded/ created in the system, e.g.assigning unique file numbers, saving, moving and versioning etc. The WebCentre Content:Records component of the solution drives the automated workflow and approvals processes andseamlessly integrates into the Oracle EDRMS architecture.What benefits will it deliver?The intended benefits of the UniDoc Project are fourfold: Increased information management efficiency Correct and relevant documents on demand Reduced corporate risk Increased document / record discoveryWhat can I be doing now?The intended benefits of the UniDoc Project are fourfold: Increased information management efficiency Correct and relevant documents on demand Reduced corporate risk Increased document / record discoveryWhen will the UniDoc Project be Deploying in my work area?The intended benefits of the UniDoc Project are fourfold: Increased information management efficiency Correct and relevant documents on demand Reduced corporate risk Increased document / record discoveryHow will the UniDoc Project affect me?The intended benefits of the UniDoc Project are fourfold: Increased information management efficiency Correct and relevant documents on demand Reduced corporate risk Increased document / record discoveryLatest Updates and Frequently Asked Questions (FAQs)The most up to date news on this project and a list of Frequently Asked Questions will be availablethrough the latest updates tab on the project webpage. This will also ideally be RSS fed to subscribers.Direct email templates for stakeholder engagement can be found in Appendix C.Page 7

UniDoc Project – Stakeholder Engagement and Communications Management Plan4 Recommended Communication MethodsTo ensure that key project messages and updates are distributed to a broad range of interestedstakeholders it will be necessary to determine the best methods to be used in communicating with allstakeholders. Possible methods include the following:MeetingsIn addition to regular meetings facilitated by the Associate Director Service Delivery and Engagementwith University Executives, The Project Steering Committee (PSC) and Project Management Group(PMG) will meet regularly and one-on-one meetings will occur as needed with key stakeholders.Special Events / PresentationsThe delivery of keynote speeches or functional demonstrations by senior executives at key times throughthe project (e. g. CIO Quarterly Update) will reinforce to the stakeholder population the commitment ofthe executive to the successful delivery of the project objectives.DoI and ANU PublicationsAn ongoing presence in the University’s established print media including the monthly newsletter, TheLink, ANU Reporter (where appropriate), and the new Executive Director of Administration and Planningnewsletter will assist in communicating regular project status updates and achievements to the widerstakeholder demographic.Project Webpage / Banner UpdatesIt is recommended that a project webpage is created and made available to all interested projectstakeholders. Feature boxes or banner updates can be used to draw attention to a ‘latest update’ on aproject page. The project webpage should contain the following information, with the first 3 titles belowbeing available from the beginning of the project: Project OverviewProject ObjectivesProject ContactsProject TimelineProject Latest Updates tabKnown Issues and/or Frequently Asked Questions (FAQs)DocumentationSocial Media (including Blogging and RSS for latest updates, when appropriate)To ensure that the information regarding the project is disseminated to a broad stakeholder range, it isrecommended that social media is utilised to communicate on behalf of the project. Suggested socialmedia approaches include: Page 8Links or references to be hosted on the ANU Student Association (ANUSA) Facebook pageANU Facebook postsANU Twitter posts (140 characters or less)DoI Facebook postsDoI Twitter Account (140 characters or less)RSS Feeds from project webpage, Latest News tab – to be developedANU Yammer postsANU Vision (for launch training video, if applicable)

UniDoc Project – Stakeholder Engagement and Communications Management PlanEmail All staff/students emails to user populationTargeted key stakeholder emailsPrint MediaThe utilisation of print media (ITS Link & On Campus) to promote the project at specific stages will assistto raise the public profile of the project and may generate strong interest in the outcomes and individualimpacts to the end user of successful project delivery.Stakeholder SurveysAt stages of the project when feedback is imperative, surveys to key stakeholders may be an appropriateway to seek feedback.Feedback (through functional email address)A functional email address will be created, monitored and utilised for receiving and responding tostakeholder feedback.4.1Decide what needs to be communicatedThe information to be distributed to Stakeholders will need to be determined.Key StakeholderCommunication ObjectiveCommunication Medium- Understand the status of the migration at a very detailedlevel.Project SteeringCommittee (PSC)- Understand how and when to get their organisations tosupport the change- Regular Face to Face Meetings- Targeted Emails- Are excited advocates for the change- Set expectations regarding the challenges of the migration- Understanding of the broader context of the projectProject ManagementGroup (PMG)- Knowledge of dependencies and interdependencies- Progress and assistance required to Project Manager tocoordinate various parts of the project- Regular Face to Face Meetings- Targeted Emails- Understand the status of the migration at a detailed level.OVC, College Heads,Service DivisionDirectors, otherDirectors, GeneralManagers- Understand the impact to their department- Regular Face to Face Meetings- Understand what tasks need to be completed andassigned in order to prepare for the migration- Briefing Workshops- Are active engaged in making the move successful- Regular Status Updates- Targeted Emails- Are excited advocates- Communicate shared information with theirportfolios/Managers/Associate Directors- Regular Face to Face MeetingsSupport Personnel (ITManagers)College/DivisionSupport Resources,Help Desk Personnel- Consistently understand what is being done and when sothat the message is the same no matter whatcommunication point is used.- Understand where to go for education and training- Are excited advocates- Are vested in the change- Localised Training Workshops- Tailored Emails- Regular Status Updates- Advertising Campaigns- Champion Interaction- ‘Look and feel’ workshops- Controlled release of ANU ServiceDesk Demo EnvironmentPage 9

UniDoc Project – Stakeholder Engagement and Communications Management Plan- Localised Training WorkshopsProfessional Staff- Know what will happen and when it will take place- Tailored Emails- Know the steps that they need to complete for asuccessful transition- Regular Status Updates- Are educated about the change and understand how toget training and support- Change Champion Interaction- Are excited for the change and see it in a positive light.- Advertising Campaigns- ‘Look and feel’ workshops- Controlled release of ANU ServiceDesk Demo Environment- Library Information screens4.2Establish a regular email communication timelineThe primary method of communication between the migration team and the rest of the organisation willbe email and through the specific project webpages. All UniDoc related emails will be sent on a specificschedule as seen at Appendix E (N.B. this timeline may vary depending on the needs of the project).5 EvaluationAn evaluation framework for the CP will be developed following approval of the plan and will bedocumented in the Benefits Realisation Plan.Page 10

6 Appendices6.1 Appendix A – Stakeholder Identification (Group)Stakeholder GroupMethod of Communication- Regular Face to Face MeetingsProject Steering CommitteeEngagement TypeInvolve & Collaboration- Targeted Emails- Regular Face to Face Meetings- Briefing WorkshopsProject Management GroupInvolve & Collaboration- Targeted Emails- Regular Status Updates- Regular Face to Face MeetingsOVC, College Heads, Service Division Directors, otherDirectors, General Managers- Briefing WorkshopsInvolve & Collaboration- Targeted Emails- Regular Status UpdatesConsult- Regular Face to Face MeetingsGroupExecutive Assistants- Localised Training Workshops- Tailored EmailsSupport Personnel (IT Managers) College / DivisionSupport Resources, Help Desk Personnel- Regular Status UpdatesInvolve & Consult- Advertising Campaigns- Champion Interaction- ‘Look and feel’ workshops- Controlled release of scripted ANU Service Desk DemonstrationVideos- Localised Training Workshops- Tailored Emails- Regular Status UpdatesProfessional Staff- Advertising CampaignsConsult- Change Champion Interaction- ‘Look and feel’ workshops- Controlled release of ANU Service Desk Demo Environment- Library Information ScreensInformConsultThis Stakeholder Group contains individualswho require a broad level of awareness of theproject. These stakeholders may also beinfluential/ important conduits of information toother stakeholders.This Stakeholder Group contains individuals whohave a requirement to possess a goodunderstanding of the project and will be invited toprovide input at critical pointsInvolveThis Stakeholder Group contains individualswho have a high- ‐level ofengagement with the project and are involvedin the decision- ‐making process.CollaborationThis Stakeholder Group contains individualstakeholders who are responsible for drivingthe project.

Executive DirectorProject Steering CommitteeDr Brok Glenn(Administration and Planning),University ExecutiveOffice of the Vice ChancellorProject Steering CommitteeToni MakkaiDeanCollege of Arts and Social SciencesProject Steering CommitteeMick SerenaDirectorFacilities and Services DivisionProject Steering CommitteePeter NikoletatosDirectorDivision of InformationCollege Heads, Service Division Directors,General ManagersProf John HoskingDean and DirectorCollege of Engineering and Computer ScienceCollege Heads, Service Division Directors,General ManagersMichelle SearleCollege General ManagerCMBE & CPMSCollege Heads, Service Division Directors,General ManagersTim BeckettRegistrarDivision of Student Administration & Student ServicesCollege Heads, Service Division Directors,General ManagersRoxanne MissinghamUniversity Librarian (Chief ScholarlyInformation Officer)Scholarly Information Services / LibraryCollege Heads, Service Division Directors,General ManagersKaren HillGeneral ManagerFacilities & Services DivisionCollege Heads, Service Division Directors,General ManagersAlison DaunGeneral ManagerANU College of LawCollege Heads, Service Division Directors,General ManagersRon WattsDirector – Human ResourcesHuman Resources DivisionCollege Heads, Service Division Directors,General ManagersDavid AkersGeneral ManagerANU College of Asia and the PacificProject Management GroupJulie GorrellSenior Project ManagerOffice of the Vice ChancellorProject Management GroupJoan AngelAssistant Registrar, Student BusinessSystemsDivision of Student Administration & Student ServicesProject Management GroupRoslyn MarkezicAssociate Director, HR Services &InformationHuman Resources DivisionProject Management GroupSam BullenManager HR Systems, HR Services &InformationHuman Resources DivisionProject Management GroupMaggie ShapleyUniversity Archivist, University Records,Division of InformationDivision of InformationProject Management GroupDavid BrumbyRecords Manager, University Records,Division of InformationDivision of InformationSpecified Personnel (IT Managers etc),College/Division Support Resources, Help DeskPersonnelGeorge LovrincevicIT ManagerCollege of Arts and Social SciencesSpecified Personnel (IT Managers etc),College/Division Support Resources, Help DeskPersonnelDavid RichardsonAssociate Director, InfrastructureServicesDivision of InformationSpecified Personnel (IT Managers etc),College/Division Support Resources, Help DeskPersonnelAllison LawrenceLawyerUniversity Legal Office

6.3 Appendix C – Email TemplatesIn 2011, five update memos were sent from July to November to a key stakeholder list including College Heads, GeneralManagers and Directors. These can be found on Alliance. An example of the first memo is below.A website was also launched in May 2011 which was made redundant in August of 2012 when it was replaced withwebpages inline with all projects. This url is information.anu.edu.au/unidocMEMOSUBJECTUniDoc – Implementing an Electronic Document and Records Management SystemTOProject Steering CommitteeDr Brok Glenn, Executive Director (Administration and Planning);Ms Anne Kealley, Acting Director Information Services, Division of Information;Professor Toni Makkai, Dean, College of Arts and Social Sciences;Mr Mick Serena, Director, Facilities & Services Division;UniDoc Project SponsorsDavid Akers, Jenny Carlin, Len Tomlinson, Maggie Shapley, Mark Erickson, Michelle Searle, Mr Brian Lane, Mr WayneFord, Ms Julie Gorrell, Ms Kathrin Kulhanek, Nadine White, Peter Shipp, Prof Andrew Cockburn, Rachel Vance, RoslynMarkezic, Tony Wynack, Vanessa QuigleyUniDoc Project BeneficiariesAlistair Rendell, Allan Williams, Andrew MacIntyre, Cameron Neal, David Sturgiss, Dr John Wellard, Ken Grime,Lachlan Murdoch, Nancy Eyers, Paul Wong, Prof Jayne Godfrey, Prof Nicholas Glasgow, Prof Toni Makkai, ProfessorAidan Byrne, Ron Watts, Sharon Bainbridge, Tracy Chalk, Trevor LangtryUniDoc Project ParticipantsBrigid Lever, Cameron Neal, Carol McAlwee, Carrie Raftery, Donna Webster, Joan Angel, Ms Delia Ritherdon, Ms SamBullen, Nalini Nair, Sue Clarke, Tim MacPhersonFROMDominy Evans, Associate Director, IT InfrastructureDivision of InformationDATE15 July 2011Dear Colleagues,In December of 2010 the Director of Information Services wrote “I write to inform you that the University has granted approval to proceedwith the acquisition and implementation of a University-wide Electronic Document and Records Management System (EDRMS). Theinitiative has strong support from Colleges and Service Divisions and has been ranked as high priority following the deliberations from thePlanning Advisory Committee process in 2010”Subsequently in December 2010 each Service Division and College was asked to nominate persons to participate in a procurementexercise, to acquire “common off the shelf” Electronic Document and Records Management software through a formal Request forProposal (RFP) process. This RFP process is now nearing completion.The project to implement this new software goes by the working title of UniDoc. It is now underway under the sponsorship of Dr BrokGlenn, Executive Director (Administration and Planning), University Executive, and will formally commence once the RFP processreaches a successful conclusion.Following on from prior reports, audits and pilot projects undertaken over recent years, UniDoc has the following, declared objectives andattendant benefits: Improve the management of the University’s information through the implementation of an EDRMS across the University’sbusiness areas; leading tooimproved work efficiency through workflows that provide control and standardisation andoan improved ability to work remotelySupport the creation/capture, revision and management of documents and records throughout their lifecycle; leading tooimproved ability to find and access relevant information quicklyogreater confidence that all business records can be read, used, and regarded as authenticoestablished rules for retention and disposition of recordsAssist in the compliance with standards and legislation; leading tooimproved compliance with recordkeeping and other business and statutory requirementsEnhance the sharing of information across the University; leading to

UniDoc Project – Stakeholder Engagement and Communications Management Planelimination of the waiting period for accessing files by multiple people, as tasks can now occur in parallel rather thansequentiallyoestablished security and authorised access to documents and recordsoa complete and reliable audit trailRemove the duplication, inefficiencies and risk associated with current practices; leading tooelimination of the “Multiple Original Syndrome”oreduction in physical storage, photocopying, paper and other consumables costso The ANU, through this RFP, is also seeking the help of an experienced partner in achieving these goals. It is expected that such a partnerwould bring experience in other, similar tertiary environments, and that this experience will be pivotal in determining the final scope andpriorities of this critical project.(Please note: information regarding the current RFP process is confidential and is not contained on the abovementioned Alliance site.Any queries about the procurement process may be directed to the Associate Director of Information Technology Infrastructure, Divisionof Information)thNext news bulletin 29 July: Progress to date; ANU participants in the project; branding.With RegardsDominy EvansAssociate Director, IT InfrastructureDivision of Information14

6.5 Appendix D – Project Communications AccountabilitiesCommunications ActivityMeetingsSpecial Events / PresentationsDoI and ANU PublicationsUniDoc Webpages and Banner updatesSocial MediaBlog / RSSEmailWebsite MessagingMobilePrint MediaStakeholder SurveysFeedback through functional email CICIICIIResponsible - Those who do work to achieve the task. There can be multiple resources responsible.Accountable - The resource ultimately accountable for the completion of the task. There must be exactly one A specified for each task.Consulted - Those whose opinions are sought. Two-way communication.Informed - Those who are kept up-to-date on progress. One-way communication.Note:Accountable Assumes IIIIIIII

OVCCollege HeadsCollege General ManagersService Division DirectorsCollege IT ManagersITS ExecutiveOMG MembersCollege General ManagersService Division DirectorsCollege IT ManagersITS ExecutiveITS StaffOMG MembersEmailMonthly ITS Portfolio Schedule ITS Portfolio Summary ITS Portfolio ScheduleMajor Project BriefMajor Project TimelineITS Portfolio SummaryITS Portfolio ScheduleAD Service Delivery and EngagementEmailFortnightly NewsletterMonthly ‘The Link’Service Delivery and Engagement ClientsMeetingScheduledITS ClientsMeetingScheduledOMG MeetingCollege General Manager / Service Division Director MeetingMeetingMeetingFortnightlyMonthly -ITS Program Road showTown HallQuarterly-ITS ExecutiveMeetingFortnightly-OMG ChairCIOAD Project OfficeAD Service Delivery and EngagementAD Service Delivery and Engagement / AD POEnd UsersWebpageTargeted EmailRoad ShowAs required-Project DirectorsAll staffAll studentsWebpageTargeted EmailAs required-Project DirectorsITS Portfolio SummaryITS Portfolio ScheduleITS Portfolio SummaryITS Portfolio ScheduleProject Communications Officer(Sharmeen Hussain interim) – PM co-ordinationITS Outreach - review, approval and distributionITS Outreach - developmentITS Executive – Review and approvalITS Outreach - distributionAD Service Delivery and EngagementCIO

7 Document Control7.1 Revision HistoryRevision DateVersionAuthor InitialsSummary of ChangesNew standard “Background”Include Governance RolesAdd College of Law in “Org as Stakeholder” listUpdate of stakeholder list to reflect Alliance siteCompress Messages into one tableAdd Reporting and Meetings rContent pdate from PMG review22/8/123.2SGeislerComplete document redraft post PMG comments6/9/123.3SGeislerDocument update with PMG comments24/09/123.4CGoughUpdates to document including history of 2011 and 2012 communications,reviewing communications methods, consistency, and adding specificANU publ

The Stakeholder Engagement and Communications Plan seeks to promote these opportunities regularly through the delivery of key messages by the Project Executive and Project Communications Officer, and the ongoing support of embedded Project Champions within Colleges and Divisions. Some

Related Documents:

Stakeholder Engagement Plan - SNNP IAIP & RTC Draft January 2017 The EIA Guideline document (2000) and the EIA Procedural Guideline (Series 1, 2003) provide specific recommendations for stakeholder engagement. Stakeholder engagement at the scoping stage typically follows the following process:

‘stakeholder management’, ‘stakeholder analysis’ and ‘stakeholder engagement’, and also clarifies the interrelationship among these three terms. Section 3 sets out the methodology followed to investigate the practice approaches for stakeholder analysis and engagement i

Oct 15, 2020 · This site includes a downloadable pdf template and a Google Sheet you can copy . 17 2. Stakeholder Analysis (6 of 11) Who are they? Tool A. Stakeholder Register. 18 2. Stakeholder Analysis (6 of 11) Who are they? Tool A. Stakeholder Register. 19 2. Stakeholder Analysis (7 of 11) Who are they?

Stakeholder Engagement Plan - Stakeholder Mapping - Information Disclosure and External Communication - Community Grievance Mechanism - Monitoring and reporting Additionally, the SEP includes the guidelines for the implementation of stakeholder engagement act

Analyzing stakeholder perspectives against the engagement objectives is critical to developing an effective engagement strategy. Primary analysis variables to consider for each stakeholder are: Power: the stakeholder’s content expertise an

need some form of stakeholder analysis. Stakeholder analysis focuses on the stakeholder’s importance to the project, and to the organization, the influence exerted by the stakeholder, plus stakeholder participation and expectations. A Stakeholder Expectations Questionnaire may be used to analyze sp

17 BAB II LANDASAN TEORI A. Teori Stakeholder (Stakeholder Theory) Ramizes dalam bukunya Cultivating Peace, mengidentifikasi berbagai pendapat mengenai stakeholder.Friedman mendefinisikan stakeholder sebagai: “any group or individual who can affect or is affected by the achievment of the organi

Apr 03, 2018 · Stakeholder Mapping Sample Stakeholder Maps Stakeholder “Flavors” External Program Service/Agency Team Sample Stakeholder Map Template. 4/2/2018 6 Sample USMC Program Stakeholder Map Marine Corps Program Mgr MARCORSYSCOM Product