Open
No relevant speech has been verified yet. A review may still be pending.
Start with the notes you already have. Find the right format, build your checklist, and walk into rehearsal ready.
Use a plain-text (.txt) or Markdown (.md) file saved as UTF-8. Put each talking point on its own line. For a predictable outline, use a dash and a space before each cue.
Use one idea per line. A cue is a reminder of what to cover.
Indent a bullet with two spaces to add a sub-cue under the preceding cue.
In the presentation editor, under Talking points, choose “Import Markdown or text file.”
- Explain the problem - Share a customer example - Describe the impact - Introduce the solution - Close with the next step
Have a multi-part point? Indented bullets become sub-cues. The parent is set to require all its sub-cues. Review the imported outline before saving.
Plain lines and numbered lists also work. Bullets can start with -, *, +, or • followed by a space. A line wrapped in bold, such as **The problem**, creates a parent for the unordered bullets that follow. Use indented bullets for the clearest hierarchy; deeper indentation still creates direct sub-cues, not extra nesting levels.
You can paste text under Talking points. Text-based PDFs can also be imported, but extracted line breaks may need cleanup. Scanned PDFs need conversion to selectable text first. For the most predictable results, use .txt or .md. Lines beginning with Presentation:, Target:, or Duration: are skipped; enter those details in the editor.
Slide notes use a separate import. Start each slide with a Markdown heading (# followed by a space). The text underneath becomes that slide’s speaker notes, up to the next heading.
# The problem Share a customer example. Describe the impact. # The solution Explain what changes and why. # Next steps Ask for a decision.
Share a customer example.
Describe the impact.
Explain what changes and why.
Ask for a decision.
Under Slide notes (optional) in the presentation editor, choose Import Markdown slide notes. Review the titles and speaker notes before saving.
Two imports, two jobs. Talking points build the checklist. Slide notes organize speaker notes; they do not add cues to your checklist or import a PowerPoint or Keynote deck.
Covered stays Covered. Once an automatic cue is covered, it stays covered for that session, including pause and resume. You can change its status manually.
A point gets an automatic checkmark when the recognized speech supports every completion requirement. You can use your own phrasing.
List what must be communicated in Completion requirements. If you leave that list empty, the point’s title and coverage detail define what is needed.
Apple’s on-device language model compares the meaning with each requirement, using recent speech and supporting passages retained for that unfinished point.
The app checks that quoted evidence exists in the transcript. It also checks required numbers and directions of change, and looks for missing information or conflicts before adding a checkmark. Required causes get an additional review for contradictory timing or a denied effect.
No relevant speech has been verified yet. A review may still be pending.
Relevant speech was found, but completion is not verified. You may have named the topic, covered only part of it, or spoken words that need another check.
Every requirement has supporting speech and the completion checks passed. It stays Covered for this session, including pause, resume, and recovery, unless you change it manually.
Emerging is a progress signal. It is not a percentage or a checkmark. Unfinished points can change as recognition is revised.
Point: Explain the launch delay and our response.
Requirements: Explain that a staff shortage delayed the launch, and explain hiring contract staff as the response.
“Let’s talk about the launch delay.”
The subject is named; the explanation is still missing.
“We couldn’t launch on time because we were short-handed.”
The cause is explained; the response is still missing.
“We couldn’t launch on time because we were short-handed. To catch up, we’re bringing in temporary help.”
Different wording communicates both required ideas.
Illustrative examples. Actual results depend on the recognized words and the local model’s assessment.
There is no fixed similarity percentage. A brief paraphrase can count if it communicates every required fact and relationship.
Naming a topic, promising to explain it later, or asking whether a fact is true does not normally establish that fact. A question can count when the requirement itself is to ask or request something.
“Eight percent” can express “8%,” but “eighteen percent” cannot satisfy an 8% requirement. For a required cause, an unrelated event or an event that happened afterward does not explain the result.
Check the recognized words and the point’s review note where available. State any missing fact or connection clearly. A low speech-confidence warning blocks new automatic completion; a busy model can delay review. The model can also miss a valid explanation.
You can always check or uncheck a point manually. If the local model is unavailable, the checklist remains manual. Automatic coverage runs on-device without a cloud fallback. Read about on-device processing →
Write concrete requirements. “Explain that a staff shortage delayed the launch” gives the app more context than “Discuss the delay.” Groups follow their configured sub-cue completion rule.
Put each idea on a separate line, preferably as a bullet. Visual word wrapping in your writing app is not the same as inserting a line break. Save a plain-text or Markdown file and import again.
Add a Markdown heading before each slide, such as # Introduction. Use “Import Markdown slide notes” under Slide notes, rather than the Talking points importer. Save the file as UTF-8 .md.
Imports append to the existing outline or slide list. Remove unwanted entries in the editor before saving, including duplicates from a second import.
The file may be a scan or an image. Copy selectable text from the original document, or convert the scan to text, then save it as .txt or .md. Check the line breaks before importing.
Check the readiness information shown in the app and the recognition privacy settings. You can continue with the manual checklist. Read about on-device processing →