Quick answer
Docsi AI turns existing notes or a transcript into structured minutes with decisions, tasks (what, who, by when) and open questions. He does not record meetings and does not invent owners or deadlines: anything missing from the notes is marked as open. Check names and decisions against the source and export the tasks as a table to follow them up.
Key takeaways
- Add date, occasion and attendees before Docsi creates the minutes.
- Keep decisions strictly separate from proposals and opinions.
- Every task needs a result, an owner and a date.
- Docsi marks missing details as open instead of guessing them.
- Follow tasks up at the next meeting using the previous minutes.
Add context to the notes
Add the date, meeting subject and participant roles where actually known. Mark your additions. If several people share a first name, use unambiguous roles instead of guessing assignments.
An idea, a proposal and a decision are different categories. Ask to preserve the wording clues. “We could” must not become “we will” without confirmation.
Build reviewable actions
- Request separate sections for decisions, actions and unresolved questions.
- Use columns for action, explicitly named owner, due date and source.
- Unknown dates and owners remain visibly “not specified”.
- Check the list against your notes before sharing.
Refine the minutes
Word is useful for editorial changes, PDF for the approved version. This request does not send minutes to participants or automatically connect a calendar.
Minutes with a clear review procedure
Before starting, note which minutes are complete and where part of the discussion is missing. Incomplete notes can still produce a useful action draft provided that the gap stays visible. Request a separate section for points requiring confirmation. If abbreviations such as “MB” are ambiguous, supply the meaning yourself or leave it unresolved. Names that appear plausible from the topic do not constitute sufficient evidence of ownership.
After reviewing, you can request a second pass limited to wording. Explicitly preserve confirmed dates, people and decisions, then compare those fields again. Terms such as “proposed” and “agreed” carry meaning and should not disappear simply to make smoother prose. Give the approved version an unambiguous name so nobody later uses the unreviewed first draft.
A proven structure for minutes
Minutes are quicker to read when they always follow the same structure: a header with date, occasion and attendees, then decisions, tasks, open questions and the next meeting. Give Docsi this outline in your request; he sticks to it and leaves sections empty when the notes contain nothing on them.
Keep decisions strictly separate from contributions to the discussion. A decision is something the group explicitly agreed on; a proposal or opinion does not belong on that list. Ask Docsi to label uncertain cases as “proposal, not confirmed”.
Phrasing tasks so they get done
A good task starts with a verb and names a checkable result: “Get a quote from supplier B” rather than “Sort out suppliers”. It needs an owner and a date. If either is missing from the notes, Docsi should mark it as open instead of guessing.
In the Markdown export, tasks can appear as a task list with checkboxes (“- [ ]”), which many note apps display directly as a checklist. For teams, an Excel or CSV table with the columns task, owner, deadline, status and source works well.
Making dates and deadlines unambiguous
Notes often contain relative expressions such as “next Friday” or “by the end of the month”. Without the meeting date, they are ambiguous. State the meeting date in your request and ask Docsi to keep the original wording and add a concrete date only if it can be derived unambiguously.
Write dates in the minutes in year-month-day format or spelled out (“29 October 2026”). That avoids confusion between German and English notation, for example with 03/04.
Confidential meetings
Meeting notes often contain names, HR topics or business figures. For an AI task, the text it needs travels encrypted through the Docsi server to Docsi AI and is not stored there. Still check whether you need all of the content, and remove beforehand what the minutes do not require.
For particularly confidential meetings, you can connect a local model through Ollama or LM Studio; the notes then do not leave your computer. Also follow your employer’s rules for minutes and AI tools.
Following tasks up until the next meeting
Before the next meeting, give Docsi the old minutes and the new notes. Ask for a table that links every earlier task to its new status: done, in progress, postponed or not discussed. That way no task gets lost between two meetings.
Tasks that have been postponed several times signal missing resources or unclear ownership. Have them listed separately in the report so the group can decide on them.
A worked scenario
An example: after a one-hour project meeting you have two pages of bullet points with initials. At the top you add the date, the attendees with initials and names and the occasion. Then you ask Docsi for minutes with decisions, tasks in a table (task, owner, deadline, source) and open questions.
Docsi finds four decisions and nine tasks; for three tasks your notes lack an owner, so they are marked as open. You clarify these three with a message to the team, add the names in the Word file and send the minutes the same day. You also export the task table as an Excel file for follow-up.
Checklist before sharing
Minutes are often forwarded and read again weeks later. This check makes sure they are still understandable then.
- Date, occasion and attendees are in the header.
- Every decision was explicitly confirmed by the group.
- Every task has a result, an owner and a date, or is marked as open.
- Names and initials are resolved correctly.
Key terms explained
- Decision
- An explicit agreement of the group, recorded in the minutes.
- Task
- A concrete action with an owner and a date, often called an action item.
- Owner
- The person who completes a task or makes sure it gets done.
- Deadline
- The date by which a task should be completed.
- Transcript
- A verbatim written version of what was said. Docsi does not create transcripts but can work with existing ones.
A worked example
A note says “Mira checks quote; deadline open; next meeting possibly Friday”. This supports an action for Mira with no due date. Friday stays a tentative idea. That distinction prevents a well-formatted list from implying an agreement. Ask the group to confirm only after review.
Adapt source and scope, then use the text in Docsi. This website starts no AI task.
Check the result
If something is wrong
| Observation | Next step |
|---|---|
| Too many supposed decisions | Check modal wording in the original and mark uncertain points as proposals. |
| Wrong person assigned | Read the named passage and add roles; do not infer ownership from the topic. |
| Minutes are too long | Prioritise decisions and next steps before background information. |
Common questions
Can Docsi record the meeting itself?
This workflow uses existing written notes or a supplied transcript. It does not assume a recording feature. Check names and decisions in that source first.
Does an unresolved date become a deadline?
No. Explicitly request “unresolved” for unspecified dates and owners. Confirm the action list before sharing it or adding it to your calendar.
What form should my notes take?
Any form you can read yourself: typed, as a Word file or as a photo of clearly printed handwritten notes.
Can Docsi resolve attendees from initials?
Only if the initials are explained in the notes. Otherwise add a short list of “initials = name”.
Can I send the minutes straight away?
Only after you have checked decisions, names and dates. As a Word file you can still add to it beforehand.
Can Docsi write English minutes from German notes?
Yes. Name the language you want; names, figures and dates stay unchanged and are backed by the notes.
Sources and further reading
Statements about Docsi are based on the product documentation by Impulse Apps. These primary sources explain the underlying formats, standards and methods.
- GitHub Flavored Markdown SpecDescribes task lists with checkboxes (“task list items”) in Markdown.
- RFC 3339: Date and time formatUnambiguous dates in year-month-day format.
- General Data Protection Regulation (EU) 2016/679Principles for handling personal data in minutes.