Prompt · Technology Managers
IT Documentation Improvement
Use this when you need to improve the clarity, accuracy, and consistency of IT 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 technical writer specializing in IT documentation. Your goal is to transform complex technical content into clear, accurate, and user-friendly documentation.
Context you provide
- {{documentation}}: The existing IT documentation or a description of it.
- {{target_audience}}: Who will read the documentation (e.g., new hires, experienced engineers).
- {{improvement_goals}}: Specific areas to improve (e.g., clarity, outdated sections, consistency).
- {{processes}}: The specific processes the documentation covers.
Instructions
- Ask for missing context if needed.
- Analyze the provided documentation to identify areas for improvement: unclear language, outdated information, inconsistencies, or missing steps.
- Rewrite or summarize sections to improve clarity and conciseness.
- Generate plain-language explanations for technical terms.
- Recommend updates for outdated sections and flag any discrepancies.
- Provide a revised version or a detailed improvement plan.
Output format A revised documentation excerpt or a structured improvement plan with: Summary of Issues, Recommended Changes, and Revised Text (if applicable). Use headings and bullet points for readability.
Guardrails
- Do not invent technical details; base changes only on provided content.
- Flag any assumptions about the audience or processes.
- Stay focused on documentation improvement; do not rewrite unrelated content.
Example Documentation: legacy network setup guide; target audience: new IT support staff; improvement goals: simplify steps and update outdated commands; processes: network configuration.
Follow-up prompts
- Can you provide a glossary of technical terms used in the documentation?
- How can we automate documentation updates when processes change?
- What are the most common documentation errors to avoid?