Turn agreed work into a register that can be closed

Deliverable, owner, due date and source timestamp. Fill the four fields for each task a meeting agreed, see what is still missing, and export the register before the notes circulate.

What this does not do

  • It does not listen to a recording, transcribe audio or recognise speakers. There is no speech recognition here.
  • It does not guess who agreed to what. It never fills in a name, a date or a deliverable for you.
  • It does not read, upload, sync or back up your files, and it sends nothing anywhere.
  • It does not score, grade, rank or recommend the register. It reports counts of what is missing.
Instrument

Action register

One row per agreed task. The six column names match the table published at action-register.csv.

Example values are invented and labelled as fictional.
Counts

What the register is missing

Counts only, with no score and no list of names to match against.

3 rows · 3 unassigned · 3 without a due date · 0 duplicate rows

Unassigned and undated

Rows with no owner, rows with no due date, and deliverables that appear more than once. A row counts as unassigned when Owner is empty or reads Not assigned, and as undated when Due date is empty or reads Not stated. The list repeats what you typed; it does not repair it.

The list appears here as you type.
Export

Hand the register on

The CSV keeps the same column names in the same order as the published file: Deliverable, Owner, Due date, Source timestamp, Status, Notes.

Nothing exported yet.

How to use it

  1. Write each agreed task on its own row and name the deliverable as a thing that can be handed over, not as an intention. Write meeting action items someone can actually close lists the four fields and how to word them.
  2. Fill Owner and Due date, or type Not assigned and Not stated when the meeting did not say. The tool asks you for a decision instead of inventing one.
  3. Keep the source timestamp on every row so the person reading the register can play the moment back. Check meeting notes against the recording and the decisions covers the check that produces those timestamps.
  4. Read the Unassigned and undated panel before you send anything: it names the rows nobody owns and the rows with no date, and flags a deliverable that appears twice.
  5. Press Load example to see a fictional register with all three cases in it, then Reset and fill your own. Download the CSV, copy the Markdown or print the page.

Method & next step

ToolVerity publishes the registers it uses, and this page uses the same six column names as the file at action-register.csv. The page records what you type and counts what is missing: it does not listen to audio, name speakers or decide who agreed to what. The counting rules above are the whole method. The file carries the six column names in this order: Deliverable, Owner, Due date, Source timestamp, Status, Notes. State words are fixed across this site: Pass — checked and it holds; Fail — checked and it does not hold; Not checked — not checked yet; Unassigned — nobody has taken the row on yet. Pass, Fail and Not checked are the three verdicts on a row; Unassigned records who owns it, not whether it holds. On this page Status says whether the row has been checked, while the unassigned count is taken from the Owner field, so an Unassigned row is a row nobody owns rather than a failed task.

How we check pages · Next: the meeting follow-up workflow from transcript to archive

Questions

Can it pull the action items out of the recording?

No. There is no audio player, no transcription and no speaker recognition on this page. You read the transcript and type the rows yourself. The panel can only report a row as unassigned when Owner is blank or reads Not assigned, and as undated when Due date is blank or reads Not stated — it cannot tell you what somebody promised.

What counts as a repeated deliverable?

Two or more rows whose Deliverable text is the same once letter case and extra spacing are ignored. The panel counts the extra rows and names the row numbers. It does not merge, delete or rewrite anything, and it will not claim that two differently worded rows describe the same task.

Runs entirely in your browser. Nothing you type or paste is sent anywhere.