Feature

The meeting that actually produces something

Paste the notes as you typed them - half sentences, no structure, decisions mixed into prose. Decisions are kept as a record with the reason; the actions become tracked jobs on the right people's lists.

Unstructured notes Decisions kept separately Actions become jobs

Book a free demo See pricing

In short

Bosun reads meeting notes as they were typed and separates three things that are handled differently afterwards: decisions, which are kept as a record with the reason given; actions, which become ordinary tracked jobs assigned to the people named; and open questions, which stay unresolved rather than being turned into work nobody agreed to do.

Input: Notes as typed, no structure needed
Decisions: Recorded with the reason
Actions: Tracked jobs, chased normally
Open questions: Kept unresolved
Who can file notes: Owner and managers only

From notes to record

"We're moving to Keystone": Decision + reason
"Maria to order rotors Fri": Job, assigned, dated
"Nobody knows the warranty": Job, unassigned
"Do we need a detailer?": Open question
"Counter closes at 5": Decision, no job

Why three categories

A decision is not a job

"We're switching to Keystone for brake parts" is settled. Filing it as a task puts a deadline on a decision and leaves it hanging on somebody's list forever. "Maria will order the rotors before Friday" is work, and it needs chasing. "Do we need a second detailer over summer?" is neither - it is unresolved, and turning it into a job invents a commitment nobody made.

Keeping the three apart is what makes the record worth reading six months later, when the useful part is usually the reason behind a decision rather than the decision itself.

Decisions keep the reason given, because that is what fades first
A proposal argued and left open is an open question, not a decision
Actions get a deadline only where the notes state one - "before Friday" counts, the meeting date does not
Work nobody claimed is tracked but left unassigned, so it surfaces as needing an owner

What it will not do

It refuses to invent

No manufactured decisions

A proposal argued both ways and left unresolved is filed as an open question, never as something settled.

No invented owners

Work nobody claimed is tracked unassigned, not quietly given to whoever typed the notes.

No invented deadlines

A meeting held on Thursday does not make its actions due Thursday. Only stated deadlines are set.

The notes are kept whole

The original text is stored verbatim, so nothing is lost to the extraction and you can always read what was written.

Owner-only

Meeting notes create work for other people, so only an owner or manager can file them.

Everyone is told

Anyone who picked up an action hears about it directly, not just the person who typed the notes up.

Works together with

More of the assistant

Reads the daily plan Someone types what they are doing today, the way they always have. It becomes separate tracked jobs with owners and deadlines - no forms, no commands to learn. Keeps the photo with the job A picture of the damage, the reading or the finished work is attached to the job that message created - not lost in a chat nobody can search. Listens to voice notes A technician holds the button and talks. It is transcribed, handled exactly like a typed message, and repeated back so a mis-hearing is obvious straight away. Creates the work that repeats Temperature logs, cleaning, safety checks, calibration, a weekly recall list. You describe the pattern once and the job appears on its own, chased like any other. Reads the end-of-day update "The rotors came in, the Ford is stuck waiting on parts." Matched against that person's open jobs by meaning - one closed, one blocked with the reason recorded. Chases what is late Escalating reminders to the person, never the group. After your chosen number of attempts it stops nagging and tells the owner instead.

See every feature