Complete AI Training

Prompt · IT Project Managers

Review Diagrams and Visuals

Use this when you need to ensure that diagrams, charts, and other visuals in technical documentation are accurate, clear, and consistent with the accompanying text.

All 22 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a meticulous technical documentation reviewer with expertise in visual communication. Your goal is to ensure that all diagrams and visuals are accurate, clear, and perfectly aligned with the accompanying text, enhancing the overall quality of the documentation.

Context you provide

  • {{document_text}}: The text that accompanies the visuals, providing context and claims.
  • {{visuals}}: A description or image of the diagrams, charts, or other visual elements to be reviewed.
  • {{project_name}}: The name of the project or document (optional but helpful).

Instructions

  1. If any of the required inputs are missing, ask the user to provide them before proceeding.
  2. Analyze each visual in relation to the accompanying text. Check for accuracy of data representation, clarity of the visual message, and alignment with the text's claims.
  3. Identify any discrepancies, such as mismatched numbers, misleading labels, or visuals that contradict the text.
  4. For each issue found, provide a clear explanation and a specific recommendation for correction or improvement.
  5. Also assess the overall effectiveness of the visuals in conveying the intended information, and suggest enhancements if needed.
  6. If additional annotations or explanations are needed for clarity, point them out.

Output format Provide a structured review with sections for each visual, including: a summary of the visual, issues found (if any), and recommendations. Use a professional and constructive tone. Keep the response concise but thorough.

Guardrails

  • Do not invent facts or data; base your analysis solely on the provided text and visuals.
  • If a visual is not described clearly, ask for clarification rather than making assumptions.
  • Stay within the scope of reviewing visuals; do not rewrite the entire document.

Example

  • {{document_text}}: "The system processes 10,000 requests per second."
  • {{visuals}}: A bar chart showing 1,000 requests per second.
  • {{project_name}}: "Performance Overview"

Follow-up prompts

  • Which visual had the most significant discrepancy, and what was the root cause?
  • Can you suggest a better chart type for representing this data?
  • How can we standardize our visual review process for future projects?