This volunteer meeting agenda template provides a proposed 35-minute role briefing for a fictional paper-craft table. Two role sheets show different gaps: V1 has an instruction reference but no supervisor route; V2 lacks its approved instruction sheet. Role buttons produce a focused handoff instead of an invented readiness score.
Prepare the role before the meeting
V1 is a proposed kit sorter who would sort red and blue paper against a supplied sample label. The fictional role example says its instruction reference is available. The actual supervisor and contact route are unconfirmed, as are the volunteer's willingness, availability, materials, and observed preparation. Keep those questions visible rather than marking the role ready.
V2 is a proposed table guide who would demonstrate one fold from an approved instruction sheet. That sheet is missing. The next step is to obtain the approved source and its version, not to invent a fold for the briefing. Neither proposed role is an actual assignment, and the example supplies no record of a walkthrough.
Use six blocks with a purpose
Spend 5 minutes on purpose and task boundaries, 8 on instructions and the model, 8 on the role walkthrough, 6 on questions and unresolved items, 5 on supervisor/contact confirmation, and 3 on the close. The total is 5 + 8 + 8 + 6 + 5 + 3 = 35 minutes.
Each block should yield a reference, observation, or question. If an instruction is missing, use its block to record the gap and request the source through the coordinator. Do not call that discussion a completed demonstration. Confirm the real location, timing, access arrangements, local rules, and permitted activity before operational use.
Inspect the right handoff
Choose V1 in the example to display the instruction reference, missing contact, and the question "Who supervises this task, and what contact route should the volunteer use?" Choose V2 to replace that handoff with a request for the approved fold instruction sheet and version. The displayed role and question update together.
The National Park Service's volunteer manual describes orientation and job-specific preparation coordinated by program managers and supervisors. This agenda uses the general role-specific briefing idea. Its fictional paper table does not adopt NPS government duties, forms, labor requirements, or safety procedures. Your coordinator supplies the actual process and authority for the activity.
Close with the record you have
A reusable role sheet needs the permitted task, instruction/version, required materials, supervision route, actual agreement, observed walkthrough and support, remaining questions, and coordinator decision. Leave unsupplied people, dates, decisions, and observations blank. The reading view deliberately keeps both roles unconfirmed even after you inspect them.
The close can identify V1's contact gap and V2's missing source without judging a person's ability. Attendance and task authorization are different records. Record an actual follow-up owner only when someone accepts that responsibility. Keep the authoritative meeting packet in the coordinator's DOCX/PDF or normal event files, alongside actual agreements and observation notes. The HTML selects role information; it enrolls nobody and sends no request.
Copy this prompt to adapt the example
Design a coordinator’s meeting sheet with timed agenda outputs, role-specific preparation questions, and a blank working handoff record. Return one self-contained HTML file with embedded styling and working interactions. Use readable type, strong contrast, clearly labeled keyboard controls, and a layout that flows on a narrow phone. Identify the supplied data as a fictional example.
Build a fictional community paper-craft volunteer briefing with a complete proposed agenda: purpose/boundaries 5 minutes, instructions/model 8, role walkthrough 8, questions 6, supervisor/contact 5, close 3; total 35. Show each block's output and clarify that no meeting or training has occurred.
Provide two accessible role buttons. V1 kit sorter: proposed sorting of supplied red/blue paper against a sample label. Instruction reference available in the fictional example; supervisor/contact unknown. V2 table guide: proposed demonstration from an approved fold sheet, but that sheet is missing. Do not create fold instructions. Each role selection must update task, supplied evidence, missing prerequisites, and a focused coordinator question. V1 asks who supervises and how to contact them. V2 asks for the approved sheet/version before a walkthrough. Both keep actual agreement, materials, observations, assignment, follow-up owner, and decision unconfirmed. Add four blank working fields for instruction/version, supervisor/contact, walkthrough/support, and gap/next owner/date. Build handoff draft combines the selected role, these fields, and its current question in a readonly textarea, substituting To confirm for blanks. Selecting either role clears all four fields and the draft; editing a field invalidates the draft. Add a reusable role-record outline. Include a planning note that actual location, access, time, and local protocols need confirmation. Attendance is not readiness or authorization. No automatic readiness toggles, personal contacts, operational actions, sending, or persistence.
Close the briefing with the selected role's unanswered question and a named person to follow it up. The agenda and role comparison can be rendered together in NOS for the coordinator's review. For V2, the next useful step is obtaining the actual fold sheet and its version; only then can the coordinator arrange a walkthrough of the task the volunteer would perform.