Structured Meeting & Incident Workflows: From Notes to Audit-Ready Records

Comment utiliser cette collection

# Turning Raw Inputs into Verifiable Office Records This collection provides a strict progression for turning messy text inputs into structured, auditable records. It is designed for team leads, project coordinators, and ops staff who need to process meetings or incidents without inventing facts. ## Prerequisites 1. **An ordinary AI chat**: Any tool that accepts pasted text (e.g., ChatGPT, Claude). No API keys or installations required. 2. **Raw Source Material**: You must have the actual meeting notes, transcript excerpts, incident logs, or event schedules. 3. **Permission**: Ensure you have the right to paste this data into the chosen AI tool. Redact sensitive personal or commercial information if necessary. ## The Progression **Step 1: Stakeholder Interest Map (`50a4b899-c4cc-48fb-91a2-1cfe30aa46f5`)** *Role*: Establish a neutral baseline. *Action*: Paste meeting notes to extract every named party's stated position, basis, and open questions. *Why*: Before assigning tasks, you must know exactly who said what. This step prevents misattribution by labeling evidence as `explicit`, `implied`, or `unclear`. **Step 2: Action Register (`a7cdc10d-46a7-4273-a857-651747981c9b`)** *Role*: Extract actionable work items. *Action*: Convert rough minutes into a Markdown table with columns for Action, Owner, Due Date, and Status. *Constraint*: If the source does not name an owner or date, these fields remain **blank**. Tentative words like "maybe" are never upgraded to firm commitments. **Step 3: Incident Timeline (`f0f33817-8fde-4806-a732-ab3e4fe69cd2`)** *Role*: Document non-meeting events (outages, complaints). *Action*: Order log entries strictly by provided timestamps. Conflicting times are shown side-by-side; untimed entries are grouped separately. *Output*: A factual narrative and a draft follow-up message for manual review. **Step 4: Photo Shot List (`a909b218-97cc-4a4c-bab7-11a9106fa9aa`)** *Role*: Forward-planning for events. *Action*: Turn a schedule into a checklist of one image per moment, specifying framing and must-show elements. *Why*: Applies the same "no-invention" discipline to planning: if details are missing, the row is marked `needs more detail` rather than guessed. ## Verification & Limitations - **Traceability**: Every row in the output must trace back to a specific phrase in your input. Delete any row that cannot be traced. - **No External Actions**: These prompts do not send emails, schedule calendar events, or access external databases. They only process the text you paste. - **Human Review Required**: The outputs are drafts. You must verify that the extracted actions and timelines align with reality before sharing them. - **Fictional Examples**: All examples within the prompts are illustrative only and do not represent real test results.