AI uses for records
Meeting action approval dataset: 305 board action items traced
By SourceX Editorial · Updated
9 sections
Short answer
A meeting action approval dataset should label suggestions, assignments and formally approved actions as different things and link each assignment to the record of its outcome. In the Apache Software Foundation's public board minutes, 129 of 305 action items created from 2021 to 2025 left the tracking list without a closure word, and only 78 of the 302 that left carried a link to evidence.
Provenance trail
Meeting action approval
Key takeaways
- Keep three tiers apart: a captured suggestion, an assignment with an owner, and an action a body with authority approved.
- Of 305 Apache board action items created from 2021 to 2025, 56.7 percent left the list with a closure word and 42.3 percent without one.
- Only 25.8 percent of items that left the list carried a link to the thread or record showing the work.
- Eleven of 300 assignment lines never reached the tracking list, and reassignment or rewording would split items identified by owner and text.
- Eleven of 15 resolution requests were followed by an approved order on the same project, but only 4 statuses ever cited one.
What should a meeting action approval dataset record?
It should record three different things as different labels: a suggestion someone made, an assignment that names an owner and a task, and an action that a body with authority formally approved. Then it should link each assignment to the record where its outcome lives, because the meeting note alone rarely says whether the work happened or was ever sanctioned.
The distinction matters more now that software writes the first draft of the to-do list. Microsoft's support page for Facilitator in Teams says it automatically captures tasks during a meeting and that a user must select Accept to sync before those tasks go to Planner. Atlassian's Confluence documentation describes action items that assign a task to a mentioned person, who is notified and sees it under Tasks. In both products a captured item and an accepted or assigned item are different states, and neither state is an approval.
A model trained on meeting notes without those states learns that every sentence shaped like a task is a commitment. A model evaluated without them is graded against a list nobody agreed to. The useful dataset keeps the tier of each item, who assigned it, the passage it came from, its status history and the link, if any, to the decision or work record that settled it.
How the Apache board records an action item from assignment to vote
The Apache Software Foundation's board publishes minutes that keep all three tiers apart, which makes them a rare public test bed. In each monthly meeting, a director who takes on a follow-up is recorded under the report it concerns, on a line that starts with @ and the director's name, followed by the task, such as pursue roll call. At the next meeting the same task appears in a section titled Review Outstanding Action Items, with its owner, a bracket naming the project and the date the item was created, and a Status line the owner fills in. Formal decisions sit elsewhere, as numbered Special Orders that end with a sentence stating that the order was approved by vote.
The record is also dated and stable. The board's calendar page says the board typically approves each meeting's minutes at the following meeting, so minutes appear roughly a month after the meeting. On October 27, 2026 we fetched every minutes file the foundation lists for 2021 to 2026, 70 files from January 20, 2021 to August 19, 2026, and read them with our own script. Sixty-eight are regular meetings with an action-item review; the two special meetings have none and were skipped.
We counted two populations. Assignment lines are the "@" lines written at the 60 regular meetings from January 2021 to December 2025. Ledger items are the distinct entries in the review section whose creation date falls in the same window, followed through every later minutes file to August 2026. Names are used only to match lines and are not kept in the saved data.
What happened to 305 board action items created from 2021 to 2025
Just over half closed with a word that says so; the rest left the list with a narrative note, nothing at all, or still open. Of 305 ledger items created at meetings from January 20, 2021 to December 17, 2025, 173 (56.7 percent) left with a status containing done, complete, resolved, not needed, cancelled or a similar closure word, and 129 (42.3 percent) left without one. Three were still open in the August 2026 minutes.
Links to evidence were thinner still. Only 78 of the 302 items that left the list (25.8 percent) carried a web link in their last status, almost all to a foundation mailing-list thread or short link, and 43 of the 166 items marked done (25.9 percent) did. Nineteen items, 6.2 percent, left with an empty status, and 13 of those never had a status at any meeting. Most items were short-lived: 157 of the 302 appeared on one meeting's list only.
The classes below come from the last status recorded before an item disappeared, using whole-word patterns applied in a fixed order. A status of "Not done." counts as explicitly not done; a status that reports an action such as sent, contacted or initiated, without a closure word, is kept apart from closed items:
| Outcome at last appearance | Items | Share of 305 | Link in last status |
|---|---|---|---|
| Closed as done | 166 | 54.4% | 43 |
| Closed as not needed or cancelled | 7 | 2.3% | 0 |
| Action reported, no closure word | 38 | 12.5% | 11 |
| Other note (context, plan or link only) | 69 | 22.6% | 24 |
| Explicitly not done | 3 | 1.0% | 0 |
| Left with no recorded outcome | 19 | 6.2% | 0 |
| Still open in August 2026 | 3 | 1.0% | Not applicable |
How many assignments never reached the tracking list?
Few, but the misses show how linkage breaks. Of 300 assignment lines written at regular meetings in the window, 289 reached the tracking list and 11 (3.7 percent) never appeared there under their meeting date. One of the 11 repeated a task that was already open from an earlier meeting; six were recorded at four consecutive meetings from January to April 2025, which points to a capture problem in that stretch rather than to owners ignoring work.
The items that did reach the list did not always arrive unchanged. Seven matched only because the project named in the heading matched the item's bracket, after the owner or the wording changed between the minutes and the list, and three ledger items in the files read were reworded between one meeting's list and the next. Going the other way, 16 ledger items had no "@" line at all; they were created in discussion or added directly. Any dataset that identifies an action by its owner and wording will split or lose these items. It needs an identifier that survives reassignment and editing.
Did resolution requests turn into approved work?
Usually, but the record that proves it is not linked to the request. Fifteen ledger items asked for a resolution, most often to move a dormant project to the Attic, the foundation's home for retired projects. The Attic's process page describes the path: the project votes on its public list, a chair adds a resolution on the Attic's "Terminate the Apache {PROJECT} Project" template to the next board agenda, and the move starts once the board approves it.
For 11 of the 15, a later meeting approved a Special Order whose title names the same project, a median of 2 regular meetings after the request (range 1 to 8). Only 4 of the 15 ever had a status that mentioned a special order. One request, to add an Attic resolution for the Mnemonic project, read "Not done." in August 2024 and left the list with a blank status in September; the board approved terminating the project in February 2025, seven regular meetings after the request, following a separate roll-call item. Another request was marked done although no later order names its project.
The scale of the formal tier is different again. Meetings in the window approved 230 Special Orders, from chair changes to new projects and terminations, against 305 action items. Assignments and authorizations are separate streams, and only a project name connects them.
The action authority map: fields that tie an item to approved work
The map below is the minimum field set for an action-item record that a model can learn from and an evaluator can grade. The third column says where the Apache minutes keep the field, which shows that a careful public body still leaves several of them to inference:
| Field | What it holds | In the Apache record | What breaks without it |
|---|---|---|---|
| Stable item ID | One identifier from capture to closure | None; owner, text and date only | Reassigned or reworded items split in two |
| Tier | Suggestion, assignment or authorized action | Implied by section | Every task-shaped sentence reads as a commitment |
| Assigner and owner role | Who asked, who owns, in which capacity | Owner name; assigner only in the August 2026 minutes | Authority cannot be checked |
| Source passage | The minute or report the item came from | Project and date in a bracket | No grounding for a generated task |
| Dated status history | Each status with the meeting it was given at | Status text, one per meeting | Silence is read as success |
| Outcome class | Done, cancelled, superseded or abandoned | Free text | Narrative notes cannot be scored |
| Evidence link | Thread, ticket or document showing the work | In 78 of 302 closed items | Closure claims cannot be verified |
| Authorization link | The resolution, vote or approval ID | Absent; project name only | Approved work cannot be tied to its request |
Is the ledger just a reminder list? The strongest objection
Partly yes, and that is the argument for linking rather than against it. The review list exists to prompt owners at the next meeting, not to archive outcomes, and the real work happens on mailing lists, in project votes and in board resolutions. Many items without a closure word were finished: statuses such as "Sent roll-call email" or a bare thread link describe completed actions in words a pattern match does not treat as closure.
So the 129 items without a closure word are not 129 failures. They are 129 cases where a reader, or a model, must open another record to learn what happened, and the link to that record is present in only a minority of them. Our classes are a lower bound on completion and an upper bound on what the list itself proves. A buyer should treat unlinked closures as unknown, never as done, and should expect the same pattern in corporate tools, where an accepted task in Planner or Jira may close without any reference to the meeting that created it.
How a buyer would test and request action-item records
Test whether a system can tell the tiers apart and ground each outcome, then request records that make both possible. A useful evaluation set gives a model the minutes and asks it to label each candidate item as suggestion, assignment or authorized action, then gives it the later records and asks for the outcome with a citation. Score the tier and the outcome separately, and count an outcome without a cited record as unsupported even when it happens to be right.
From a company's own systems, the valuable unit is the linked chain: meeting notes or transcripts, the task records they produced, status changes with dates, and the approval or decision record where one exists, with attendee names replaced by roles. SourceX licenses business data directly from companies and sources datasets on request rather than holding them in stock; a buyer can describe the chain it needs, with scope, volume, language, format, timing and licensing, through the request-data form, and attach the tier and outcome test as the acceptance check.
Ask for these properties before any record moves:
- An item identifier that survives reassignment, rewording and merging across meetings.
- The tier of every item, set by the record's own structure rather than inferred by a model.
- Dated status history, with blank statuses kept as blanks rather than dropped.
- Links from closed items to the thread, ticket or document that shows the work, and the share of items that have one.
- Links from authorized actions to the vote or approval record, with the approving body named.
- Roles in place of names, and a rights review of any customer or partner content quoted in notes.
Methods note: Apache minutes, matching rules and what was not measured
Source: every board minutes file listed on the foundation's minutes pages for 2021 to 2026, fetched over HTTPS on October 27, 2026; the SHA-256 hash of each file is saved with the scripts. Only text before the first attachment is read. Regular meetings are files with a Review Outstanding Action Items section. A ledger entry is a starred line with an owner, followed by a bracket with a context and a date and a Status line. Text is compared after removing accents, lowercasing and collapsing spaces. An item is identified by its creation date, context and text; a new owner does not create a new item. An entry that ends at one meeting and reappears at the next with the same date and context but new wording is merged as one item (3 merges).
An assignment line is a line beginning with "@" outside the review section. It reached the list if an item with the same creation date matches its text exactly, or on the first 25 characters or more, or names the project in the assignment's heading, claimed one to one in three passes. Outcome classes use the whole-word patterns listed in the script, first match wins. A resolution request is an item containing the word resolution; it counts as followed when a later file holds an approved Special Order whose title, at most 200 characters, names the item's context. A Special Order counts as approved when its title is followed by "was approved", including sentences that break onto a new line after the title. Percentages are rounded once, half up.
Not measured: whether the work behind each item was actually done, which would require reading every linked thread; action items recorded only on mailing lists; meetings before 2021; and any company's internal meetings. The saved snapshot keeps item numbers, dates, project contexts, classes and link hosts, with no names and no action text.
Frequently asked questions
What is the difference between an action item and an approved action?
An action item assigns a task to an owner, usually at a meeting, and records that someone agreed to do it. An approved action is a decision taken by a body with authority, such as a board resolution or a signed approval. In the Apache board's minutes the two live in different sections, and only a project name connects them.
Can AI-generated meeting tasks be used as training labels?
Only as candidates. Tools such as Teams Facilitator capture tasks automatically and ask a user to accept them before they sync to Planner, so the captured list is a suggestion layer. Labels should come from what people accepted, assigned or approved, with the source passage attached.
How do you link an action item to the work that followed?
Give the item a stable identifier at capture, record each dated status, and require a link to the thread, ticket or document when the item closes. In the Apache record, only about a quarter of closed items carried such a link, which is typical of lists kept as reminders rather than evidence.
Why not use the task tracker instead of meeting minutes?
The tracker shows the work but not why it was assigned, who asked or what authority stood behind it. The minutes show the assignment but rarely the outcome. A dataset needs both ends and the link between them.
Do meeting records with action items contain personal data?
Usually, because owners, attendees and the people discussed are named. Replace names with roles before licensing, review any customer or partner content quoted in the notes, and keep the structure that makes items linkable. This page's saved data holds no names.
Sources
- The Apache Software Foundation's published board minutes for 2021 to 2026, fetched on October 27, 2026, supply every count of assignments, ledger items, outcomes, links and approved Special Orders on this page. Source
- The August 19, 2026 minutes show the action-item review format: each item lists an owner, a bracket with the project and creation date, and a Status line, and newer items note who created them. Source
- The April 15, 2026 minutes record assignments as @ lines under each committee report and decisions as numbered Special Orders approved by vote. Source
- The February 19, 2025 minutes record the board's approval of a Special Order terminating the Apache Mnemonic project. Source
- The September 18, 2024 minutes list the Mnemonic Attic resolution request with an empty status, its last appearance on the action-item list. Source
- The ASF board calendar page says the board typically approves each meeting's minutes at the following meeting, so minutes are published roughly a month after the meeting. Source
- The Apache Attic's process page describes a public project vote, a resolution on the Terminate the Apache {PROJECT} Project template added to the next board agenda, and the move starting after board approval. Source
- Microsoft's support page for Facilitator in Teams says Facilitator captures tasks during meetings, and that users select Accept to sync to send those follow-up tasks to Planner. Source
- Atlassian's Confluence Cloud documentation says that assigning an action item to a mentioned person notifies them and lists the task under their Tasks. Source
Tell us what data you need
Share scope, volume, format, timing and licensing needs. Datasets are sourced on request.