Volver a la biblioteca

Stakeholder Map and Communication Plan

Stakeholder Map and Communication Plan converts stakeholder role, project impact, influence level, information need into stakeholder register and communication calendar with audience, purpose, message, channel, cadence, owner, decision dependency, and evidence, with cited evidence, explicit rules, and unresolved exceptions. Use for stakeholder map and communication plan, recurring review, and decision preparation.

por adlass TemplatesVersión 1Usa herramientas de adlassUniversal

Publicado 21 de ago de 2026 · Actualizado 26 de ago de 2026

Útil · 0Ver SKILL.md sin formato

Requisitos

Map the process identifiers, source columns, and row citation convention. Add the governing policy, rubric, schema, or reference tables to the scope. Define thresholds, status values, units, and exception severity.

Documento de la habilidad

El SKILL.md completo que tu agente lee y sigue.

Stakeholder Map and Communication Plan

Purpose

Stakeholder Map and Communication Plan turns the supplied records into stakeholder register and communication calendar with audience, purpose, message, channel, cadence, owner, decision dependency, and evidence. It keeps source facts, derived values, recommendations, and limitations separate so each conclusion can be checked.

Scope

Cover stakeholder role, project impact, influence level, information need, message, channel, cadence, owner, decision right, escalation trigger. Preserve source identifiers, dates, units, and wording needed to trace every result.

Excluded for stakeholder audiences and governance cadence: changing source records, taking external actions, making a human approval or employment decision, and asserting facts absent from the corpus.

Data basis

  • Process documents and tables containing stakeholder role, project impact, influence level, information need, message, channel, cadence, owner, decision right, escalation trigger.
  • Company policy, rubric, schema, templates, and reference tables in scope.
  • Run input for period, audience, entity, or threshold when it changes this run.

Result

Produce stakeholder register and communication calendar with audience, purpose, message, channel, cadence, owner, decision dependency, and evidence. Each material row and conclusion cites a document, section, page, row, field, or run input.

Quality criteria

  • Every audience, channel, owner, and escalation coverage record is included or has an exclusion reason.
  • Calculations state fields, units, denominator, and rule.
  • Missing, contradictory, stale, and ambiguous values stay labelled rather than guessed.
  • Facts, interpretations, and proposed next actions use separate fields.
  • Supplied terminology, thresholds, and status values are used consistently.
  • The final limitations section states what the corpus could not establish.

Instructions

Use the organization chart and governance plan. Distinguish influence, impact, and engagement. Do not infer preferences or assign owners without evidence. Every recurring communication needs purpose, audience, cadence, owner, and trigger. Preserve original values beside normalized values, cite every material finding, and use “not assessed” when required evidence or a rule is absent. When sources disagree, show both citations and explain the conflict. Keep row-level evidence in the supporting sheet and summarize only supported conclusions in the document.

Adapt before use

  • Map the organization-chart and stakeholder mapping fields and row citation convention.
  • Add the governing policy, rubric, schema, or reference tables to the scope.
  • Define thresholds, status values, units, and exception severity.

Habilidades relacionadas

  • Change request assessment

    Assesses a project change request against the approved baseline and produces a traceable impact analysis for scope, schedule, cost, quality, risk, resources, and dependencies. Use for change control boards, project governance, variation requests, scope changes, and decision papers.

  • Construction change-order pack

    Builds a documented construction variation package from the change trigger, contract terms, quantities, rates, and time effects. Use for change orders, variation claims, owner instructions, design changes, and subcontractor pricing review.

  • executive document brief

    Creates a source-linked executive document brief deliverable using concrete fields, rules, exceptions, and review controls. Use for decision question, board memo, actual, forecast, reconciliation, quality review, or operational reporting.

  • hr record data quality

    Creates a source-linked hr record data quality deliverable using concrete fields, rules, exceptions, and review controls. Use for employee_id, hire_date, manager_id, duplicate, reconciliation, quality review, or operational reporting.