This meeting checklist template records the required evidence, actual reference and next action for each preparation task. It checks readiness records before the meeting; it does not replace an agenda or report that the meeting happened.
Define the check before the checkbox
A CDC-hosted discussion guide includes preparation categories such as date/location, participants, note taking, handouts and supplies. Use those general organizational categories here, without adapting the guide's public-health scenario or copying its checklist form. Pre-activity organizational checklist
For this original fictional project review M01, use five explicit checks. The snapshot is October 13, 2026, date-only. Actual meeting timing, role holders, contact routes and the organization's decision about unresolved prerequisites need confirmation.
“Confirmed” in this example means the specified evidence has been supplied for that check's current scope. It is not a universal permission to hold a meeting.
Review the five preparation rows
| Check | Task/role | Required evidence | Supplied state | Status and next action |
|---|---|---|---|---|
| C01 | Organizer: date/location | Current date/location reference | E01 supplied in the fictional fixture | Confirmed for this check; retain E01. |
| C02 | Organizer: participant confirmation | Actual participant confirmation records | Missing | Unresolved; obtain confirmation through the actual approved route. |
| C03 | Organizer: note-taker role | Role holder's acceptance | Note taker proposed; no acceptance supplied | Unresolved; confirm the proposed person's agreement. |
| C04 | Material owner: correct pre-read | Current required document/version reference | E04 verifies v2 | Confirmed for v2; retain the version reference. |
| C05 | Actual display-check owner | Performed room-display check/result | Not performed | Unresolved; assign and complete the applicable check. |
The actual task owners are TO CONFIRM. Role labels indicate responsibility categories, not accepted assignments. No participant names or private contacts are supplied.
Under these fictional evidence rules, there are two confirmed checks and three unresolved checks. Report the count that way. Do not turn two out of five into a “40% meeting quality” score, a guarantee of readiness or authorization to proceed.
Keep drafts and proposals visible as proposals
An invitation draft can support message preparation. It cannot fill an “invitation sent” evidence field, and sending an invitation would still not prove participant confirmation. Keep draft reference, actual send record and actual response reference separate if the organizer uses those fields.
Similarly, a proposed note taker does not establish that someone accepted the role. Use this unsent request:
Please confirm whether you can take notes for M01 and acknowledge the agreed recordkeeping role. The preparation log currently records the role as proposed, with acceptance not yet supplied.
Record actual acceptance only after it arrives. Do not replace an unresolved row with a checkmark merely because someone was named in a draft.
Reopen the version-dependent check
Now suppose the client changes the required pre-read to v3. E04's v2 check is still useful history, but it does not verify the new document.
Retain the original snapshot, record C04: v2 → requested v3, and mark the current v3 check unresolved. Request the current v3 reference and the appropriate material-owner review. Do not edit E04 to say v3 without new evidence.
If the other rows stay unchanged, this hypothetical new snapshot has one confirmed check and four unresolved checks until v3 evidence is supplied. That is a changed evidence count, not proof that the meeting became worse.
Use a changed-prerequisite log with original check/version/reference, changed requirement, actual recheck evidence, date/role, status and next action. The actual v3 check fields remain blank.
Close the preparation review with a decision record
Before the meeting, the organizer reviews unresolved prerequisites and records the actual decision under the organization's rules. This example supplies no go/no-go policy. It does not assume that every unresolved item cancels a meeting or that a count alone permits it.
Keep a blank form for review date, reviewer, outstanding check IDs, decisions about each gap, follow-up owner and actual outcome. Do not mark the meeting held, attendance confirmed or invitations sent without the corresponding records.
Copy this prompt for the readiness log
Prepare an original US-English meeting preparation checklist with task/role/required evidence/actual reference/status/next action, changed-prerequisite log and blank organizer decision record. No actual meeting, invitations or confirmations claimed.
Fictional M01 project review, as of October 13, 2026 date-only. Five checks:
C01 date/location evidence E01 supplied -> confirmed under fixture rules.
C02 participant confirmation missing -> unresolved.
C03 note-taker role proposed without acceptance -> unresolved.
C04 correct pre-read v2 reference E04 supplied -> confirmed for v2 only.
C05 room-display check not performed -> unresolved.
Actual owners/contacts/routes/timing and organization's proceed/hold criteria TO CONFIRM. Two confirmed/three unresolved, not 40% quality or permission.
Separate invitation draft, actual send and participant response evidence. Proposed note taker not accepted role; include a labeled unsent acceptance request. No private names/contacts invented.
Hypothetical required pre-read changes to v3: retain E04v2/history, make current C04 unresolved, request new v3 check/reference. With other rows unchanged one confirmed/four unresolved; do not overwrite v2 evidence. Actual v3 review fields blank. Record version change, required evidence, actual recheck, date/role/status/next action. Organizer's actual preparation decision/outcome blank; no automatic readiness permission or meeting-quality score. Native maintained preparation records authoritative.
Review the gaps beside their evidence
An optional prepared HTML review in NOS can show M01's five checks beside the version-dependent pre-read history and follow-up requests. NOS supports saving and rendering HTML. Keep the maintained preparation log and actual confirmations authoritative; the review does not send invitations or accept roles.
Explore NOS to present the prepared readiness review. Leave the organizer with a named unresolved check and a specific evidence request for every remaining gap.