“Someone needs to confirm the workshop location.” Who? The notes don’t say. Another item is due “next Friday,” but there’s no meeting date.
We put both gaps into a five-item test for Brainmox, asked for an action list, then supplied the missing details. Comparing the two CSVs showed four changed cells: the owner, the deadline and their two clarification flags. Everything else stayed the same.
This was a founder-run test with fictional notes, reviewed on September 12, 2026. The screenshots and downloadable files below come from that run.
The notes
- Maya will send the revised proposal by September 18, 2026.
- Leo finished checking the supplier quote.
- Someone needs to confirm the workshop location.
- Nina will review the draft agenda “next Friday,” but the meeting date was not recorded.
- The team discussed a customer survey but made no decision to proceed.
The prepared prompt asked for a table and downloadable CSV with Task, Owner, Deadline, Status and Clarification needed columns. Missing owners and deadlines were to stay “Not specified,” and unapproved ideas were to be separated from confirmed actions. It also prohibited sending messages, creating events or scheduling reminders. The original screenshot captures the notes and final instructions, but not the top of the prompt.
The first file
Brainmox left the workshop owner and Nina’s deadline as “Not specified.” It kept Nina as the agenda owner, recorded Maya’s September 18 deadline and marked only Leo’s task done. The survey stayed separate with the status “No decision recorded.”
Two details deserve a closer look. Brainmox added a Category column to separate actions from ideas, so the file has six columns rather than the five requested. That matters if you’re importing into a tool that expects a fixed format.
The explanation also groups the workshop and agenda items as having “no recorded owner or date.” That’s loose wording: Nina is already named. The table and CSV correctly leave only her deadline unresolved.
The correction
We then supplied two clarifications:
Omar owns confirming the workshop location; no deadline is agreed. Nina’s agenda review is due September 25, 2026.
The follow-up asked for a revised table and CSV, with everything else unchanged.
We parsed both CSVs and compared every cell. Each file has six columns and five data rows. These are the only changes; the two original clarification messages are shortened here:
| Field | Initial file | Revised file |
|---|---|---|
| Workshop owner | Not specified | Omar |
| Workshop clarification | Owner not assigned | None |
| Agenda deadline | Not specified | September 25, 2026 |
| Agenda clarification | No anchor date for “next Friday” | None |
Maya’s proposal, Leo’s quote check and the survey row are unchanged.
Before using this for real work
This run produced the requested action list and applied the corrections without changing other cells. It doesn’t establish how reliably the same task would work across repeated runs or longer notes, and we didn’t measure time saved.
The review used two screenshots and two CSVs, not a full chat export or activity log. The assistant’s statement that it sent no messages or created events or reminders was not independently verified. This wasn’t a permissions test.
To repeat the file check, use the fictional notes above, download the first result before asking for a revision, and compare both files. Check the column layout as well as the values. The evaluation scorecard covers the broader checks this small exercise leaves open.