Guide
How to use AI for meeting notes
A practical, no-bot workflow for recording a meeting, checking the transcript and generated briefing, and carrying the decisions into your next step.
By tentus team · Updated 2026-10-26 · 4 min read
Record one meeting from the app
In the authenticated app, open Meetings or use /record in a doc, then choose Record meeting. Before recording, tell the participants and get the consent your circumstances require: no bot joins, but people are not automatically notified. Select Start recording and allow microphone access when the browser asks. This flow records this device's microphone input only — it is not system audio, so remote participants may not be captured reliably when you are wearing headphones. When the meeting ends, choose Stop & save. The recording uploads as a meeting source; it is not inserted into a text cursor.
Worked example: say the decisions out loud
For a launch review, make the important handoff explicit: "Decision: ship the export beta Thursday. Alex drafts the help copy by Wednesday. Priya checks the auth logs Tuesday. Follow-up: review both in the next launch check-in." This is an instructional example, not a customer result. After processing completes, open the recording from Meetings or Library and compare the transcript and any generated Briefing. If a Briefing is present, it may include summary, key points, decisions, action items, and follow-ups; verify each item against the original meeting.
Check the saved source against the original meeting
The recording appears in the Meetings list while it is transcribing and links to its source when ready. After processing completes, the source detail can keep the transcript and display any generated Briefing. Transcription and briefing generation can both be wrong or unavailable, so compare them with the recording or your original meeting notes before acting on owners, dates, or decisions.
Carry the follow-up into your own workflow
If an Action items section is present, use it as a review checklist: confirm the owner and due date against what the group actually agreed, then copy the confirmed work into the task or project system your team uses. This meeting recorder captures and structures the conversation; it does not silently approve decisions or replace that final human check.
Fictional example · source excerpts and human review
Client meeting preparation: follow the evidence
Alder Studio and everyone below are fictional. This is a hand-written teaching example, not generated tentus output or a customer result. Imagine preparing for the Alder pilot review on 27 October 2026. The task is to reconcile two prior notes and one newer message before deciding what to ask.
Source A — scope note
Alder Studio wants a support-documentation pilot for two teams. Client review is booked for 29 October. We have not agreed a budget.
Source B — handoff note
Alex will draft the pilot help page by 27 October. Priya promised an accessibility checklist; no due date was agreed. We still need to name the final approver.
Source C — deadline message
Move Alex's help-page draft to Wednesday 28 October. The client review stays on Thursday 29 October. The pilot still covers two teams.
A brief after human review
- Scope
- The pilot covers two teams. The newer message reconfirms the original scope. Source A — scope noteSource C — deadline message
- Changed deadline
- Alex owns the help-page draft. 28 October replaces 27 October; the client review remains 29 October. Keep the old date in its source, but use the newer instruction for this handoff. Source B — handoff noteSource C — deadline message
- Open commitment
- Priya promised the accessibility checklist. No due date or completion confirmation appears in these excerpts. Ask for its status and agree a date; do not assume it is late. Source B — handoff note
- Missing facts
- Budget and final approver remain unknown in the supplied sources. Ask who approves the pilot and whether a budget has since been agreed. Source A — scope noteSource B — handoff note
Check before sharing
Open every cited source. Confirm that the newer message is authoritative and look for later changes. Check each owner, date and unresolved question with the participants. Remove sensitive client material before sharing. A workspace boundary does not establish separate access controls for each client inside it.
How this relates to Meeting Prep in tentus
In tentus, Meeting Prep on Today looks for the next timed event within 18 hours on a connected calendar. It uses the event title and description to retrieve selected excerpts from your workspace; it does not read every document for every meeting. A brief may be reused for up to six hours, so check recent updates yourself. Email preparation requires the email-digest opt-in and is not a delivery guarantee.
Decision citations link to retrieved sources, but a link does not prove that the generated sentence is correct. With no matching evidence, the brief reports that no context was found. If generation fails after evidence is retrieved, it can fall back to excerpts. Other loading or service errors can prevent a brief. The example above shows a human review method, not a promise that Lumi will detect every conflict or missing fact.
tentus is in pre-beta preparation. Access and a complete calendar-to-brief workflow have not been verified for public use. Check access and the plan requirements for your intended workflow before relying on it.
Put this into practice
tentus makes it practical. Capture, connect, and retrieve with Lumi working in the background.
More guides
How to use AI for research
Build a small, checkable research note with source links, competing claims and explicit gaps.
How to use AI for journaling
Review your own dated entries with optional AI assistance, while keeping interpretation separate from what you recorded.
How to use AI for idea generation
Turn a few saved observations into ideas you can explain, challenge and test.