Write & communicate

Adapt writing for a different audience

Change tone and depth while protecting facts and decisions

4 min setupTested with:ChatGPTClaudeGeminiReviewed: 2026-08-27
1

Add your context

Your text stays in this browser. AILesson Prompts does not send it to a model or server.

2

Your prompt

Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt

Adapt the source text for this audience and goal.

Source text:
[source]

New audience:
[audience]

Communication goal:
[goal]

Preserve names, numbers, dates, commitments, decisions, and uncertainty exactly unless the source is internally inconsistent. Change vocabulary, explanation depth, order, and tone as needed for the audience. Do not introduce new claims.

Return:
1. Adapted version
2. Information intentionally preserved
3. Changes made for the audience
4. Any source ambiguity that needs confirmation
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.

From input to outcome

A worked example

See how concrete context turns this recipe into a usable result

Actual input

Source text
On 14 September, Acme Analytics will move the Dashboard service to a new database cluster. The maintenance window is 02:00–02:30 UTC. We expect the Dashboard to remain available, but it may be read-only for up to 8 minutes. Scheduled exports will continue. Customers do not need to take action before the maintenance. Anyone editing a dashboard during the window should save their draft first. The migration has passed staging tests, although the exact read-only duration remains uncertain. We will post updates on the status page.
New audience
Customers who use Acme Analytics but are unfamiliar with databases or infrastructure terminology.
Communication goal
Help customers understand the limited impact, know whether they need to prepare, and find updates during the maintenance.

Example output

  1. Adapted version

Acme Analytics Dashboard maintenance on 14 September

We will perform scheduled maintenance on the Dashboard service from 02:00 to 02:30 UTC on 14 September.

We expect the Dashboard to stay available throughout the maintenance. For up to 8 minutes, however, you may be able to view dashboards without being able to save changes. Scheduled exports will continue as usual.

You do not need to take any action before the maintenance. If you plan to edit a dashboard during this time, save your draft before the maintenance begins.

The migration has passed staging tests, but the exact length of the possible read-only period remains uncertain. We will share progress on the status page.

  1. Information intentionally preserved

The date, maintenance window, possible read-only period, continued exports, lack of required advance action, draft-saving advice, completed staging tests, uncertainty, and status-page updates are unchanged.

  1. Changes made for the audience

Replaced database-cluster language with scheduled-maintenance wording; explained read-only as viewing without saving; moved customer impact and required action ahead of technical context; used a calm, direct tone.

  1. Source ambiguity that needs confirmation

The source does not provide a status-page link or specify which year 14 September refers to.

Why this works

  1. 1

    It defines factual invariants before allowing stylistic change.

  2. 2

    The change log makes silent meaning drift easier to catch.

Check the result

  • Did any number, date, commitment, or decision change?

  • Can the audience understand the required next action?

Keep the work moving