Practical guide
AI fluency for communications and knowledge management
Design communication and knowledge-maintenance exercises that preserve decisions, versions and audience needs.
Communications, administration and knowledge-management teams often turn dispersed information into messages or records others act on. AI can assist that transformation, but the work still needs clear status, source fidelity and ownership. This original guide uses a fictional internal service change to distinguish announcement writing, meeting administration and knowledge maintenance as separate practice tasks.
Choose the artifact's job
Start with whether the output informs, requests a decision or maintains a reference.
A fictional organisation is changing an internal service process. The announcement explains what is changing and when. The meeting record preserves decisions and open questions. The knowledge entry explains the current procedure after approval. These outputs should share facts, but their structures and release conditions differ.
Ask the team to name the reader and next action for each artifact. Do not use an announcement as the only durable process record or treat a meeting summary as proof that every discussed proposal was approved. Selecting the right artifact is part of the work.
Preserve decision status in meeting records
Distinguish discussion, agreement, assignment and unresolved questions.
The fictional notes include a suggested launch date, an approved owner and a question about access. Ask the participant to produce a decision-and-action record. AI may help organize the notes, but the author must check that a suggestion has not become a commitment and that the access question remains open.
Use explicit fields for the decision, owner, timing and dependency where the supplied material supports them. If the notes do not identify an owner, mark that gap instead of assigning one creatively. A complete-looking action table can still be misleading.
Adapt the announcement to the reader
The audience needs usable information, not a condensed transcript of the planning discussion.
For the fictional service change, explain who is affected, what they should do and where unresolved questions should go. Keep background detail only when it helps the reader act or understand a meaningful limitation. Do not bury the effective date under an abstract description of organisational improvement.
Check the announcement against the decision record. If approval is pending, label the message accordingly and do not circulate it as a final instruction. An assistant's confident tone should never be used as evidence that the underlying decision has been made.
Update the reference without erasing history
Knowledge maintenance should distinguish the current procedure from superseded guidance.
Ask the participant to identify which sections of a fictional knowledge entry must change after approval. Preserve a short change note and a route to the responsible owner. Remove contradictory instructions from the active procedure while keeping necessary history in an appropriate place.
Test links, document titles and references to forms or access steps. A correct paragraph pointing to an obsolete form still creates a broken handoff. If a required form is not available in the exercise, state the dependency rather than inventing a destination or assuming it will exist.
Review the information chain end to end
Trace one important fact across the notes, announcement and reference entry.
Change the proposed launch date and ask which artifacts need updating. Check that the meeting record preserves what was actually decided, the announcement uses the current approved timing and the reference does not publish future instructions prematurely. This exposes coordination errors that a sentence-level copy review can miss.
Use the result to select follow-up practice in status discipline, audience adaptation or version maintenance. Keep conclusions tied to the observed artifacts. The communication and delivery capability guide examines a single handoff more deeply; this function map helps leaders choose among the broader coordination tasks their team performs.
Sources and scope
NIST addresses AI risk management. Skills England describes workplace AI foundations.
These sources provide background, not endorsement of this exercise. The worked example and suggested review method are original illustrative guidance. They are not customer results, validated benchmarks or evidence of a particular product capability. Adapt the exercise to the task and use qualified review where consequences require it.
Sources: [1] [2]
Sources
- 1.AI RMF Core · NIST
- 2.AI foundation skills for work benchmark · Skills England