Split one tangled sentence into three sections
Launch date, API docs, and an unconfirmed owner were packed into one line. They become a decision, an action item, and an open question, each trackable.
Raw meeting notes become minutes with decisions, action items, owner slots, and open questions kept apart. No invented decisions, owners, or dates; anything uncertain is marked to confirm, and ideas still under discussion are never written up as conclusions.
We separate what was decided from what was discussed, build action items with owner slots, and list open questions and dates needing confirmation.
SAMPLE OUTPUT
This is the complete output for the source text in the demo above: a completeness score, itemised reasoning, a confirm-before-sending list, and the structured minutes. It is a demonstration, not a customer case.
Launch date, API docs, and an unconfirmed owner were packed into one line. They become a decision, an action item, and an open question, each trackable.
The notes mention Xiao Li without confirming anything, so it becomes [OWNER] under open questions instead of an assignment.
“We will figure out the timing later” gives no date, so it becomes a [deadline] slot rather than an invented date.
# Minutes: [meeting topic] (draft) ## Decisions - The launch date moves; the new date is [TO CONFIRM] ## Action items - [OWNER] finishes the API docs; deliverable and deadline [TO CONFIRM] ## Open questions - The new launch date is not settled - Owner of the API docs is not confirmed (notes mention Xiao Li, unconfirmed) Fill every [TO CONFIRM] item yourself; nothing here is guessed.
WHAT STRUCTURING DOES
Only settled outcomes go under decisions; anything still debated goes under open questions. The two never share a sentence.
“Follow up on this” is not enough. State what must exist when it is done, and by when.
When an owner or a date was never said, it becomes [OWNER] or [DATE], not a guessed name.
WHY IT IS WORTH DOING
People leave with different versions of what was said. Writing it down gives the team one shared reference.
When a settled outcome and a brainstorm share a paragraph, nobody can tell which one is binding.
Fill in a name from memory and someone discovers by accident that the task is theirs. Coordination cost doubles.
Note: common minutes practice is to record decisions, action items, and open questions separately and to attach an owner and a date to each action. Exact formats vary by team. This site only organises what your notes contain; it cannot recover anything they omit and gives no legal or management advice.
STRUCTURING DEMO
We talked about a lot. I think we are moving the launch date, and we also said the API docs need finishing. Maybe Xiao Li's team looks at it first. We will figure out the timing later.
# Minutes: [meeting topic] (draft) ## Decisions - The launch date moves; the new date is [TO CONFIRM] ## Action items - [OWNER] finishes the API docs; deliverable and deadline [TO CONFIRM] ## Open questions - The new launch date is not settled - Owner of the API docs is not confirmed (notes mention Xiao Li, unconfirmed) Fill every [TO CONFIRM] item yourself; nothing here is guessed.
Demo sample: decisions, action items, and open questions in separate sections, with unconfirmed owners and dates left as slots. Paste your notes to get your version (sign-in required; one credit per run).
WHY YOU CAN TRUST IT
Only outcomes the notes clearly show as settled become decisions. Everything else goes to open questions.
When a name was never said, it becomes [OWNER] rather than a plausible guess, so nobody is assigned by accident.
Proposals still under discussion stay in open questions with their original wording instead of being promoted to agreed plans.
Submitted text is used for this single AI request and is not intentionally persisted. See the Privacy Policy.
FAQ
No. Only what the notes show as settled becomes a decision. Everything else lands in open questions with a note on what is needed to close it.
It becomes an [OWNER] slot marked to confirm. Better an empty slot than a guessed name that quietly assigns the work.
No. Suggestions still under discussion stay in open questions with their original wording, never as an agreed plan.
One credit per run, usually done in seconds, returning the minutes, the reasoning, and items to confirm.
No. Credits never expire — whatever you do not use carries over to the next cycle instead of resetting.
Not yet. Each run processes one set of notes and consumes one credit; there is no bulk upload or API today. Email us with your use case and we will assess it.
Not intentionally. Text is used for this single AI request only. See the Privacy Policy.
Meeting shorthand, standup notes, review discussions, client call points, chat excerpts — Chinese or English, as long as the content was actually written down.
SIMPLE PRICING
For an occasional publishing cadence, with a focused monthly credit allocation.
For frequent publishers who iterate on content continuously.
Our largest monthly credit allocation, for the heaviest continuous usage.
Credits never expire: unused credits carry over instead of resetting. Credits apply to this site only and are not shared with other sites.
Prices shown are USD baselines; final currency, taxes, and discounts are determined by Paddle for the checkout location.