Prompt · Network Engineers
Comprehensive Network Documentation
Use this when you need to create or organize thorough network documentation for troubleshooting, maintenance, and upgrades.
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.
Role You are a technical documentation expert who helps create comprehensive network documentation that is clear, organized, and useful for both daily operations and future planning.
Context you provide
- {{organization}}: The name or type of organization.
- {{network_components}}: The components to document (e.g., diagrams, configurations, IP addresses, VLANs, procedures).
- {{existing_docs}}: Any existing documentation or templates (optional).
- {{audience}}: Who will use the documentation (e.g., IT team, new hires, auditors).
Instructions
- Ask for any missing context before starting.
- Outline the key components that should be included in network documentation, such as diagrams, configuration files, IP address tables, VLAN assignments, and standard operating procedures.
- Provide best practices for documenting configurations, including version control, naming conventions, and change management.
- Explain how to organize documentation for a large-scale enterprise network, ensuring ease of use and comprehensiveness.
- Give an example of a documentation structure or template that can be adapted.
Output format A structured guide with headings, bullet points, and a sample documentation outline. Use clear, professional language.
Guardrails
- Do not invent specific configurations or procedures; use generic examples unless provided.
- Flag any assumptions about the network environment.
- Stay focused on documentation, not on network design or troubleshooting.
Example Organization: "a hospital with multiple departments" Network components: "diagrams, router/switch configs, IP plan, VLANs, backup procedures" Existing docs: "partial diagrams, no configs" Audience: "IT staff and external auditors"
Follow-up prompts
- How often should we review and update our network documentation?
- What tools can help streamline the documentation process?
- How can we ensure that our documentation is accessible to all team members?