Question and scope
This protocol tests whether action items from a recurring meeting carry a named due date and a named owner. An action can sound clear in the room and still fail because nobody knows when it should finish. The measure counts how many actions have both fields and how many have only one. It does not judge whether the action itself was important or well chosen.
Scope is one recurring meeting and one defined period, such as six consecutive sessions. Include actions recorded in the minutes and actions added during the meeting itself. Exclude decisions that were logged without an assigned task and ideas that were parked for later discussion. State the scope and the session count so another reviewer can repeat the test on the same boundary.
Population and unit of analysis
The unit is one action item attached to one meeting and one accountable person. An action that covers several deliverables should be split when each deliverable has a different owner or date. If the team wrote one combined action, keep one unit and record the lower precision. Use the actual minutes as the list rather than a cleaned summary prepared after the meeting.
Record the action reference, meeting date, owner, due date, and the evidence that the action was completed. Include actions that were edited after the meeting and keep the version that participants actually saw. Exclude actions that were closed before the meeting ended and note the reason for each exclusion. A stable unit keeps the denominator honest when attendance or agenda length changes.
Definitions and measures
A named due date is a calendar date that someone can check without asking a follow-up question. A named owner is one person who accepts responsibility, not a team or a shared inbox. An action is complete only when the owner has recorded evidence that the work happened. Count the presence of each field separately so a date without an owner does not look like a usable action.
Report the share of actions with both fields, the share with only one, and the share with neither. Break the result down by action type, because a status update and a customer commitment have different consequences. Show the count behind every percentage in the same table. A rate from ten actions should not carry the same weight as a rate from a hundred.
Evidence and data dictionary
Each action needs the meeting date, the action reference, the owner, the due date, and the completion evidence. Evidence of completion is a message, a document, or a system change that another person can inspect. A note that says done is not evidence by itself. Keep the minutes export with the coding sheet so the result can be reconstructed later.
Write a short working dictionary that defines named owner, named due date, complete, and abandoned. Include the rule for an action assigned to a person who was absent from the meeting, and show one example of each category. Mark unclear entries as unresolved instead of forcing them into a category that does not fit. A compact dictionary of one page keeps two reviewers aligned on the same words.
Test design and sampling
Use a census for a short series and a documented sample for a long one. The sample should include every meeting type and at least one session with an unusual agenda or a key absence. Freeze the sample before coding so the reviewer cannot pick actions that support a preferred result. Have a second person review a subset and record disagreements before they are fully resolved.
A practical window is six sessions or the most recent complete planning cycle. If the minute-taking format changes during the window, split the analysis at the change and report both parts separately. Do not merge the old and new format into one average. The comparison is only meaningful when the definition of a complete action stayed stable across the period.
Decision rules before the test
Decide before coding what counts as a named due date and what counts as an acceptable owner. State whether a relative date such as next Friday counts, and whether a team name ever counts as an owner. Decide how to treat an action that was reassigned during the period. These rules change the rate, so they must be written before the first action is read.
Agree on the action that follows a high missing rate. One option is to require an owner and a date before the minutes can be circulated. Another is to review open actions at the start of each meeting and close or re-date each one. Avoid a general reminder to be more specific, because the gap usually comes from the template rather than from intent.
Analysis and reporting
Report the share of actions with both fields, with a date only, with an owner only, and with neither. Show the oldest action in the sample that had no date and the meeting where it sat. Pair the count with a review of completion evidence, because a date does not prove that the action moved. The report should help a manager decide whether to change the template or the review routine.
Break the result down by action type and by meeting, and show the number of actions behind each figure. A comparison between a planning session and a status session is useful only when both have enough actions to support it. If the sample is small, report counts and describe the uncertainty in plain language. A useful report ends with the change the team will test next.
Reporting template
Use a one-page template with four blocks: scope, share with both fields, share with neither, and the action agreed at review. Keep raw counts beside every percentage so the reader can judge the evidence behind it. Add a short note for each exclusion and each format change during the period. The template should be short enough to complete in the review meeting.
Store the completed template in the same folder as the minutes export and the coding sheet. A later reviewer should be able to reproduce the main number without asking anyone for extra context or help. If several versions exist, mark the final one clearly and date each change. Evidence that cannot be found is treated as missing when the result is questioned.
Limits and sources of error
The cited public sources describe records, internal control, and project practice in general terms; they do not provide a local result for a specific meeting series. A named date does not prove that the action was realistic, and a missing date does not prove that the work was ignored. The measure also depends on how the team defines an owner. A loose definition can count an uninformed name as accountability.
Edited minutes and reconstructed records are common sources of error in a retrospective test. Use the version that participants saw and mark any action that was changed later. Exclude an action when the owner field cannot be verified, but report the exclusion count and the reason for it. A clear rule is better than a precise-looking number built on uncertain records.
Review cadence
Review the result at a fixed date and end with one change, one owner, and one check date. A repeated gap should change the template or the review routine before it changes coaching. Keep the minutes, the coding sheet, and the notes together for the next reviewer. Compare like periods and clearly mark any change to the meeting process on the timeline.
Repeat the review after two full cycles, then move to a monthly rhythm if the measure is stable. Retire the measure if it stops informing a decision, because a metric nobody uses will be maintained badly. The purpose is an action that someone can start and finish, not a perfect record. Stop when the team can show that outcome consistently.
Sources
- U.S. Department of Labor — reviewed November 7, 2026.
- U.S. Government Accountability Office — reviewed November 7, 2026.
- Project Management Institute — reviewed November 7, 2026.
- U.S. Small Business Administration — reviewed November 7, 2026.
- NIST Cybersecurity Framework — reviewed November 7, 2026.
