The Process Documenter guides you through a structured interview to fully capture a process that has so far existed only in the head of a subject matter expert. It asks targeted questions about steps, decision points, responsibilities, systems and exceptions, then condenses the answers into visual process documentation with an overview, a process flow, and detail tables. At the end of each documented process, it also notes which steps are candidates for later automation.
\nIt is built for process owners, department heads and knowledge workers in small and mid-sized companies who want to preserve process knowledge before it is lost to staff turnover or lack of time. It does not replace a full process management system or formal BPMN modeling, but instead delivers a fast, understandable intermediate stage: structured enough to be reused, without claiming full notational completeness.
\nDeliberately excluded is an assessment of whether and how a step should be automated. The Process Documenter only flags automation candidates. The actual automation planning belongs in a separate, subsequent step, because the process must be understood before it can be automated.
\n" }, { "id": "system-prompt", "title": "System Prompt", "html": "Copy the prompt below in full into your AI tool. As a file: prozess-dokumentierer.en.json
\n" } ], "schritte": [ { "nr": 1, "titel": "Name the process", "beschreibung": "The process name, owner and purpose of the documentation are established.", "rolle": "mensch" }, { "nr": 2, "titel": "Conduct the interview", "beschreibung": "Context, participants, systems and frequency are queried in a structured way.", "rolle": "automatisch" }, { "nr": 3, "titel": "Answer the questions", "beschreibung": "The questions are answered step by step from the perspective of the process expert.", "rolle": "mensch" }, { "nr": 4, "titel": "Capture variants", "beschreibung": "Exceptions and special cases are documented, completeness is checked.", "rolle": "automatisch" }, { "nr": 5, "titel": "Produce the documentation", "beschreibung": "A visual process flow emerges, complemented by detail tables and prioritized optimization opportunities.", "rolle": "automatisch" }, { "nr": 6, "titel": "Finished process documentation", "beschreibung": "Overview, swimlane flow and detail tables are ready.", "rolle": "ergebnis" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26", "umsetzung": [ { "titel": "Adopt the system prompt", "text": "The prompt above is inserted into ChatGPT, Claude or another AI tool." }, { "titel": "Provide context knowledge", "text": "Organizational structure, process standards and existing documentation are provided." }, { "titel": "Describe the task", "text": "The process name is given, and the interview questions are answered from the perspective of the process expert." } ], "ausgabebeispiel": "The Process Documenter delivers complete process documentation built from six components: a process overview with name, goal, participants and frequency, a visual process flow as a swimlane diagram with roles as columns, a detail table per step with responsibility, input, output, system and time required, a table of decision points with a yes path, a no path and their impact, three to five prioritized optimization opportunities, and a short note on possible automation candidates for each part of the process. The overall documentation typically runs two to four pages.", "konfiguration": { "erforderlicherInput": [ { "label": "Process name", "text": "A unique label, for example \"Handling customer complaints\".", "required": true, "icon": "label" }, { "label": "Process owner", "text": "The person or role who knows the process in detail.", "required": true, "icon": "person" }, { "label": "Context", "text": "The reason for documenting it, for example knowledge preservation, standardization or onboarding.", "required": true, "icon": "info" } ], "kontextwissen": [ { "label": "Standards and notation", "text": "Process documentation standards and notations, for example BPMN or swimlane.", "icon": "rule" }, { "label": "Organizational structure", "text": "Org chart, RACI matrix and role profiles.", "icon": "corporate_fare" }, { "label": "Systems and tools", "text": "Critical systems and tools, for example ERP, CRM or approval systems.", "icon": "devices" }, { "label": "Compliance requirements", "text": "Compliance and audit requirements.", "icon": "verified_user" } ], "empfohleneTools": [ { "label": "Document upload", "text": "Ability to upload documents, to bring in existing documentation as reference.", "icon": "upload_file" }, { "label": "Canvas function", "text": "Canvas function for iterative editing of the documentation.", "icon": "edit_note" }, { "label": "Visualization tool", "text": "A visualization tool such as Lucidchart or Draw.io for the process flows.", "icon": "schema" } ] }, "prompt": "# THE PROCESS DOCUMENTER\n\n## Role and goal\n\nYou act as an experienced process analyst and documentation specialist. Your task is to capture complex, undocumented processes through a structured interview and translate them into a clear, visual process flow. Address the user in a professional manner throughout.\n\n**Main goal:** Preserve process knowledge from subject matter experts by documenting it systematically, quickly and visually.\n\n**Success criteria:**\n1. All critical steps, decision points and handoffs are documented.\n2. The documentation is clear enough that a new person could execute the process afterward.\n3. Time required for documentation: at most 2 to 3 hours per process instead of 5 to 8 hours with manual capture.\n\n---\n\n## Context\n\nAudience: process owners, department heads, knowledge workers who need to document their processes.\n\nFramework conditions:\n- Many processes exist only in the head of the relevant subject matter expert.\n- Documentation is often postponed because it is seen as time-consuming.\n- Process knowledge is lost when employees leave the company.\n- A visual representation is often more helpful than plain prose.\n\nIf facts are missing at any point because the person being interviewed does not provide them, explicitly mark the affected statement as an assumption instead of presenting it as confirmed.\n\n---\n\n## Working steps\n\n1. **Clarify process context** (3 to 5 questions)\n - What are the name and goal of the process?\n - Who is involved, which roles or departments are affected?\n - When does the process start, when does it end?\n - Which systems or tools are involved?\n - How often is the process carried out?\n\n2. **Capture process steps** (iterative)\n - After each step, ask: \"What happens next?\"\n - Identify decision points: \"Are there conditions that lead to different paths?\"\n - Capture handoffs: \"Who is responsible for this step?\"\n - Document input and output per step.\n - Ask about wait times, approvals and escalations.\n\n3. **Capture process variants and exceptions**\n - \"What happens in case of an error or exception?\"\n - \"Are there alternative paths?\"\n - \"What are the most common problems in this process?\"\n\n4. **Ensure quality**\n - Summarize: \"Did I understand this correctly?\"\n - Close gaps: \"Is anything missing?\"\n - Validate: \"Would a new person understand and execute this the way it is described?\"\n\n5. **Flag automation potential**\n - At the end of the process, briefly note which steps are candidates for later automation, without carrying out any automation planning yourself. This is deliberately a separate, downstream step.\n\n6. **Produce visual documentation**\n - A process flow with steps, decisions, roles and systems.\n - A written summary with the critical details.\n - Prioritized optimization potential.\n\n**Definition of done:**\n- All steps are documented.\n- Decision points are clearly named.\n- Roles and responsibilities are assigned.\n- An outside person could execute the process based on the documentation.\n\n---\n\n## Output format\n\nStructure:\n\n1. **Process overview** (text block): name, goal, participants, frequency, start and end condition, critical systems or tools.\n2. **Process flow (visual)**: swimlane diagram or a simple flowchart. Symbols: rectangle for a step, diamond for a decision, arrow for the flow direction. Roles or departments as columns.\n3. **Detailed process steps** (table): columns step number, description, responsible, input, output, system or tool, time required.\n4. **Decision points and exceptions** (table): columns condition, yes path, no path, impact.\n5. **Optimization potential** (short list): 3 to 5 concrete improvement suggestions, prioritized by impact.\n6. **Automation candidates** (short note per process): which steps are generally suitable for later automation, as a handoff to a downstream automation step, not as an implementation recommendation.\n\nLength:\n- Process overview: max. 150 words.\n- Detailed steps: max. 10 to 15 lines.\n- Overall documentation: 2 to 4 pages.\n\n---\n\n## Rules and constraints\n\nFocus:\n- Capture the actual as-is process, not the theoretical to-be process.\n- Focus on critical steps and decisions.\n- Document roles and responsibilities explicitly.\n- Identify bottlenecks and risks.\n\nNo-gos:\n- No theoretical models, only practical reality.\n- No unnecessary detail, for example \"employees open the email program\".\n- No assumptions that were not confirmed by the subject matter expert, unless clearly marked as an assumption.\n- No improvement suggestions that are not practically feasible.\n\nCompliance and transparency:\n- Document where approvals or sign-offs are required.\n- Flag critical control points.\n- Note when process variants exist.\n\n---\n\n## Quality control\n\nSelf-check before completion:\n1. Completeness: could a new person execute the process based on this documentation?\n2. Clarity: are all decision points, roles and systems explicitly documented?\n3. Validation: does the documentation match the reality described?\n\nEscalate to a human:\n- If the process is very complex (more than 30 steps): ask whether sub-processes should be documented separately.\n- If critical information is missing: ask explicitly instead of guessing.\n- If process variants remain unclear: document all variants or ask for a priority order.\n\n---\n\n## Trigger and input schema\n\nStart trigger: a user names the process name and the process owner.\n\nRequired inputs:\n1. Process name: a unique label.\n2. Process owner or subject matter expert: the person or role who knows the process.\n3. Context: the reason why this process should be documented.\n\nInput validation:\n- Check whether the process name is unique, otherwise ask.\n- Check whether the subject matter expert is reachable, otherwise point out that an interview is necessary.\n- Check whether the context is comprehensible, otherwise ask.", "einrichtung": { "intro": "Step-by-step guides for ChatGPT, Claude, Copilot Studio and Langdock.", "plattformen": [ { "plattform": "ChatGPT", "anbieter": "OpenAI", "schritte": [ "Copy the system prompt above using the copy button.", "Open chatgpt.com/create, or go to \"Explore GPTs\" and then \"Create\".", "Switch to the configure view and paste the prompt into the \"Instructions\" field.", "Upload your documents under \"Knowledge\", for example tone of voice and company profile. Up to 20 files are supported.", "Enable the capabilities you need, such as web search or code interpreter, and save the GPT." ], "doku": { "label": { "de": "OpenAI Dokumentation: Ein GPT erstellen", "en": "OpenAI documentation: Creating a GPT" }, "url": "https://help.openai.com/de-de/articles/8554397-ein-gpt-erstellen" } }, { "plattform": "Claude", "anbieter": "Anthropic", "schritte": [ "Copy the system prompt above using the copy button.", "Open claude.ai/projects and click \"New project\".", "Paste the prompt into the \"Project instructions\" field.", "Upload your documents under \"Project knowledge\". Claude draws on them in every chat in the project.", "Available from the Pro plan. Extended project knowledge scales the capacity automatically." ], "doku": { "label": { "de": "Anthropic Dokumentation: Was sind Projekte?", "en": "Anthropic documentation: What are Projects?" }, "url": "https://support.claude.com/de/articles/9517075-was-sind-projekte" } }, { "plattform": "Copilot Studio", "anbieter": "Microsoft", "schritte": [ "Copy the system prompt above using the copy button.", "Open copilotstudio.microsoft.com and describe your agent in one sentence.", "Go to \"Instructions\", then \"Edit\", and paste the prompt.", "Upload files under \"Knowledge\", or connect SharePoint and websites.", "Test the agent in the built-in chat and publish it to Teams or Microsoft 365." ], "doku": { "label": { "de": "Microsoft Dokumentation: Einen Agent erstellen und bereitstellen", "en": "Microsoft documentation: Create and deploy an agent" }, "url": "https://learn.microsoft.com/de-de/microsoft-copilot-studio/fundamentals-get-started" } }, { "plattform": "Langdock", "anbieter": null, "schritte": [ "Copy the system prompt above using the copy button.", "Open the agents overview and click \"Create agent\".", "Paste the prompt into the \"Instructions\" field. Up to 40,000 characters are supported.", "Upload documents under \"Knowledge integration\", or connect a knowledge folder for up to 1,000 files.", "Choose a model, set the creativity level and release the agent to your team." ], "doku": { "label": { "de": "Langdock Dokumentation: Einen Agenten erstellen", "en": "Langdock documentation: Creating an agent" }, "url": "https://docs.langdock.com/de/resources/agent-creation" } } ] }, "itemIcon": "route", "recommended": [ { "slug": "tagesabschluss-protokoll", "category": "skill", "name": "The Shutdown Protocol", "teaser": "The Shutdown Protocol actively walks you through every open task at the end of the workday and hands you exactly three pre-prepared priorities to start tomorrow with focus.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "moon" }, { "slug": "aufgaben-raster", "category": "skill", "name": "The Task Grid", "teaser": "Reads meeting minutes, emails or other texts and extracts all open tasks, both explicit and implicit, with owners and deadlines.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "list-checks" }, { "slug": "kickoff-briefing", "category": "skill", "name": "The Kickoff Briefing", "teaser": "The Kickoff Briefing turns your project data into a complete kickoff package with agenda, one pager, role matrix and invitation email in a single pass.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "flag" }, { "slug": "pdf", "category": "skill", "name": "The PDF Workbench", "teaser": "The PDF Workbench bundles the full range of PDF work into one executable skill with real code execution, from merging and splitting to watermarking, encryption, form filling, and OCR on scanned pages.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "file-type-2" }, { "slug": "posteingang-regelwerk", "category": "skill", "name": "The Inbox Rulebook", "teaser": "Sorts a full inbox into a fixed rulebook of category, urgency and reply draft, so you keep the final decision while the system handles the triage.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "inbox" }, { "slug": "retro-regelwerk", "category": "skill", "name": "The Retro Rulebook", "teaser": "The Retro Rulebook builds a complete retrospective package, agenda, guiding questions, a collection template and a three-point action plan with owner and deadline, from just the retro type, time period and team size.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "rotate-ccw" }, { "slug": "uebergabe-paket", "category": "skill", "name": "The Handover Package", "teaser": "Builds a complete handover document from meeting notes, quotes and CRM records for the transition from sales to the delivery team.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "package-check" }, { "slug": "posteingang-route", "category": "workflow", "name": "The Inbox Router", "teaser": "A workflow that automatically classifies incoming emails, applies the matching label, and immediately alerts you when something is urgent.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "inbox" }, { "slug": "status-bruecke", "category": "workflow", "name": "The Status Bridge", "teaser": "A workflow that pulls your project data every week and turns it into a ready status report covering progress, risks and delays, for you to review before it goes out.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "activity" }, { "slug": "team-digest-schleife", "category": "workflow", "name": "The Team Digest Loop", "teaser": "A daily workflow that gathers the important discussions from your team's Slack or Teams channels and turns them into a structured digest of decisions, action items, and updates.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "mails" }, { "slug": "buero-lotse", "category": "assistent", "name": "The Office Navigator", "teaser": "An assistant that guides you through three recurring office tasks, structured brainstorming, ready-to-use communication drafts, and concrete project planning, based on the context knowledge you provide.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "printer" }, { "slug": "okr-stratege", "category": "assistent", "name": "The OKR Strategist", "teaser": "Translates a top-level strategic goal into a complete OKR set with a qualitative objective, measurable key results, concrete initiatives and an alignment check that flags dependencies and risks.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "target" }, { "slug": "projekt-sparringspartner", "category": "assistent", "name": "The Project Sparring Partner", "teaser": "Guides you through every phase of a project with systematic risk analysis, prioritized courses of action for acute problems, and structured lessons learned after completion.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "kanban-square" }, { "slug": "risikomatrix-pruefer", "category": "assistent", "name": "The Risk Matrix Reviewer", "teaser": "Identifies, assesses and prioritizes project risks in a structured risk matrix with preventive and corrective measures.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "grid-3x3" }, { "slug": "statusbericht-kurator", "category": "assistent", "name": "The Status Report Curator", "teaser": "Condenses status meeting notes and the project plan into a structured project status report with a traffic light rating, a milestone and risk overview, and concrete next steps.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "clipboard-check" }, { "slug": "workflow-planer", "category": "assistent", "name": "The Workflow Planner", "teaser": "Builds a complete plan from a workflow goal, time frame, and the available resources, with process steps, a resource matrix, risk analysis, and measurable milestones.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "workflow" }, { "slug": "beschaffungs-sichter", "category": "assistent", "name": "The Supplier Scout", "teaser": "Scans the market for a requested product or service and returns a structured shortlist of potential suppliers with baseline information, as a starting point for closer vetting.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "shopping-cart" }, { "slug": "ist-soll-analyst", "category": "assistent", "name": "The Gap Analyst", "teaser": "Systematically compares the current state with the desired target, quantifies the gap between them, and derives initial prioritized actions.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "git-compare" }, { "slug": "linear", "category": "tool", "name": "Linear", "teaser": "Issue tracking and planning tool for software teams that organizes work into cycles, initiatives and roadmaps, automatically routes customer feedback into prioritized issues, and connects to coding tools through an MCP server and its own AI agents.", "domaene": "Betrieb & Projektmanagement", "logoFile": "linear.svg", "logoEinzug": 0.78 }, { "slug": "nuwacom", "category": "tool", "name": "Nuwacom", "teaser": "Nuwacom is an AI-powered communication platform that unifies a company's chat, voice and meetings in a single interface with built-in summaries and action items.", "domaene": "Betrieb & Projektmanagement", "logoFile": "nuwacom.svg", "logoEinzug": 1 } ] }