A message in the morning, a job list by nine
Someone types what they are doing today the way they always have. Bosun splits it into separate pieces of work, keeps the details that identify each one, and assigns them to the person who sent it.
A daily plan is the message a staff member sends at the start of the day describing what they intend to do. Bosun reads it as free text, splits each distinct deliverable into its own tracked job, keeps the identifying details - stock numbers, part numbers, customer names - in the title, and sets a deadline only where the message actually states one.
- Input
- Any plain-language message
- Output
- One job per deliverable
- Assigned to
- The sender
- Deadline
- Only when stated
- Unsure entries
- Flagged for the owner
The structuring nobody wants to do by hand
Splits compound sentences
"Order rotors and book the Civic in for Thursday" is two jobs, not one line nobody can half-close.
Keeps the identifying detail
Stock numbers, part numbers, registrations and customer names stay in the title. They are how the work is found again next week.
Assigns to the sender
A daily plan only ever creates work for the person who wrote it. Nobody can put a job on a colleague's list this way.
Never invents a deadline
A due date is a commitment the assistant will chase somebody about. It sets one only when the message states one.
Ignores what is not work
"Morning", "cheers", "have a good one" and "catch up on emails" do not become jobs.
Flags what it is unsure about
Ambiguous wording produces a job marked for review rather than a confident-looking guess.
What becomes a job
- A distinct deliverable
- Yes
- Two things in one sentence
- Two jobs
- Work already finished
- No - that is an update
- "Catch up on emails"
- No - no deliverable
- Pleasantries
- No
"Today:" is not a deadline
A staff member writing "Today: order the rotors, call Mrs Diaz" is telling you when they wrote the list, not promising both are finished by five. Reading that heading as a deadline means chasing two people that evening about work nobody committed to that day - and the fastest way to make a team mute an assistant is to nag them about deadlines they never agreed to.
So the rule is strict: a deadline is set only when the item itself names one. "Before Friday" and "by Wednesday" are deadlines. A heading is not.
- "Order the rotors before Friday" gets a Friday deadline
- "Today: order the rotors" gets none, and is never chased that evening
- Relative dates are read against the sender's own local date
- A job with no deadline is still tracked, and appears in the owner's undated list
More of the assistant
On this page
What if someone sends a plan as a list?
That works too - bullets, dashes, numbers or one long sentence all read the same. The formatting does not matter; the deliverables do.
Can someone add a job for a colleague this way?
No. A daily plan only creates work for the person who sent it, and that is enforced in the code. Only an owner or a manager can put a job on someone else's list, and they do it explicitly.
What if they mention a job that already exists?
Restating existing work is treated as an update rather than a new job, so you do not collect duplicates every morning from somebody listing what they are still working on.