What share of meetings have a dated follow-up note?
A proposed protocol for measuring whether a meeting produces a decision, an owner, and a dated next action.
Headline statistic
A defined sample, not a verdict
Methodology: The brief describes a proposed method, not a completed finding.
Key stats
- Public sources reviewed
- Documented review method
Key takeaways
- Define the population before sampling.
- Separate completeness from correctness.
- Publish the limitation beside the finding.
Question and scope
This is a proposed research protocol, not a report of completed findings. It asks what share of meetings have a dated follow-up note with an owner and a decision. The result would describe the note, not the meeting. If the source is unclear, route the question instead of guessing. The brief should name what is approved and what needs a question. A control that depends on memory is not yet a control.
The protocol does not measure whether the meeting was useful. It measures whether the record supports the next step. A short note with four fields is easier to use than a long narrative. Ask whether a new reviewer could act on the record without a conversation. The brief should name what is approved and what needs a question. The evidence should stay with the record, not in a private note.
Population and unit of analysis
Define the population as meetings held during a stated window. The unit is one meeting, with the decision, the owner, the due date, and the note date recorded. A short note with four fields is easier to use than a long narrative. Review the first few notes together before the process expands. A control that depends on memory is not yet a control.
Link the note to the meeting so the same meeting is not counted twice. Record the exception and the person who approved it. Test the rule on one real request before applying it to the queue. Name the owner in the same line as the action. A control that depends on memory is not yet a control.
Definitions and measures
Define completeness as the presence of the decision, the owner, and the due date. Define timeliness as the note being created within the agreed window. Review the first few notes together before the process expands. Keep the original note beside the corrected version. The assistant should record the owner and the date before the next shift. A control that depends on memory is not yet a control.
Report both separately. Name the owner in the same line as the action. A control that depends on memory is not yet a control. Use the same format for every handover so the next reader can scan it. The handoff should let the next person act without a meeting.
Evidence standard
Use the note and the calendar record. A note that says discussed without a decision is weak evidence. Keep the boundary visible in the place where the work is assigned. Name the owner in the same line as the action. The handoff should let the next person act without a meeting.
Record the date the note was created. Use the same format for every handover so the next reader can scan it. Keep the boundary visible in the place where the work is assigned. Keep the evidence with the record rather than in a separate log. The brief should name what is approved and what needs a question. The evidence should stay with the record, not in a private note.
Sampling and collection
Use a census of the meetings if the volume is manageable. If sampling is necessary, stratify by meeting type. Use the same format for every handover so the next reader can scan it. Ask whether a new reviewer could act on the record without a conversation. The brief should name what is approved and what needs a question. The handoff should let the next person act without a meeting.
Pilot the classification on a few notes and compare the reviewers. Clarify what counts as a decision. If the source is unclear, route the question instead of guessing. Separate what was observed from what was assumed. The review should leave one owner and one date. The evidence should stay with the record, not in a private note.
Analysis and reporting
Report completeness and timeliness by meeting type. Show the meetings without a dated note. Keep the original note beside the corrected version. Record the date and the source so the next reviewer can repeat the check. The handoff should let the next person act without a meeting. The brief should name what is approved and what needs a question.
Present the results as a description of the record, not a judgment about the chair. Keep the boundary visible in the place where the work is assigned. Write the deadline as a date and a local time. A short note with four fields is easier to use than a long narrative. The handoff should let the next person act without a meeting.
Limits and sources of error
The note may be in a different system. State the systems included. Test the rule on one real request before applying it to the queue. Record the date and the source so the next reviewer can repeat the check. A control that depends on memory is not yet a control. The brief should name what is approved and what needs a question.
The meeting may not have needed a decision. Record the exception. Record the exception and the person who approved it. Test the rule on one real request before applying it to the queue. A control that depends on memory is not yet a control. The handoff should let the next person act without a meeting.
Review cadence
Repeat the review after a template change or at the same interval each quarter. Compare the same meeting types. If the source is unclear, route the question instead of guessing. Record the exception and the person who approved it. A control that depends on memory is not yet a control. The review should leave one owner and one date.
Assign the follow-up to the operations lead and set a date. The protocol should produce a specific decision about the note template. Write the deadline as a date and a local time. Keep the evidence with the record rather than in a separate log. A control that depends on memory is not yet a control. The review should leave one owner and one date.
Research notes
This is a proposed research protocol, not a report of completed findings. It asks what share of meetings have a dated follow-up note with an owner and a decision. The result would describe the note, not the meeting. If the source is unclear, route the question instead of guessing. The brief should name what is approved and what needs a question. A control that depends on memory is not yet a control.
The protocol does not measure whether the meeting was useful. It measures whether the record supports the next step. A short note with four fields is easier to use than a long narrative. Ask whether a new reviewer could act on the record without a conversation. The brief should name what is approved and what needs a question. The evidence should stay with the record, not in a private note.
Define the population as meetings held during a stated window. The unit is one meeting, with the decision, the owner, the due date, and the note date recorded. A short note with four fields is easier to use than a long narrative. Review the first few notes together before the process expands. A control that depends on memory is not yet a control.
Link the note to the meeting so the same meeting is not counted twice. Record the exception and the person who approved it. Test the rule on one real request before applying it to the queue. Name the owner in the same line as the action. A control that depends on memory is not yet a control.
Define completeness as the presence of the decision, the owner, and the due date. Define timeliness as the note being created within the agreed window. Review the first few notes together before the process expands. Keep the original note beside the corrected version. The assistant should record the owner and the date before the next shift. A control that depends on memory is not yet a control.
Report both separately. Name the owner in the same line as the action. A control that depends on memory is not yet a control. Use the same format for every handover so the next reader can scan it. The handoff should let the next person act without a meeting.
Use the note and the calendar record. A note that says discussed without a decision is weak evidence. Keep the boundary visible in the place where the work is assigned. Name the owner in the same line as the action. The handoff should let the next person act without a meeting.
Record the date the note was created. Use the same format for every handover so the next reader can scan it. Keep the boundary visible in the place where the work is assigned. Keep the evidence with the record rather than in a separate log. The brief should name what is approved and what needs a question. The evidence should stay with the record, not in a private note.
Use a census of the meetings if the volume is manageable. If sampling is necessary, stratify by meeting type. Use the same format for every handover so the next reader can scan it. Ask whether a new reviewer could act on the record without a conversation. The brief should name what is approved and what needs a question. The handoff should let the next person act without a meeting.
Pilot the classification on a few notes and compare the reviewers. Clarify what counts as a decision. If the source is unclear, route the question instead of guessing. Separate what was observed from what was assumed. The review should leave one owner and one date. The evidence should stay with the record, not in a private note.
Report completeness and timeliness by meeting type. Show the meetings without a dated note. Keep the original note beside the corrected version. Record the date and the source so the next reviewer can repeat the check. The handoff should let the next person act without a meeting. The brief should name what is approved and what needs a question.
Present the results as a description of the record, not a judgment about the chair. Keep the boundary visible in the place where the work is assigned. Write the deadline as a date and a local time. A short note with four fields is easier to use than a long narrative. The handoff should let the next person act without a meeting.
The note may be in a different system. State the systems included. Test the rule on one real request before applying it to the queue. Record the date and the source so the next reviewer can repeat the check. A control that depends on memory is not yet a control. The brief should name what is approved and what needs a question.
The meeting may not have needed a decision. Record the exception. Record the exception and the person who approved it. Test the rule on one real request before applying it to the queue. A control that depends on memory is not yet a control. The handoff should let the next person act without a meeting.
Repeat the review after a template change or at the same interval each quarter. Compare the same meeting types. If the source is unclear, route the question instead of guessing. Record the exception and the person who approved it. A control that depends on memory is not yet a control. The review should leave one owner and one date.
Assign the follow-up to the operations lead and set a date. The protocol should produce a specific decision about the note template. Write the deadline as a date and a local time. Keep the evidence with the record rather than in a separate log. A control that depends on memory is not yet a control. The review should leave one owner and one date.
Questions people ask
Sources
- U.S. Small Business Administration: Public guidance consulted for general context.
- U.S. Department of Labor: Public guidance consulted for general context.
- NIST Privacy Framework: Public guidance consulted for general context.