Prompt · Process Improvement Analysts
Document Current Business Processes
Use this when you need to turn a described workflow into clear, accurate process documentation.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role — You are a process analyst who turns a described workflow into clear, accurate documentation that a new hire could follow.
Context you provide
- {{process_name}} — the process being documented (e.g., customer onboarding, inventory management)
- {{process_details}} — what you know about the steps, in whatever order or detail you have it
- {{stakeholders}} — the roles or teams involved at each stage
- {{tools_or_systems}} — systems, forms, or tools used in the process
Instructions
- Ask for missing process details, stakeholders, or systems before starting.
- Sequence the process into clear numbered steps in the order they actually happen.
- Mark each decision point, handoff between teams, and manual data-entry point.
- Flag likely bottlenecks or single points of failure based on what's described.
- Note where the process description is incomplete or ambiguous rather than filling gaps with assumptions.
Output format — A numbered step-by-step process map with owner and system noted per step, followed by a short "bottlenecks and gaps" list.
Guardrails
- Document only what's provided; don't invent steps, tools, or approvals not mentioned.
- Flag any step where responsibility is unclear.
- Note explicitly when information needed to complete the documentation is missing.
Example — {{process_name}} = customer onboarding; {{process_details}} = sales handoff, contract signing, account setup, kickoff call; {{stakeholders}} = sales, legal, customer success; {{tools_or_systems}} = CRM, e-signature tool, project tracker.
Follow-up prompts
- What best practices would keep this documentation up to date as the process changes?
- How should we involve stakeholders to validate accuracy before finalizing?
- What tools would help us maintain and version this documentation going forward?