Page 216 - CyberSecurityEssentialsEnglish

The applications that follow do not cover every kind of work equally. They focus on three
bundles that recur inside organizations: documents and communication, meetings and
decisions, and data and briefing. Policies, translation, and presentations appear as

institutional outputs that need the same foundation: a clear source, an appropriate step, a
quality gate, and an approval owner.

5.5 The Documents and Communication Workflow: From Source to Approval

◆ Key idea: professional writing is an approval cycle, not a moment of
generation.

Professional writing is not a moment of generation. It is a cycle that begins by defining
the purpose, the sources, and the audience, then drafting, then checking facts, tone, and
commitments, then approval, distribution, and archiving.

AI can accelerate the preparation of emails, letters, reports, and memos, but the largest
saving does not come from writing sentences. It comes from reducing the search for
information, the reformatting, and the repeated revisions. We therefore build a single

request template that defines the type of document, the purpose, the recipient, the tone,
the sources, the deadline, and the limits of what may be said.

The process begins when you assemble a source pack. It may include a previous decision, a
table, or correspondence. Separate confirmed information from unapproved notes. You

then build a content map before drafting: what is the core message? What is required of the
reader? What is the evidence? What are the attachments? This map prevents long text that
leads to no action.

The model can produce a first draft, or several, and the draft then passes through gates:

checking names, figures, and dates; checking legal or financial commitments; checking tone;
checking that attachments are complete; and then approval. In sensitive messages, the
human sender must be able to explain every sentence, not merely feel that the text looks

fine.

Summarizing inside a workflow requires deciding what kind of summary is needed. An
executive summary focuses on the decision, the impact, and the options; a follow-up

summary focuses on commitments and deadlines; and a technical summary preserves
terminology and constraints. Using one summary for every purpose deletes what the actual
reader needs.

215