Organize information

Turn a long document into an actionable summary

Condense a document around decisions and next steps while preserving evidence and uncertainty

6 min setupTested with:ChatGPTReviewed: 2026-08-28

Add your context

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

Source documentReader and decisionLength and evidence rules

Your prompt

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

Turn the source document into an actionable summary for the stated reader and decision.

Source document:
[document]

Reader and decision:
[reader]

Length, citation, deadline, and required-detail constraints:
[constraints]

Use only the source. Separate stated facts, recommendations, and your inferences. Preserve material numbers, dates, scope limits, dependencies, disagreement, and uncertainty. Attach a heading, page, section, or short source phrase to every important claim when the source permits. Return: decision snapshot; key findings; actions with owner and due date exactly as stated or marked Not specified; risks and dependencies; open questions; and details intentionally omitted for brevity. Never invent an owner, deadline, consensus, or level of confidence.

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 document: [Section 1: Pilot results] The six-week returns pilot reduced average handling time from 18 to 12 minutes across 420 cases. Two of eight agents were not trained. [Section 2: Customer impact] Complaint rate was 3.1%, compared with 2.8% before the pilot; the team cannot determine causality. [Section 3: Recommendation] Operations recommends extending the pilot for four weeks and training the remaining agents. Finance has not approved the £6,000 training cost. A final rollout decision is planned for 30 November.
Reader and decision: The operations director must decide whether to request funding and extend the pilot.
Length and evidence rules: Maximum 220 words. Cite section names. Keep all metrics, limitations, costs, and dates.

Example output

Decision snapshot: decide whether to seek approval for £6,000 and extend the returns pilot by four weeks; the document recommends both actions, but funding is not approved [Section 3].

Key findings: average handling time fell from 18 to 12 minutes across 420 cases during the six-week pilot [Section 1]. Two of eight agents remain untrained, limiting comparison [Section 1]. Complaints were 3.1% versus 2.8% before the pilot, and the team cannot attribute the change to the pilot [Section 2].

Actions: request training-cost approval—owner and due date not specified; train two remaining agents—owner and due date not specified; extend the pilot four weeks—owner and start date not specified; make the final rollout decision by 30 November [Section 3].

Risks and open questions: funding may delay training; the complaint-rate movement needs investigation; success criteria for the extension are not stated. No material metrics or limitations were omitted.

Why this works

1
A decision-first structure makes the summary useful without hiding the document's limits.
2
Source locators and explicit missing fields make important claims easier to verify.