Write & communicate

Turn spoken notes into a structured article

Organize a transcript into coherent prose while preserving the speaker's claims, uncertainty, and voice

7 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.

Spoken notes or transcriptArticle briefFacts and voice to preserve

Your prompt

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

Turn the spoken notes into a structured article.

Complete notes or transcript:
[notes]

Purpose, audience, length, format, tone, and call to action:
[brief]

Required stories, voice, facts, quotations, privacy edits, and verification needs:
[invariants]

Use only content supported by the notes. Remove filler, false starts, and repetition while preserving material qualification, sequence, personal perspective, and uncertainty. Do not convert recollection into verified fact, smooth over contradictions, invent transitions that imply causality, or create quotations from paraphrase. Return: working title; structured article; source map from each section to note markers; statements needing fact-check or permission; unresolved ambiguities; and material edits made. If the desired article requires missing context, use a clearly marked editorial note rather than filling it in.

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

Spoken notes or transcript: [00:00] I started a monthly repair table in our apartment lobby last winter—actually, I think the first one was February, need to check. [01:10] At first it was just me and Sam, and we fixed lamps and loose chair legs. I don't want to claim we save everything. [02:05] The useful thing was neighbors began bringing tools and teaching each other. [03:20] In June the building manager let us use the storage cupboard. Maybe attendance doubled after that, but I never counted consistently. [04:40] One Saturday we could not repair a radio, but its owner showed a teenager how to replace a plug safely; that felt like success even though the radio stayed broken. [06:00] Advice: start with one table, publish what you cannot accept, and find someone who knows electrical safety.
Article brief: 700-word first-person community newsletter article for residents considering a repair table. Warm, practical, not promotional. End with three starting suggestions, not a request to join our event.
Facts and voice to preserve: Keep the radio story and the distinction between repair and learning. Preserve first-person voice. Verify the first event month and storage permission before publication. Do not name Sam; call them a neighbor. Do not claim attendance doubled or quantify waste saved.

Example output

Working title: What One Repair Table Taught Our Building

Last winter, I put a table in our apartment lobby and invited neighbors to bring small household items that needed attention. [Editorial check: confirm whether the first session was in February.] At the beginning, it was simply a neighbor and me tightening chair legs and looking at lamps. We were careful not to promise that everything could be repaired.

The most useful result was not a perfect repair rate. Neighbors began arriving with their own tools, then showing one another what they knew. In June, the building manager allowed us to use a storage cupboard [confirm permission wording before publication], which made keeping basic supplies easier. I cannot say reliably how attendance changed because we did not count consistently.

One Saturday, a radio left exactly as it had arrived: broken. During the session, however, its owner showed a teenager how to replace a plug safely. That moment changed my definition of success. A repair table can produce a working object, but it can also produce practical knowledge and a reason for neighbors to talk.

If you are considering one, start with one table rather than a full program. Publish a clear list of items you cannot accept. Finally, involve someone who understands electrical safety.

Source map: opening 00:00/01:10; shared learning 02:05/03:20; radio 04:40; suggestions 06:00. Removed unsupported attendance doubling and Sam's name. Fact-check: first month and storage permission.

Why this works

1
Source mapping keeps editorial reordering traceable to the original speaker's material.
2
Separate fact-check and ambiguity lists prevent fluent prose from laundering uncertain recollection.

Check the result

Can each material statement be traced to a note marker?
Were quotations, uncertainty, chronology, and personal perspective preserved accurately?
Are missing context and contradictions visible outside the polished prose?

More ways to explore