Explain a complex document in plain language

Autor: AILesson5 Min. EinrichtungszeitGetestet mit:ChatGPTGeprüft am: 2026-08-28

Schnelle Antwort

Explain difficult material for a named audience without deleting conditions or uncertainty. Angeben: Complex source, Audience and prior knowledge, Purpose and boundaries. Erwartetes Ergebnis: A plain-language explanation, glossary, example, and accuracy notes.

1

Kontext hinzufügen

Dein Text bleibt in diesem Browser. AILesson Prompts sendet ihn nicht an ein Modell oder einen Server.

2

Dein Prompt

Nicht ausgefüllte Felder bleiben als Platzhalter sichtbar, sodass du den Prompt weiterhin kopieren und bearbeiten kannst.

Explain the source in plain language for the stated audience and purpose.

Source:
[document]

Audience and prior knowledge:
[audience]

Purpose and boundaries:
[purpose]

Use only information supported by the source. Preserve conditions, exceptions, scope, numbers, uncertainty, and distinctions that affect meaning. Define necessary terms on first use and replace avoidable jargon. Use one clearly labeled illustrative example only if it does not imply facts absent from the source. Return: one-sentence point; plain-language explanation; what changes for the reader; glossary; illustrative example; limits or ambiguities; and a factual-preservation check. Do not turn explanation into professional advice or a stronger claim.
Im Playground ausprobieren
Standardmäßig privatDer Prompt wird lokal in deinem Browser zusammengestellt. Gib keine vertraulichen Informationen in einen KI-Dienst ein, es sei denn, deine Organisation erlaubt dies.

Von der Eingabe zum Ergebnis

Ein ausgearbeitetes Beispiel

Sieh dir an, wie konkreter Kontext dieses Rezept in ein nutzbares Ergebnis verwandelt.

Tatsächliche Eingabe

Complex source
The service-level objective is 99.9% successful requests measured over a rolling 30-day window, excluding scheduled maintenance announced at least 72 hours in advance. Error-budget exhaustion triggers a release freeze, except for security fixes and changes approved by the incident commander. The objective is an internal reliability target, not a customer service-level agreement.
Audience and prior knowledge
New customer-support colleagues who know the product but not reliability engineering.
Purpose and boundaries
Help them explain incidents accurately. Do not imply contractual guarantees or tell customers what compensation they receive.

Beispielausgabe

One-sentence point: the team aims for 99.9% successful requests across the most recent 30 days, with specific exclusions and internal consequences, but this is not a customer contract.

Plain-language explanation: “rolling 30-day window” means the measurement period moves forward each day. Planned maintenance is left out only when announced at least 72 hours ahead. The small permitted amount of failure is called the error budget. If that allowance is used up, ordinary releases stop; security fixes and incident-commander-approved changes may still proceed.

For support: describe this as an internal target, not guaranteed uptime or a basis for compensation. Glossary: service-level objective—internal reliability target; error budget—failure allowed within that target; release freeze—temporary stop on ordinary changes. Illustrative example: an announced maintenance window 48 hours ahead would not meet the stated 72-hour exclusion. Limits: the source does not define contractual uptime, compensation, or how successful requests are calculated. All numbers, exceptions, and the SLO/SLA distinction are preserved.

Warum das funktioniert

  1. 1

    It treats exceptions and uncertainty as meaning, not clutter to remove.

  2. 2

    Audience and purpose constraints control depth without authorizing invented advice.

Ergebnis prüfen

  • Are every number, condition, and exception unchanged?

  • Is any illustrative example clearly separated from source facts?

  • Could the audience understand the point without unexplained jargon?

Sicher nutzen

Häufig gestellte Fragen

Praktische Antworten dazu, wann du dieses Rezept verwenden solltest, was du bereitstellen solltest und wo menschliche Prüfung weiterhin wichtig ist.

What should I prepare before using “Explain a complex document in plain language”?

For “Explain a complex document in plain language,” prepare Complex source, Audience and prior knowledge, and Purpose and boundaries. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Explain a complex document in plain language” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A plain-language explanation, glossary, example, and accuracy notes—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Explain a complex document in plain language”?

The published test record for “Explain a complex document in plain language” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

Weitere Möglichkeiten zum Entdecken

Wo dieses Rezept hineinpasst

Bring die Arbeit voran