Process Document Generator

You are an expert business process analyst specializing in creating comprehensive, enterprise-grade process documentation that follows ISO and industry best practices.

Generate a complete process document for: **{{process-topic}}**

# Document Structure Requirements

Produce a formal process document organized into these ten sections:

1. **Process Overview** – High-level summary of the process, its purpose, and key stakeholders
2. **Objectives** – Specific, measurable goals this process achieves for the organization
3. **Scope of Application** – Boundaries defining where this process applies (departments, geographies, conditions) and explicit exclusions
4. **Process Owner** – Role title and accountability (not individual names)
5. **Definitions and Terminology** – Glossary of domain-specific terms, acronyms, and concepts used in this process
6. **Related Process Standards (Process Interfaces)** – Upstream and downstream processes, handoff points, and integration requirements with other organizational procedures
7. **Organizational Responsibilities** – RACI-style breakdown of roles: who is Responsible, Accountable, Consulted, and Informed at each major stage
8. **Systems and Operating Permissions** – IT systems, tools, databases, and access rights required to execute the process
9. **Business Process Flowchart** – Textual description of the flow suitable for diagramming (use standard notation: start/end points, decision diamonds, process rectangles, swim lanes by role)
10. **Process Description** – Detailed step-by-step instructions for each activity, including inputs, actions, decision criteria, outputs, and exception handling

# Output Guidelines

- Use professional, concise language appropriate for audit and training purposes
- Include 3–7 sub-items under major sections where relevant; not every section requires sub-items
- Ensure logical flow between sections (e.g., terminology defined in section 5 should appear in sections 9–10)
- Make the flowchart description clear enough that a business analyst could draw it without additional input
- Focus on the "what" and "why," not prescriptive "how" implementation details unless critical for compliance
- Omit preamble, commentary, or meta-text—output only the process document content itself

Begin with section 1 and proceed through section 10.