OctiAI

Categories

Decision Log & Risk Register Prompt Pack

Convert emails, chats and meeting notes into compliance-ready decision records, an auditable risk register, and machine-friendly CSV exports (Markdown output).

What You'll Get

How to Use

Quick formatting tip

Always provide raw source text with original timestamps and sender names, and specify a time zone and ISO 8601 date format up front. This prevents the assistant from pausing for clarification and ensures all audit timestamps are consistent and export-ready.

Works Best With

Works best when you provide:

Prompt Template


# Work Ops (Meetings, Docs, Support) Prompt Blueprint

## Goal
Produce a compliance-ready decision log and linked risk register from email/chat threads and meeting notes. Each decision must include rationale, considered alternatives, impacted systems/teams, mitigations, action owners, and an audit-ready timestamped entry suitable for distribution and archival.

## Inputs
Provide the following when you paste this prompt into the assistant (if any item is missing the assistant must ask clarifying questions before producing the final artifact):
- Raw source material: email threads, chat transcripts, meeting notes (paste full text, preserve timestamps and sender names).
- Stakeholders and decision owners (list of names, roles, or teams).
- Project/context summary and time window to analyze.
- Desired tone for distribution (compliance-formal, neutral, or action-oriented).
- Time zone and preferred date format (ISO 8601 recommended).

If you cannot provide one or more inputs immediately, state which are missing and answer the assistant’s clarifying questions before finalizing.

## Prompt
You are an operations analyst producing a compliance-grade Decision Log and Risk Register. Follow these steps exactly. If required inputs are missing, stop and ask the user only the specific clarifying questions listed below.

1. Confirm receipt of these required inputs: raw source material, stakeholders, project/context summary, tone, time zone/date format. If any are missing, ask these clarifying questions:
   - Which timeframe should I analyze (start and end dates)?
   - Who are the authoritative stakeholders or approvers to attribute decisions to?
   - Which time zone and date format should I use for timestamps?
2. Parse the supplied raw sources and extract all candidate statements that represent decisions, proposals, approvals, or explicit commitments. Keep the verbatim excerpt (10-30 words) and cite source, sender, and timestamp for each excerpt.
3. Deduplicate candidate decisions by grouping semantically identical entries; list grouped source excerpts under the same decision.
4. For each final Decision entry produce the following structured record (use the exact field order and labels):
   - Decision ID: D-YYYYMMDD-NN (use the date of first source mention and sequential NN).
   - Timestamp (ISO 8601 with time zone) of the authoritative confirmation or earliest explicit approval.
   - Decision (concise single-sentence statement).
   - Rationale (summary of reasons cited in sources; include verbatim supporting quote(s) with source and timestamp).
   - Considered Alternatives (bullet list of alternatives explicitly discussed; if not discussed, state "No alternatives recorded" instead of inventing).
   - Impacted Systems/Teams (bullet list).
   - Mitigations / Acceptance Criteria (actions, constraints, or conditions tied to the decision).
   - Action Items (bullet list of actions required to implement the decision with Owner — Role or Person — Due date — Status [Proposed/Confirmed]).
   - Confidence Level (High/Medium/Low) and brief justification for the confidence.
   - Source list (all source excerpts cited, sender, channel, timestamp).
   - Audit trail entry: who recorded the entry, timestamp of log creation, and a unique log ID that matches Decision ID.
5. Create a linked Risk Register. For each decision, identify risks introduced or shifted by the decision and create risk entries using this exact field order:
   - Risk ID: R-YYYYMMDD-XXX (date of decision linkage, sequential XXX).
   - Timestamp (ISO 8601 with time zone).
   - Risk Description (concise).
   - Likelihood (Low/Medium/High) and Impact (Low/Medium/High).
   - Risk Score (Likelihood × Impact expressed as Low/Medium/High with numeric equivalent: Low=1, Medium=2, High=3).
   - Owner (Role or Person; mark as Proposed if not assigned in sources).
   - Mitigation Actions (bullet list with Owner and Due date).
   - Current Status (Open/Monitoring/Mitigated/Accepted).
   - Linked Decision IDs.
   - Source citations (verbatim excerpts if present).
6. Generate an Executive Summary at the top with: number of decisions, number of risks, immediate critical actions (owners + due dates within 7 days), and next recommended follow-ups (who should convene and when).
7. Provide an “Open Questions / Clarifications” section listing unresolved items extracted from sources; tag each with suggested owner and recommended due date for resolution.
8. Add a “Facts vs Assumptions” table that separates statements explicitly supported by source citations (Facts) from reasonable inferences or suggestions made by the assistant (Assumptions). Mark all Assumptions with a confidence rating and a remediation step to convert them into Facts.
9. Produce two machine-friendly attachments at the end:
   - CSV table for Decisions with columns: Decision ID, Timestamp, Decision, Owner(s), Due date(s), Confidence, Source IDs.
   - CSV table for Risks with columns: Risk ID, Timestamp, Description, Likelihood, Impact, Score, Owner, Status, Linked Decision IDs.
10. Final delivery requirements:
   - Use clear Markdown headings and bullet lists.
   - Use ISO 8601 timestamps including time zone.
   - Always include verbatim source excerpts (quoted) with sender and timestamp for each fact used.
   - Do not invent approvals, owners, or dates; if assigning, label them as Proposed.
   - Append a short audit statement: who produced the log (assistant), timestamp of generation, and processing notes (files processed, number of source items).
11. Before finalizing, list any missing input or ambiguities and indicate which items remain Proposed or Assumed.

If at any step the assistant lacks sufficient evidence to populate a required field, do not guess: mark the field as Proposed or Unknown, provide the reasoning for that classification, and add a recommended owner and due date to resolve it.

## Output Format
Produce the artifact in this exact arrangement and headings:

- Executive Summary
  - Totals, critical actions, next follow-ups

- Decisions
  - For each Decision entry use the Decision record format exactly (Decision ID, Timestamp, Decision, Rationale, Considered Alternatives, Impacted Systems/Teams, Mitigations / Acceptance Criteria, Action Items, Confidence Level, Source list, Audit trail entry)

- Risk Register
  - For each Risk entry use the Risk record format exactly (Risk ID, Timestamp, Risk Description, Likelihood, Impact, Risk Score, Owner, Mitigation Actions, Current Status, Linked Decision IDs, Source citations)

- Open Questions / Clarifications
  - Unresolved items with suggested owner and due date

- Facts vs Assumptions
  - Two columns/lists separating Facts (with citations) and Assumptions (with confidence and remediation steps)

- Machine Attachments (CSV)
  - Decisions table (CSV)
  - Risks table (CSV)

- Audit Statement
  - Who produced the log, generation timestamp, number of source items processed, processing notes

Use only Markdown formatting. Ensure the Decision and Risk entries are fully self-contained and citation-backed.

## Guardrails
- Separate facts from assumptions explicitly; never present assumptions as facts.
- Always include verbatim source excerpts with sender and timestamp for any claim derived from source material.
- Do not invent approvals, owner assignments, or due dates. If the assistant assigns one, label it Proposed.
- Provide a confidence level for each Decision and Risk and explain the reasoning.
- Use ISO 8601 timestamps with the user’s time zone; if user did not specify a time zone, ask before finalizing.
- Flag and list potential compliance-sensitive items (privacy, regulatory, contractual) and cite the exact source language that raises them.
- Do not make policy or legal claims; instead, flag items that require legal review and include the source text for review.
- Maintain an audit trail: every Decision and Risk must include source excerpts and a creation log entry.

## Examples
Example Decision excerpt:

- Decision ID: D-20250412-01  
  Timestamp: 2025-04-12T15:03:00-07:00  
  Decision: Migrate payments API to Gateway X by end of Q3.  
  Rationale: "We need the higher throughput and PCI scope reduction" — Product Lead, email, 2025-04-12T14:55:10-07:00.  
  Considered Alternatives:
  - Keep current provider and optimize caching (explicitly discussed).
  - Use in-house proxy (no formal evaluation recorded).
  Impacted Systems/Teams:
  - Payments service, Fraud detection, DevOps, Customer Support.  
  Mitigations / Acceptance Criteria:
  - End-to-end tests pass, performance targets met, rollback plan documented.  
  Action Items:
  - Run capacity test — Owner: SRE Team — Due: 2025-04-19 — Status: Proposed.  
  Confidence Level: Medium — justification: decision phrased as plan, not approved by CFO in sources.  
  Source list:
  - "We need the higher throughput and PCI scope reduction" — Product Lead — email thread: payments@company — 2025-04-12T14:55:10-07:00.  
  Audit trail entry:
  - Recorded by assistant — 2025-04-13T09:12:00-07:00 — Log ID D-20250412-01

Example Risk excerpt:

- Risk ID: R-20250412-001  
  Timestamp: 2025-04-12T15:10:00-07:00  
  Risk Description: Increased vendor lock-in and potential pricing exposure from Gateway X.  
  Likelihood: Medium — Impact: High — Risk Score: Medium (2×3).  
  Owner: Procurement (Proposed)  
  Mitigation Actions:
  - Negotiate termination clauses — Owner: Procurement — Due: 2025-05-01 — Status: Proposed.  
  Current Status: Open  
  Linked Decision IDs: D-20250412-01  
  Source citations:
  - "Gateway X terms require annual renewal" — Vendor reply — 2025-03-28T11:02:00-07:00

Now paste the raw source material and the required inputs so I can begin extraction and produce the Decision Log and Risk Register.

Variables

Usage Notes

Not for

Do not include

Decision Log & Risk Register Prompt Pack

Turn noisy meeting notes, email/chat threads, and ad-hoc inputs into a standardized, auditable Decision Log and linked Risk Register with explicit rationale, mitigations, owners, and CSV exports.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

What you'll get

Output format

Markdown

Best used when

Avoid when

Sign in to save, like, or rate this prompt.

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

No placeholders required for this prompt.

Rules

Canonical Examples

Input: 30-min product + infra sync (Slack thread + meeting notes) about migrating the user-events pipeline from self-hosted Cassandra to ManagedDB (AcmeDB), plus retention policy changes. Stakeholders: Product Lead (A. Chen), SRE Lead (R. Gupta), CTO (M. Silva). Time window: 2026-02-01 to 2026-02-03. Tone: compliance-formal. Time zone: America/Los_Angeles (ISO 8601).

Loading result...

Failed to load output.


- Executive summary: 2 decisions, 3 risks. Critical actions: run migration test (SRE) due within 5 days.

- Decision D-20260202-01: Migrate user-events pipeline to AcmeDB (Managed) by 2026-04-01. Rationale: performance & ops overhead reduction. Confidence: Medium.

Why it works: This example demonstrates extracting decisions from a mixed Slack + meeting-notes input, grouping semantically identical proposals, producing audit-ready decision records with verbatim excerpts, and creating a linked risk register with proposed mitigations and machine-friendly CSVs—exactly matching the prompt blueprint.

Input: Email thread and Slack about hiring a contract recruiter to accelerate Q2 hiring and standardizing the Product Manager job description. Stakeholders: Head of People Ops (L. Ortiz), Hiring Manager (B. Patel), CEO (K. Sun). Time window: 2026-01-25 to 2026-01-27. Tone: neutral. Time zone: Europe/London (ISO 8601).

Loading result...

Failed to load output.


- Decision D-20260126-01: Engage contract recruiter for Q2 hiring (90-day contract). Action: Procurement to process SOW. Risks include budget overrun and candidate quality.

- Decision D-20260126-02: Adopt standardized Product Manager JD template; Hiring Manager to validate.

Why it works: Shows how the prompt converts an email + Slack hiring discussion into discrete decisions (hire contract recruiter; adopt JD template), captures verbatim excerpts, creates action items with Proposed owners when missing, and generates linked risks (budget, compliance) and CSV attachments for downstream automation.

Works Best With

Works best when you provide: